I suppose you can say, "Not our problem" because I have diddled the
startup scripts.  I HATE those useles timestamps--it takes as long as it
takes, telling people HOW LONG it takes just makes them anxious, and
booting only happens once--not like it's happening over and over.  My
paradigm is KISS, so I tend to strip out anything not necessary.
They're disabled in the kernel, and in init functions.

Nevertheless, what I've got works flawlessly without framebuffers!  With
framebuffers it's off by one once udev starts the driver.  (fbcon is
internal.)  Why/Where are framebuffers changing the line length?  And it
there a proper way to fix it without checking for framebuffers in the
init functions and subtracting one--that's so ugly it's got to be the
wrong thing!
-- 
Paul Rogers
[email protected]
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL
:-)

-- 
http://www.fastmail.com - Same, same, but different...

-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Reply via email to