Slashdot is powered by your submissions, so send in your scoop


Forgot your password?

Comment Re:Why? (Score 1) 65

Thank goodness. It's embarrassing how long my desktop machines have had the habit of looking completely locked up whenever they're asked to copy a large file in the background. It's especially bad when a slow-ish NAS server is involved. I've tried the existing optional IO schedulers, and they don't fix the problem.

Comment Bit by Bit, and Designing My Own (Score 2) 132

I self-host and encrypt where possible. For other things, I use providers as trustworthy as I can find.

Email privacy is a tough problem, but a solvable one. I'm working on a project that will give me gmail-like convenience without entrusting my data to Google, and might eventually grow automated/transparent encryption capabilities. It's going to be a while before it's usable, though; nobody is paying me to work on it, so it doesn't get enough of my time. (The mailpile project overlaps some of my goals in this area, and might be worth a look to anyone interested in the topic.)

A Facebook replacement is another tough one, perhaps even tougher than email, but I believe it's also solvable.

Please keep asking questions like this, and sharing what you discover. The more of us we have thinking about these problems, the more likely we are to work out their solutions.

Comment wire wrap serial interface (Score 2) 210

The Commodore 64 had a nonstandard serial port, meaning that I couldn't connect my standard RS-232 modem directly to it. Being just a kid, I couldn't afford the $50 or so that an adapter would cost.

My solution: I borrowed a family friend's RS-232 adapter, opened it up, examined the components and circuit board traces, bought the parts from a local electronics shop, and built the same circuit with perfboard and wire wrap. I cut a slot in the back of my C64, mounted a DB-25 connector in it, wired it to my frankenboard, and stuffed the whole thing into the free space inside the computer.

It worked like a charm. I was the only kid I ever met whose C64 had a standard serial port on the back.

Comment Re:Experts... (Score 1) 345

C++ gives a nice balance between high performance and relatively good safety.

Huh? Relative to what?

C++ was my primary language for quite a few years. I was very good at using it effectively while introducing far fewer bugs than most coders I encountered, but I would never call that language anything near safe.

Maybe you're talking about a subset of C++ that does not include things like pointers and arrays?

Comment Re:Why do people dislike systemd so much? (Score 1) 229

All it takes is the motivation, a group of likeminded individuals and the willpower to deliver a dist that does not use systemd. I expect most packages in the debian universe have no deps on systemd and therefore no work required to support those packages. So we're talking system packages, some daemons and maybe a few shims for edge cases.

You're implying that it would be easy. I'd like to think you're right. One group has already announced such a derivative. I'd love to see it succeed, but I'm not holding my breath. Maintaining a linux distribution as well as debian does, including timely security updates, package builds, downstream bug tracking, release management, and uniformity across so many installations as to form a vast support community, is a much bigger job than one might think. There's also the issue of various unrelated but popular packages developing dependencies on systemd, which means any such derivative distro would also be in the business of developing and maintaining forked versions of those packages; also not a trivial task. I guess we shall see.

As for why there are only 2 dists left not to have gone to systemd, perhaps that should serve as a clue in itself.

Many of them seem to be derivative distros that simply don't want to diverge from their upstream distribution's init system, so they have little choice. (Counting them as independent decision makers would be dishonest.) As for the upstream distros, I think it's more telling to note how very divided their communities were in the vote for/against systemd. A strong argument could be made that anything so integral to the core of an OS distribution should not be replaced with something so divisive to the community.

Speaking for myself, I'm a bit disappointed in the loudest factions of this disagreement. Most of what I see in these discussions is two mobs of people pushing for a decision *right now* (meaning this year, or next). The voices shouting "we need systemd!" or "we need nothing of the kind!" dominate the discussion, while a third option seems to have been forgotten: How about waiting until something can be developed that offers important core improvements over sysv init, but isn't as invasive as systemd? Most of us can obviously get by just fine with our existing init systems for a little longer; we've been doing it for years. The uproar over the topic is surely enough to motivate the development (or modification) of an init system that most of the community would find suitable. I'd love to see that happen.

In any case, I think the original question here has been answered. :)

Slashdot Top Deals

It is difficult to soar with the eagles when you work with turkeys.