Hi All,
I've been trying to put together a one off CentOS 4 based distro, and I ran into some trouble. First off just so you know we've been doing this with CentOS 3 and with RedHat 9 before that, so the inexperience is only with the delta between CentOS 3 and CentOS 4 (and RHEL 3 and RHEL 4 by extension).
Anyway, the problem is that for some reason /dev/console is not getting created. We get completely through the installation, in what looks like a successful manner, but when we reboot at the point init would come up with see nothing at all, and there it sits. I went through many contortions including including using bash as init and then starting init manually with strace turned on. This all lead to the conclusion that for some reason init was not getting a console. I happened to look in the dev directory between a normal minimal install of CentOS 4 and our "minimal install" and noticed there was no /dev/console. I manually added this and now the system boots fine.
For now I've added the creation of /dev/console to the end of the kickstart's %post, which works, but does anyone have any ideas why its not being created?
Thanks...james
You should be enabling sysfs and friends
2006/3/15, James Olin Oden james.oden@gmail.com:
Hi All,
I've been trying to put together a one off CentOS 4 based distro, and I ran into some trouble. First off just so you know we've been doing this with CentOS 3 and with RedHat 9 before that, so the inexperience is only with the delta between CentOS 3 and CentOS 4 (and RHEL 3 and RHEL 4 by extension).
Anyway, the problem is that for some reason /dev/console is not getting created. We get completely through the installation, in what looks like a successful manner, but when we reboot at the point init would come up with see nothing at all, and there it sits. I went through many contortions including including using bash as init and then starting init manually with strace turned on. This all lead to the conclusion that for some reason init was not getting a console. I happened to look in the dev directory between a normal minimal install of CentOS 4 and our "minimal install" and noticed there was no /dev/console. I manually added this and now the system boots fine.
For now I've added the creation of /dev/console to the end of the kickstart's %post, which works, but does anyone have any ideas why its not being created?
Thanks...james _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Eduardo Grosclaude Universidad Nacional del Comahue Neuquen, Argentina
On 3/15/06, Eduardo Grosclaude eduardo.grosclaude@gmail.com wrote:
You should be enabling sysfs and friends
Hmmm...Why wouldn't anaconda just do that? I haven't done anything to tell it not to, that I know of. I'm reading up on sysfs and udev as I type this, but when I do a minimal install, I don't ask for anything special and things just work. When I run my kickstart file with a hand selected set of packages (which very closely mimick the minimal install (depsolvers are great)), I get a different behavior.
Cheers...james
On 3/15/06, James Olin Oden james.oden@gmail.com wrote:
On 3/15/06, Eduardo Grosclaude eduardo.grosclaude@gmail.com wrote:
You should be enabling sysfs and friends
Hmmm...Why wouldn't anaconda just do that? I haven't done anything to tell it not to, that I know of. I'm reading up on sysfs and udev as I type this, but when I do a minimal install, I don't ask for anything special and things just work. When I run my kickstart file with a hand selected set of packages (which very closely mimick the minimal install (depsolvers are great)), I get a different behavior.
OK, I've done some more research on my own, and it would appear that a non-udev /dev/console and /dev/null must exist before udev is started, because udev is started in "user" land (thus u-dev), and thus before init starts. So init needs these device files to exist a priori.
The question that still remains is why are they not showing up with my custom package set? Who is repsonsible for creating the a priori /dev/console that init uses, and what would prevent that from occuring?
Anyone have any clues they can throw my way?
Thanks...james
Cheers...james
One other thing, I am doing a serial install. Thanks...james
On 3/15/06, James Olin Oden james.oden@gmail.com wrote:
On 3/15/06, James Olin Oden james.oden@gmail.com wrote:
On 3/15/06, Eduardo Grosclaude eduardo.grosclaude@gmail.com wrote:
You should be enabling sysfs and friends
Hmmm...Why wouldn't anaconda just do that? I haven't done anything to tell it not to, that I know of. I'm reading up on sysfs and udev as I type this, but when I do a minimal install, I don't ask for anything special and things just work. When I run my kickstart file with a hand selected set of packages (which very closely mimick the minimal install (depsolvers are great)), I get a different behavior.
OK, I've done some more research on my own, and it would appear that a non-udev /dev/console and /dev/null must exist before udev is started, because udev is started in "user" land (thus u-dev), and thus before init starts. So init needs these device files to exist a priori.
The question that still remains is why are they not showing up with my custom package set? Who is repsonsible for creating the a priori /dev/console that init uses, and what would prevent that from occuring?
Anyone have any clues they can throw my way?
Thanks...james
Cheers...james
On 15/03/06, James Olin Oden james.oden@gmail.com wrote:
OK, I've done some more research on my own, and it would appear that a non-udev /dev/console and /dev/null must exist before udev is started, because udev is started in "user" land (thus u-dev), and thus before init starts. So init needs these device files to exist a priori.
The question that still remains is why are they not showing up with my custom package set? Who is repsonsible for creating the a priori /dev/console that init uses, and what would prevent that from occuring?
What packages are installed/removed by your minimal Kickstart? Might be useful to sort and diff that list against a default, unmolested minimal install.
Will.
On 15/03/06, Will McDonald wmcdonald@gmail.com wrote:
On 15/03/06, James Olin Oden james.oden@gmail.com wrote:
OK, I've done some more research on my own, and it would appear that a non-udev /dev/console and /dev/null must exist before udev is started, because udev is started in "user" land (thus u-dev), and thus before init starts. So init needs these device files to exist a priori.
The question that still remains is why are they not showing up with my custom package set? Who is repsonsible for creating the a priori /dev/console that init uses, and what would prevent that from occuring?
What packages are installed/removed by your minimal Kickstart? Might be useful to sort and diff that list against a default, unmolested minimal install.
Further checking, there's a mknod /dev/console called in initrd.
[root@stella tmp]# cd /tmp/; mkdir initrd; cp /boot/initrd-`uname -r`.img /tmp/initrd/initrd.gz; gunzip /tmp/initrd/initrd.gz; cd /tmp/initrd; cpio -cid -I /tmp/initrd/initrd; grep /dev/console /tmp/initrd/init 4114 blocks mknod /dev/console c 5 1
Will.
What packages are installed/removed by your minimal Kickstart? Might be useful to sort and diff that list against a default, unmolested minimal install.
Its exactly the same except for these:
rpmdb-CentOS specspo bluez-hcidump finger anacron fbset rdist setarch ntsysv statserial krb5-workstation irda-utils nano python-elementtree rhnlib nscd python-sqlite xmlsec1 apmd dhcpv6_client isdn4k-utils nss_ldap iptstate pcmcia-cs up2date comps bluez-libs lha bluez-bluefw diskdumputils pam_smb rdate rsh wireless-tools jwhois OpenIPMI pyOpenSSL python-urlgrabber jpackage-utils xmlsec1-openssl pam_krb5 acpid bluez-utils NetworkManager system-config-network-tui yum
Thanks...james
Will. _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Maybe you need to insure there's an /initrd empty directory as a mounting point for initrd?
2006/3/15, James Olin Oden james.oden@gmail.com:
What packages are installed/removed by your minimal Kickstart? Might be useful to sort and diff that list against a default, unmolested minimal install.
Its exactly the same except for these:
rpmdb-CentOS specspo bluez-hcidump finger anacron fbset rdist setarch ntsysv statserial krb5-workstation irda-utils nano python-elementtree rhnlib nscd python-sqlite xmlsec1 apmd dhcpv6_client isdn4k-utils nss_ldap iptstate pcmcia-cs up2date comps bluez-libs lha bluez-bluefw diskdumputils pam_smb rdate rsh wireless-tools jwhois OpenIPMI pyOpenSSL python-urlgrabber jpackage-utils xmlsec1-openssl pam_krb5 acpid bluez-utils NetworkManager system-config-network-tui yum
Thanks...james
Will. _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Eduardo Grosclaude Universidad Nacional del Comahue Neuquen, Argentina
-
Eduardo Grosclaude -
James Olin Oden -
Will McDonald