RE: Mentioning Layne one more time
Hi, guys! I would remember one ancient story... It's name was Herodot... So let Layne to rest on his laurels... Don't call him in vain... :) > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Christian Haugan Toldnes > Sent: Wednesday, November 14, 2001 12:02 PM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re: Mentioning Layne one more time > Importance: High > > > Dmitriy Kropivnitskiy <[EMAIL PROTECTED]> writes: > > > I have just found a residiual page in the google cache. It > shows that Layne > > remember the rude guy from september was subscribed to a whole > bunch of mls > > most of them debian related ) > > > http://www.google.com/search?q=cache:SPW2_7zBmf8:justinfinity.2y.n et:8080/misc/subscribe-fucker.html+a515luna&hl=en > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > Makes me wonder... If Layne (female-dog)ed half as much on the other lists, as he did on this one, he would have been kept from doing anything else at all... cute. c -- Christian H. Toldnes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Mentioning Layne one more time
Dmitriy Kropivnitskiy <[EMAIL PROTECTED]> writes: > I have just found a residiual page in the google cache. It shows that Layne ( > remember the rude guy from september was subscribed to a whole bunch of mls > most of them debian related ) > >http://www.google.com/search?q=cache:SPW2_7zBmf8:justinfinity.2y.net:8080/misc/subscribe-fucker.html+a515luna&hl=en > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > Makes me wonder... If Layne (female-dog)ed half as much on the other lists, as he did on this one, he would have been kept from doing anything else at all... cute. c -- Christian H. Toldnes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Mentioning Layne one more time
Well this explains it. But the page name describes him well! On Tue, Nov 13, 2001 at 02:15:13PM -0500, Dmitriy Kropivnitskiy wrote: > I have just found a residiual page in the google cache. It shows that Layne ( > remember the rude guy from september was subscribed to a whole bunch of mls > most of them debian related ) > http://www.google.com/search?q=cache:SPW2_7zBmf8:justinfinity.2y.net:8080/misc/subscribe-fucker.html+a515luna&hl=en pgpBw35XJUNpN.pgp Description: PGP signature
Re: Mentioning Layne one more time
Well this explains it. But the page name describes him well! On Tue, Nov 13, 2001 at 02:15:13PM -0500, Dmitriy Kropivnitskiy wrote: > I have just found a residiual page in the google cache. It shows that Layne ( > remember the rude guy from september was subscribed to a whole bunch of mls > most of them debian related ) > >http://www.google.com/search?q=cache:SPW2_7zBmf8:justinfinity.2y.net:8080/misc/subscribe-fucker.html+a515luna&hl=en msg04176/pgp0.pgp Description: PGP signature
Mentioning Layne one more time
I have just found a residiual page in the google cache. It shows that Layne ( remember the rude guy from september was subscribed to a whole bunch of mls most of them debian related ) http://www.google.com/search?q=cache:SPW2_7zBmf8:justinfinity.2y.net:8080/misc/subscribe-fucker.html+a515luna&hl=en
SSH-RSH Conflict
Can anyone enlighten me as to why openssh-2.9..(deb package) would have a conflict with (rsh-client << 0.16.0)? I can see that other packages might need rsh-client, but why would ssh not install unless rsh-client > 0.16? Isn't ssh a replacement for rsh-apps? This happens while back-porting openssh-2.9p2-6 to potato. -Walter [EMAIL PROTECTED]
Mentioning Layne one more time
I have just found a residiual page in the google cache. It shows that Layne ( remember the rude guy from september was subscribed to a whole bunch of mls most of them debian related ) http://www.google.com/search?q=cache:SPW2_7zBmf8:justinfinity.2y.net:8080/misc/subscribe-fucker.html+a515luna&hl=en -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
SSH-RSH Conflict
Can anyone enlighten me as to why openssh-2.9..(deb package) would have a conflict with (rsh-client << 0.16.0)? I can see that other packages might need rsh-client, but why would ssh not install unless rsh-client > 0.16? Isn't ssh a replacement for rsh-apps? This happens while back-porting openssh-2.9p2-6 to potato. -Walter [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Freeware for the AS400: CAT produces a catalog of files in a library.
FREEWARE: AS400 Library Catalog Software (source included.) As thanks for visiting our web site at www.rapidfire400.com, we would like you to have our CAT Freeware package. You can use CAT to gather information about the files in a library and print reports; by Date Last Used, by File Size, by File Name. We have included the source code with CAT. We used RapidFire400 to automatically generate the programs for the reports. RAPIDFIRE400 ! Free DEMO How would you like to cut your applications development time in half? What if your programmers could produce RPG ILE code for reports and file manipulations in a tenth of the time it now takes them? Our program generator is easy to learn and run. If you know AS400 query, there is almost no learning curve! Rapidfire400 takes AS400 Query definitions and creates source programs ready for testing!
Re: Vulnerable SSH versions
On Tue, Nov 13, 2001 at 01:09:46PM +0100, Jørgen Hermanrud Fjeld wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Tuesday 13 November 2001 09:52, Ethan Benson wrote: > > 2.4 is also especially problematic on i386 since you have to fit it on > > all these archaic 1.22MB floppies and such. > > Hmm, I thought the 2.4 kernel was quite compact, and sometimes smaller, when > compiled than the 2.2, ( I don't know though. ) quite the opposite, its much much larger. > Having had the need of a 2.2.13 kernel for installing Debian on a machine > with HW RAID and reiserfs, I rolled my own boot disks. Although I didnt > install lots of stuff in my kernel, it isn't overly sized. > This is 'df -h' when mounting the rescue disk for 1220 floppy: > > /usr/src/boot-floppies/resc1200.bin > 1.2M 993k 192k 84% /usr/src/boot-floppies/resc > > This kernel is admittedly not very versatile. > I'll attach my config file as well > My drivers.tgz file is quite small, but then again, I have very few modules. > > I assume someone have tried making 1220 floppies with 2.4.x, finding it > difficult, and were not just assuming? yes, see -boot archives. > And will the next generation bootstrap system make it any easier to switch? > If not, what is crucial for the switch to happen? debian-installer is not anywhere near ready for prime-time and won't be used for woody, development is concentrated on boot-floppies otherwise we will never have any kind of working install system. besides the size problem the decision is not up to -boot, i386 woody will ship with 2.2.19 or 2.2.20, that is not going to change. (aph the boot-floppies maintainer has spoken on this already). -- Ethan Benson http://www.alaska.net/~erbenson/ pgp9UJ6NynyV6.pgp Description: PGP signature
Freeware for the AS400: CAT produces a catalog of files in a library.
FREEWARE: AS400 Library Catalog Software (source included.) As thanks for visiting our web site at www.rapidfire400.com, we would like you to have our CAT Freeware package. You can use CAT to gather information about the files in a library and print reports; by Date Last Used, by File Size, by File Name. We have included the source code with CAT. We used RapidFire400 to automatically generate the programs for the reports. RAPIDFIRE400 ! Free DEMO How would you like to cut your applications development time in half? What if your programmers could produce RPG ILE code for reports and file manipulations in a tenth of the time it now takes them? Our program generator is easy to learn and run. If you know AS400 query, there is almost no learning curve! Rapidfire400 takes AS400 Query definitions and creates source programs ready for testing! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Vulnerable SSH versions
On Tue, Nov 13, 2001 at 01:09:46PM +0100, Jørgen Hermanrud Fjeld wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Tuesday 13 November 2001 09:52, Ethan Benson wrote: > > 2.4 is also especially problematic on i386 since you have to fit it on > > all these archaic 1.22MB floppies and such. > > Hmm, I thought the 2.4 kernel was quite compact, and sometimes smaller, when > compiled than the 2.2, ( I don't know though. ) quite the opposite, its much much larger. > Having had the need of a 2.2.13 kernel for installing Debian on a machine > with HW RAID and reiserfs, I rolled my own boot disks. Although I didnt > install lots of stuff in my kernel, it isn't overly sized. > This is 'df -h' when mounting the rescue disk for 1220 floppy: > > /usr/src/boot-floppies/resc1200.bin > 1.2M 993k 192k 84% /usr/src/boot-floppies/resc > > This kernel is admittedly not very versatile. > I'll attach my config file as well > My drivers.tgz file is quite small, but then again, I have very few modules. > > I assume someone have tried making 1220 floppies with 2.4.x, finding it > difficult, and were not just assuming? yes, see -boot archives. > And will the next generation bootstrap system make it any easier to switch? > If not, what is crucial for the switch to happen? debian-installer is not anywhere near ready for prime-time and won't be used for woody, development is concentrated on boot-floppies otherwise we will never have any kind of working install system. besides the size problem the decision is not up to -boot, i386 woody will ship with 2.2.19 or 2.2.20, that is not going to change. (aph the boot-floppies maintainer has spoken on this already). -- Ethan Benson http://www.alaska.net/~erbenson/ msg04172/pgp0.pgp Description: PGP signature
Re: Vulnerable SSH versions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 13 November 2001 09:52, Ethan Benson wrote: > 2.4 is also especially problematic on i386 since you have to fit it on > all these archaic 1.22MB floppies and such. Hmm, I thought the 2.4 kernel was quite compact, and sometimes smaller, when compiled than the 2.2, ( I don't know though. ) Having had the need of a 2.2.13 kernel for installing Debian on a machine with HW RAID and reiserfs, I rolled my own boot disks. Although I didnt install lots of stuff in my kernel, it isn't overly sized. This is 'df -h' when mounting the rescue disk for 1220 floppy: /usr/src/boot-floppies/resc1200.bin 1.2M 993k 192k 84% /usr/src/boot-floppies/resc This kernel is admittedly not very versatile. I'll attach my config file as well My drivers.tgz file is quite small, but then again, I have very few modules. I assume someone have tried making 1220 floppies with 2.4.x, finding it difficult, and were not just assuming? And will the next generation bootstrap system make it any easier to switch? If not, what is crucial for the switch to happen? Sincerely Jørgen Hermanrud Fjeld [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjvxDYoACgkQCx+ABR2dqkKcJgCeLAsxAxETIuFvSlGCIvtCqA1G HugAniu8q0CN9GIoeWyJdNhpYgvxn6Iu =IwVG -END PGP SIGNATURE- # # Automatically generated by make menuconfig: don't edit # CONFIG_X86=y CONFIG_ISA=y # CONFIG_SBUS is not set CONFIG_UID16=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # # Loadable module support # CONFIG_MODULES=y # CONFIG_MODVERSIONS is not set CONFIG_KMOD=y # # Processor type and features # CONFIG_M386=y # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MCRUSOE is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MCYRIXIII is not set # CONFIG_X86_CMPXCHG is not set # CONFIG_X86_XADD is not set CONFIG_X86_L1_CACHE_SHIFT=4 CONFIG_RWSEM_GENERIC_SPINLOCK=y # CONFIG_RWSEM_XCHGADD_ALGORITHM is not set # CONFIG_TOSHIBA is not set # CONFIG_MICROCODE is not set # CONFIG_X86_MSR is not set # CONFIG_X86_CPUID is not set CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set # CONFIG_MATH_EMULATION is not set # CONFIG_MTRR is not set # CONFIG_SMP is not set # CONFIG_X86_UP_APIC is not set # CONFIG_X86_UP_IOAPIC is not set # # General setup # CONFIG_NET=y CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GODIRECT is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_NAMES=y # CONFIG_EISA is not set # CONFIG_MCA is not set CONFIG_HOTPLUG=y # # PCMCIA/CardBus support # # CONFIG_PCMCIA is not set CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_KCORE_ELF=y # CONFIG_KCORE_AOUT is not set CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y # CONFIG_PM is not set # CONFIG_ACPI is not set # CONFIG_APM is not set # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Parallel port support # CONFIG_PARPORT=m CONFIG_PARPORT_PC=m CONFIG_PARPORT_PC_CML1=m # CONFIG_PARPORT_SERIAL is not set # CONFIG_PARPORT_PC_FIFO is not set # CONFIG_PARPORT_PC_SUPERIO is not set # CONFIG_PARPORT_AMIGA is not set # CONFIG_PARPORT_MFC3 is not set # CONFIG_PARPORT_ATARI is not set # CONFIG_PARPORT_SUNBPP is not set # CONFIG_PARPORT_OTHER is not set CONFIG_PARPORT_1284=y # # Plug and Play configuration # CONFIG_PNP=y CONFIG_ISAPNP=y # CONFIG_PNPBIOS is not set # # Block devices # CONFIG_BLK_DEV_FD=y # CONFIG_BLK_DEV_XD is not set # CONFIG_PARIDE is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set CONFIG_BLK_DEV_DAC960=y CONFIG_BLK_DEV_LOOP=y CONFIG_BLK_DEV_NBD=m CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_SIZE=4096 CONFIG_BLK_DEV_INITRD=y # # Multi-device support (RAID and LVM) # # CONFIG_MD is not set # CONFIG_BLK_DEV_MD is not set # CONFIG_MD_LINEAR is not set # CONFIG_MD_RAID0 is not set # CONFIG_MD_RAID1 is not set # CONFIG_MD_RAID5 is not set # CONFIG_MD_MULTIPATH is not set # CONFIG_BLK_DEV_LVM is not set # # Networking options # CONFIG_PACKET=y # CONFIG_PACKET_MMAP is not set CONFIG_NETLINK=y CONFIG_RTNETLINK=y CONFIG_NETLINK_DEV=y CONFIG_NETFILTER=y # CONFIG_NETFILTER_DEBUG is not set # CONFIG_FILTER is not set CONFIG_UNIX=y CONFIG_INET=y CONFIG_IP_MULTICAST=y # CONFIG_IP_ADVANCED_ROUTER is not set # CONFIG_IP_PNP is not set # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE is not set # CONFIG_IP_MROUTE is not set # CONFIG_ARPD is not set CONFIG_INET_ECN=y CONFIG_INET_ECN_DISABLED=y CONFIG_SYN_COOKIES=y # # IP: Netfilter Configuration # CONFIG_IP_NF_CONNTRACK=y CONFIG_IP_NF_FTP=y # CONFIG_IP_NF_QUEUE is not set CONFIG_IP_NF_IPTABLES=
Re: Vulnerable SSH versions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 13 November 2001 09:52, Ethan Benson wrote: > 2.4 is also especially problematic on i386 since you have to fit it on > all these archaic 1.22MB floppies and such. Hmm, I thought the 2.4 kernel was quite compact, and sometimes smaller, when compiled than the 2.2, ( I don't know though. ) Having had the need of a 2.2.13 kernel for installing Debian on a machine with HW RAID and reiserfs, I rolled my own boot disks. Although I didnt install lots of stuff in my kernel, it isn't overly sized. This is 'df -h' when mounting the rescue disk for 1220 floppy: /usr/src/boot-floppies/resc1200.bin 1.2M 993k 192k 84% /usr/src/boot-floppies/resc This kernel is admittedly not very versatile. I'll attach my config file as well My drivers.tgz file is quite small, but then again, I have very few modules. I assume someone have tried making 1220 floppies with 2.4.x, finding it difficult, and were not just assuming? And will the next generation bootstrap system make it any easier to switch? If not, what is crucial for the switch to happen? Sincerely Jørgen Hermanrud Fjeld [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjvxDYoACgkQCx+ABR2dqkKcJgCeLAsxAxETIuFvSlGCIvtCqA1G HugAniu8q0CN9GIoeWyJdNhpYgvxn6Iu =IwVG -END PGP SIGNATURE- # # Automatically generated by make menuconfig: don't edit # CONFIG_X86=y CONFIG_ISA=y # CONFIG_SBUS is not set CONFIG_UID16=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # # Loadable module support # CONFIG_MODULES=y # CONFIG_MODVERSIONS is not set CONFIG_KMOD=y # # Processor type and features # CONFIG_M386=y # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MCRUSOE is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MCYRIXIII is not set # CONFIG_X86_CMPXCHG is not set # CONFIG_X86_XADD is not set CONFIG_X86_L1_CACHE_SHIFT=4 CONFIG_RWSEM_GENERIC_SPINLOCK=y # CONFIG_RWSEM_XCHGADD_ALGORITHM is not set # CONFIG_TOSHIBA is not set # CONFIG_MICROCODE is not set # CONFIG_X86_MSR is not set # CONFIG_X86_CPUID is not set CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set # CONFIG_MATH_EMULATION is not set # CONFIG_MTRR is not set # CONFIG_SMP is not set # CONFIG_X86_UP_APIC is not set # CONFIG_X86_UP_IOAPIC is not set # # General setup # CONFIG_NET=y CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GODIRECT is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_NAMES=y # CONFIG_EISA is not set # CONFIG_MCA is not set CONFIG_HOTPLUG=y # # PCMCIA/CardBus support # # CONFIG_PCMCIA is not set CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_KCORE_ELF=y # CONFIG_KCORE_AOUT is not set CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y # CONFIG_PM is not set # CONFIG_ACPI is not set # CONFIG_APM is not set # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Parallel port support # CONFIG_PARPORT=m CONFIG_PARPORT_PC=m CONFIG_PARPORT_PC_CML1=m # CONFIG_PARPORT_SERIAL is not set # CONFIG_PARPORT_PC_FIFO is not set # CONFIG_PARPORT_PC_SUPERIO is not set # CONFIG_PARPORT_AMIGA is not set # CONFIG_PARPORT_MFC3 is not set # CONFIG_PARPORT_ATARI is not set # CONFIG_PARPORT_SUNBPP is not set # CONFIG_PARPORT_OTHER is not set CONFIG_PARPORT_1284=y # # Plug and Play configuration # CONFIG_PNP=y CONFIG_ISAPNP=y # CONFIG_PNPBIOS is not set # # Block devices # CONFIG_BLK_DEV_FD=y # CONFIG_BLK_DEV_XD is not set # CONFIG_PARIDE is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set CONFIG_BLK_DEV_DAC960=y CONFIG_BLK_DEV_LOOP=y CONFIG_BLK_DEV_NBD=m CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_SIZE=4096 CONFIG_BLK_DEV_INITRD=y # # Multi-device support (RAID and LVM) # # CONFIG_MD is not set # CONFIG_BLK_DEV_MD is not set # CONFIG_MD_LINEAR is not set # CONFIG_MD_RAID0 is not set # CONFIG_MD_RAID1 is not set # CONFIG_MD_RAID5 is not set # CONFIG_MD_MULTIPATH is not set # CONFIG_BLK_DEV_LVM is not set # # Networking options # CONFIG_PACKET=y # CONFIG_PACKET_MMAP is not set CONFIG_NETLINK=y CONFIG_RTNETLINK=y CONFIG_NETLINK_DEV=y CONFIG_NETFILTER=y # CONFIG_NETFILTER_DEBUG is not set # CONFIG_FILTER is not set CONFIG_UNIX=y CONFIG_INET=y CONFIG_IP_MULTICAST=y # CONFIG_IP_ADVANCED_ROUTER is not set # CONFIG_IP_PNP is not set # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE is not set # CONFIG_IP_MROUTE is not set # CONFIG_ARPD is not set CONFIG_INET_ECN=y CONFIG_INET_ECN_DISABLED=y CONFIG_SYN_COOKIES=y # # IP: Netfilter Configuration # CONFIG_IP_NF_CONNTRACK=y CONFIG_IP_NF_FTP=y # CONFIG_IP_NF_QUEUE is not set CONFIG_IP_NF_IPTABL
Re: Vulnerable SSH versions
On Tue, Nov 13, 2001 at 09:02:46AM +0100, Stefan Schwandter wrote: > On Mon, Nov 12, 2001 at 04:54:04PM -0900, Ethan Benson wrote: > > > > Which makes me wonder, why ship Woody with 2.2.20 at all? Oh well, not > > > my decision. > > > because 2.4 is not stable yet. > > Hmmm... I think it will take some months before woody is released. Don't > you think 2.4 will have stabilized enough by that time? because then we have to break boot-floppies and start the long arduous process of stabelizing them all over again. 2.4 is also especially problematic on i386 since you have to fit it on all these archaic 1.22MB floppies and such. however do note that some of debian's architectures will ship with 2.4 simply because 2.2 doesn't properly support them, or 2.4 is actually more stable then 2.2 (due to the various stages porting work is/was at). for the curious here is the current rundown: ifeq "$(architecture)" "alpha" kver:= 2.2.19 endif ifeq "$(architecture)" "arm" kver:= 2.2.19 endif ifeq "$(architecture)" "i386" kver:= 2.2.19 endif ifeq "$(architecture)" "m68k" kver:= 2.2.19 endif ifeq "$(architecture)" "powerpc" kver:= 2.2.19 pcmcia_kver := 2.2.19-pmac apuskver:= 2.2.10 endif ifeq "$(architecture)" "sparc" kver:= 2.2.19 kver_sun4u := 2.4.10 endif ifeq "$(architecture)" "ia64" kver:= 2.4.9 endif ifeq "$(architecture)" "hppa" kver:= 2.4.9 endif ifeq "$(architecture)" "mips" kver:= 2.4.9 endif ifeq "$(architecture)" "mipsel" kver:= 2.4.9 endif ifeq "$(architecture)" "s390" kver:= 2.4.7 endif so if you want a 2.4 kernel by default switch to one of the above 2.4 listed architectures :P otherwise just apt-get install kernel-image-2.4.YY after install. -- Ethan Benson http://www.alaska.net/~erbenson/ pgptkDFeXMNI2.pgp Description: PGP signature
Re: Vulnerable SSH versions
On Mon, Nov 12, 2001 at 04:54:04PM -0900, Ethan Benson wrote: > > Which makes me wonder, why ship Woody with 2.2.20 at all? Oh well, not > > my decision. > because 2.4 is not stable yet. Hmmm... I think it will take some months before woody is released. Don't you think 2.4 will have stabilized enough by that time? regards, Stefan
Re: Vulnerable SSH versions
On Tue, Nov 13, 2001 at 09:02:46AM +0100, Stefan Schwandter wrote: > On Mon, Nov 12, 2001 at 04:54:04PM -0900, Ethan Benson wrote: > > > > Which makes me wonder, why ship Woody with 2.2.20 at all? Oh well, not > > > my decision. > > > because 2.4 is not stable yet. > > Hmmm... I think it will take some months before woody is released. Don't > you think 2.4 will have stabilized enough by that time? because then we have to break boot-floppies and start the long arduous process of stabelizing them all over again. 2.4 is also especially problematic on i386 since you have to fit it on all these archaic 1.22MB floppies and such. however do note that some of debian's architectures will ship with 2.4 simply because 2.2 doesn't properly support them, or 2.4 is actually more stable then 2.2 (due to the various stages porting work is/was at). for the curious here is the current rundown: ifeq "$(architecture)" "alpha" kver:= 2.2.19 endif ifeq "$(architecture)" "arm" kver:= 2.2.19 endif ifeq "$(architecture)" "i386" kver:= 2.2.19 endif ifeq "$(architecture)" "m68k" kver:= 2.2.19 endif ifeq "$(architecture)" "powerpc" kver:= 2.2.19 pcmcia_kver := 2.2.19-pmac apuskver:= 2.2.10 endif ifeq "$(architecture)" "sparc" kver:= 2.2.19 kver_sun4u := 2.4.10 endif ifeq "$(architecture)" "ia64" kver:= 2.4.9 endif ifeq "$(architecture)" "hppa" kver:= 2.4.9 endif ifeq "$(architecture)" "mips" kver:= 2.4.9 endif ifeq "$(architecture)" "mipsel" kver:= 2.4.9 endif ifeq "$(architecture)" "s390" kver:= 2.4.7 endif so if you want a 2.4 kernel by default switch to one of the above 2.4 listed architectures :P otherwise just apt-get install kernel-image-2.4.YY after install. -- Ethan Benson http://www.alaska.net/~erbenson/ msg04170/pgp0.pgp Description: PGP signature
Re: Vulnerable SSH versions
On Mon, Nov 12, 2001 at 04:54:04PM -0900, Ethan Benson wrote: > > Which makes me wonder, why ship Woody with 2.2.20 at all? Oh well, not > > my decision. > because 2.4 is not stable yet. Hmmm... I think it will take some months before woody is released. Don't you think 2.4 will have stabilized enough by that time? regards, Stefan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
