Solved Animated boot loader

R

rmomota

Hi,
I've seen several post regarding enabling the boot splash.
The best I could achieve was to enable a nice FreeBSD white demon logo shown for few seconds.
But I've that feeling that it's not doing anything in background and delaying the boot time just to show that.
What I really would like to get is an animated loader gif that hides those not so nice to see text boot messages.
I know some prefer to see what's happening during boot but I prefer to see a nice loader logo and press ESC in case I want to see what's happening behind and ESC again goes back to loader logo.
I've seen this in some Linux distros like Fedora.
I know it's just a useless to the system visual effect but it would look sooooooo great.
Just imagine if someone bring the laptop to the office and the boss sees those fast scrolling boot messages?
The first though that will get into is mind is "Hey! we have an hacker here" or the system has a severe problem and that does not seem to be a good image.
It's not like I need to impress someone, it's more like not giving that image of someone is using a system that shouldn't.
Is it possible to get this in FreeBSD?
Is there a plan for that in a future release?

Thanks
 
If there is a need to present a thing looking shiny, life experience should tell you that there is most likely going something wrong. Blowhards behave like this. They do not anticipate the emotions after the shininess has been unveiled.

BTW the shiny whistling thrush is a pitch black bird.
 
take a look at this page

forums.freebsd.org

Booting splash screen

When booting freebsd. Or you can log all messages to screen Or hide them behind a textual splash, a beastie in text. Or hide them behind a graphical splash, a beastie in high-resolution. But how do you configure for these 3 situations.
forums.freebsd.org forums.freebsd.org
 
Somewhere I remember seeing something about reducing the output of the booting process displayed on the screen to like two or three lines. I want to say that it was in one of the more popular threads in the "How To" section on setting up a GUI environment. However, the memory isn't as sharp as it used to be and I may be totally mistaken about where I read it.
 
zirias@ said:
"Hiding information" is one of the things FreeBSD typically avoids. And for this, it is liked by many. Just saying ;)
Click to expand...
Not completely hiding, in other systems I saw this whenever there's a critical error that need attention it takes the loader image of the way to show the error.
 
userxbw said:
take a look at this page

forums.freebsd.org

Booting splash screen

When booting freebsd. Or you can log all messages to screen Or hide them behind a textual splash, a beastie in text. Or hide them behind a graphical splash, a beastie in high-resolution. But how do you configure for these 3 situations.
forums.freebsd.org forums.freebsd.org
Click to expand...
Well, this is hiding the errors.
Changing the text colors to black, etc, does not seem to be the solution I'm looking for.
 
rmomota said:
Not completely hiding, in other systems I saw this whenever there's a critical error that need attention it takes the loader image of the way to show the error.
Click to expand...

well you can go big time old school and just slap a piece of paper with the FreeBSD logo on it over top of the screen .. it is an option.

me I like seeing text scroll lets them know you know something instead of being paranoid about someone thinking you're a hacker maybe educate your audience instead.

the term hacker, which got a bad rep due to the poorly eduacgted masses watching mass media and how they presented a hacker to be for profit and not truth because a hacker is just someone who "bangs away on the keyboard (hacking away on the keyboard) until he gets the results he is looking for." brut force password "hacking" is all they show
 
userxbw said:
well you can go big time old school and just slap a piece of paper with the FreeBSD logo on it over top of the screen .. it is an option.

me I like seeing text scroll lets them know you know something instead of being paranoid about someone thinking you're a hacker maybe educate your audience instead.

the term hacker, which got a bad rep due to the poorly eduacgted masses watching mass media and how they presented a hacker to be for profit and not truth because a hacker is just someone who "bangs away on the keyboard (hacking away on the keyboard) until he gets the results he is looking for." brut force password "hacking" is all they show
Click to expand...
Please don't take that to the real meaning of word.
I was trying to explain that this boot doesn't seem nice and that's it.
Take a deep breath and relax in a Zen moment.
All I'm looking for is a nice loader logo instead of text.
I totally respect others preferences, if most like the text it's alright to me but I prefer to see a nice logo and there's nothing wrong with that.
Seems I've to wait or develop one by myself, you know, I'm a "hacker" too but I'm avoiding to "reinvent the wheel". :)
 
rmomota said:
Please don't take that to the real meaning of word.
I was trying to explain that this boot doesn't seem nice and that's it.
Take a deep breath and relax in a Zen moment.
All I'm looking for is a nice loader logo instead of text.
I totally respect others preferences, if most like the text it's alright to me but I prefer to see a nice logo and there's nothing wrong with that.
Seems I've to wait or develop one by myself, you know, I'm a "hacker" too but I'm avoiding to "reinvent the wheel". :)
Click to expand...
you said "The first though that will get into [h]is mind is "Hey! we have an hacker here" or the system has a severe problem and that does not seem to be a good image."

and now you're telling me that was a lie or make up something completely different .. or you don't want people knowing you're actually a HACKER. :eek: ??

thanks for the heads up afterwords
 
A system boots. What is important? To me, it boots correctly, errors are clearly discernible. I don't care about pretty fancy spinny shiny boot logos or icons (but acknowledge some folk consider them mandatory). I don't want too many "printfs" I want "printf error happened here".

I want the system to boot correctly, 100% of the time.
I have no problem with the OP wanting a nice logo, but I don't want that as the default. That is my biggest "nit" with systemd on Linux. Oh there's a nice pretty logo but the system didn't boot correctly and all I see is a cryptic "error 12345 during boot".
Now I need another system to google "what does error 12345 during boot on Linux distro Blah mean and how do I fix it?"
 
If someone wants to expend energy on something useful for vt(4) they could fix the sadly broken behaviour of its text cut and paste, compared to historic sc(4).

Namely that cut text pasted into an editor such as vi or ee, has each line at the full width of the source screen, with all trailing whitespace - even on otherwise empty lines - followed by a null (visually ^@) which ee and less show, but vi makes an empty line - ugly either way.

This restricts the 1kB copy buffer to half a screen at most, even at 80 x 25.

I had to write a non-trivial script to clean up pastes.
 
mer said:
I have no problem with the OP wanting a nice logo, but I don't want that as the default.
Click to expand...
I think an ugly/plain and unassuming but useful default is a good choice, too.

smithi said:
If someone wants to expend energy on something useful for vt(4) they could fix the sadly broken behaviour of its text cut and paste, compared to historic sc(4).

Namely that cut text pasted into an editor such as vi or ee, has each line at the full width of the source screen, with all trailing whitespace - even on otherwise empty lines - followed by a null (visually ^@) which ee and less show, but vi makes an empty line - ugly either way.

This restricts the 1kB copy buffer to half a screen at most, even at 80 x 25.

I had to write a non-trivial script to clean up pastes.
Click to expand...
You might want to report this issue, even if it doesn't qualify as bug.
 
smithi said:
Namely that cut text pasted into an editor such as vi or ee, has each line at the full width of the source screen, with all trailing whitespace - even on otherwise empty lines - followed by a null (visually ^@) which ee and less show, but vi makes an empty line - ugly either way.
Click to expand...
Can't reproduce this (on -CURRENT, at least), and looking at the vt code (https://cgit.freebsd.org/src/tree/sys/dev/vt/vt_buf.c#n792), it explicitly strips trailing "space" characters.

What are the steps to reproduce?

EDIT: I see that there were some fixes in that area that are only in main and stable/13 (so upcoming 13.2-RELEASE), but not in 13.1-RELEASE; not sure which one you are running, if 13.1, could you please retest with 13.2?
 
You must log in or register to reply here.
Back
Top