You are not logged in.
Pages: 1
[...]
[Starting SOMETHING ... DONE ]
[... BUSY ]
[Doing SOMETHING ... FAILED ]
[...]
what about having the DONE, BUSY and FAILED in green, yellow and red? ... as on my machine it goes so fast i cannot find the line that went wrong if everything is in grey ... on my SuSE-box (well it has a lot of disadvantages, but not on this part) the coulour indicaors helps to see what happened (you read the things faster)
how do they bring colour in this screen? (in suse there are no standard /etc/files --- that's the main reason i dont use it for work)
how can i color (my) archlinux bootscreen (and console-login-screens)? /// i mean coloring the text, not the background!
The impossible missions are the only ones which succeed.
Offline
I wouldn't mind knowing that myself. I prefer colour over black and white any day.
Kritoke
http://counter.li.org/ Registered Linux User #318963 kritoke@jabber.org
Offline
bootsplashes and colour in the boot process? for what reason you see the damn thing for mere seconds?
AKA uknowme
I am not your friend
Offline
It makes it all pretty, lol. Some of us like customizing our system way too much and there should be laws against it, heh.
Kritoke
http://counter.li.org/ Registered Linux User #318963 kritoke@jabber.org
Offline
bootsplashes and colour in the boot process? for what reason you see the damn thing for mere seconds?
no, bootsplashes are only for the image of the distribution ... if it looks nice, more people would like it (i dont want bootsplashes in official-base at all!!!)
the other thing: color: i dont think it take any machine to color a string in green or red more than 1ns :-) ... and the visibility will be enhanced (the bootscreen in knoppix: this is too much color, but the bootscreen in archlinux: this is no color --- what about a middle-way?)
The impossible missions are the only ones which succeed.
Offline
yes eye candy. some folks do seem to like it . me i am impartial as i try not to reboot regularily. like fonts...when i have trouble seeing fonts i change them...but that is really really rare.
AKA uknowme
I am not your friend
Offline
The code to make those "DONE", "BUSY", etc messages is pretty standard. They're all defined in /etc/rc.d/functions. I can't remember what you need to specify colours in bash for text... but those are the functions you want to change to get where you're going.
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal
Offline
eye candy ... what a nice word
well i use archlinux on a server (in the lab --- intranet) and on my laptop ... not rebooting the server every 5min is ok, but when you are using a laptop and booting in front of 100 people for a presentation, it makes some sence to have a nice bootsplash (else all not-unix-users mean you use a dos or something else prehistoric --- well at least they do not think you use the most popular one ... if you boot SuSE or RedHat, everybody knows that it is a modern linux-distro ... archlinux is one too, but dont look like this at boot
-> eye candies are worth much more to some people than the performance behind ... and again: today there is no performance problem adding 2 jpegs in the kernel and having some colours around
The impossible missions are the only ones which succeed.
Offline
The code to make those "DONE", "BUSY", etc messages is pretty standard. They're all defined in /etc/rc.d/functions. I can't remember what you need to specify colours in bash for text... but those are the functions you want to change to get where you're going.
i found out:
you have to use escape-sequences ... here the link where i found details
http://www-106.ibm.com/developerworks/l … ip-prompt/
The impossible missions are the only ones which succeed.
Offline
A patch for the current functions file can be found here now:
http://archlinux.veloxis.de/functions-color.patch
EDIT: No longer available there. Go to http://archlinux.veloxis.de/howtos/colo … olor.patch instead!
Use and edit at your leisure. To apply the patch do the following:
- gain root access
- change the working directory to /etc/rc.d
- run patch -p1 -i <location of patch file>
Easy as pie.
"That's the problem with good advice. Nobody wants to hear it."
-- Dogbert
Offline
Geez... I figured I would leave something as an exercise for the user
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal
Offline
thanks Gyroplast, the patch worked great. :-D
"Contrary to popular belief, penguins are not the salvation of modern technology. Neither do they throw parties for the urban proletariat."
Offline
... aaahhh nice colours ...
The impossible missions are the only ones which succeed.
Offline
HUMMMMM...Green
Offline
as the colors in booting are so nice now ... i wondered if it is possible to have some colors in the login-screens of the VC's ... of course it is ... but where are these functions in the system i dont know
(i mean the "Arch Linux 0.5 (Nova) ...")
The impossible missions are the only ones which succeed.
Offline
/etc/issue
You could have just grepped the /etc directory for "Arch Linux 0.5" to find that.
"That's the problem with good advice. Nobody wants to hear it."
-- Dogbert
Offline
/etc/issue
You could have just grepped the /etc directory for "Arch Linux 0.5" to find that.
thank you for the help, and the advice (the only thing is: i'm afraid of calling commands on system-relevant dirs ... a typing error can be horrible: instead of grep -r "Arch Linux" /etc you can type rm -r /etc what can be the end of your config-files and the begining of a long weekend :-) )
... after trying to change the color: adding escape-sequences in /etc/issue do not work (the function that echos it is without "-e" i think) ... where can i find this function, and where it is called from?
The impossible missions are the only ones which succeed.
Offline
a typing error can be horrible: instead of grep -r "Arch Linux" /etc you can type rm -r /etc what can be the end of your config-files and the begining of a long weekend
You are afraid of typing rm -r /etc instead of grep -r "Arch Linux" /etc?! Come on now, that's about the cheapest excuse one can think of, especially since you don't need root privilegues to do that. If you're honest about this, may I suggest using a typewriter instead?
However, the /etc/issue is interpreted by the getty program, agetty in Arch, and does interpret ANSI codes. You just can't use the same escape sequence as in the the bash. Open your issue file with vim , change into insert mode and type CTRL+V, CTRL+ESC to generate the escape sequence. Don't let the inserted bracket fool you, you still have to add a normal open bracket after it, followed by the ANSI codes as usual. Check http://hints.ca.linuxfromscratch.org/hi … _logon.txt for some more info on this.
Greets,
Dennis
"That's the problem with good advice. Nobody wants to hear it."
-- Dogbert
Offline
About colors and eze candy in the startup :
I hacked rc.d/functions the other way round to not even show the state like "busy" etc. Just starting the various things and that's it ;-) .... nothing fancy
Offline
a typing error can be horrible: instead of grep -r "Arch Linux" /etc you can type rm -r /etc what can be the end of your config-files and the begining of a long weekend
You are afraid of typing rm -r /etc instead of grep -r "Arch Linux" /etc?! Come on now, that's about the cheapest excuse one can think of, especially since you don't need root privilegues to do that. If you're honest about this, may I suggest using a typewriter instead?
actually you do need root-privileges to grep everything in /etc, because some files are only for root to 'rw-' and to others '---' (and you get something like
grep -r "Arch" /etc/
grep: /etc/ppp/pap-secrets: Permission denied
grep: /etc/ppp/chap-secrets: Permission denied
grep: /etc/ssl/certs/imapd.pem: Permission denied
grep: /etc/ssl/certs/ipop3d.pem: Permission denied
[...]
)
-------------------------------
However, the /etc/issue is interpreted by the getty program, agetty in Arch, and does interpret ANSI codes. You just can't use the same escape sequence as in the the bash. Open your issue file with vim , change into insert mode and type CTRL+V, CTRL+ESC to generate the escape sequence. Don't let the inserted bracket fool you, you still have to add a normal open bracket after it, followed by the ANSI codes as usual. Check http://hints.ca.linuxfromscratch.org/hi … _logon.txt for some more info on this.
thanx for that hint ... to summarize the site behind that URL more or less in one sentence:
/etc/issue is interpreted by agetty and you have to use ANSI codes, and not bash escape sequences
[/code]
The impossible missions are the only ones which succeed.
Offline
Pages: 1