> > In that case just boot off a Solaris install DVD > > (or any of > > the livecds today) mount your harddisk and fix > > things. > > Works great on a desktop; not so good on a server whose > console is being accessed remotely (unless a suitable CD/DVD > remains in the drive at all times). Actually, with planning ahead > (how often does _that_ actually happen?), > I'd want _4_ bootable copies of the root filesystem: 2 active mirrors, > 1 spare for recovery not normally mounted, and 1 for Live Upgrade. > If they were also split across two controllers, that, plus the remote > hard reset possible on many of the servers, should allow most situations > to be recoverable without physical access. > > Any set of solutions that fails to address all scales of desktop or > server support isn't complete.
How to make trivial things looking complicated ?? Two linear steps: #0) A dynamically linked bash should go into /sbin/bash (or, better, /sbin/sh) #1) its dependencies go into /lib. Both are inside the rootfs and are always accessible. So what? The old bourne shell is "slightly" outdated. Has too many restrictions in virtually every aspect (i.e. limited language syntax, maximum length of command line very short, no rc-file, no history, no cmd-line-editing). I can name many concrete examples, where scripts do break: IF /bin/sh is _not_ bash. -- Martin Bochnig _______________________________________________ opensolaris-discuss mailing list [email protected]
