@nazokiyoubinbou
You can run systemd without systemd-resolved. I have done so ~forever.
The idea is that it makes certain things easier (e.g., having different DNS configs for different network interfaces), but the systemd developers know and understand that it isn't a valid thing everywhere.
@waldi @veronica
You can run systemd without systemd-resolved. I have done so ~forever.
The idea is that it makes certain things easier (e.g., having different DNS configs for different network interfaces), but the systemd developers know and understand that it isn't a valid thing everywhere.
@waldi @veronica
Choose the 'set debconf priority' option
Remember what the priority is set to currently.
Select 'low'. Congratulations, you're now in expert mode
Choose the 'set users and passwords' option.
You will now see a question whether you want to set a root PW. Choose not to.
Finish the 'set users and passwords' menu item
Go back to the 'set debconf priority' option.
Set the priority back to what it was.
You're not in expert mode anymore.
(2/2)
@veronica @Linux
Remember what the priority is set to currently.
Select 'low'. Congratulations, you're now in expert mode
Choose the 'set users and passwords' option.
You will now see a question whether you want to set a root PW. Choose not to.
Finish the 'set users and passwords' menu item
Go back to the 'set debconf priority' option.
Set the priority back to what it was.
You're not in expert mode anymore.
(2/2)
@veronica @Linux
@Linux
Sudo is enabled if you choose not to set the root password. This requires you to go into expert mode in the installer though, although you don't have to do the full install that way.
What I do:
Run the installer normally
When prompted to enter the root PW, use the 'back' button until you're in the main menu
(1/2)
@veronica
Sudo is enabled if you choose not to set the root password. This requires you to go into expert mode in the installer though, although you don't have to do the full install that way.
What I do:
Run the installer normally
When prompted to enter the root PW, use the 'back' button until you're in the main menu
(1/2)
@veronica
Never let anyone try to talk you out of a quick half hour DIY project. Those three hours will be the best six days of your life.
@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
@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).