On Mon, Nov 14, 2005 at 08:38:03PM -0800, Steve Langasek wrote:
> On Mon, Nov 14, 2005 at 10:38:41PM +0100, Sven Luther wrote:
> > I still think choice is good, and also what users expect of debian. A sane
> > default, plus the ability to override that in expert mode.
>
> Choice is overrated, and
On Tue, Nov 15, 2005 at 02:18:14AM +0100, Erik van Konijnenburg wrote:
> On Sat, Nov 12, 2005 at 11:55:37AM +0100, Marco Amadori wrote:
> > Another question, could you use already setup svn for yaird? there is
> > already
> > a yaird subversion repo in d-i alioth svn.
>
> As Sven noted, that's p
Your message dated Tue, 15 Nov 2005 07:41:17 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed with latest kernel package :-)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
On Mon, Nov 14, 2005 at 10:38:41PM +0100, Sven Luther wrote:
> I still think choice is good, and also what users expect of debian. A sane
> default, plus the ability to override that in expert mode.
Choice is overrated, and a poor substitute for properly working tools.
"Which initramfs generator d
James Bottomley <[EMAIL PROTECTED]> wrote:
> Can you try with the attached patch, which will force DV to ignore
> the echo buffer write tests?
I'll certainly try.
The kernel I was using was a prebuilt Debian kernel. I'm not sure how
to rebuild it from source. Horms, if you could point me in the r
On Sat, Nov 12, 2005 at 11:55:37AM +0100, Marco Amadori wrote:
> Another question, could you use already setup svn for yaird? there is already
> a yaird subversion repo in d-i alioth svn.
As Sven noted, that's part of kernel tree; it includes the debian parts,
not only the core.
At the moment, I
On Sat, Nov 12, 2005 at 11:55:37AM +0100, Marco Amadori wrote:
> I would like to know how do you feel in splitting Plan.pm's trySomething()
> functions in separate files putted in a directory
> like ./perl/plugins/trySomething.pm and then scan it from Plan.pm.
> Also Test suite should be splitted
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 14 Nov 2005 18:33:06 -0500
Curt Howland <[EMAIL PROTECTED]> wrote:
> Well, it worked today when it didn't work when I first installed
> 2.6.14, so indeed something in the mean time changed for the better.
>
> Can you think of any additionall
I noticed that this evening there's been an update to 2.6.14-2-686, so
I installed it and tried again. No change, I still receive this
error:
dierdre# uname -a
Linux dierdre 2.6.14-2-686 #1 Mon Nov 14 14:19:05 UTC 2005 i686
GNU/Linux
~
dierdre# hdparm -d 1 /dev/hda
/dev/hda:
setting using_dma
On Monday 14 November 2005 17:03, Jonas Smedegaard was heard to say:
> No need for excuse: this is highly relevant info, as I suspect it
> shows that the recent yaird inclusion of fbcon is what solves this.
>
> Could it be that even if you noticed the new fbcon line in
> Default.cfg, your image is
On Mon, Nov 14, 2005 at 01:37:18AM +0100, Jonas Smedegaard wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Sun, 13 Nov 2005 17:28:38 -0500
> Jeff Bailey <[EMAIL PROTECTED]> wrote:
>
> > On dim, 2005-11-13 at 20:28 +0100, Frans Pop wrote:
> > > On Sunday 13 November 2005 08:16, Sve
On Sun, Nov 13, 2005 at 05:26:17PM -0500, Jeff Bailey wrote:
> On dim, 2005-11-13 at 22:49 +0100, Sven Luther wrote:
> > I wonder about one thing though, since this is basically a ramdisk, once the
> > boot is over, what happens to the memory used to hold it ?
> It gets freed as part of run-init,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Huh ? It contain the list of the names of the flavours for a given arch. In
> this sense it is exactly the info provided in the arch//defines file,
> and once you have that, you prefix it to the version-abi, and you know which
> kernels you then need
This was discussed on debian-devel [1]. As long as the debian kernel is
shipped with CONFIG_LEGACY_PTYS enabled I'd say that the current
behaviour is correct.
The proper fix would be to:
a) change the default kernel config; or
b) change the udev rules
not to do any special changes to initramf
Russel Coker wrote:
The initramfs generated on a LVM IDE system does not create /dev/hda* device
nodes, so vgchange doesn't discover any LVM devices and therefore the
machine can't boot.
That is weird, I have root-on-lvm-on-hda and the devices are created
+ the system boots just fine for me.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 14 Nov 2005 22:06:55 +0100
Frans Pop <[EMAIL PROTECTED]> wrote:
> One thing to keep in mind if we should go for initramfs-tools.
> debian-cd will include yaird and dependencies by default on CD images
> to satisfy kernel-image dependencies as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 14 Nov 2005 15:09:27 -0500
Curt Howland <[EMAIL PROTECTED]> wrote:
> Just after I filed this wishlist item, I decided to try again. This
> time vga=791 works. Surprisingly, the characters are even smaller
> than when running 2.6.12. It's bet
Package: initramfs-tools
Severity: minor
Tags: patch
Currently /usr/share/initramfs-tools/init kills udev after init-premount
scripts have executed. However, more devices might become available as a
result of running the local scripts.
I therefore suggest to kill udev as late as possible (rig
Package: initramfs-tools
Severity: minor
Tags: patch
This patch adds a separate function to load a filesystem driver which
first checks if it is already compiled into the kernel which should
remove some superflous modprobe error messages if it is.
Re,
David
Index: initramfs-tools-0.38/scripts
Package: initramfs-tools
Severity: minor
Tags: patch
Since the HACKING file included with the initramfs-tools package isn't
very helpful, I've attached a stab at a man page giving a brief introduction
to writing initramfs-tools scripts.
Feel free to proofread, alter and possibly add it to the
Package: initramfs-tools
Severity: wishlist
Currently /usr/share/initramfs-tools/scripts/local checks for the
presence of the root device node after local-top has been run but before
local-premount has been run an panics if it can't find it:
# Get the root filesystem type
if [ ! -e "${ROOT}"
Package: initramfs-tools
Severity: wishlist
Currently the last line in
/usr/share/initramfs-tools/scripts/local-top/lvm only activates the
volume group which seems to contain the root fs.
In order to support features such as root-auto-probing (bug #337682) and
cryptoroot-over-lvm, it would b
On Mon, Nov 14, 2005 at 10:06:55PM +0100, Frans Pop wrote:
> On Monday 14 November 2005 21:47, Joey Hess wrote:
> > This seems more in-scope for the kernel team to decide than the d-i
> > team, but if it would help I can flip a coin..
>
> Note that one consideration is consistency between Debian a
On Mon, Nov 14, 2005 at 03:47:57PM -0500, Joey Hess wrote:
> Sven Luther wrote:
> > Ok, but who will chose which will be the default one ? The d-i team, or the
> > kernel team ?
>
> It's more important to make a choice than what the choice is.
>
> d-i chose between lilo and grub before; we did i
thank you!
On Mon, Nov 14, 2005 at 11:33:30AM -0800, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> #338543: linux-image-2.6.14-1-686: CONFIG_SECURITY_NETWORK is disabled which
> totally breaks SE/Linux,
> which was filed against the linux-image-
Jonas Smedegaard wrote:
> Initramfs-tools May produce too big images for some arches. This needs
> to be verified and documented (Sven seems most knowledgable about this).
>
> Yaird needs sysfs on running system so cannot be used from a 2.4
> system. This may not be an issue to d-i.
>
> Yaird doe
On Monday 14 November 2005 21:47, Joey Hess wrote:
> This seems more in-scope for the kernel team to decide than the d-i
> team, but if it would help I can flip a coin..
Note that one consideration is consistency between Debian and Ubuntu in
d-i. Ubuntu have implemented initramfs-tools and in fac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 14 Nov 2005 14:54:10 -0500
Joey Hess <[EMAIL PROTECTED]> wrote:
> Frans Pop wrote:
> > Both initrd generators have limitations in what they currently
> > support. We may have to either always install both, or include
> > logic that pre-install
Package: linux-2.6
Tags: patch
Since beginning of 2005 I tried different kernel/Linux-images 2.6.x
on my Alphastation 500/500:
=
cpu : Alpha
cpu model : EV56
cpu variati
Sven Luther wrote:
> Ok, but who will chose which will be the default one ? The d-i team, or the
> kernel team ?
It's more important to make a choice than what the choice is.
d-i chose between lilo and grub before; we did it by listening to what
users wanted and looking at which worked best over
Just after I filed this wishlist item, I decided to try again. This
time vga=791 works. Surprisingly, the characters are even smaller
than when running 2.6.12. It's better than 80x25, though.
Please excuse the bug report, I guess it's already obsolete.
Curt-
--
September 11th, 2001
The pro
On Mon, Nov 14, 2005 at 03:17:24PM -0500, Joey Hess wrote:
> Sven Luther wrote:
> > Also, we have perl-base in base, or used to at least, would yaird not be
> > able
> > to depend on perl-base only ?
>
> yaird uses at lest the following perl modules which are not currently
> present in perl-base
Sven Luther wrote:
> Also, we have perl-base in base, or used to at least, would yaird not be able
> to depend on perl-base only ?
yaird uses at lest the following perl modules which are not currently
present in perl-base but are in perl:
./Image.pm:use File::Copy;
./Pack.pm:use File::Temp;
On t
On Mon, Nov 14, 2005 at 02:54:10PM -0500, Joey Hess wrote:
> Frans Pop wrote:
> > Both initrd generators have limitations in what they currently support. We
> > may have to either always install both, or include logic that
> > pre-installs one or the other depending on the situation.
>
> Based o
Package: linux-image-2.6.14-1-686
Version: 2.6.14-2
Severity: wishlist
First, thank you for all your astounding work keeping Debian the best
distribution bar none.
Until 2.6.14, I was able to use "vga=791" for framebuffer in lilo.conf,
and found the substantially larger console very useful. "vga
Accepted:
kernel-image-2.6-386_2.6.14-3_i386.deb
to pool/main/l/linux-2.6/kernel-image-2.6-386_2.6.14-3_i386.deb
kernel-image-2.6-686-smp_2.6.14-3_i386.deb
to pool/main/l/linux-2.6/kernel-image-2.6-686-smp_2.6.14-3_i386.deb
kernel-image-2.6-686_2.6.14-3_i386.deb
to pool/main/l/linux-2.6/kern
Frans Pop wrote:
> Both initrd generators have limitations in what they currently support. We
> may have to either always install both, or include logic that
> pre-installs one or the other depending on the situation.
Based on http://wiki.debian.org/InitrdReplacementOptions I didn't see
any item
Package: linux-image-2.6.14-1-686
Version: 2.6.14-2
Severity: important
I have 2.6.12 and 2.6.14 (686 P4) installed on this machine. If I boot back into
2.6.12 DMA is on for /dev/hda. It is off in 2.6.14 and will not enable:
# hdparm -d 1 /dev/hda
/dev/hda:
setting using_dma to 1 (on)
HDIO_SET
Your message dated Mon, 14 Nov 2005 11:19:30 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#338911: fixed in linux-2.6 2.6.14-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Mon, 14 Nov 2005 11:19:30 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#338543: fixed in linux-2.6 2.6.14-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Mon, 14 Nov 2005 11:19:30 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#337713: fixed in linux-2.6 2.6.14-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Mon, 14 Nov 2005 11:19:30 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#337089: fixed in linux-2.6 2.6.14-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Mon, 14 Nov 2005 11:19:30 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#337072: fixed in linux-2.6 2.6.14-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Mon, 14 Nov 2005 11:19:30 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#336450: fixed in linux-2.6 2.6.14-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Mon, 14 Nov 2005 11:19:30 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#336450: fixed in linux-2.6 2.6.14-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Mon, 14 Nov 2005 11:19:30 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#336424: fixed in linux-2.6 2.6.14-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Mon, 14 Nov 2005 11:19:30 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#336431: fixed in linux-2.6 2.6.14-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Mon, 14 Nov 2005 11:19:30 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#321200: fixed in linux-2.6 2.6.14-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Mon, 14 Nov 2005 11:19:30 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#267600: fixed in linux-2.6 2.6.14-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
kernel-image-2.6-386_2.6.14-3_i386.deb
to pool/main/l/linux-2.6/kernel-image-2.6-386_2.6.14-3_i386.deb
kernel-image-2.6-686-smp_2.6.14-3_i386.deb
to pool/main/l/linux-2.6/kernel-image-2.6-686-smp_2.6.14-3_i386.deb
kernel-image-2.6-686_2.6.14-3_i386.deb
to pool/main/l/linux-2.6/kernel-image-2.
linux-2.6_2.6.14-3_i386.changes uploaded successfully to localhost
along with the files:
linux-2.6_2.6.14-3.dsc
linux-2.6_2.6.14-3.diff.gz
linux-doc-2.6.14_2.6.14-3_all.deb
linux-manual-2.6.14_2.6.14-3_all.deb
linux-patch-debian-2.6.14_2.6.14-3_all.deb
linux-source-2.6.14_2.6.14-3_all.d
On Mon, Nov 14, 2005 at 11:35:27AM +0100, Maximilian Attems <[EMAIL PROTECTED]>
wrote:
> please reassign in those cases. :)
ok! :)
> > This happens whenever I want to upgrade gnu virtual private ethernet and
> > kill it (which should free the tun interface it uses). Following ifconfig
> > -a or
Processing commands for [EMAIL PROTECTED]:
> reassign 337881 linux-2.6
Bug#337881: udev post-inst fails
Bug reassigned from package `udev' to `linux-2.6'.
> severity 337881 grave
Bug#337881: udev post-inst fails
Severity set to `grave'.
> retitle 337881 CONFIG_KOBJECT_UEVENT must always be defin
Processing commands for [EMAIL PROTECTED]:
> reassign 338973 linux-image-2.6.14-1-686-smp
Bug#338973: unregister_netdevice: waiting for vpn0 to become free. Usage count
= 23
Bug#323860: unregister_netdevice: waiting for vpn0 to become free. Usage count
= 23
Bug reassigned from package `linux-ima
Processing commands for [EMAIL PROTECTED]:
> reassign 323860 linux-image-2.6-686-smp
Bug#323860: unregister_netdevice: waiting for vpn0 to become free. Usage count
= 23
Bug reassigned from package `linux-image-2.6.12-1-686-smp' to
`linux-image-2.6-686-smp'.
> reassign 338973 linux-image-2.6-686
reassign 323860 linux-image-2.6-686-smp
reassign 338973 linux-image-2.6-686-smp
merge 338973 323860
stop
On Mon, Nov 14, 2005 at 06:11:13AM +0100, Marc Lehmann wrote:
> Package: linux-image-2.6.14-2
> Version: 2.6.14-2
> Severity: important
>
>
> The same bug as reported against earlier debian k
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 14 Nov 2005 12:15:29 +0100
Sven Luther <[EMAIL PROTECTED]> wrote:
> On Mon, Nov 14, 2005 at 11:46:07AM +0100, Jonas Smedegaard wrote:
> > On Mon, 14 Nov 2005 09:57:22 +0100
> > Sven Luther <[EMAIL PROTECTED]> wrote:
> >
> > > On Sun, Nov 13,
On Mon, Nov 14, 2005 at 11:46:07AM +0100, Jonas Smedegaard wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Mon, 14 Nov 2005 09:57:22 +0100
> Sven Luther <[EMAIL PROTECTED]> wrote:
>
> > On Sun, Nov 13, 2005 at 10:56:40PM +0100, Jonas Smedegaard wrote:
>
> > > On Sun, 13 Nov 2005
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 14 Nov 2005 09:57:22 +0100
Sven Luther <[EMAIL PROTECTED]> wrote:
> On Sun, Nov 13, 2005 at 10:56:40PM +0100, Jonas Smedegaard wrote:
> > On Sun, 13 Nov 2005 20:03:59 +0100
> > Sven Luther <[EMAIL PROTECTED]> wrote:
> >
> > > > I'm not sure
On Mon, Nov 14, 2005 at 01:37:18AM +0100, Jonas Smedegaard wrote:
> If I understand it correctly, ldd only correctly resolves libraries
> linked with glibc, and yaird includes a more generic tool - documented
> here: http://www.xs4all.nl/~ekonijn/yaird/yaird.html#shlibs
Err, yaird uses ldd and suf
On Sun, Nov 13, 2005 at 10:56:40PM +0100, Jonas Smedegaard wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Sun, 13 Nov 2005 20:03:59 +0100
> Sven Luther <[EMAIL PROTECTED]> wrote:
>
> > > I'm not sure about the linux-initramfs-tool part of the dependency.
> >
> > That is a virtua
Processing commands for [EMAIL PROTECTED]:
> reassign 338973 linux-2.6
Bug#338973: unregister_netdevice: waiting for vpn0 to become free. Usage count
= 23
Warning: Unknown package 'linux-image-2.6.14-2'
Bug reassigned from package `linux-image-2.6.14-2' to `linux-2.6'.
> --
Stopping processing h
On Sun, Nov 13, 2005 at 07:01:28PM -0800, wolftales wrote:
> Jonas Smedegaard wrote:
> >-BEGIN PGP SIGNED MESSAGE-
> >Hash: SHA1
> >
> >On Sun, 13 Nov 2005 12:38:35 -0800
> >Wolftales <[EMAIL PROTECTED]> wrote:
> >
> >
> >>I had no luck running this with yaird as I showed below.
> >>
On Mon, Nov 14, 2005 at 01:37:18AM +0100, Jonas Smedegaard wrote:
> Would it perhaps make sense to provide the yaird "findlibs" binary in a
> separate package for initramfs-tools to also use?
findlibs is crippled replacement for mklibs-readelf, a tool which I
decided to use for mklibs-copy, not a
After looking for possible reasons (iptables, tc etc.), I found that the
usage count reported by the kernel corresponds exactly to the permanent arp
entries:
frank ~# ip neigh ls dev vpn0
10.0.0.22 lladdr fe:fd:80:00:00:07 nud permanent
10.9.0.33 lladdr fe:fd:80:00:00:12 nud permanent
On Sun, Nov 13, 2005 at 05:26:17PM -0500, Jeff Bailey wrote:
> On dim, 2005-11-13 at 22:49 +0100, Sven Luther wrote:
> > > FWIW, Ubuntu's install defaults to 'most' mode on the grounds that for
> > > most systems (not lowmem, not oldworld ppc, not netboot) there's no harm
> > > in having a larger i
Package: linux-image-2.6.14-2
Version: 2.6.14-2
Severity: important
The same bug as reported against earlier debian kernels (#323860) still
persists with 2.6.14, and does not happen with my own compiled kernels.
This happens whenever I want to upgrade gnu virtual private ethernet and
kill it (wh
I recompiled the kernel with the missing option, reinstalled udev
0.074-2 again - udev works as exspected. The linux-images should all
be checked, that this option is enabled (I do not know how this
affecs older images <2.6.14 - eventually there should be a dependance
of udev to the newer linux
On Sun, Nov 13, 2005 at 10:59:10PM +0100, Maximilian Attems wrote:
> On Sun, Nov 13, 2005 at 10:34:27PM +0100, Sven Luther wrote:
> > On Sun, Nov 13, 2005 at 09:23:14PM +0100, Maximilian Attems wrote:
> > > On Sun, Nov 13, 2005 at 08:01:38PM +0100, Sven Luther wrote:
> > > > On Sun, Nov 13, 2005 at
69 matches
Mail list logo
