General Linux Chat and Small Questions v. Year of the Linux Desktop! - Hardware & Software

Virtualbox emulates BIOS unless you go into the settings and check "enable EFI", also, if you're using GRUB2 all you should need to do is run three commands as root: [code]pacman --I-dont-remember-the-args grub2 --or-whatever-the-package-is-called grub-install /dev/sda grub-mkconfig -o /boot/grub/grub.cfg[/code] (Arch may name the binaries as "grub2-*") If that doesn't work, pick a better distro

The GRUB section of my personal install notes were still valid when I switched to Arch a few weeks ago. [url]https://github.com/TheNikomo/arch_install/blob/master/INSTALL.md[/url]

Cool, I had EFI ticked on the settings of my virtual machine. Turned it off after I installed bios grub, it works! hell yeah, that took all day

Is there any way to write some information down that allows you to regenerate SSH keys? I don't mean like recovering lost keys, I mean using existing keys to generate information that allows you to regenerate those keys again later.

[QUOTE=mastersrp;47789261]Is there any way to write some information down that allows you to regenerate SSH keys? I don't mean like recovering lost keys, I mean using existing keys to generate information that allows you to regenerate those keys again later.[/QUOTE] Make a backup.

[QUOTE=mastersrp;47789261]Is there any way to write some information down that allows you to regenerate SSH keys? I don't mean like recovering lost keys, I mean using existing keys to generate information that allows you to regenerate those keys again later.[/QUOTE] If you could trivially regenerate SSH keys, that'd... kind of compromise the whole idea of them

[QUOTE=Darkwater124;47789377]Make a backup.[/QUOTE] Already in place, but I may not have them with me when I need them. [QUOTE=esalaka;47789406]If you could trivially regenerate SSH keys, that'd... kind of compromise the whole idea of them[/QUOTE] Depends on how it's done. When you think of how they're already generated, it seems to me that it should be possible to do this somehow. I know that one can do something "like" this with GPG subkeys, but that still requires me to have a master key with me at all times in digital form.

Unfortunately, I don't think so. Best you could do, if you're in a situation where you might need key access from anywhere, is a Tor hidden service, serving an encrypted file, that contains your (obviously passphrase-protected) private key. Then you can just write down the onion address, and keep the passwords in your head.

So I accidently installed 4.0.2 instead of 4.0.4. And I'm running ext4. Time to reinstall, the filesystem is so fucked it can't even write new files anymore.

[QUOTE=Tobba;47793250]So I accidently installed 4.0.2 instead of 4.0.4. And I'm running ext4. Time to reinstall, the filesystem is so fucked it can't even write new files anymore.[/QUOTE] Wait what? Pretty sure I was running 4.0.2 without issues, and I'm running ext4 too.

[QUOTE=DerpishCat;47793414]Wait what? Pretty sure I was running 4.0.2 without issues, and I'm running ext4 too.[/QUOTE] Shouldn't be much of an issue, but if you're running RAID0, it is.

[QUOTE=mastersrp;47793775]Shouldn't be much of an issue, but if you're running RAID0, it is.[/QUOTE] I wasn't using RAID0, but a shitload of files got corrupted or truncated. I reinstalled with btrfs instead. [url]https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785672[/url]

i skipped from 4.0.0 to 4.0.3 sounds like i dodged a damn bullet

The bug was in older kernels too, and 4.0.3 4.0.4 was first release that fixed it, alongside whatever stable release has a fix for it, gregkh would know.

well then i guess i don't actually know what the bug [b]is[/b] because my ext4 seems fine

[QUOTE=lavacano;47795225]well then i guess i don't actually know what the bug [b]is[/b] because my ext4 seems fine[/QUOTE] might only affect specific setups and usage cases, like how it's especially bad for ext4 raid0 arrays.

[code] This bug only showed up when non-standard mount options (journal_async_commit and/or journal_checksum) were enabled, and when the file system was not cleanly unmounted, [/code] oh thank god, i can stop worrying so much i don't use weird ext4 options (unless noatime counts as weird), and the past several times I've had to REISUB I only get as far as "RE" before the reboot unblocks and finishes cleanly still though, i'm still on 4.0.3 and who knows what my NFS server is on, i should run updates

[QUOTE=lavacano;47795924][code] This bug only showed up when non-standard mount options (journal_async_commit and/or journal_checksum) were enabled, and when the file system was not cleanly unmounted, [/code] oh thank god, i can stop worrying so much i don't use weird ext4 options (unless noatime counts as weird), and the past several times I've had to REISUB I only get as far as "RE" before the reboot unblocks and finishes cleanly still though, i'm still on 4.0.3 and who knows what my NFS server is on, i should run updates[/QUOTE] noatime counts as weird, what's wrong with relatime?

nothing i have actually cares when something was last accessed, and someone somewhere once told me noatime speeds up drive access

Last I checked, the bug wasn't in filesystem code, it was in the MD code. Some idiot on reddit posted a thread with ext4 in the title and then everyone copypasted it.

any idea how to prevent Plasma from overriding my GTK settings? even after removing it, it still keeps the plasma settings over Gnome's settings. forces me to keep Plasma installed just to be able to edit the Gnome Application Style in Plasma. I tried removing it using -Rns which should remove all config files, yet the settings somehow still reside on my system. [t]http://pred.me/pics/1432516209.png[/t]

I'm thinking of buying a [url=http://tweakers.net/pricewatch/442500/asus-eeebook-f205ta-bing-fd018bs.html]Asus EeeBook F205TA-BING-FD018BS[/url]. The only thing I could find about it and it's Linux compatibility was from December last year. Any clue how well it'd work or should I pick a different laptop (~11" for traveling)? [editline]25th May 2015[/editline] The X250TA seems to work [url]https://wiki.debian.org/InstallingDebianOn/Asus/X205TA[/url]

[QUOTE=Mega1mpact;47797199]I'm thinking of buying a [url=http://tweakers.net/pricewatch/442500/asus-eeebook-f205ta-bing-fd018bs.html]Asus EeeBook F205TA-BING-FD018BS[/url]. The only thing I could find about it and it's Linux compatibility was from December last year. Any clue how well it'd work or should I pick a different laptop (~11" for traveling)? [editline]25th May 2015[/editline] The X250TA seems to work [url]https://wiki.debian.org/InstallingDebianOn/Asus/X205TA[/url][/QUOTE] [url=http://us.hardware.info/productinfo/269729/asus-eeebook-f205ta-fd018bs/specifications]This page[/url] says your wi-fi chipset is a Broadcom, so you're in for a ride. Everything else checks out, though

[QUOTE=lavacano;47797234][url=http://us.hardware.info/productinfo/269729/asus-eeebook-f205ta-fd018bs/specifications]This page[/url] says your wi-fi chipset is a Broadcom, so you're in for a ride. Everything else checks out, though[/QUOTE] We all know the ride never ends. Still don't know why broadcom can get away with shit like that. [editline]a[/editline] Just noticed I still have my user agent spoofer turned on

I just spent 4 hours trying to get my printer to work and I head people send longer than that. I guess this mean that the year of the Linux desktop is getting closer guys. Anyway Linux is rad. [IMG_THUMB]http://puu.sh/i0Lbg/3ad4cb82c8.png[/IMG_THUMB]

Kinda depends on the printer but gnome tends yo just give you the correct driver suggestion. Worked like a charm for the network Epson printer we have at home.

not exactly fair to use "how easy was it to set up my printer" as a benchmark for how easy Linux is, since printers are satanic

How many of them work with absolutely no hitch?

The Epson printer at home works fine :v:

HP and Brother have decent Linux support I've never even owned an Epson