[gentoo-user] How to config-protect /sbin/rc and /sbin/functions.sh ?

2005-11-11 Thread Jimmy Rosen
Hi, during my recent battle with updating my system I ran across an 
old problem I haven't figured out.

How to CONFIG_PROTECT /sbin/rc and /sbin/functions.sh ? Is there a 
way. Just putting them in CONFIG_PROTECT doesn't help and gentoo 
complains about them not beeing directories.

I have a work around that is ok, to softlink them from /sbin/rc.safe 
and /sbin/functions.sh.safe.


Anyone know?

Thanks
Jimmy
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] How to config-protect /sbin/rc and /sbin/functions.sh ?

2005-11-11 Thread Richard Fish
On 11/11/05, Jimmy Rosen [EMAIL PROTECTED] wrote:
 Hi, during my recent battle with updating my system I ran across an
 old problem I haven't figured out.

 How to CONFIG_PROTECT /sbin/rc and /sbin/functions.sh ? Is there a
 way. Just putting them in CONFIG_PROTECT doesn't help and gentoo
 complains about them not beeing directories.

 I have a work around that is ok, to softlink them from /sbin/rc.safe
 and /sbin/functions.sh.safe.

I think that trying to CONFIG_PROTECT these is a _very_ bad idea. 
They are part of baselayout, and pretty much go hand-in-hand with the
/etc/init.d and /lib/rcscripts scripts.  If a new version of
baselayout is merged with an old functions.sh, you risk ending up with
an essentially unbootable system.

If you don't want those modified, mask out newer versions of
baselayout in /etc/portage/package.mask.

-Richard

-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] How to config-protect /sbin/rc and /sbin/functions.sh ?

2005-11-11 Thread Jimmy Rosen
Hi,

Well, it's not that I don't want them modified by new baselayout. It's 
just that I would like to have the convenience of using etc-update to 
remind me that I need to update them manually.
I have some modifications in those files that allow me to boot a 
diskless cluster from a single regular gentoo installation.
Right now I always watch very carefully when I have to bring in a new 
baselayout since I have to keep those two scripts working. But I have 
been known to forget.
I also have modifications in a few of the critical /etc/init.d scripts 
as well, but they are caught by the CONFIG_PROTECT and I'm 
immediately reminded to update and manually merge my functionality 
changes when a new version is in.

So this is essentially just for me to get autoreminders when they need 
attention. My teflon memory is dangerous enough, and I need all the 
help I can get from automated tools and reminders.

Thanks
Jimmy


On Friday 11 November 2005 19.03, Richard Fish wrote:
 On 11/11/05, Jimmy Rosen [EMAIL PROTECTED] wrote:
  Hi, during my recent battle with updating my system I ran across
  an old problem I haven't figured out.
 
  How to CONFIG_PROTECT /sbin/rc and /sbin/functions.sh ? Is there
  a way. Just putting them in CONFIG_PROTECT doesn't help and
  gentoo complains about them not beeing directories.
 
  I have a work around that is ok, to softlink them from
  /sbin/rc.safe and /sbin/functions.sh.safe.

 I think that trying to CONFIG_PROTECT these is a _very_ bad idea.
 They are part of baselayout, and pretty much go hand-in-hand with
 the /etc/init.d and /lib/rcscripts scripts.  If a new version of
 baselayout is merged with an old functions.sh, you risk ending up
 with an essentially unbootable system.

 If you don't want those modified, mask out newer versions of
 baselayout in /etc/portage/package.mask.

 -Richard
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] How to config-protect /sbin/rc and /sbin/functions.sh ?

2005-11-11 Thread Richard Fish
On 11/11/05, Jimmy Rosen [EMAIL PROTECTED] wrote:
 Hi,

 Well, it's not that I don't want them modified by new baselayout. It's
 just that I would like to have the convenience of using etc-update to
 remind me that I need to update them manually.
 I have some modifications in those files that allow me to boot a
 diskless cluster from a single regular gentoo installation.
 Right now I always watch very carefully when I have to bring in a new
 baselayout since I have to keep those two scripts working. But I have
 been known to forget.
 I also have modifications in a few of the critical /etc/init.d scripts
 as well, but they are caught by the CONFIG_PROTECT and I'm
 immediately reminded to update and manually merge my functionality
 changes when a new version is in.

 So this is essentially just for me to get autoreminders when they need
 attention. My teflon memory is dangerous enough, and I need all the
 help I can get from automated tools and reminders.

Well, this is probably evil, but I like it anyway:

Edit /etc/portage/bashrc and add:

test /sbin/rc -nt /sbin/rc.safe  printf \n /sbin/rc needs to be
updated NOW  \n\n

Then when you update baselayout and a new /sbin/rc comes along, you
will get a notice after it is merged but before the 'clean'step runs. 
Presumably you can then diff /sbin/rc and /sbin/rc.safe to figure out
the differences.

-- 
gentoo-user@gentoo.org mailing list