Who cares about root! My home directory is WAY more important than the system.
Which means you should have backups that are not writeable by your account, and the easiest way of doing so is having cron create a tarball of
And we already have the solution too - the one guy who was running it under SELinux got an error message instead of a wiped system.
(He also appears to be the one responsible for the bug in the first place...)
To play devil's advocate, the init-related complexity exists either way, so what it really comes down to is where it gets handled.
I think that systemd's approach to daemons (declarative config files about 5 lines long) is much simpler than the sysvinit approach of having a few pages of bash.
Journald is admittedly more complicated that traditional syslogs, but the ability to query a database with a simple command instead of several lines of perl is potentially worth it. (I say potentially because I haven't yet figured out which daemons actually log to journald, and which just use their own log files.)
Making systemd ignore all of fstab is painful because you're trying to disable an entire 'feature'. (The inability to do so contributes to the perception that it's monolithic, but I digress.) What would probably work better is adding 'noauto' to the entry for the file system in question, then add a
Correct me if I'm wrong, but doesn't that only mean that systemd needs to be the root of the tree of processes whose resources it manages, as opposed to the root of all processes on the system (which is implied by pid1)? Systemd-init expressly checks that it's running as pid1, but this seems to be an artificial constraint and more of a recommendation than a hard requirement.
Win10 doesn't look too bad, but the damage has already been done. I jumped ship for Linux when Win8 was in RC, and now it's almost comical how many different tools you have to install that come out of the box on pretty much every Linux distro (text editor, 7zip, compiler, a browser other than IE, codecs, etc.).
Microsoft's problem is that even if Win10 is on par with Win7 in terms of usability, they've still lost customers and marred their image. The Metro apps in the start menu (literally the first thing seen in pretty much any screenshot of the OS) are an immediate reminder of Win8 and everything disliked about it. Win10 needs to be significantly better than Win7, otherwise they're not going to be able to recover.
I agree. This is really the sort of thing that the government should be doing - tax software is just the modern reincarnation of the forms. In Australia, they've been doing this for as long as I can remember, and it works brilliantly. (My only complaint is that it's Windows only, though they do have a new (more limited) website that can be used instead.)
Bell is just an intermediary - the plaintiffs would have to be the recipients of the notices. The problem is you then have your classic big company vs. the little guy scenario, where the imbalance of power makes pursuing justice expensive. In Canada and Australia, this is normal resolved via regulations (which were omitted in this case). (The US approach seems to rely more on class action law suits.)
I'd say the bigger issue is that Java is not as portable as C, partly because of its overhead. The difference is really only negligible on a desktop.
the hard work is the cryptography
Agreed, and if there's one thing the OpenSSL folks have shown, it's that doing it right is hard. The more components you have in your stack, the more opportunities there are for bugs to slip in. (e.g. the infamous OpenSSL allocator). Java has a very thick stack (especially due to its tendency to use layers of objects for everything) - I'm not sure I'd rely on it for something security critical like this.
But on ordinary desktop OS? Since Windows 95, RAMDisks have been dead. Since then, we've been using RAM better to cache all recent filesystem accesses. There's very, very, very, very little that will ever benefit from a RAMDisk over just having that RAM as filesystem cache automatically anyway. You still have to read the data from permanent storage anyway, and once you've done that, it's in RAM until you start to fill up RAM. Read it often enough and it will never drop out of the cache. If you're not reading it often enough, why the hell bother to RAMDisk it?
This is consistent with my experiences on Linux. When compiling the kernel, I found no significant difference in compilation times on a SSD and tmpfs. If you only have a mechanical hard drive, it might make sense to use a tmpfs, but if you don't have a SSD you probably don't have enough RAM for that anyway.
Better security in Linux, you say? Tighter control of permissions? Bzzzzt, nope, doesn't apply. What makes Crypto$shit so dangerous is exactly that it does not need any kind of elevated permissions. It does not want to touch any "system" areas, all it does is execute in the user context and encrypt files in the user's directory. That is something you can do on Linux with the permissions of the current user just as well as you can do it in Windows.
Btrfs snapshots would have defended against this sort of attack effectively - they provide incremental backups that can only be deleted by root. It's trivially easy to setup a cron job to perform a daily snapshot of
While Windows does have various mechanisms for creating backups, I'm not aware of anything equivalent to btrfs on it (incremental backups, takes less than a second to create the backup/snapshot).
I have a laptop with optimus (Lenovo T440p with GeForce GT 730M), and external monitors work fine for me. (I just tested this with 'optirun glxgears'.)
I'm using Sabayon, and the only thing I had to do was install the Nvidia drivers - after that it worked perfectly. Sabayon made optimus support one of their selling points back in 2013, so it's possible it has a better default configuration than Ubuntu / whatever you're using.
Of course, it's entirely possible that your specific laptop is designed such that the external monitors can only be driven by the integrated graphics, but that's the fault of the laptop manufacturer, not Nvidia.
Package versions:
Linux 3.18
Bumblebee 3.2.1
Nvidia drivers 340.58
The owner of the vehicle is presumed to be the driver unless they either nominate another driver, or file a police report stating that it was stolen.
Naturally, if you're renting a car Avis, etc. will record your ID.
If you're watching it full screen, you could just turn it off temporarily.
On Unix, sadly, only Adobe Flash player detects color corrections and plays your video in proper color. Neither Google nor Mozilla have figured this out for flash video, either.
Strictly speaking, wouldn't you want the video to be in the adjusted colour? Most of my late night PC usage is watching video, and I don't even notice the change anymore. (It helps that Redshift gradually changes the colour temp.) That said, I found it made a huge difference to my sleeping patterns.
Understanding is always the understanding of a smaller problem in relation to a bigger problem. -- P.D. Ouspensky
