@aard@kyu.de
@aard@kyu.de avatar

aard

@aard@kyu.de

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

aard,
@aard@kyu.de avatar

Do you happen to have pictures/videos? I can’t imagine what you’re talking about.

aard,
@aard@kyu.de avatar

Wow. Do you have a product name so I can gift that to people I hate?

Also, who exactly did you piss off to get that as present?

aard,
@aard@kyu.de avatar

Thank you, the search result for that is glorious.

I’ll probably need to look into setting up a dead man switch now to let everyone know if I get murdered by disgruntled parents.

What's (are) the funniest/stupidest way(s) you've broken your linux setup?

Tinkering is all fun and games, until it’s 4 am, your vision is blurry, and thinking straight becomes a non-option, or perhaps you just get overly confident, type something and press enter before considering the consequences of the command you’re about to execute… And then all you have is a kernel panic and one thought...

aard,
@aard@kyu.de avatar

A good starting point for a wikipedia rabbit hole covering the software aspects on how to drive a display: en.wikipedia.org/wiki/XFree86_Modeline

aard,
@aard@kyu.de avatar

On a real UNIX (not only AiX) killall is part of the shutdown process - it gets called by init at that stage when you want to kill everything left before reboot/shutdown.

Linux is pretty unique in using that for something else.

aard,
@aard@kyu.de avatar

Back then I was testing modelines to see the maximum I could push to my 14" monitor. I then backed it with a 1200x1600 virtual screen.

My girlfriend got sick from watching me scrolling around and bought me a 19" display which could do that resolution - and ended up frustrated when I added a larger virtual screen.

aard, (edited )
@aard@kyu.de avatar

killall typically sends SIGTERM by default. It accepts a single argument, the signal to send - so shutdown would call it once with SIGTERM, then with SIGKILL. killall is not meant to to be called interactively - which worked fine, until people who had their first contact with UNIX like systems on Linux started getting access to traditional UNIX systems.

It used to be common to discourage new Linux users from using killall interactively for exactly that reason. Just checked, there’s even a warning about that in the killall manpage on Linux.

aard,
@aard@kyu.de avatar

I’m using opensuse tumbleweed a lot - this summer I’ve found an installation not touched for 2 years. Was about to reinstall when I decided to give updating it a try. I needed to manually force in a few packages related to zypper, and make choices for conflicts in a bit over 20 packages - but much to my surprise the rest went smoothly.

aard,
@aard@kyu.de avatar

Also quite important to make sure we don’t have just a single strong x86 vendor - even though currently looking at price/performance you’d almost always go for AMD.

The time before ryzen was horrible - a 4-core-CPU was considered high end, and if you needed something more you needed to go for ridiculously overpriced Xeons. Similar for servers - you could get slightly higher core counts there, but when going for more than 8 cores it’d also get expensive very quickly.

Now we’re talking about 16 cores in high end notebook, and 64 cores in still reasonably priced pro workstations.

aard,
@aard@kyu.de avatar

Just don’t buy nvidia (or stuff from any other company openly hostile towards their users)

aard,
@aard@kyu.de avatar

I’ve been a Linux user since the 90s, and nvidia has been a problem as long as I can remember. The wayland issues are just a new chapter in a long saga. ATI used to be the same, but they came around after having been bought by AMD.

If you’re already planning to use Linux on something a quick search will directly tell you that nvidia is a problem. If you got the hardware before nvidia that sucks - but again, it’s nvidias fault.

I think we absolutely should neglect nvidias market share, and just fully drop support for nvidia cards - either they’ll get pressured by angry users to no longer behave like dicks, or they keep doing it, and people will only make the mistake of buying nvidia once (or not use Linux) - either way, we’ll have gotten rid of a massive headache.

aard,
@aard@kyu.de avatar

I don’t think infotainment systems need a concept of copy/paste but having to write:

Having lived through the whole “phones don’t need copy and paste debate”, which fortunately got solved by now having it everywhere I’m in the camp “just stick that everywhere, just in case somebody might use it one day”

aard,
@aard@kyu.de avatar

It shows a message which wastes valuable screen estate, especially on low resolution terminals, containing a message I have to read every single time because the keys are not in muscle memory, and never will because the bindings are stupid.

On systems I have control over the reaction to nano popping up is exiting, removing it, making sure the package system blocks reinstallation attempts, and go back to what I was initially doing in a sane editor.

aard,
@aard@kyu.de avatar

I always get annoyed when I’m on some system and nano pops up and I need to figure out how to kill that thing.

aard,
@aard@kyu.de avatar

CUPS is horrible, and also had its share of critical vulnerabilities. It is just better than the LPD mess we had before.

It is not a Linux specific thing - it was developed when there still were a lot of UNIX variants around. Apple was a very early contributor, and had quite a bit of influence in making it successful.

aard,
@aard@kyu.de avatar

Friendly reminder: just don’t buy nvidia

aard,
@aard@kyu.de avatar

Make sure you use a long extension cord to a fuse without RCD for the hair dryer, though - otherwise the constant resetting of the breaker will eat up all your time savings.

aard,
@aard@kyu.de avatar

While failing at art he was still Austrian.

aard,
@aard@kyu.de avatar

It’s a similar thing with four leaf clovers - I never in my life found one, even during periods where I’ve been scanning every bit of green while hiking. But then we had a friend who isn’t really paying attention to her surroundings, and just randomly goes ‘oh, moment’, and picks up a four leave clover from a few metres away.

Seems my daughter is also developing that talent - last summer she picked up a few while playing outside.

What would be the best way for me to recover data from my old laptop's hard drive, which seems to have a bad superblock?

I got an external hard drive enclosure for the purpose of recovering some of the files from my old laptops hard drive. The hard drive and all of it’s partitions show up in both disks and gparted but it wont mount. When I tried to mount it manually, it gave the error message stating that it can’t read the superblock. I’ve...

aard,
@aard@kyu.de avatar

First step, in case you didn’t do that yet: Create a disk image of the partition - you don’t want to try data recovery on the actual data. Easiest is just using dd to dump the disk to another drive.

Next try running testdisk on the image to see if it can find the backup superblocks - if it does you can feed that to fsck to restore the filesystem.

If you know the blocksize of the filesystem you can also run mke2fs with the -S parameter - this will just write the superblocks. Again, only do that on a disk image, not the actual drive.

aard,
@aard@kyu.de avatar

In that case I’d recommend waiting until next year before attempting recovery.

aard,
@aard@kyu.de avatar

After reading about it - true. Disadvantage of doing this stuff for a long time - you miss new developments. Only reason I’m aware of testdisk is that I lost the sources of my own superblock search tool, my old binaries broke with a newer glibc, and before reimplementing it I checked if sombody else had done that in a more usable form in the meantime.

aard,
@aard@kyu.de avatar

That has changed over the last few years - I’d prefer a proper usb3 to sata bridge over a shitty sata controller - and the quality of integrated sata controllers isn’t that great nowadays.

aard,
@aard@kyu.de avatar

You can do all of that on the device - but you only get one shot. If you mess up that’s it - so no sensible person would try any form of data rescue directly on the device. Storage is cheap, if you don’t have sufficient space on your computer just get another external disk.

aard,
@aard@kyu.de avatar

The problems come when the woman turns around and keeps closing the notebook with her breasts.

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