luthis

@luthis@lemmy.nz

This profile is from a federated server and may be incomplete. Browse more on the original instance.

luthis,

Also come on guys, let’s prove that the Arch community isn’t all full of assholes, let’s help this dickhead sort their stupid ass issue.

(/s)

luthis,

Should there be a space between ‘relatime, flask=’ ? Is that in fstab? It should all be one string, like in mine mine rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro

luthis,

We don’t, it’s a psy-op.

luthis, (edited )

Tried a different way:


<span style="color:#323232;"> filefrag -v testfile 
</span><span style="color:#323232;">Filesystem type is: ef53
</span><span style="color:#323232;">File size of testfile is 6 (1 block of 4096 bytes)
</span><span style="color:#323232;"> ext:     logical_offset:        physical_offset: length:   expected: flags:
</span><span style="color:#323232;">   0:        0..       0:    4660742..   4660742:      1:             last,eof
</span>

Went to offset 4660742 in wxhexeditor, but still when I copy out the hex and convert to ascii, it’s nonsense

luthis,

True, now you have the power to find your files manually!

luthis,

Yeah now I stand a better chance of recovering files if something catastrophic happens

luthis,

You can of course do it this way too, it’s just extra typing:

docker container stop $(docker container ls -qf name=snikket)

luthis,

Cool, didn’t know that!

Just tested, so you have to cd to the directory with the docker-compose.yml file in it first

luthis,

Is there a way to do this without cd-ing to the directory with the compose file first?

luthis, 

<span style="color:#323232;">Usage:  docker stop [OPTIONS] CONTAINER [CONTAINER...]
</span><span style="color:#323232;">
</span><span style="color:#323232;">Options:
</span><span style="color:#323232;">  -s, --signal string   Signal to send to the container
</span><span style="color:#323232;">  -t, --time int        Seconds to wait before killing the container
</span>

Unfortunately no filter here

luthis,

If I eventually get around to using a GUI, I’ll check out portainer

luthis,

Dude, I use the CLI all day, every day and I can’t freakin remember half the commands I need.

If it’s something I use often, I’ll make an alias even if it’s just so I can run ‘alias’ in the terminal to get a list of things I use often.

luthis,

Only if you know what the [service] is. In my case, I’m prone to forgetting so this way I can see what should be running but isn’t

luthis,

Yes,

systemctl start [servicename]

But I wanted to see what I have stopped and not started again

luthis,

I think you’re thinking of

systemctl list-units --type=service --state=stopped

status gives the state of the system and a cgroup tree

luthis,

Actually, I suspect ‘login’ refers to init and logind,

Back to the wiki to find out the steps during late userspace…

luthis,

I just discovered cgroups, so it’s cool to see some practical examples here.

Looks like not far off having easily managed load-balancing for I/O which is pretty cool.

luthis,

It’s really hard to [accidentally] permanently break Linux to the point of requiring a reinstall.

Here’s a really good tip: Keep a live distro (I use Mint) on a USB drive. If something real bad happens, you can boot into the live distro, and chroot into your OS and do the repairs you need. While also having a live distro with web access and a browser to help.

I broke my GRUB once (or twice) and fixed it again this way.

Keep a backup of your /boot folder, GRUB (or equivalent) configs, etc, also check documentation on Arch wiki for boot process. 99.9% of the time you should be able to fix things to at least get to a TTY after boot.

luthis,

That’s the best part about Linux. You’re allowed to do anything even when it’s definitely a bad idea.

luthis, (edited )

systemd-analyze plot > boottimes.svg

Open the SVG and have a look at what’s happening during boot.

journalctl -b will give you some more info too. If you’re using grub to boot (probably in /boot/grub/grub.cfg), you can change the loglevel and add the udev option to get a bunch more info. Helped me with a random issue recently. Here’s mine for an example:


<span style="color:#323232;">### BEGIN /etc/grub.d/10_linux ###
</span><span style="color:#323232;">menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-a96b3354-70dd-45ed-8c6c-95171e9f1e82' {
</span><span style="color:#323232;">	load_video
</span><span style="color:#323232;">	set gfxpayload=keep
</span><span style="color:#323232;">	insmod gzio
</span><span style="color:#323232;">	insmod part_gpt
</span><span style="color:#323232;">	insmod ext2
</span><span style="color:#323232;">	search --no-floppy --fs-uuid --set=root a96b3354-70dd-45ed-8c6c-95171e9f1e82
</span><span style="color:#323232;">	echo	'Loading Linux linux ...'
</span><span style="color:#323232;">	linux	/boot/vmlinuz-linux root=UUID=a96b3354-70dd-45ed-8c6c-95171e9f1e82 rw  loglevel=3 udev.log-priority=debug 
</span><span style="color:#323232;">	echo	'Loading initial ramdisk ...'
</span><span style="color:#323232;">	initrd	/boot/amd-ucode.img /boot/initramfs-linux.img
</span><span style="color:#323232;">}
</span>
luthis,

Plex, CUPS (printing services), Minecraft servers, VPN, file sharing, DHCP/DNS/Wifi, bluetooth are some examples of basic level things systemd can help regular users manage.

Systemd goes far beyond that too.

luthis,

“Specifically no calling people eggs, also known informally as egging.”

What the hell is egging??

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • localhost
  • All magazines
    •
    Loading…
    Loading the web debug toolbar…
    Attempt #