Bryan Kadzban wrote:
[EMAIL PROTECTED] wrote:
and the screen display will look something like this (excerpt):
Mounting root file system in read-only mode... [ OK ]
Checking file systems...
/dev/hdb4: clean, 133764/960992 files, 921705/1919767 blocks (check in [ OK ])
Remounting root file system in read-write mode... [ OK ]
Not on my system. ;-) I run vesafb @ 1280x1024, so I have a 160-column
display, so this isn't an issue. Also, if you have more than one FS
being checked, it's not a problem for any except the last. *Also*, if
your filesystem's size is a different order of magnitude, then you'll
see either more or less of the "check in X days/mounts" message.
That being said, I don't know whether "just use *fb" is a good solution
either. I doubt it.
If it were possible to read whatever's on the display, then perhaps
echo_ok (and friends) could check that the positions they're going to
write to are empty before writing, and skipping the $CURS_UP if they're
not empty. But I'm not sure whether that's even possible, let alone a
good idea. (It could also break the "parallel bootscripts" that someone
was working on a while ago.)
Honestly, IMO, it's too much work to fix it correctly. I suppose as you
mentioned above, the output could be captured and counted...but it'd
make the scirpt pretty much unreadable (much like the current boot_mesg
function script in 3.2.{1,2}) because you can't use wc (it might not be
availible as it's in /usr/bin, not to mention it's brokeness with utf8).
The other (and easier) solution is to echo "mounting...", capture output
of mount and grep for the check message, if then spit the message to
screen and add another line (echo) and then echo_ok.
-- DJ Lucas
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
