Boot scripts can't write /etc/sysconfig

Forum: HD Install
Topic: Boot scripts can't write /etc/sysconfig
started by: flogsticator

Posted by flogsticator on Dec. 09 2006,16:32

I've been told that HD debian installs are a shakey undertaking, but it would help me remaster a kiosk iso based on MyDSL. So I kept going at it.

The present is a Debian multi-user HD install on a AMD Duron/750MHz with 128MB Ram. DSL as 2nd OS on a 2nd HD. Changed grub kernel invocation - edited out 'frugal' command. Left : quiet vga=normal noacpi noapm nodma noscsi. Using non-us-english keyboard. Xvesa. Serial wheelmouse on ttyS0. As root: chgrp staff /opt/.mydsl_dir . Updated to Gnu-utils and enabled Apt. Used MyDSL to get kernel-source.

Was able to mount -o loop image.iso directory on the same day / session.

Powered off on 07/12, and rebooted today.

Upon boot, the /etc/rcS.d/ S00... and S01... scripts are having trouble altering /etc/sysconfig/... files. "Read-only file system". Same for /etc/fstab.new (cannot be created ). mtab serves a complaint that fstab doesn't have a trailing newline.

I get the impression that part of the scripts are run twice.

Can't poweroff, it stays in the tty. logoff just hangs the tty.

The boot messages are approximately as follows :

Quote

[mntent]: no final newline at end of /etc/fstab

( autoconfiguring ... )

Can't write to '/etc/sysconfig/ mouse.sound.xserver.floppy': Read-only file system.

/etc/rcS.d/S00knoppix-autoconfig: line 393: /etc/sysconfig/progress: Read-only file system. (1)

AGP bridge detected

repeat (1)

/etc/rcS.d/S00knoppix-autoconfig: line 734: cannot create temp file for here document: Read-only file system. (2)

repeat (1)

Network eth0 detected DHCP broadcast for IP (background)

/etc/rcS.d/S00knoppix-autoconfig: line 966: cannot create /etc/fstab.new: Read-only file system. (3)

AGP bridge detected (Again)

repeat (1)(2)

Network eth0 ... (Again)

repeat (3)

mv: unable to rename '/etc/fstab.new': no such file or directory.

repeat (1)

/etc/rcS.d/S00dsl-config: line 166: /etc/sysconfig/mydsl: Read-only file system.

+ 4-5 screenfulls of :
/etc/rcS.d/S00dsl-config: line 168: /etc/sysconfig/mydsl: Read-only file system.

Finally :
syslogd: could not connect to socket /dev/log: Address already in use.

Upon login as dsl ( dsl@tty1[dsl] ) :

Quote

Unable to change tty `/dev/tty1´: Read-only file system.
login[280]: unable to change tty '/dev/tty1' for user 'dsl'

Script or shell or mount write permission issue ?

Thanks for your time and patience in reading this. I hope that it might be of use.

Posted by roberts on Dec. 09 2006,17:15

This is precisely why I don't want much to do with traditional hard drive installs. A user starts to change things, i.e., trying to do a remaster, then system gets messed up.

What we don't know is what you did after the:
"Was able to mount -o loop image.iso directory on the same day / session." This would appear to introduce read-only files.

I also do not appreciate your posting the same thing three times. If you want to do a remaster, I suggest you read the remaster topic and post your questions there. We have many users who are successfully making remasters. And finally, please only one post will suffice.

Posted by flogsticator on Dec. 09 2006,17:42

Sorry about reposting. I was trying to be thorough and leave a follow-up trail. Thought it might help. Wrong idea, then. Sorry.
Ditto about still trying the HD install. A bit maniac on my part. But I wouldn't be using Linux otherwise.

Just as added info : As for the possibly offending command, I was trying to implement some of the instructions found on this page : < Kiok CD Remastering Guide >

The commands actually issued were :

Code Sample

mkdir remaster
cd remaster
mkdir image
mkdir -p source/KNOPPIX
mkdir -p master/KNOPPIX

mount -o loop dsl.iso image
(cd image; find . -size -10000k -type f -exec cp -p --parents '{}' ../master/ \;)
extract_compressed_fs image/KNOPPIX/KNOPPIX > tmp.iso

The last one didn't work (didn't expect it to, just seeing what could be done), so I unmounted everything and powered off.

Nevertheless, I've found out that it can probably be done - specially if I keep away from the HD install.

Thanks for your help. Wouldn't have gotten this far without it.