And the best way tools such as this have to communicate updates to those who shoupd get the updates is .... by email. And the Daimler solution would mean I wouldn't easily be able to see the updates I missed.

Surely there are other mechanisms to keep people stress-free while on leave? I just turn off email synching until the morning I return to work (with a suitable OoO message set).

On Android, access to the contents of the device requires the screen to be unlocked. Does iOS also require this?

(Access to the device without installing drivers isn't an issue, but the computer OS should prompt before automatically mounting the device too, which I believe Linux does but Windows doesn't).

Yeah, and don't forget that "loud pipes save lives" around typical inattentive drivers. This thing is silent but deadly.

It'swould be more like Cisco requiring ypu to buy a software/feature licence to use 10Gbps ports on hardware you already paid for.

Oh wait, they do that already (e.g. on ASA-5585-X, probably other ASA nodels too)

More pseudoscience. They say that they're not sure whether this means that porn shrinks your brain, or if the shrunken brain causes porn viewing. But, this leaves out the very real possibility that this correlation means nothing whatsoever. The site below collects correlations that look pretty convincing in the graphs, but quite obviously are unlikely to be cases of causation in either direction:

http://www.tylervigen.com/

It could be cleverly disguised as a bit of MD5 but is actually something encrypted with a 33 character one time pad.

This technique works best when combined with cold fusion. Also, don't forget about step 3.

They may not even need any fine print. Accepting compensation can affect your right to seek damages later.

1) You can use a different logger with systemd
2)To watch log messages with journal, journalctl -f

There are still some things I don't like about the journal (I haven't seen how to specify different retention rules for logs of different applications), but then I've only spent a few minutes actively using it.

Maybe the thing that irritates me about journal is I don't know what previously unsolved problem it is trying to solve, while making some log processing difficult.

But, if you are booting from CDs, and the CD has the rest of the media, why do you need the utility for verifying signatures on the boot media (1.44MB image)? Bootstrap the installation image from the iso9660 part of the CD (or network in the case if a network install)? and have that contain the signature verification utility.

Hint: RPM-baswd distro have been doing this since rpm 3.x, or about 1999.

Really, who uses floppies for installation these days? Sure, maybe floppy emulation on a DRAC or iLO or ILOM, but they all
-support CDROM or DVD emulation
-PXE boot (with relatively large images possible via TFTP)

If none of these are options, just write the whole (hybrid) ISO image to a 4GB USB flash disk and be done with it.

I personally haven't used an actual CD-RW or DVD to install a syatem in about 5 years. Either network install booted via PXE for servers, or USB flash disk for laptops.

I am on Android, and I don't see any way to see the video from m.slashdot.org.

Oh, and that still doesn't answer why laptops are trickier than desktops in this regard.

Of course it is. Any other FDE is the sprinkling of magic encryption dust kind of FDE. Both initscripts (on RH-style systems) and systemd support this, and have for years.

Why?

I have been using full (or, full enough, /boot isn't encrypted) disk encryption on my laptops for years. Since my only non-laptop is a workstation in a secure facility, I only did full disk encryption on that a few months after first doing it on my laptop (which is a much bigger security risk than my workstation).

I have used KDE for a long time. My laptop has an embedded 3G card that works better / more easily with NetworkManager/ModemManager than with more traditional (e.g. pppd, wvdial etc.) setups. Thus, I tried KNetworkManager.

However, I use WiFi networks with both WPA2 Personal, and WPA2 Enterprise, security. I don't mind my WiFi keys for the WPA2 Personal networks being stored somewhere, but I don't want my passwords for WPA2 Enterprise networks stored *anywhere*. Before trying NetworkManager/KNetworkManager, I would have all the WiFi configuration in /etc/wpa_supplicant.conf except the username and password, and run wpa_gui. The first time a specific instance of wpa_supplicant connected to said WiFi network, wpa_gui would pop up a dialog prompting for username and password, and I wouldn't need to enter the same credentials for the lifetime of that wpa_supplicant process (typically longer than the lifetime of the password).

However, with KNetworkManager, my options are:
-Store
-Always Ask

In the 'Store' case, due to my KDE Wallet settings (including 'close when screensaver starts'), now every time I resume my laptop, I will be prompted to enter my KDE wallet password (longer/more complex than the WPA Enterprise password).

In the 'Always Ask' case, I am required to enter my password *every* *time* I associate to the the SSID.

So, maybe it is better than nm-applet (I haven't used nm-applet *that* much) or the Gnome 3 integration (which I only see when trying to help a colleague), but it most definitely isn't better than the old /etc/sysconfig/network-scripts in conjunction with wpa_supplicant approach that I have been using for the past 7 years. On Mandriva (and Mageia), the net_applet tool can do all that configuration anyway, so there really doesn't seem to be any benefit. Of course, systemd will most likely require NetworkManager only at some point. I hope someone fixes NetworkManager to be more sane before then.

At present, I don't care about having a WiFi network connected before a user is logged in. Surely on a typical laptop, that occurs once a month or so? We have network authentication with cached crendentials, and I can kinit after logging in anyway. If this is really a requirement, using TPM (with all of its failings) would probably be a better approach.