The host hosting blog.zugschlus.de, ivanova.notwork.de, was down due to a network failure in the hoster's network for a few minutes today around 2 pm CEST.
After returning, I found a lot of my syndicated articles anew on Planet Debian, known as the "flood" phenomenon. Is it possible that the Planet software does react in a non-graceful way when an RSS feed cannot be pulled?
Mako, can you investigate this?
A few months ago, I have reported about getting the winmodem in my hp compaq nc 8000 to work.
Aside from the abysmally slow performance, the dependency on out-of-tree, non-free modules has been cause of grief since it has almost constantly forced me to keep an outdated kernel version around just in case that I would need the modem.
Fortunately, _this_ is over now since more recent kernel versions (I suspect somewhere in the 2.6.16 era) support my winmodem natively without out-of-tree modules. All I need to get only on a POTS line is sl-modem-daemon, which is reasonably painless.
My notebook is an hp compaq nc8000 running Debian unstable, and I'd like to know whether it is "already" possible to use software suspend (hibernation). To my knowledge, there is a lot of different ways to do suspension, all of them differently broken and/or incompatible.
I't like to run with an unpatched vanilla kernel, use suspend-to-ram and suspend-to-disk according to my choice at suspend time, and have the notebook wake up with the X session unhampered and the important hardware (sound, synaptics) still useable. Additional bonus points if wireless and/or wired network remains useable and USB/PCMCIA devices don't need an unplug/plug cycle.
Which solutions should I investigate, which web pages should I read?
The last days, Debian suffered a bug in the reportbug package which made it fail in postinst. This bug was promptly fixed, but reported like THIRTEEN times as a bug in the BTS. If I were reportbug maintainer, I'd have gone ballistic at this ignorance of bug reporters.
Guys, all of you who have reported this bug are running Debian unstable, an unreleased development version of your distribution. Is it asking too much to follow basic etiquette to look in the BTS whether a fatal bug might already been reported? I mean, THIRTEEN nearly identical reports?
I am wondering whether it is currently possible to run a personal laptop with Debian unstable and some init scheme that allows parallel startup of the services. Naturally, it would be very good to start the X server early to be able to log in faster.
Is this concept ready for testing and use? Which packages should I investigate? Any URLs that might be enlightning?