@strypey
I agree with the message, but I read "masking" first as the type involving ffp2 etc things and so I was very confused when it started talking about autism 😂
@autistics @ashiel
I agree with the message, but I read "masking" first as the type involving ffp2 etc things and so I was very confused when it started talking about autism 😂
@autistics @ashiel
@mattskala
Oh no. That was discussed in a bug report that this thread links to, but that's a terrible idea.
This is about adding an *option* to ls to swap the symlink and what that points to around in the ls output.
@bkuhn @vagrantc @mjw
Oh no. That was discussed in a bug report that this thread links to, but that's a terrible idea.
This is about adding an *option* to ls to swap the symlink and what that points to around in the ls output.
@bkuhn @vagrantc @mjw
@mattskala
Anyone who tries to parse the ls output for symlink status rather than using https://manpages.debian.org/trixie/coreutils/stat.1.en.html (and doesn't do so in a shell with potential output-changing environment variables cleared) deserves for their scripts to be broken.
ls is an interactive program, its output should not be considered parseable.
@bkuhn @vagrantc @mjw
Anyone who tries to parse the ls output for symlink status rather than using https://manpages.debian.org/trixie/coreutils/stat.1.en.html (and doesn't do so in a shell with potential output-changing environment variables cleared) deserves for their scripts to be broken.
ls is an interactive program, its output should not be considered parseable.
@bkuhn @vagrantc @mjw
A single contact in my #signal list which I have an empty chat with (not communicated in years) keeps sending "chat session refreshed" like no tomorrow. Two updates yesterday, roughly 200+ (yes, two hundred) in the last hour.
I blocked the contact, but am still receiving a plethora of "chat session refreshed"
Does this match any known attack patterns, or does anyone have another explanation?
I am wary of replying in case it's part of some attack pattern.
#retoot and reasonable speculation OK
@collinfunk
That bug fails to notice that it is using confusing language in the documentation.
ln TARGET LINK_NAME
the target can reasonably be assumed to be the file that is created. But in the case of ln, it's the target *of* the file that is created.
I think that is where my confusion stems from, and I think this language should be updated.
I can't quite think of a good replacement for TARGET, though.
@bkuhn @mjw
That bug fails to notice that it is using confusing language in the documentation.
ln TARGET LINK_NAME
the target can reasonably be assumed to be the file that is created. But in the case of ln, it's the target *of* the file that is created.
I think that is where my confusion stems from, and I think this language should be updated.
I can't quite think of a good replacement for TARGET, though.
@bkuhn @mjw
@foone
Ok, ok, I lie. These days there's 'emile', which is able to boot Linux without Mac OS on some m68k models. But not then. And I don't think Emile ever supported the Q950.
Ok, ok, I lie. These days there's 'emile', which is able to boot Linux without Mac OS on some m68k models. But not then. And I don't think Emile ever supported the Q950.
@foone
Eventually I decide it's not going to work, give up and load Linux again (the machine was an official Debian build host for the m68k port).
Mid boot it just started making this... noise. As if there's an air plane lifting off. I panic, check the console... and discover that Linux found the disk and sent it the spin up command.
Reboot, open the partitioning tool, everything works. 🤦
Eventually I decide it's not going to work, give up and load Linux again (the machine was an official Debian build host for the m68k port).
Mid boot it just started making this... noise. As if there's an air plane lifting off. I panic, check the console... and discover that Linux found the disk and sent it the spin up command.
Reboot, open the partitioning tool, everything works. 🤦
@foone
It turned out that these specific AS/400 drives needed to be spun up before they could be used, they don't do that on power up.
So here I go, trying to upgrade a Mac Quadra 950 with a 2G(!😱) hard drive, but nothing happens. I'm thinking maybe I did something wrong? But after searching for hours, replacing the cable, and fiddling with various things it just never shows up in Mac OS. And in order to use it under Linux, you need to partition it under Mac OS.
It turned out that these specific AS/400 drives needed to be spun up before they could be used, they don't do that on power up.
So here I go, trying to upgrade a Mac Quadra 950 with a 2G(!😱) hard drive, but nothing happens. I'm thinking maybe I did something wrong? But after searching for hours, replacing the cable, and fiddling with various things it just never shows up in Mac OS. And in order to use it under Linux, you need to partition it under Mac OS.
@foone
That reminds me of my experience with installing a hard disk from an old AS/400 into an m68k Mac.
Fun fact: Mac OS classic does not support drives that need to be spun up.
Linux does. But booting Linux on an m68k Mac requires that you boot Mac OS first, then run the 'penguin' program, which loads the Linux kernel and boots that (not very secure, this Mac OS thing).
That reminds me of my experience with installing a hard disk from an old AS/400 into an m68k Mac.
Fun fact: Mac OS classic does not support drives that need to be spun up.
Linux does. But booting Linux on an m68k Mac requires that you boot Mac OS first, then run the 'penguin' program, which loads the Linux kernel and boots that (not very secure, this Mac OS thing).
Me, years ago:
I'm going to buy a bean-to-cup machine! So much easier? And no pods, for the environment!
Me, these days:
Oh the drip tray is full. *Empties drip tray*
Oh the used coffee compartment is also full. *Empties that*
*Powers on machine*
Oh the water compartment is empty. *Adds water* *starts coffee cycle*
Oh that grinder doesn't sound right. *Cancels coffee cycle* *adds beans*
There are times where I yearn back for the predictability of a French press.
I'm going to buy a bean-to-cup machine! So much easier? And no pods, for the environment!
Me, these days:
Oh the drip tray is full. *Empties drip tray*
Oh the used coffee compartment is also full. *Empties that*
*Powers on machine*
Oh the water compartment is empty. *Adds water* *starts coffee cycle*
Oh that grinder doesn't sound right. *Cancels coffee cycle* *adds beans*
There are times where I yearn back for the predictability of a French press.
@mirabilos
Charles is the author in the same way that Linus is the author of Linux: he kickstarted it and wrote the initial batch of code, but he hasn't touched it in years, and most of the current code is yours.
You're the author.
@navi @dalias
Charles is the author in the same way that Linus is the author of Linux: he kickstarted it and wrote the initial batch of code, but he hasn't touched it in years, and most of the current code is yours.
You're the author.
@navi @dalias
@b0rk
To demonstrate how far this goes: Debian's policy document (https://www.debian.org/doc/debian-policy) explains the technical requirements of a Debian package. The first 5 chapters explain the technical details of the packaging system; the next 2 explain how the packaging-specific bits should act. The 5 remaining chapters explain how the packaged software should behave.
@bookwar
To demonstrate how far this goes: Debian's policy document (https://www.debian.org/doc/debian-policy) explains the technical requirements of a Debian package. The first 5 chapters explain the technical details of the packaging system; the next 2 explain how the packaging-specific bits should act. The 5 remaining chapters explain how the packaged software should behave.
@bookwar
@b0rk
That's one example.
In general, distributions are points where standardisation between various bits of the Linux ecosystem actually matters.
For instance, you can rely on your system following the FHS, not because upstream developers care, but because distributions do. Reproducible builds are another example of things that were pushed by distributions.
@bookwar
That's one example.
In general, distributions are points where standardisation between various bits of the Linux ecosystem actually matters.
For instance, you can rely on your system following the FHS, not because upstream developers care, but because distributions do. Reproducible builds are another example of things that were pushed by distributions.
@bookwar