On Fri, May 18, 2007 at 09:26:25PM +0200, Tim Dijkstra wrote:
> Come on. `useless debconf proliferation'? The question has medium
> priority. I can also make it an configration option somewhere and use
> that, but it was just a convenient why to get info from a user.
I'd also say a debconf questi
On Wed, Jan 04, 2006 at 01:10:49AM +0100, Sven Luther wrote:
> But yes, udev is the problematic case, altough i run 2.6.14 with sarge udev
> and it works.
AFAIK it should work with the default ruleset. It breaks only with
certain custom rules due to a bug in the libsysfs version used by udev.
So
On Wed, Jan 04, 2006 at 12:23:31AM -0200, Felipe Augusto van de Wiel (faw)
wrote:
> Perhaps the idea of maintain a kernel with other distros is not bad,
> if Ubuntu shows up as a candidate, I would like to add Progeny, Linspire,
> Xandros, "DCC Alliance Fan Club" and also other Debian Deriv
On Wed, Jan 04, 2006 at 02:26:51PM +0100, Maximilian Attems wrote:
> the -rc kernels are build in experimental, staging area for unstable
> and without any potential d-i breakage.
Ah, nice, I did not notice it. Perhaps it should get some more publicity
to attract more testers :-)
Gabor
--
On Tue, Aug 15, 2006 at 06:11:18PM +0200, Aurelien Jarno wrote:
> It already started to annoy some people having their log filled with
> such messages.
IMHO if the message is not rate-limited you should bug the kernel
developers (preferably upstream on linux-kernel). Printing the message
1-2 time
On Fri, Dec 07, 2007 at 11:15:00AM +0100, maximilian attems wrote:
> please try newer, unstalbe has 2.6.23-1 that installs just fine in
> testing.
Well, I'm actually using unstable, but linux-image-2.6-686 still pulled
2.6.22. Next time I'll try 2.6.23 but I'll not be near that machine for
approx
Package: linux-image-2.6.22-3-686
Version: 2.6.22-6
Severity: normal
Hi,
After upgrading to linux-image-2.6.22-3, networking no longer works. In
fact, lspci does no longer show the network card at all.
linux-image-2.6.20-1 (version 2.6.20-3) works fine. dmesg and lspci for
both versions are belo
On Fri, Dec 07, 2007 at 11:15:00AM +0100, maximilian attems wrote:
> please try newer, unstalbe has 2.6.23-1 that installs just fine in
> testing.
I've tested now 2.6.23-2 and the bug is still present, but only when
powering on the machine. After a reboot (or when booting Windows before
Linux) th
On Tue, Dec 25, 2007 at 11:30:32PM +0100, maximilian attems wrote:
> please report back if aboves fixes it.
Ok, but it may take 1-2 weeks when I'm next near that machine.
Gabor
--
-
MTA SZTAKI Computer and Automation Research In
On Mon, Sep 01, 2008 at 09:04:35PM +0200, Frank Küster wrote:
> Although I personally feal the bug is super-duper-hyper-grave, I leave
> the judgement to the linux maintainers.
FYI: I've tried 2.6.27-rc5 and it is up for more than 15 hours now.
That's far more than 2.6.25/26 ever managed on this
Hi,
Mee too! It'd be really nice to have this integrated.
To add something constructive, mdadm, and lvm2 scripts already use sed
without checking for it or making sure that it is available, so the use
of sed should not be a problem. cryptsetup also uses sed but it at least
forces "BUSYBOX=y". IMH
On Sun, Jan 03, 2010 at 06:31:20PM +0200, Pasi Kärkkäinen wrote:
> So the change has happened, lthough it took painfully long to get the
> upstream Linux pv_ops framework in shape and all that.. and obviously
> the pv_ops dom0 patches still need to get merged upstream.
That was opposed quite stro
Hi,
IMHO you are confused: /proc/sys/kernel/domainname is the NIS domain name
and has nothing to do with DNS; in fact, the NIS domain can be different
from the DNS domain. Thus your script is doubly wrong: on a NIS system
hostnames are normally not qualified so you cannot obtain the NIS domain
fro
On Fri, Dec 26, 2008 at 06:49:05PM +0100, Moritz Muehlenhoff wrote:
> Does this error still occur with more recent kernel versions?
I've tried once during the christmas holidays with 2.6.26 and it worked,
so the bug can be closed.
Gabor
--
-
On Sat, Dec 27, 2008 at 02:44:21PM +0100, Moritz Muehlenhoff wrote:
> Does this error still occur with more recent kernel versions?
No idea, all our Dells are now running Mandriva with a 2.6.18-based Xen
kernel, and there is no chance in the near future to try Debian on them
again. I've had other
15 matches
Mail list logo
