On Saturday 21 July 2007, Roy Marples wrote: > On Sat, 2007-07-21 at 11:48 -0700, Josh Saddler wrote: > >From our perspective, /etc/conf.d/* is quite well documented, so GDP > > could easily diff the files to see what has changed. > > > Of equal concern to me, however are a few issues: > > > > 1) How will stabilization work? Is it a forced upgrade from stable 1.x > > to 2.x, or can it be slotted? > > It cannot be slotted in any way or form. > Also, the daemon state data is non transferable as the format has > changed in baselayout-2. This is the data that records how a daemon was > started by s-s-d so we can check if it's running or not. However, most > end users won't be concerned by this. > > I've tested the ebuilds for upgrading and downgrading quite extensively, > with the following notes. > baselayout-1 *requires* bash. As such /bin/sh should point to bash > before downgrading. > If the /etc/init.d files are not immediately updated by etc-update or > other means then errors will happen. What errors and how severe entirely > depend on the scripts the user has in /etc/init.d
i really think this bash vs POSIX issue is getting way more emphasis than it should. i'd make the claim the majority of people out there dont even know about /bin/sh, bash, dash, and friends, so most people out there will have /bin/sh pointing to bash and as such, none of these things will be an issue for them. anyone who has tried to switch /bin/sh to point to something else has already seen their system blow up. or they're using baselayout-2 and so they're aware of the issues. in other words, you want to put info in there about POSIX shell and changing your conf.d files, great ... but dont emphasize it like it's doomsday and all hell's gonna break loose when you upgrade. -mike
signature.asc
Description: This is a digitally signed message part.
