[nSLUG] Re: migrating to debian sarge

Donald Teed donald.teed at gmail.com
Sun Jun 12 10:23:17 ADT 2005


It seems that getty is dying off immediately. I've checked that getty has its
requirements with ldd within the chroot environment.

Here is what Debian set up in the inittab:

1:2345:respawn:/sbin/getty 38400 tty1
2:23:respawn:/sbin/getty 38400 tty2
3:23:respawn:/sbin/getty 38400 tty3
4:23:respawn:/sbin/getty 38400 tty4
5:23:respawn:/sbin/getty 38400 tty5
6:23:respawn:/sbin/getty 38400 tty6

Seems reasonable.  The devices exist:

crw-------  1 root tty 4, 0 Jun 10 21:38 /dev/tty0
crw-------  1 root tty 4, 1 Aug 20  2003 /dev/tty1
crw-------  1 root tty 4, 2 Aug 20  2003 /dev/tty2
crw-------  1 root tty 4, 3 Aug 20  2003 /dev/tty3
crw-------  1 root tty 4, 4 Aug 20  2003 /dev/tty4
crw-------  1 root tty 4, 5 Aug 20  2003 /dev/tty5
crw-------  1 root tty 4, 6 Aug 20  2003 /dev/tty6

The kernel has vc support buillt in to it.

I made my kernel from vanilla 2.4.31, with a make oldconfig from
my previous Gentoo.  Perhaps there is some devfs problem - I was
using that in Gentoo and Debian probably doesn't support it out of
the box.  I'll try a new kernel without devfs.


On 6/12/05, Donald Teed <donald.teed at gmail.com> wrote:
> I have a server I'd like to migrate to debian from gentoo.
> The game plan is to install debian on a regular linux partition (hdi11),
> move my data and configs over to it, then recreate software raid
> partitions and move debian over to it.
> 
> The first method I tried was the Debian sarge net install CD.
> I booted from the CD.  I was installing to a fresh partition it had fdisked,
> or whatever it uses. At about 50% of installing the base layout, there
> is an error that
> says something to the effect of my kernel is out of step with
> the modules.conf, and I need to reboot "soon", but not immediately
> since my installation isn't finished.  I figure this is just a warning
> that would apply in circumstances other than the install, and try
> to proceed.  No matter what option I picked in the next few installer
> menu options, it always wanted to restart the base layout install part
> at 0%, and bombed out with the same error at around 50%.
> 
> Next up: debootstrap.  I install it and apt-get in Gentoo, and
> tell it to place sarge on /dev/hdi11.  That seems to work OK.  I chroot
> into the new debian partition and set up a few packages from apt-get
> run base-config, build my own 2.4.31 kernel from kernel.org.
> Exit chroot, add an entry in grub.conf for the debian location.
> 
> Debian boots without error, but when it arrives at the point of
> starting inits, it has errors.  This from daemon.log:
> 
> Jun 11 20:21:59 artistic lwresd[296]: starting BIND 9.2.4
> Jun 11 20:21:59 artistic lwresd[296]: using 2 CPUs
> Jun 11 20:21:59 artistic lwresd[301]: loading configuration from
> '/etc/bind/lwresd.conf'
> Jun 11 20:21:59 artistic lwresd[301]: none:0: open:
> /etc/bind/lwresd.conf: file not found
> Jun 11 20:21:59 artistic lwresd[301]: loading configuration from
> '/etc/resolv.conf'
> Jun 11 20:21:59 artistic lwresd[301]: no IPv6 interfaces found
> Jun 11 20:21:59 artistic lwresd[301]: command channel listening on 127.0.0.1#953
> Jun 11 20:21:59 artistic lwresd[301]: lwres listening on 127.0.0.1#921
> Jun 11 20:21:59 artistic lwresd[301]: running
> Jun 11 20:22:06 artistic rpc.statd[454]: Version 1.0.6 Starting
> Jun 11 20:22:06 artistic rpc.statd[454]: statd running as root. chown
> /var/lib/nfs/sm to choose different user
> Jun 11 20:23:46 artistic init: Id "1" respawning too fast: disabled
> for 5 minutes
> Jun 11 20:23:46 artistic init: Id "2" respawning too fast: disabled
> for 5 minutes
> Jun 11 20:23:46 artistic init: Id "3" respawning too fast: disabled
> for 5 minutes
> Jun 11 20:23:46 artistic init: Id "5" respawning too fast: disabled
> for 5 minutes
> Jun 11 20:23:46 artistic init: Id "6" respawning too fast: disabled
> for 5 minutes
> Jun 11 20:23:46 artistic init: Id "4" respawning too fast: disabled
> for 5 minutes
> Jun 11 20:23:46 artistic init: no more processes left in this runlevel
> 
> dmesg is error free.
> 
> Googling for the errors on init doesn't show a solution or typical
> cause for this.
> I did see one other debian user that had an existing grub set up on his
> MBR (as I did) and ran into this.  But I can't see how it could effect it.
> We are way beyond the boot loader when this is going berserk.
>

!DSPAM:42ac3744323276887420965!




More information about the nSLUG mailing list