Follow Slashdot stories on Twitter


Forgot your password?

Comment Re:application of "whole proteome tiling microarra (Score 1) 111

It is not a Nature or Science paper because it is just a standard target enrichment library. They've been doing this for a long time to profile things like cancer markers, disease panels, etc. These guys just made a library to target viruses. That's all. It can do both RNA and DNA because they do a reverse transcriptase reaction first (required anyway to sequence RNA), and then pull down the resulting cDNA along with DNA and sequence it. Kind of cool, but not really groundbreaking.

Comment Re:Come On Enough Strawmen (Score 1) 232

Those desiring the change are the ones that need to explain why the change is needed/desirable in the first place.

They have, many times and in different places. If you didn't know that, maybe you should do some research.

I said that the arguments typically presented were weak and unreasonable.

So you do know that arguments and rationale have been made. Ok, how about a substantive counterargument then. Preferably one that actually addresses the arguments given and doesn't just dismiss them as "weak and unreasonable."

The ridiculously common command line that you wrote above fails on many/most distros that have chosen systemd as a default. These systems have no syslog at all.

Every distro that I know of (Red Hat, CentOS, Debian, Ubuntu, Arch) currently installs syslog alongside journald. If you don't have syslog installed, install it, and take it up with your distro for not including it. What your distro decides and decides not to bundle is not the fault of systemd.

Installing syslog on such a system doesn't log systems messages unless you reroute all of them away form systemd/journalctl.

Newsflash: you cannot have two logging daemons listening on the same socket and receiving the same system calls. If you want two logging daemons, one will need to forward that information to the other. JournalD does this, syslog does not, hence the current arrangement where journald forwards logging information to syslog.

But, do carry on insinuating that my log usage or viewing habits are inferior or inadequate because they use the preferred methods of the last 20+ years, rather than your preferred and totally new method. While we're at it, how about the fact that the log file itself is now formatted differently and is binary encoded rather than text. No, that doesn't break anything, 'except old people stuff'.

Wow, defensive much? Whether or not they are inferior or inadequate depends on what you are doing. They are for some people, and journalctl is the solution. If you don't want to use it, that's your choice. Do continue using your method of 20+ years, but you will be missing out on the advantages that journald provides.

As for dependencies, log dependencies are broken, despite your childish refrain of veiled insults. Startup scripts are broken. and the list of broken projects/packages/scripts goes on and on.

If there is a new init system, then old init scripts will be have to rewritten to use it. There is a compatibility method to ease the migration, but a migration will still be necessary eventually. I'm not sure why this is so shocking to you. Your argument basically boils down to "systemd is bad because it isn't sysvinit." If you don't see why that is a ridiculous argument, I don't know what else to say.

These facts aside, you're still arguing with insults.

I am not doing that at all. I am explaining to you how systemd works. You are the one taking it as an insult.

You're not presenting arguments that demonstrate any actual value of the new system/way.

Why do I need to present the arguments in favor of systemd, again, when they have already been made repeatedly elsewhere? At any rate, systemd advocacy is not the purpose of my reply. I am just explaining to you how it works and dispelling the myths that you are perpetuating.

All you've said, like I claimed in the GP, is that my 'unwillingness to accept the new way is because I'm inadequate in my use of Linux and that real users like yourself need all this old shit gone because it's old'.

Nowhere did I say anything like that.

I still say that this is not a valid or logical reason.

It's a good thing that is not one of the reasons then. There is a pretty good summary here (since you insist),

Comment Re: why bother? (Score 1) 232

You are all completely fucked, and clearly show your lack of maturity and competence.

What an odd statement.

Look AC, learn something about the way the linux kernel works, and then maybe you will be able to understand the problem. There can only be one logging daemon attached to /dev/log. If it is journald it is journald, if it is syslog it is syslog. If you want both, one has to forward information to the other, and the amount and speed by which that forwarding can take place (via sockets) is limited by the kernel. So syslog missing messages that journald forwards, is an inherent limitation of the system and not the (direct) fault of journald. Since all of the logging information (more than syslog collects on its own) is there in the journal, and you just have to learn one command to get at it (journalctl), it is not seen as the travesty it is made out to be by the anti-systemd crowd.

Comment Re: why bother? (Score 1) 232

Well, if you understood anything about the project, you would know that rebuilding the init system and rebuilding the log system are two separate projects. There are independent rationales for each of them. You are free to disagree, of course, but they exist. And a counterargument of "it works for me" is less than useless in a discussion about whether the change is necessary. Given that there are a lot of people who do think a change is necessary, you should make a better attempt to understand why and make a more substantive counterargument. Saying "Red Hat is an abomination" is not an argument.

Nor does it mean that the commands for accessing and controlling the system log needs to be abruptly deprecated

cat /var/log/syslog | grep

has not been deprecated. If that is the extent of your log analysis, it still works just fine. Just know that, in that case, you are getting the log information from syslog, not from journald, and there are inherent limitations to the forwarding mechanism that journald uses to share logging information with syslog. If you want to have complete access to all of the logging that journald does, you need to use its own interface, journalctl. It is really that simple and does not require a tremendous effort.

Nor does it mean that breaking many dependencies is acceptable.

No dependencies have been broken. If your log analysis tools require grep scraping a text log, they need to be rewritten to take full advantage of the data that journald provides. That is not a broken dependency. That is the normal course of software development that occurs when underlying system components are changed.

Comment Re: why bother? (Score 1) 232

That's not to say the OS can't change, but the new pieces must be backwards compatible

Sure. But the limitation here is not with systemd, but the fact that systemd has to communicate with syslog through a socket, and the socket has a limited buffer for storing queued messages. So if you need critical, timing-dependent log messages, you really need to use journalctl. If you refuse to use journalctl then you are shooting yourself in the foot and complaining that it hurts.

Comment Re:SubjectsInCommentsAreStupid (Score 1) 254

No, but it is in the areas that matter to most people. The thing is, people (at least the people I know) don't spend a lot of time working on older documents. They are working on new documents. And when they upgrade their Office version, usually everybody is upgrading their Office version, so Office 2003 vs. Office 2013 incompatibilities don't matter to very many people. But there is no LibreOffice version that will import a complex Word document of any version without some major flaws (minor flaws are usually ok). Floating figures that move around or disappear, captions that disappear, tables that get mangled, line art that doesn't render or renders incorrectly.... If you are writing a simple office memo, LibreOffice works perfectly fine, but many people use it to do complex formatting, and for those people the incompatibilities are a big problem.

Comment Re:SubjectsInCommentsAreStupid (Score 1) 254

There is perfect and then there is perfect. It is true, Microsoft Office compatibility is the last major remaining issue that most of the people I talk to care about. They will even use LibreOffice on Windows, they love the idea of LibreOffice, but Microsoft Office file formats are the currency of document exchange among many academics. It is usually not things like font substitution that matter to them, though. It is tables, charts, floating figures, line art, 3D arrows, OLE objects, etc. If the margins are bit off when you send a document to somebody, no big deal, but if the table with the latest data in a progress report to the NIH doesn't show up or gets mangled, that screws the pooch. LibreOffice is really close, but it is that last 1-2% that is really critical for many people to switch. OOXML has made this process a lot easier, but it is still a beast of a file format.

Comment Re:if that's true, (Score 1) 487

Um, sure ok, if you want to think about it that way. I see what you are saying, but the question relevant to the discussion is "How do you share a passphrase when its only representation on the system is as a hashed key?" That is the question that started off the whole discussion. For example, if I steal your desktop's hashed password list, I can't use that to break into your system (not easily) because you need to know the actual passphrase (not just the hash) to authenticate. With WPA-PSK this is not the case, but it's the risk everyone accepts when they use it.

Comment Re:if that's true, (Score 1) 487

Ok, since you are the second person to say this, I guess I was unclear. The way PSK works in WPA when you use a passphrase is:

(passphrase + SSID) * hash algorithm = pre-shared key (PSK)

The PSK is not the passphrase; it is a deterministic transformation of the passphrase, much like the way passwords on your local system are stored. Why is this distinction important? Well, for one the PSK is much less susceptible to dictionary-style brute-force attacks than the passphrase it is derived from. Second, if your key becomes compromised, you can do something as simple as changing the SSID, and that will generate a sufficiently different key without needing to change the passphrase.

So, the answer to the original question in this thread, "How do you securely share the wi-fi password with your contacts?" is "You don't, directly. You share the PSK, because that is all that is stored locally on your client." And the reason that works is because the way your computer authenticates locally with a password database is fundamentally different from the way your client authenticates with your AP.

Comment Re:if that's true, (Score 2) 487

Did you read my comment? The key is derived from the passphrase, it is not the passphrase itself. Neither the key nor the passphrase is ever transmitted. There is a handshake protocol where both the AP and the client demonstrate they both know the key and then a unique session key is generated from the key to encrypt traffic.

Comment Re:if that's true, (Score 4, Informative) 487

I was curious about this too. But the AC below gave a nice hint, so I went looking for a better explanation. Here is the blurb from the Wiki,

Also referred to as WPA-PSK (Pre-shared key) mode, this is designed for home and small office networks and doesn't require an authentication server.[9] Each wireless network device encrypts the network traffic using a 256 bit key. This key may be entered either as a string of 64 hexadecimal digits, or as a passphrase of 8 to 63 printable ASCII characters.[10] If ASCII characters are used, the 256 bit key is calculated by applying the PBKDF2 key derivation function to the passphrase, using the SSID as the salt and 4096 iterations of HMAC-SHA1.[11] WPA-Personal mode is available with both WPA and WPA2.

So it seems the PSK can be passed around without revealing the passphrase. But if I also remember correctly, the PSK is supposed to rotate (or maybe that's WPA2).

Comment Re:FreeNAS (Score 1) 212

Same here.

zfsonlinux doesn't have built in CIFS export

It's not built in, but it is integrated. Just use
zfs set sharesmb=on pool/srv

If you are having perms issues, make sure you have acl support enabled in your kernel and userland, and then use the aclinherit property on your zfs pool. Samba should handle the translation between NT and posix ACLs seamlessly, but you may need to use Samba4 for the best results.

Comment Re:FreeNAS (Score 1) 212

I'll go with one of the co-architects of ZFS, Matthew Ahrens,

There's nothing special about ZFS that requires/encourages the use of ECC RAM more so than any other filesystem. If you use UFS, EXT, NTFS, btrfs, etc without ECC RAM, you are just as much at risk as if you used ZFS without ECC RAM. Actually, ZFS can mitigate this risk to some degree if you enable the unsupported ZFS_DEBUG_MODIFY flag (zfs_flags=0x10). This will checksum the data while at rest in memory, and verify it before writing to disk, thus reducing the window of vulnerability from a memory error.

I would simply say: if you love your data, use ECC RAM. Additionally, use a filesystem that checksums your data, such as ZFS.

In other words, there is a non-zero chance that you will get silent data corruptions on disk if you don't use ECC RAM. It is the same risk with ZFS as with any other filesystem. And yet, personal computers have been running without ECC RAM for decades and it hasn't been a travesty. So yeah, if you are running in the type of situation where you absolutely must ensure the highest level of data integrity, then you must use ECC RAM. If you are running your own personal home media NAS, it is probably not an unmitigable risk to buy cheaper hardware. The storage gurus will argue, "Why use ZFS if you don't care about it's data integrity features?" My response is that ZFS has a ton of other very useful features that make it a great filesystem.

BTW, bad vs. good RAM is not the same thing as non-ECC vs. ECC RAM. While ECC RAM will protect you from bit flips, a bad stick of RAM is still a bad stick with or without the extra parity bit. Aaron Toponce has a good (non-sensational) discussion on the topic,

"I have five dollars for each of you." -- Bernhard Goetz