Initscripts and tput

Scott James Remnant scott at netsplit.com
Tue Aug 31 14:15:17 CDT 2004


On Tue, 2004-08-31 at 12:11 -0700, Matt Zimmerman wrote:

> On Tue, Aug 31, 2004 at 08:07:08PM +0100, Scott James Remnant wrote:
> 
> > On Tue, 2004-08-31 at 14:56 -0400, Nathaniel McCallum wrote:
> > 
> > > After a long session hacking initscripts today, I realized that we are
> > > relying on tput to get ansi control characters.  This is not bad except
> > > that tput is in /usr/bin/ and /usr may not be available to use before
> > > mounting filesystems.  There is a couple solutions as i see it:
> > > 
> > > 1. move tput from /usr/bin to /bin in the terminfo-bin package
> > > 2. fall back to hardcoded ansi control characters (may not work on some
> > > strange terminals)
> > > 3. other solution...
> > > 
> > Why are we using ansi control characters?
> 
> In order to beautify the boot sequence (right-aligned success/failure
> indications, highlighted failures, etc.).
> 
Are these just adding random stuff to each initscript, or is this some
kind of wrapper around them to print the messages?  If the latter, isn't
it rather late in the warty process to be doing this kind of change and
aren't we going for usplash in hoary?

Scott
-- 
Have you ever, ever felt like this?
Had strange things happen?  Are you going round the twist?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.ubuntu.com/archives/sounder/attachments/20040831/692ef465/attachment.pgp


More information about the sounder mailing list