orsetto

The following is something I wrote earlier. I don't know the validity of it, and I'm not sure I correctly expressed the concepts of "power" and "rights" after translating them from italian.

--

Lately I had in mind the concept of right. Specifically, the idea Stirner had about it.

When I read The Ego and It's Own, that passage stuck with me.

[omitted unrelated stuff, because I started thinking about other things before writing what follows]

I'm thinking how the whole action of Giorgio Rosa [1] was anarchist in it's essence. He created that island just because he could do it: he had the power to do it.

I'm thinking about how many times I did something just because I could, and because I felt like it. I'm sure that more than once me and that-one-friend answered the question "why?" with "because we can". And I'm thinking how "because I can" is one of the fundamental hackers' "ideology" - mostly.

I'm thinking about how "because I can" is one of the most genuine motive that people have to justify their actions.

And, in fact, what I'm saying is somewhat tied to the concept of right. Right now, the first to decide if I have the power to do something is exactly my right to do it. And my rights, at the same time, are decided by people who have power over me! And so I say that the concept of "right" has no meaning, because I won't allow those people to hold power over me.

[1] (but not in its execution) https://en.wikipedia.org/wiki/Republic_of_Rose_Island

Hi all! I have always only used sed with s///, becouse I've never been able to figure out how to properly make use of its full capabilities. Right now, I'm trying to filter the output of df -h --output=avail,source to only get the available space from /dev/dm-2 (let's ignore that I just realized df accepts a device as parameter, which clearly solves my problem).

This is the command I'm using, which works:

df -h --output=avail,source \
    | grep /dev/dm-2 \
    | sed -E 's/^[[:blank:]]*([0-9]+(G|M|K)).*$/\1/

However, it makes use of grep, and I'd like to get rid of it. So I've tried with a combiantion of t, T, //d and some other stuff, but onestly the output I get makes no sense to me, and I can't figure out what I should do instead.

In short, my question is: given the following output

$ df -h --output=avail,source 
Avail Filesystem
  87G /dev/dm-2
 1.6G tmpfs
  61K efivarfs
  10M dev
...

How do I only get 87G using only sed as a filter?

EDIT:

Nevermind, I've figured it out...

$ df -h --output=avail,source \
    | sed -E 's/^[[:blank:]]*([0-9]+(G|M|K))[[:blank:]]+(\/dev\/dm-2).*$/\1/; t; /.*/d'
85G

If you have typed an <ESC> by mistake, you can get rid of it with a C-g.

quoting the emacs tutorial. made me giggle

Hi. I'm working on a project that compiles Rust code to WASM, and uses WASI in Node.js to execute it. After some development, I encountered a segmentation fault happening in the wasi.start() function. Considering that I'm kinda new to Node I was only able to understand that it was happening after the call to the exported WASM method returned.

This happened almost two months ago, and while I thought about reporting this to the node devs (WASI's also experimental), I was going to move soon and a lot has gone on.

Yesterday I tried to reproduce the bug on my laptop (that is not my usual development environment, which I don't have access to right now) but I wasn't able to.

I had to start fresh and install all the necessary tools from zero, so my theory is that there was something wrong in the previous environment. I'm also on Gentoo now, while I was running Arch previously.

Unfortunately I don't have the means to check on other environments. I tried to reproduce the old environment, installing the same versions of node and rust, with no luck. I also tested this with the latest versions and everything works fine.

This situation is upsetting. I don't know what's changed that caused the problem to "disappear", so i feel uncomfortable considering this solved. What would be the best approach in this situation?

EDIT: I also just tested it on Debian live, and I still wasn't able to reproduce the segfault