Skip to contentSkip to conversation

mdev.sh: permit serial console login and permit correct runlevel

PATCH New Denis 'Gnutoo' Carikli 4 participants 9 messages Jul 14, 2009 – Jul 18, 2009

lore
Share & tools
lore
#0 lore raw

Hi, This patch is permit the login via serial console,and to go to the correct runlevel(2345), without this patch init is blocked at the last script of runlevelS and we can never login via serial console (the patch created /dev/null and /dev/console)
I send it for review because it touch a core part and that I'm not shure how the others distro handle that. Here I used:
*wrt54.conf
*micro-base-image
*micro-uclibc

Denis

#1 lore raw

PATCH 1/1 mdev: mdev.sh: permit serial console login and correct init runlevel

create /dev/console and /dev/null in order to permit someone to login via serial console and to be able to go to others runlevel than runlevel S : for instance runlevel 2345

recipes/mdev/mdev-1.2.1/mdev.sh +8 -0
index 9744322..b4bb28c 100755
@@ -66,4 +66,12 @@ ln -sf /proc/self/fd/2 /dev/stderr
 ln -sf /proc/kcore /dev/core
 ln -sf /proc/asound/oss/sndstat /dev/sndstat
 
+if [ ! -e /dev/console ]; then
+mknod /dev/console c 5 1
+fi
+
+if [ ! -e /dev/null ]; then
+mknod /dev/null c 1 3
+fi
+
 exit 0
Signature · 1 line
1.6.0.6
author
#2 lore raw

PATCH 1/1 mdev: mdev.sh: permit serial console login and correct init runlevel

In reply to Denis 'Gnutoo' Carikli

create /dev/console and /dev/null in order to permit someone to login via serial console and to be able to go to others runlevel than runlevel S : for instance runlevel 2345

recipes/mdev/mdev-1.2.1/mdev.sh +8 -0
index 9744322..b4bb28c 100755
@@ -66,4 +66,12 @@ ln -sf /proc/self/fd/2 /dev/stderr
 ln -sf /proc/kcore /dev/core
 ln -sf /proc/asound/oss/sndstat /dev/sndstat
 
+if [ ! -e /dev/console ]; then
+mknod /dev/console c 5 1
+fi
+
+if [ ! -e /dev/null ]; then
+mknod /dev/null c 1 3
+fi
+
 exit 0
Signature · 1 line
1.6.0.6
#3 lore raw

Re: [PATCH] mdev: mdev.sh: permit serial console login and correct init runlevel

Hello,

I think you missed the new busybox packages that also provides mdev no? IMO it ought to kept in sync.

Signature · 3 lines
Otavio Salvador                  O.S. Systems
E-mail: [email protected]  http://www.ossystems.com.br
Mobile: +55 53 9981-7854         http://projetos.ossystems.com.br
author
#4 lore raw
In reply to Denis 'Gnutoo' Carikli

I'm sorry for sending twice the same patch...I thought that the patch didn't reach the mailing list...I saw the patch without [oe] in my mail client
Then only after re-sending it I had the idea of verifying on the mailing list archives...sorry

Denis.

#5 lore raw
In reply to Denis 'Gnutoo' Carikli
Quoted 8 lines · Denis 'Gnutoo' Carikli

Hi, This patch is permit the login via serial console,and to go to the correct runlevel(2345), without this patch init is blocked at the last script of runlevelS and we can never login via serial console (the patch created /dev/null and /dev/console)
I send it for review because it touch a core part and that I'm not shure how the others distro handle that. Here I used:
*wrt54.conf
*micro-base-image
*micro-uclibc

Does mdev not create certain classes of devices then? IOW, why isn't mdev -s creating these nodes?

Signature · 1 line
Tom Rini
#6 lore raw
Quoted 11 lines · Tom Rini
Quoted 8 lines · Denis 'Gnutoo' Carikli

Hi, This patch is permit the login via serial console,and to go to the correct runlevel(2345), without this patch init is blocked at the last script of runlevelS and we can never login via serial console (the patch created /dev/null and /dev/console)
I send it for review because it touch a core part and that I'm not shure how the others distro handle that. Here I used:
*wrt54.conf
*micro-base-image
*micro-uclibc

Quoted 2 lines

Does mdev not create certain classes of devices then? IOW, why isn't mdev -s creating these nodes?

To follow up to myself, the 'mdev' package should just go away really. This particular bug is because 'mdev' has an empty mdev.conf while busybox's mdev does not, and it contains console/null/etc entries.

Signature · 1 line
Tom Rini
#7 lore raw
Quoted 3 lines · Tom Rini

To follow up to myself, the 'mdev' package should just go away really. This particular bug is because 'mdev' has an empty mdev.conf while busybox's mdev does not, and it contains console/null/etc entries.

Ah yes, right. It looks like the immediate bug is that micro-base-image is setting IMAGE_DEV_MANAGER = "mdev", which is causing the bogus package to get dragged in. I guess that variable should probably just be left empty to use busybox mdev.

p.

#8 lore raw
Quoted 9 lines · Phil Blundell
Quoted 3 lines · Tom Rini

To follow up to myself, the 'mdev' package should just go away really. This particular bug is because 'mdev' has an empty mdev.conf while busybox's mdev does not, and it contains console/null/etc entries.

Ah yes, right. It looks like the immediate bug is that micro-base-image is setting IMAGE_DEV_MANAGER = "mdev", which is causing the bogus package to get dragged in. I guess that variable should probably just be left empty to use busybox mdev.

No, I think it needs to be set to busybox-mdev, as busybox and udev can coexist.

Signature · 1 line
Tom Rini