Hi, guys. Besides the VastOne's advices on keeping full system backpups with fsarchiver for recovery purposes, I use rsync daily but not fsarchiver...

Well, a couple of days ago I had to move my computer to other room. Disassembled everything and gently carry all the stuff. Put everything together, booted and... blinking cursor. What the.... 

Tried everything, swapping drives, cables, SATA ports... the disk was apparently dead. Decided to try to recover it just in case it wans't actually dead. Booted my Vsido live ISO (it has fsarchiver on-board!) and was able to mount and read the disk contents, so crossed my fingers and run fsarchiver, erased and reformated the disk, and restored the partitions. Still no joy but again everything was readable, the partitions mounted and worked correctly, so the apparent culprits would be grub and the efi things. time to chroot.

I didn't either remembered the cool vchroot script by harckerdefo (also a vsido default tool) . A great rediscovering! Long story short, I managed to put everything onto a bigger brand new SSD I had around and restoring the grub/efi stuff, plus installing via chroot a fresh Void Linux system on the older SSD. Both systems are now up and running perfectly well. All done from Vsido!

Yes guys, Vsido is a darn great recovery live system with all the needed tools already included. Thanks a billion for your brilliant work, VastOne.

P.S. Don't be lazy and run fsarchiver from a Vsido live ISO regularly whatever the systems you use on your machines. I'll do it from now on. Promise!

This a kind of noob question... I've been using Nvivia cards since... forver. But I'm a total noob about AMD. It's the first time I put my hands on one of these.

The situation is I'm tired of struggling with the Nvidia propietary drivers since I've got the GTX960. Switched to nouveau a couple of months ago and performance is not so great. So I've got an RX560 trying to say goodbye to the Nvidia hardware for once and forget about the drivers mess just using what's in the kernel.

The thing is I don't know how the heck to switch the drivers in sid. The card works right out of the box in my Void install, but for some reason I don't manage to get it working for the sidbox. If I blacklist nouveau, poweroff, switch the GPUs and boot, grub doesn't even show up and the boot process stalls with udev saying something like that "the slot" is already in use and it freezes there forever.

Apparently I already have all the needed packages (firmware, xserver-xorg-video-amdgpu, the mesa stuff, etc...) onboard.

Please, someone able to shed some light?

Thanks a bunch in advance.

@VastOne: maybe you'll like this

https://forums.bunsenlabs.org/viewtopic.php?pid=10928#p10928

I want to group any/all the libreoffice writer windows in the current desktop but they are not responding. I can group them manually, of course, but they doesn't group automatically via the apps file.

If I'm not wrong, this seems to be the obvious config (it's what xprop outputs) but it does nothing.
[group] (workspace=[current])
  [app] (name=libreoffice) (class=libreoffice-writer)
[end]
Or this:

[group]
  [app] (name=libreoffice) (class=libreoffice-writer)
  [Workspace] {CURRENT}
[end]
Tried some other variations including this ignoring workspaces:

[group]
  [app] (title=.*odt - LibreOffice Writer)
[end]
Still not working. Is Libreoffice different than the usual windows or am I missing something?

Please, share your favorite monospace fonts for minimal eye straining. I'm very picky with the fonts. I've found my holy grial ttf for most uses; OpenSans. but for the monos I'm still not comfortable enough. I tipically use DejaVu Sans Mono. It's quite good, but still far away from the OpenSans easy reading. Post your favs and suggestions. I'm all eyes. 

PS, I forgot it. The best ones around size 9. Size uses to make a big difference. For Dejavu I find size 9 too rough and size 8 smooth enough, but starts to be too small.

After last update, a quite big one since I wasn't dist-upgrading regularly due to my recent HD problems, vsido-exit is not fully working. Only logout works. Not reboot or power off. I suspect of lightdm. Got an update and I found surprising that it doesn't autologin or selects my username as it should. The user field is blank. Then found this about the exit. Anyone else or it's only here?

After four long days of hard struggling trying to make my main hard disk to be able to boot a system again and researching a bit, I discovered that this HD had all the symptoms of a rootkit.

Apparently they like to live at the kernel level, they use to be injected while installing drivers, and they use to fuck up your MBR... exactly what I was doing and what happened. Plus, formating doesn't help. Exactly what happened to me. Installed like eight different systems with different grub options. Nothing worked even after a low level formating. Scanning and trying to discard damaged or faulty HD sectors reported nothing wrong in the entire disk. Everytime GRUB failed to boot. The systems were bootable from the GRUB in my second drive. The only solution I've found is going for GPT partition table. This has a smaller 64 MB efi_grub partition instead of the 446 or thereabouts for GRUB, or 512 MB in total including 64 MB for the partitions in a DOS partition table. This excluded the screwed up part from the equation altogether and finally the HD is bootable again. I was about to trash it and buying a new one... phew!

I cannot tell for sure if it's a rootkit there, but given my recent damned experience, be careful if you use smxi to instal Nvidia drivers. And better have rkhunter and/or chkrootkit on hand. I had no idea of this in advance and it gave no time to react. Chose to install the drivers and then all went south. No way to fix my system or booting it again. All destroyed and gone in seconds. Perhaps downloading only and running rkhunter before doing anything might be a wise option.

Well, I think I've had my first rootkit experience. I'm not a virgin anymore... but I don't recommend the experience to anyone. BTW, Fucking bastards! Why they do this?

AFAIK, In the Debian world only antiX keeps going with sysvinit leaving systemd off the equation. But if I got it right (I might be wrong, as usual), only for Stable. It seems they want to make this possible for the rolling flavors too. But for now if you want to be sure to keep going with sysvinit you must stick to Jessie.

In a different territory, the guys from the BBQ used to build systemd-free Sid based isos instead, but since machinebacon stopped handling the grill, it seems all quiet over there with no new releases in months. I wonder how the BBQ will evolve. In any case, for now, the sysvinit door for Sid seems to be closed for that neighborhood too. Their last isos are already too old and having 4.0 kernels not usable in virtualbox without struggling, tweaking and remastering to make them login the X.

I'm wondering... is there still a way to switch to sysvinit (or any other init system)? The Arch guys can do it. But it seems is not that easy in Debian.