Forgot your password?

Comment: Re:What's wrong with Windows Server? (Score 1) 613

by Uncle Warthog (#47819095) Attached to: You Got Your Windows In My Linux

I would add that the main problem they seem to be solving is slow bootup times, which are slow because you can't run startup processes in parallel. .

That was the original reason for systemd before they decided to start the feature bloat. The fact though is that you can run startup processes in parallel and could without systemd. SUSE linux was able to do this and did a good job of it long before they switched to systemd while still using standard init scripts. On my system, the switch from that to systemd actually _slowed_ my boot process by about 10% because systemd insists on waiting for things that don't need to be waited for. Through some careful tuning, I've managed to get that slowdown to about 4-5% but it's still slower than the old parallel-run init scripts were.

Comment: Re:TOR (Score 1) 427

by Uncle Warthog (#47647527) Attached to: Ask Slashdot: Life Beyond the WRT54G Series?

I hear these onion routers are all the rage now.

Well if you want to route onions around the internet, then, yeah, it's an ok router (hint: puree routes better than whole onions and onion soup is even better until you get to the crouton and cheese). I'm mainly looking for a better way to route data from my home network to my Internet connection though.

Comment: Re:And no one will go to jail - just like bankers! (Score 1) 266

9/11 was the most spectacular win for the authoritarians, because they more or less kicked the foundations out from Western society, and have helped to create the worst form of surveillance state you can imagine.


No, you didn't. You just made it say the same thing again.

Comment: A simple solution? (Score 1) 264

by Uncle Warthog (#45736283) Attached to: Scientists Extract RSA Key From GnuPG Using Sound of CPU

Since they're attacking using high frequency sound, maybe have the machine emit some random noise in the same spectrum using its sound hardware while encrypting or decrypting or performing key generation. Wouldn't something like that jam such an attack (at least from a distance; if someone got microphones into your hardware that might be a different story)?

+ - Dice Ruins Slashdot-> 12

Submitted by Anonymous Coward
An anonymous reader writes "In an attempt to modernize Slashdot, Dice has removed everything that made Slashdot unique and worthwhile and has turned it into a generic blog site. User feedback has been unanimously negative, but this is to no avail, and users will have to head elsewhere for insightful and entertaining commentary on tech news."
Link to Original Source

Comment: Re:Improvements (Score 3, Insightful) 38

by Uncle Warthog (#40325245) Attached to: OpenSUSE Team Reworking Dev Model, Delays 12.2 Release

I'm not disappointed in a slower release cycle. It should improve the quality of each release.

I think so too. I've been using openSUSE since it was SuSE Linux Professional and, before that, just S.u.S.E. Linux. They had an approximately annual release schedule for the newer, pre-Novell, versions and didn't try to stuff in every single newest thing going. I like to think this gave them the time to make sure that the vast majority of what they did ship worked well.

Unfortunately, a combination of changing to the "me-too" scheduling of releases (IIRC, the original discussion of the release schedule was calling for 6-month releases so they could be just like Fedora; after an attempt or two to maintain that, they switched to the schedule they're on now) and turning it into a beta-test for unfinished and premature software (systemd, pulseaudio, KDE 4.0, and the disaster that was online updates starting in the 10.x versions) have really degraded the distribution from what it once was.

From what I can see this moved the emphasis from shipping a distribution with what I'd call good "fit and finish", a good selection of software almost all of which worked correctly, no nasty surprises in the base functionality of the OS, etc., to trying to ship to a schedule, ready or not and ignoring anything that didn't get them there. I know the majority of bug reports I've made in newer versions got marked "wont fix"; not "can't duplicate" or "working as designed", but "won't fix", i.e. "yes, we know about it and know that it's broken but won't do anything about it". Not a good sign for a distribution that had been previously known for its functionality and stability.

I'm hoping that this serves as a wake-up call to the developers and that the suggestions coolo and others in the discussion are making will get them back toward shipping a distribution that's closer to what the old SuSE Linux was known for. What I'm seeing in the discussion is looking good so far.

New crypt. See /usr/news/crypt.