Lonnie Abelbeck wrote:
> Hi,
>
> I was looking at the [Notes] of the 0.4.3 release on sourceforge.net
>
> http://sourceforge.net/project/shownotes.php?release_id=441863&group_id=170462
>
> <http://sourceforge.net/project/shownotes.php?release_id=441863&group_id=170462>
>
> Included under "changes" is
>
> Changes:
> rc.conf.d has been created. It allows you to create sets of config
> files in /stat/etc/rc.conf.d and /mnt/rc.conf.d and automatically have
> them appended to form /etc/rc.conf upon every boot. If you have an old
> keydisk, you will need to rename rc.conf to rc.conf.d/main.conf (or
> something like it).
>
> Hmmmm, I'm confused.
>
> Lonnie
>
Lonnie,
I think we have talked about this here before, but just in case...
As if AstLinux already wasn't totally confusing :), rc.conf.d has been
created. Try to stay with me here, I'll try to explain it.
Upon startup, /etc/rc will look in /stat/etc/rc.conf.d and
/mnt/kd/rc.conf.d for files ending in ".conf". Any files that it finds
are copied to "/tmp/etc/rc.conf.d". They are then, in typical sort
order, concatenated together and saved as /tmp/etc/rc.conf, which is
then sourced by all of the other startup scripts just like rc.conf
always was.
What? Why do this?
Config file updates. Eventually, when we create new variables, we can
add them like this:
/stat/etc/rc.conf.d/astlinux-0.4.3.conf
/stat/etc/rc.conf.d/astlinux-0.4.4.conf
/stat/etc/rc.conf.d/astlinux-0.4.5.conf
/etc/rc basically does this:
cat /stat/etc/rc.conf.d/*.conf > /tmp/etc/rc.conf
That way, if we need to override a default variable from a previous
release we really can. Also, we can add variables without having to
overwrite your config file (and they are easier to find out about in a
shorter file).
Now, what if you already have an rc.conf? I suggest that you filter
out any commented lines and save it in /mnt/kd/rc.conf.d/local.conf or
something. That way, it will always override any of the astlinux*
config files when copied to /tmp/etc/rc.conf.d.
Now, here is the tricky part - what values are used from what file, and
how do you save them? Obviously, in this scenario /tmp/etc/rc.conf is
saved in RAM, and if you edit it directly your changes will not be saved
across reboots. You will most likely need to copy the variable and the
value that you want into your local.conf in order for it to be saved.
I should point out that for now, if you have /mnt/kd/rc.conf, it will
still use that like it always did. However, if you have ANY rc.conf.d
directories, your system could get really confusing really fast...
While it will work, I strongly advise against have both /mnt/kd/rc.conf
(and /stat/etc/rc.conf) AND any rc.conf.d's.
This is brand new, and I'm totally open to suggestions. What do you
think?
--
Kristian Kielhofner
_______________________________________________
Astlinux-users mailing list
[email protected]
http://lists.kriscompanies.com/mailman/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to [EMAIL
PROTECTED]
