--- configs/syslinux-iso/overlay/etc/inittab | 45 ++++++++++++++++++++++++ configs/syslinux-iso/overlay/usr/bin/autologin | 2 + 2 files changed, 47 insertions(+), 0 deletions(-) create mode 100644 configs/syslinux-iso/overlay/etc/inittab create mode 100755 configs/syslinux-iso/overlay/usr/bin/autologin
diff --git a/configs/syslinux-iso/overlay/etc/inittab b/configs/syslinux-iso/overlay/etc/inittab new file mode 100644 index 0000000..aff6d72 --- /dev/null +++ b/configs/syslinux-iso/overlay/etc/inittab @@ -0,0 +1,45 @@ +# +# /etc/inittab +# + +# Runlevels: +# 0 Halt +# 1(S) Single-user +# 2 Not used +# 3 Multi-user +# 4 Not used +# 5 X11 +# 6 Reboot + +## Only one of the following two lines can be uncommented! +# Boot to console +id:3:initdefault: +# Boot to X11 +#id:5:initdefault: + +rc::sysinit:/etc/rc.sysinit +rs:S1:wait:/etc/rc.single +rm:2345:wait:/etc/rc.multi +rh:06:wait:/etc/rc.shutdown +su:S:wait:/sbin/sulogin -p + +# -8 options fixes umlauts problem on login +c1:2345:respawn:/sbin/agetty -n -l /usr/bin/autologin -8 38400 tty1 linux +c2:2345:respawn:/sbin/agetty -8 38400 tty2 linux +c3:2345:respawn:/sbin/agetty -8 38400 tty3 linux +c4:2345:respawn:/sbin/agetty -8 38400 tty4 linux +c5:2345:respawn:/sbin/agetty -8 38400 tty5 linux +c6:2345:respawn:/sbin/agetty -8 38400 tty6 linux + +# Hypervisor Virtual Console for Xen and KVM +#h0:2345:respawn:/sbin/agetty -8 38400 hvc0 linux + +ca::ctrlaltdel:/sbin/shutdown -t3 -r now + +# Example lines for starting a login manager +x:5:respawn:/usr/bin/xdm -nodaemon +#x:5:respawn:/usr/sbin/gdm -nodaemon +#x:5:respawn:/usr/bin/kdm -nodaemon +#x:5:respawn:/usr/bin/slim >/dev/null 2>&1 + +# End of file diff --git a/configs/syslinux-iso/overlay/usr/bin/autologin b/configs/syslinux-iso/overlay/usr/bin/autologin new file mode 100755 index 0000000..c124f9e --- /dev/null +++ b/configs/syslinux-iso/overlay/usr/bin/autologin @@ -0,0 +1,2 @@ +#!/bin/bash +/bin/login -f root
On Tue, 01 Mar 2011 17:48:05 +0100 Charles Vejnar ce@vejnar.org wrote:
configs/syslinux-iso/overlay/etc/inittab | 45 ++++++++++++++++++++++++ configs/syslinux-iso/overlay/usr/bin/autologin | 2 + 2 files changed, 47 insertions(+), 0 deletions(-) create mode 100644 configs/syslinux-iso/overlay/etc/inittab create mode 100755 configs/syslinux-iso/overlay/usr/bin/autologin
diff --git a/configs/syslinux-iso/overlay/etc/inittab b/configs/syslinux-iso/overlay/etc/inittab new file mode 100644 index 0000000..aff6d72 --- /dev/null +++ b/configs/syslinux-iso/overlay/etc/inittab @@ -0,0 +1,45 @@ +# +# /etc/inittab +#
+# Runlevels: +# 0 Halt +# 1(S) Single-user +# 2 Not used +# 3 Multi-user +# 4 Not used +# 5 X11 +# 6 Reboot
+## Only one of the following two lines can be uncommented! +# Boot to console +id:3:initdefault: +# Boot to X11 +#id:5:initdefault:
+rc::sysinit:/etc/rc.sysinit +rs:S1:wait:/etc/rc.single +rm:2345:wait:/etc/rc.multi +rh:06:wait:/etc/rc.shutdown +su:S:wait:/sbin/sulogin -p
+# -8 options fixes umlauts problem on login +c1:2345:respawn:/sbin/agetty -n -l /usr/bin/autologin -8 38400 tty1 linux +c2:2345:respawn:/sbin/agetty -8 38400 tty2 linux +c3:2345:respawn:/sbin/agetty -8 38400 tty3 linux +c4:2345:respawn:/sbin/agetty -8 38400 tty4 linux +c5:2345:respawn:/sbin/agetty -8 38400 tty5 linux +c6:2345:respawn:/sbin/agetty -8 38400 tty6 linux
+# Hypervisor Virtual Console for Xen and KVM +#h0:2345:respawn:/sbin/agetty -8 38400 hvc0 linux
+ca::ctrlaltdel:/sbin/shutdown -t3 -r now
+# Example lines for starting a login manager +x:5:respawn:/usr/bin/xdm -nodaemon +#x:5:respawn:/usr/sbin/gdm -nodaemon +#x:5:respawn:/usr/bin/kdm -nodaemon +#x:5:respawn:/usr/bin/slim >/dev/null 2>&1
+# End of file diff --git a/configs/syslinux-iso/overlay/usr/bin/autologin b/configs/syslinux-iso/overlay/usr/bin/autologin new file mode 100755 index 0000000..c124f9e --- /dev/null +++ b/configs/syslinux-iso/overlay/usr/bin/autologin @@ -0,0 +1,2 @@ +#!/bin/bash +/bin/login -f root
I'm all in favor of autologin as root on tty1 (though we probably should put something like "For your convenience, we automatically logged you as root on tty1" in the MOTD) Can someone who's into archiso take care of this? thanks,
Dieter
Hi,
I proposed this patch more than 2 weeks ago. It's essential to achieve automatic install (look at my post about Trapezium).
I don't known how it is suppose to work: who is in charge to accept patches to archiso ? Is there any problem with this patch ?
Thanks
Charles
On Thu, 17 Mar 2011 16:35:35 +0100 Charles Vejnar ce@vejnar.org wrote:
Hi,
I proposed this patch more than 2 weeks ago. It's essential to achieve automatic install (look at my post about Trapezium).
I don't known how it is suppose to work: who is in charge to accept patches to archiso ? Is there any problem with this patch ?
Thanks
Charles
Aaron is the maintainer, but he is inactive. Gerhard is inactive. Since I'm the only other releng person, some people expect me to do it, even though I don't like being involved in archiso and I already spend a lot of time on all other releng tasks (aif, image building, image testing, releasing, ...) Gerardo knows archiso and has commit access to it, but he also has little time and he never made any commitment to us in any way (he is just a community member). Thomas (and a few other devs) know archiso and has commit access, but he also has more then enough Arch stuff on his plate.
We should probably have put a position for archiso maintainer on http://www.archlinux.org/news/contributors-wanted/
Anyway, if you complain enough on this list, someone will eventually step up and do it.
In the meanwhile, I'll bring up the issue internally.
Dieter
Am 17.03.2011 16:50, schrieb Dieter Plaetinck:
Gerhard is inactive. Since I'm the only other releng person, some people expect me to do it, even though I don't like being involved in archiso and I already spend a lot of time on all other releng tasks (aif, image building, image testing, releasing, ...) Gerardo knows archiso and has commit access to it, but he also has little time and he never made any commitment to us in any way (he is just a community member).
Gerardo has done some work in the past, but not in the last 3 months.
This is worse than I thought: I saw Gerardo reply to some patch sent, but he never commited it. I even sent him an email if he could finish some cool work that I started, but he never got back to me. I assumed he was semi-active, which apparently is false.
(The work I started was about making a self-contained image in the /arch/ directory on the ISO. This is partially done already, but I recently succeeded in moving /syslinux/ into /arch/ and only leave behind a tiny /boot/ directory that would chdir() to /arch/boot/syslinux when loading. This would further simplify installing onto an existing vfat USB drive, as you only need to 1) copy the whole /arch folder 2) extlinux --install /mnt/arch/boot/syslinux 3) adjust the archisolabel in the syslinux configuration files)
Thomas (and a few other devs) know archiso and has commit access, but he also has more then enough Arch stuff on his plate.
Hell, and I can't even get that done.
If someone can collect the pending patches from this list (and maybe Gerardo's github) for me, I can check and apply them. But I guess we desperately need a maintainer for archiso. It is a task with not a lot to do, but still needs to be done.
On 03/17/2011 01:00 PM, Thomas Bächler wrote:
Am 17.03.2011 16:50, schrieb Dieter Plaetinck:
Gerhard is inactive. Since I'm the only other releng person, some people expect me to do it, even though I don't like being involved in archiso and I already spend a lot of time on all other releng tasks (aif, image building, image testing, releasing, ...) Gerardo knows archiso and has commit access to it, but he also has little time and he never made any commitment to us in any way (he is just a community member).
Gerardo has done some work in the past, but not in the last 3 months.
This is worse than I thought: I saw Gerardo reply to some patch sent, but he never commited it. I even sent him an email if he could finish some cool work that I started, but he never got back to me. I assumed he was semi-active, which apparently is false.
(The work I started was about making a self-contained image in the /arch/ directory on the ISO. This is partially done already, but I recently succeeded in moving /syslinux/ into /arch/ and only leave behind a tiny /boot/ directory that would chdir() to /arch/boot/syslinux when loading. This would further simplify installing onto an existing vfat USB drive, as you only need to
- copy the whole /arch folder
- extlinux --install /mnt/arch/boot/syslinux
- adjust the archisolabel in the syslinux configuration files)
Thomas (and a few other devs) know archiso and has commit access, but he also has more then enough Arch stuff on his plate.
Hell, and I can't even get that done.
If someone can collect the pending patches from this list (and maybe Gerardo's github) for me, I can check and apply them. But I guess we desperately need a maintainer for archiso. It is a task with not a lot to do, but still needs to be done.
Hello,
First, sorry for "no response".
I can take this weekend to review all pending archiso patches.
I think that there are at least three patches:
1) Thomas: syslinux/arch directory structure. 2) Charles: autologin on tty1 3) Simo: serial port support.
Please let me know if there are more. Please resend to ML and append in the tittle [archiso].
There are minor issues (can be considered as cosmetic) with aufs2 and util-linux-2.19 that I want to report to upstream.
PS: I will change compression from gzip -> xz by default when 2.6.38 hits [core].
Am 18.03.2011 22:09, schrieb Gerardo Exequiel Pozzi:
First, sorry for "no response".
No worries, I am the last one who can complain here.
The real question is: Can you and will you keep maintaining archiso, or does your time not permit it?
We should have someone who actively maintains it. In the past you were that guy, but are you still that guy? Answering that question is a lot about being honest to yourself (I learned that the hard way *sigh*).
On 03/18/2011 09:35 PM, Thomas Bächler wrote:
Am 18.03.2011 22:09, schrieb Gerardo Exequiel Pozzi:
First, sorry for "no response".
No worries, I am the last one who can complain here.
The real question is: Can you and will you keep maintaining archiso, or does your time not permit it?
We should have someone who actively maintains it. In the past you were that guy, but are you still that guy? Answering that question is a lot about being honest to yourself (I learned that the hard way *sigh*).
Hello,
No, currently do not have time to take on this task. Anyway, I wish to retain access to commit access. While I have some spare time, I could not perform many tests over and over again as before.
PS: A similar situation is in FS, I am no longer "official bug wrangler, " but every so often, I usually go in and assign some tickets, since I still have those privileges.
Good Luck!
Le 18/03/2011 22:09, Gerardo Exequiel Pozzi a écrit :
On 03/17/2011 01:00 PM, Thomas Bächler wrote:
Am 17.03.2011 16:50, schrieb Dieter Plaetinck:
Gerhard is inactive. Since I'm the only other releng person, some people expect me to do it, even though I don't like being involved in archiso and I already spend a lot of time on all other releng tasks (aif, image building, image testing, releasing, ...) Gerardo knows archiso and has commit access to it, but he also has little time and he never made any commitment to us in any way (he is just a community member).
Gerardo has done some work in the past, but not in the last 3 months.
This is worse than I thought: I saw Gerardo reply to some patch sent, but he never commited it. I even sent him an email if he could finish some cool work that I started, but he never got back to me. I assumed he was semi-active, which apparently is false.
(The work I started was about making a self-contained image in the /arch/ directory on the ISO. This is partially done already, but I recently succeeded in moving /syslinux/ into /arch/ and only leave behind a tiny /boot/ directory that would chdir() to /arch/boot/syslinux when loading. This would further simplify installing onto an existing vfat USB drive, as you only need to
- copy the whole /arch folder
- extlinux --install /mnt/arch/boot/syslinux
- adjust the archisolabel in the syslinux configuration files)
Thomas (and a few other devs) know archiso and has commit access, but he also has more then enough Arch stuff on his plate.
Hell, and I can't even get that done.
If someone can collect the pending patches from this list (and maybe Gerardo's github) for me, I can check and apply them. But I guess we desperately need a maintainer for archiso. It is a task with not a lot to do, but still needs to be done.
Hello,
First, sorry for "no response".
I can take this weekend to review all pending archiso patches.
I think that there are at least three patches:
- Thomas: syslinux/arch directory structure.
- Charles: autologin on tty1
- Simo: serial port support.
Please let me know if there are more. Please resend to ML and append in the tittle [archiso].
There are minor issues (can be considered as cosmetic) with aufs2 and util-linux-2.19 that I want to report to upstream.
PS: I will change compression from gzip -> xz by default when 2.6.38 hits [core].
Hi,
I also have this one:
Allow to execute a script at boot specified with the kernel boot parameters
http://mailman.archlinux.org/pipermail/arch-releng/2011-March/001537.html
Thanks
Charles
On 03/17/2011 01:00 PM, Thomas Bächler wrote:
Am 17.03.2011 16:50, schrieb Dieter Plaetinck:
Gerhard is inactive. Since I'm the only other releng person, some people expect me to do it, even though I don't like being involved in archiso and I already spend a lot of time on all other releng tasks (aif, image building, image testing, releasing, ...) Gerardo knows archiso and has commit access to it, but he also has little time and he never made any commitment to us in any way (he is just a community member).
Gerardo has done some work in the past, but not in the last 3 months.
This is worse than I thought: I saw Gerardo reply to some patch sent, but he never commited it. I even sent him an email if he could finish some cool work that I started, but he never got back to me. I assumed he was semi-active, which apparently is false.
(The work I started was about making a self-contained image in the /arch/ directory on the ISO. This is partially done already, but I recently succeeded in moving /syslinux/ into /arch/ and only leave behind a tiny /boot/ directory that would chdir() to /arch/boot/syslinux when loading. This would further simplify installing onto an existing vfat USB drive, as you only need to
- copy the whole /arch folder
- extlinux --install /mnt/arch/boot/syslinux
- adjust the archisolabel in the syslinux configuration files)
Thomas (and a few other devs) know archiso and has commit access, but he also has more then enough Arch stuff on his plate.
Hell, and I can't even get that done.
If someone can collect the pending patches from this list (and maybe Gerardo's github) for me, I can check and apply them. But I guess we desperately need a maintainer for archiso. It is a task with not a lot to do, but still needs to be done.
Hello,
First, sorry for "no response".
I can take this weekend to review all pending archiso patches.
I think that there are at least three patches:
1) Thomas: syslinux/arch directory structure. 2) Charles: autologin on tty1 3) Simo: serial port support.
Please let me know if there are more. Please resend to ML and append in the tittle [archiso].
There are minor issues (can be considered as cosmetic) with aufs2 and util-linux-2.19 that I want to report to upstream.
PS: I will change compression from gzip -> xz by default when 2.6.38 hits [core].
On 03/01/2011 01:48 PM, Charles Vejnar wrote:
configs/syslinux-iso/overlay/etc/inittab | 45 ++++++++++++++++++++++++ configs/syslinux-iso/overlay/usr/bin/autologin | 2 + 2 files changed, 47 insertions(+), 0 deletions(-)
Pushed to master with one fix.
Added missing agetty ttyS0 in the patch. (Gerardo)
arch-releng@lists.archlinux.org