Re: new 2.6.13 kernel
Le 02.09.2005 03:14:20, Marco Amadori a écrit :
On Thursday 01 September 2005 22:36, Jean-Luc Coulon (f5ibh) wrote:
[...] [DevFS]
I *need* it for my lvm on raid
In this bug #323391 [1] there is a patch to make yaird works, I use
it,
works for my lvm on raid systems, remember to add --verbose on the
script
`dpkg --listfiles yaird | grep -i raidtab` (I do not remember the
name) if u
encounter the bug #324774 [2]
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=323391
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=324774
So if kernel-package will default with yaird initramfs no devfs will
be
needed, btw I think that devfs only disappeared from kconfig...
Yes, I've patched it myself with the attached patch
The only problem is hat it breaks the normal way to build a package
with make-kpkg, you have to manage the initrs separately.
--
ESC:wq
Jean-Luc
--- RaidTab.pm.orig 2005-08-31 16:36:42.558731626 +0200
+++ RaidTab.pm 2005-08-31 16:37:41.889476015 +0200
@@ -40,7 +40,7 @@
# my $name = Conf::get('fstab');
$raidTab = [];
my $in;
- if (! open ($in, -|, /sbin/mdadm --detail --scan)) {
+ if (! open ($in, -|, /sbin/mdadm --detail --scan --verbose)) {
Base::fatal (Can't read mdadm output);
}
my @lines = $in;
pgpQvUQJ70X7R.pgp
Description: PGP signature
Re: new 2.6.13 kernel
On Thursday 01 September 2005 21:14, Marco Amadori wrote: On Thursday 01 September 2005 22:36, Jean-Luc Coulon (f5ibh) wrote: [...] [DevFS] I *need* it for my lvm on raid In this bug #323391 [1] there is a patch to make yaird works, I use it, works for my lvm on raid systems, remember to add --verbose on the script `dpkg --listfiles yaird | grep -i raidtab` (I do not remember the name) if u encounter the bug #324774 [2] [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=323391 [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=324774 So if kernel-package will default with yaird initramfs no devfs will be needed, btw I think that devfs only disappeared from kconfig... Devfs is gone for good. uDev replaces it. The problem with devfs was, from the kernel list, that is was buggy, racey and unmaintained. Over a year ago it was announced that it was going away in the Doc/feature-removal-schedule.txt file in the kernel source. Debain has just been slow to adapt. Ed Tomlinson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: new 2.6.13 kernel
I'm running the stock 2.6.13 kernel (from kernel.org) on my amd64 laptop without any problems. I chose option 3 (PREEMPT) in the config. Of course, YMMV... -Ted On Thursday 01 September 2005 11:56, [EMAIL PROTECTED] wrote: Did you download it from www.kernel.org? Is there a debian source package? Could you tell me the url in that circumstance? tnx! Rafael Rodríguez ha scritto: Hi. In the new kernel, when make oldconfig'ing, i've seen a new option: Preemption Model 1. No Forced Preemption (Server) (PREEMPT_NONE) (NEW) 2. Voluntary Kernel Preemption (Desktop) (PREEMPT_VOLUNTARY) (NEW) 3. Preemptible Kernel (Low-Latency Desktop) (PREEMPT) Does anyone know if it's already safe to select a preemptive kernel in amd64¿ Regards, Rafael Rodríguez
Re: new 2.6.13 kernel
Did you download it from www.kernel.org? Is there a debian source package? Could you tell me the url in that circumstance? tnx! Rafael Rodríguez ha scritto: Hi. In the new kernel, when make oldconfig'ing, i've seen a new option: Preemption Model 1. No Forced Preemption (Server) (PREEMPT_NONE) (NEW) 2. Voluntary Kernel Preemption (Desktop) (PREEMPT_VOLUNTARY) (NEW) 3. Preemptible Kernel (Low-Latency Desktop) (PREEMPT) Does anyone know if it's already safe to select a preemptive kernel in amd64¿ Regards, Rafael Rodríguez -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: new 2.6.13 kernel
Le 01.09.2005 21:07:18, Theodore Kisner a écrit : I'm running the stock 2.6.13 kernel (from kernel.org) on my amd64 laptop without any problems. I chose option 3 (PREEMPT) in the config. Of course, YMMV... But if you want to build an intird with mkinitrd (or --initrd option of make-kpkg), the initrd needs devfs which has been dropped from kernel-2.6.13. I failed to boot my system (lvm over raid1) this way. So I tried yaird and this one need to be patched if used with mdadm 1.12.0... -Ted Jean-Luc pgp9MKgHfBxhZ.pgp Description: PGP signature
Re: new 2.6.13 kernel
On 9/1/05, Jean-Luc Coulon (f5ibh) [EMAIL PROTECTED] wrote: But if you want to build an intird with mkinitrd (or --initrd option of make-kpkg), the initrd needs devfs which has been dropped from kernel-2.6.13. I didn't know that initrd depends on it, but certainly the debian installer needs devfs. So that means no recent kernels for the debian installer, I guess? I certainly think that this is going to be a problem for installing Sarge on modern machines, and an unnecessary one too, because devfs was declared dead a long time ago. Thomas
Re: new 2.6.13 kernel
What are we supposed to do instead? Fix mkinitrd so it doesn't need devfs. Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: new 2.6.13 kernel
Le 01.09.2005 22:06:49, Neil Gunton a écrit : Thomas Steffen wrote: On 9/1/05, Jean-Luc Coulon (f5ibh) [EMAIL PROTECTED] wrote: But if you want to build an intird with mkinitrd (or --initrd option of make-kpkg), the initrd needs devfs which has been dropped from kernel-2.6.13. I didn't know that initrd depends on it, but certainly the debian installer needs devfs. So that means no recent kernels for the debian installer, I guess? I certainly think that this is going to be a problem for installing Sarge on modern machines, and an unnecessary one too, because devfs was declared dead a long time ago. Thomas Sorry, I'm a bit confused (also new here, so please forgive my ignorance)... could someone please explain why on the one hand devfs has (apparently) been dropped, but on the other hand it appears to be required for installing with initrd on modern machines??? What are we supposed to do instead? Is there reasoning behind this, or is it a mistake of some kind? devfs has been dropped because it is considered as obsolete (replaced by udev). mkinitrd needs devfs but there are several other ways to build and initrd and these other ways dont necessarily needs devfs. There is yaird which is an alternative or mkinitramfs (Ubuntu). See this topic: http://lists.debian.org/debian-kernel/2005/08/msg01018.html TIA, /Neil Jean-Luc pgp0dGjWZRDvC.pgp Description: PGP signature
Re: new 2.6.13 kernel
On Thursday 01 September 2005 4:06 pm, Neil Gunton wrote: Thomas Steffen wrote: On 9/1/05, Jean-Luc Coulon (f5ibh) [EMAIL PROTECTED] wrote: But if you want to build an intird with mkinitrd (or --initrd option of make-kpkg), the initrd needs devfs which has been dropped from kernel-2.6.13. I didn't know that initrd depends on it, but certainly the debian installer needs devfs. So that means no recent kernels for the debian installer, I guess? I certainly think that this is going to be a problem for installing Sarge on modern machines, and an unnecessary one too, because devfs was declared dead a long time ago. Thomas Sorry, I'm a bit confused (also new here, so please forgive my ignorance)... could someone please explain why on the one hand devfs has (apparently) been dropped, but on the other hand it appears to be required for installing with initrd on modern machines??? What are we supposed to do instead? Is there reasoning behind this, or is it a mistake of some kind? I am a bit confused myself. I have been building and running initrd kernels for over a year now and have not been using devfs at all. I have been running 2.6.13 from kernel.org since this past weekend. -- John C. Martin - http://www.cs.utk.edu/~jomartin * Please be aware that non-encrypted e-mail is NOT a secured communication * vehicle, and that others may in certain circumstances be able to view its * contents. You should encrypt your e-mail. Disclaimers in your e-mail * signature about confidentiality and designated recipients are silly and * useless. * Use my gpg key to ensure privacy - http://www.cs.utk.edu/~jomartin/John.gpg pgpnicODcdGh1.pgp Description: PGP signature
Re: new 2.6.13 kernel
On Thu, Sep 01, 2005 at 04:13:10PM -0400, John C. Martin wrote: I am a bit confused myself. I have been building and running initrd kernels for over a year now and have not been using devfs at all. I have been running 2.6.13 from kernel.org since this past weekend. d-i uses devfs. The normal initrd for the system does not in my experience. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: new 2.6.13 kernel
Le 01.09.2005 22:17:21, Lennart Sorensen a écrit : On Thu, Sep 01, 2005 at 04:13:10PM -0400, John C. Martin wrote: I am a bit confused myself. I have been building and running initrd kernels for over a year now and have not been using devfs at all. I have been running 2.6.13 from kernel.org since this past weekend. d-i uses devfs. The normal initrd for the system does not in my experience. I *need* it for my lvm on raid Here is the script file in my initrd built with mkinitrd: mdadm -A /dev/md1 -R -u 476bfe75:5179335f:4d060da2:c2ff4965 /dev/sda2 /dev/sdb2 mkdir /devfs/vg00- mount_tmpfs /var if [ -f /etc/lvm/lvm.conf ]; then cat /etc/lvm/lvm.conf /var/lvm.conf fi mount_tmpfs /etc/lvm if [ -f /var/lvm.conf ]; then cat /var/lvm.conf /etc/lvm/lvm.conf fi mount -nt devfs devfs /dev - vgchange -a y vg00 umount /dev umount -n /var umount -n /etc/lvm ROOT=/dev/mapper/vg00-root_lv mdadm -A /dev/md1 -R -u 476bfe75:5179335f:4d060da2:c2ff4965 /dev/sda2 /dev/sdb2 Len Sorensen Jean-Luc pgpIFgqX2f4KQ.pgp Description: PGP signature
Re: new 2.6.13 kernel
Thomas Steffen wrote: On 9/1/05, Jean-Luc Coulon (f5ibh) [EMAIL PROTECTED] wrote: But if you want to build an intird with mkinitrd (or --initrd option of make-kpkg), the initrd needs devfs which has been dropped from kernel-2.6.13. I didn't know that initrd depends on it, but certainly the debian installer needs devfs. So that means no recent kernels for the debian installer, I guess? I certainly think that this is going to be a problem for installing Sarge on modern machines, and an unnecessary one too, because devfs was declared dead a long time ago. Thomas Sorry, I'm a bit confused (also new here, so please forgive my ignorance)... could someone please explain why on the one hand devfs has (apparently) been dropped, but on the other hand it appears to be required for installing with initrd on modern machines??? What are we supposed to do instead? Is there reasoning behind this, or is it a mistake of some kind? TIA, /Neil -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: new 2.6.13 kernel
Sorry, but i use vanilla kernels (plus ck patchsets). U are not going to see a debianized kernel that fast after the official release, r u? Rafael Rodríguez El Jueves, 1 de Septiembre de 2005 19:56, [EMAIL PROTECTED] escribió: Did you download it from www.kernel.org? Is there a debian source package? Could you tell me the url in that circumstance? tnx! Rafael Rodríguez ha scritto: Hi. In the new kernel, when make oldconfig'ing, i've seen a new option: Preemption Model 1. No Forced Preemption (Server) (PREEMPT_NONE) (NEW) 2. Voluntary Kernel Preemption (Desktop) (PREEMPT_VOLUNTARY) (NEW) 3. Preemptible Kernel (Low-Latency Desktop) (PREEMPT) Does anyone know if it's already safe to select a preemptive kernel in amd64¿ Regards, Rafael Rodríguez
Re: new 2.6.13 kernel
On Thursday 01 September 2005 22:36, Jean-Luc Coulon (f5ibh) wrote: [...] [DevFS] I *need* it for my lvm on raid In this bug #323391 [1] there is a patch to make yaird works, I use it, works for my lvm on raid systems, remember to add --verbose on the script `dpkg --listfiles yaird | grep -i raidtab` (I do not remember the name) if u encounter the bug #324774 [2] [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=323391 [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=324774 So if kernel-package will default with yaird initramfs no devfs will be needed, btw I think that devfs only disappeared from kconfig... -- ESC:wq -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: new 2.6.13 kernel
On Monday 29 August 2005 09:25, Rafael Rodríguez wrote: Does anyone know if it's already safe to select a preemptive kernel in amd64¿ If it wasn't save them I've had an unsafe kernel since I got myself an Amd64. Anyway, It never crashed on me, (that I know of). I and my pc is switched on nearly permanently. Ernest. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: new 2.6.13 kernel
Ernest jw ter Kuile [EMAIL PROTECTED] writes: Anyway, It never crashed on me, (that I know of). I and my pc is switched on nearly permanently. I enabled the forcible preempt option and it seems to work fine on my Ferrari. -- * Sufficiently advanced magic is indistinguishable from technology (T.P) * * PGP public key available @ http://www.iki.fi/killer * -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: new 2.6.13 kernel
The same help of the option in kernels = 2.6.12 gave you a hint that it wasn't very safe in x86_64... however, i don't see any help at all in 2.6.13... Rafael Rodríguez El Lunes, 29 de Agosto de 2005 17:34, Ernest jw ter Kuile escribió: On Monday 29 August 2005 09:25, Rafael Rodríguez wrote: Does anyone know if it's already safe to select a preemptive kernel in amd64¿ If it wasn't save them I've had an unsafe kernel since I got myself an Amd64. Anyway, It never crashed on me, (that I know of). I and my pc is switched on nearly permanently. Ernest.
