Changes to contrib bootscripts
DJ, You need to change the version/release date in general.ent and lfs-bootscripts-version in packages.ent to actually publish the bootscript changes. Do you wnat me to do it? -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: Changes to contrib bootscripts
On 05/14/2011 02:47 PM, Bruce Dubbs wrote: DJ, You need to change the version/release date in general.ent and lfs-bootscripts-version in packages.ent to actually publish the bootscript changes. Do you wnat me to do it? -- Bruce No, I'm still working on them. Besides, they are in contrib and are no longer compatible with the instructions in the book. I have just about completed the necessary changes. I made a mistake when I reread the original thread and put the interface configuration files in /etc/network-devices instead of /etc/network. The big changes are coming in a few moments, after I go back and fix the placement of the network config files. There is really no need for a change in the book until we are ready to switch (which requires some other changes to the book anyway). I also plan to move them out of the bootscripts folder before they go into the book and move the old to bootscripts-old afterward. I'll post a patch for the necessary book, udev-config, and rendering changes to the list at that time. -- DJ Lucas -- This message has been scanned for viruses and dangerous content, and is believed to be clean. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: Changes to contrib bootscripts
DJ Lucas wrote: On 05/14/2011 02:47 PM, Bruce Dubbs wrote: DJ, You need to change the version/release date in general.ent and lfs-bootscripts-version in packages.ent to actually publish the bootscript changes. Do you wnat me to do it? -- Bruce No, I'm still working on them. Besides, they are in contrib and are no longer compatible with the instructions in the book. I have just about completed the necessary changes. I made a mistake when I reread the original thread and put the interface configuration files in /etc/network-devices instead of /etc/network. The big changes are coming in a few moments, after I go back and fix the placement of the network config files. There is really no need for a change in the book until we are ready to switch (which requires some other changes to the book anyway). I also plan to move them out of the bootscripts folder before they go into the book and move the old to bootscripts-old afterward. I'll post a patch for the necessary book, udev-config, and rendering changes to the list at that time. OK, sounds good. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Summary: Using the LSB Bootscripts
Everything is covered per this conversation in SVN with the exception of
accounting for missing /run in LightCube OS, but I think it was decided
that it would be added. Also no ip flush (I forgot, but will get it in a
day or two) on down interface, and dhcp calls not accounted for. Quite a
few changes are required for the book to work with them now including:
* rendering of scripts in the book, path and name changes
* tarball creation with book render job
* inittab is installed by the bootscripts package (this could be changed
if desired)
* initd-tools page needs to be added
* the path for the setclock script in 55-lfs.rules needs to be changed
* the network interface configuration file should be placed in
/etc/network/ifconfig.int/
* setting clock parameters for the setclock script is done in /etc/rc.site
* setting the hostname is now done in /etc/rc.site
* add mention of turning off bootlogging and interactive prompt
For LightCube OS (or anyone else that would like to customize the
scripts for their release), hopefully all that is needed is a similar
patch to the one below, in addition to the one adding additional
services and scripts (which will need to be rediffed for the new file
layout),
diff -Naur lsb-bootscripts-20110514/etc/default/rc.site
lsb-bootscripts-20110514-LCOS/etc/default/rc.site
--- lsb-bootscripts-20110514/etc/default/rc.site2011-05-14
16:00:31.0 -0500
+++ lsb-bootscripts-20110514-LCOS/etc/default/rc.site2011-05-14
16:30:27.0 -0500
@@ -9,7 +9,7 @@
BOOTLOG_ENAB=yes
# Hostname
-HOSTNAME=lfs
+HOSTNAME=lightcube
# System time variables
UTC=1
@@ -17,12 +17,12 @@
# Manual input is not appropriate on remote systems. Define what
happens when
# an error is encountered that interupts the boot/shutdown proceess
-FAILURE_ACTION=read ENTER
+FAILURE_ACTION='echo '
# Distro Information
-DISTRO=Linux From Scratch # The distro name
-DISTRO_CONTACT=lfs-dev@linuxfromscratch.org # Bug report address
-DISTRO_MINI=lfs # Short name used in filenames for distro config
+DISTRO=LightCube OS
+DISTRO_CONTACT=http://dev.lightcube.us/projects/lightcubeos/issues;
+DISTRO_MINI=lightcube
# Define custom colors used in messages printed to the screen
BRACKET=\\033[1;34m # Blue
@@ -45,9 +45,9 @@
export PREFIX_SUCCESS PREFIX_WARNING PREFIX_FAILURE
# Interactive startup
-iprompt=yes # Wether to display the interactive boot promp
+iprompt=no # Wether to display the interactive boot promp
itime=2 # The ammount of time (in seconds) to display the prompt
-dlen=29 # The total length of the distro welcome string
+dlen=23 # The total length of the distro welcome string
ilen=38 # The total length of the interactive message
welcome_message=Welcome to ${INFO}${DISTRO}${NORMAL}
i_message=Press '${FAILURE}I${NORMAL}' to enter interactive startup
diff -Naur lsb-bootscripts-20110514/Makefile
lsb-bootscripts-20110514-LCOS/Makefile
--- lsb-bootscripts-20110514/Makefile2011-05-14 16:00:31.0 -0500
+++ lsb-bootscripts-20110514-LCOS/Makefile2011-05-14
16:26:42.0 -0500
@@ -25,7 +25,7 @@
install: create-dirs
install -m ${MODE} etc/init.d/checkfs ${EXTDIR}/init.d/
install -m ${MODE} etc/init.d/cleanfs ${EXTDIR}/init.d/
-install -m ${CONFMODE} etc/init.d/lfs-functions ${EXTDIR}/init.d/
+install -m ${CONFMODE} etc/init.d/lfs-functions
${EXTDIR}/init.d/lightcube-functions
install -m ${MODE} etc/init.d/halt ${EXTDIR}/init.d/
install -m ${MODE} etc/init.d/console ${EXTDIR}/init.d/
install -m ${MODE} etc/init.d/localnet ${EXTDIR}/init.d/
Think that covers it all. Time for some testing.
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Re: Changes to contrib bootscripts
On 05/14/2011 04:09 PM, Bruce Dubbs wrote: DJ Lucas wrote: On 05/14/2011 02:47 PM, Bruce Dubbs wrote: DJ, You need to change the version/release date in general.ent and lfs-bootscripts-version in packages.ent to actually publish the bootscript changes. Do you wnat me to do it? -- Bruce No, I'm still working on them. Besides, they are in contrib and are no longer compatible with the instructions in the book. I have just about completed the necessary changes. I made a mistake when I reread the original thread and put the interface configuration files in /etc/network-devices instead of /etc/network. The big changes are coming in a few moments, after I go back and fix the placement of the network config files. There is really no need for a change in the book until we are ready to switch (which requires some other changes to the book anyway). I also plan to move them out of the bootscripts folder before they go into the book and move the old to bootscripts-old afterward. I'll post a patch for the necessary book, udev-config, and rendering changes to the list at that time. OK, sounds good. -- Bruce Attached patch is pretty invasive, 33 KB uncompressed. :-) I wasn't sure whether to leave inittab in the book where it is currently, but I am thinking from a packaging POV that it should remain as is and be removed from the bootscripts tarball now. It was required in the tarball previously because of the path changes. -- DJ Lucas -- This message has been scanned for viruses and dangerous content, and is believed to be clean. LSB.diff.xz Description: Binary data -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: Summary: Using the LSB Bootscripts
On 05/14/2011 04:37 PM, DJ Lucas wrote: Everything is covered per this conversation in SVN with the exception of accounting for missing /run in LightCube OS, but I think it was decided that it would be added. Also no ip flush (I forgot, but will get it in a day or two) on down interface, and dhcp calls not accounted for. I'll need to setup both DHCP clients to test functionality for this, which is why I didn't just do it tonight. The problem I want to avoid is if we do a flush, but the client daemon is still running, come expiration, the client daemon might try to reconfigure the device...even if it means adding dhcp logic in the lfs scripts (or replacing them in BLFS). Also, is anyone still using RP for PPPoE, alos simple ppp, that is willing to test? I unfortunately no longer have a ?DSL circuit to test with so I'll need some help from somebody who does. I would think if the link is set down the client daemons for the dhcp clients would exit, but would ppp attempt to reconnect? I'm also thinking that the added functionality for ifdown can be done in a modular way in /lib/network-services so that it can be divvied up for each who needs it. -- DJ Lucas -- This message has been scanned for viruses and dangerous content, and is believed to be clean. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: Summary: Using the LSB Bootscripts
On May 14, 2011, at 11:36 PM, DJ Lucas wrote: I'll need to setup both DHCP clients to test functionality for this, which is why I didn't just do it tonight. The problem I want to avoid is if we do a flush, but the client daemon is still running, come expiration, the client daemon might try to reconfigure the device...even if it means adding dhcp logic in the lfs scripts (or replacing them in BLFS). Could we just do this in ifdown: if [ -x /lib/network-services/dhcp ]; then /lib/network-services/dhcp $interface down fi and assume that whatever DHCP client is installed (if any) provides a script appropriate to handle the interface shutdown? Zach smime.p7s Description: S/MIME cryptographic signature -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
