Puppy Linux Discussion Forum

[Guest]

I want to ask that how to skip or hide the loading process while booting into puppy.
thanks!

[Bruce B]

[Guest]

thank you for your mention
I use IDE adapter with CF card boot from IDE, I brun a CD that is include version 1.0.3 and follow the CD's instruction to do that.

[Bruce B]

[Guest]

Turn off your monitor and wait 5 minutes until puppy has fully booted to hide the boot process.

[rarsa]

Don't be so mean blade.

I was going to recommend the same but only wait 2 minutes.

Although I've never booted from a CF card, maybe 5 minutes is accurate. My live CD takes 1 minute, my HDD installation takes 30 seconds.

An alternative is to turn on the computer and go prepare a sandwich and milk (Or hard liquor for some people). That will serve two purposes. You won't see the puppy boot instructions and you will have a more pleasant puppy experience.

You see... Linux is about choices, you can choose not to look at the screen.

[babbs]

I'd like to ask the question too... Is there any way to hide the boot-up lines that flash up the screen? I can't read things going by that fast, why show them? Would the boot-up speed get any faster if the system was not worrying about displaying the progress? I know there isn't much that can be done about how long the OS takes to load into RAM, likewise about loading /home from a USB device, but are there any speed benefits by not printing the commands/results to the display? I actually think that this question can be looked at for reasons other than cosmetics. I do think that this data should be visable during the first boot (or during testing) in case there is a problem and the progress/error is shown, but if it works, why keep showing it if you don't have to?

[rarsa]

[Pizzasgood]

Well, you could go into /etc/rc.d and go through the scripts there and just comment/delete any lines that say echo. That would get rid of much of it, and wouldn't insrease strain at all.

[babbs]

rarsa - If you say so, I'll take your word for it since I don't know one way or the other and I believe you know what you are talking about.

Pizzasgood - Interesting concept. Any idea how many lines that would be? Also, is this something we would really want to recommend to new Puppy users?

Since it doesn't appear that boot speed can be affected in this mannor... If commenting out lines in the rc.d would reduce the number of lines of code displayed during the boot process, maybe a simple boolean test of "is there a pup00x file?" If yes, and if the last shut down was clean, use the commented out rc.d; otherwise, use the normal rc.d file. Just rambling on here... I don't know what the answer is, could be, or should be... I'm just so glad that Puppy works!

[Guest]

You wont get rid of the kernel messages without patching the kernel......But why do ppl get so hung up about boot messages ?

[rarsa]

Beats me. But don't take it personal Bladehunter, it's not you, it's them.

[Pizzasgood]

From what I can tell, they seem to think displaying text as it starts is either "primitive" or "scary." I think text is cool, but I don't count because I'm weird. It's all the fault of WindowsXP. Everyone just assumes that if it is how Gates does it, it must be right. I think Gates is getting senile, but that's just me.

I have no idea how many lines that would be, but I guess you could write a script to find and remove them if you were ambitious enough. It shouldn't be too hard for a beginner. Look through a file, see echo, add a # to the beginning of the line. Procede to the next file. Reboot to have only limited text messages, and a dumbed down puppy

[Flash]

[rarsa]