1
1
/*--------------------------------------------------------------------------*\
2
LINUX_LOGO 4.14 -- Shows a Logo With some System Info - 20 July 2006
3
by Vince Weaver (vince@deater.net, http://www.deater.net/weave )
4
SUPPORTS Linux (most architectures) and some non-Linux OS's
2
LINUX_LOGO 5.01 -- Shows a Logo With some System Info - 9 July 2007
3
by Vince Weaver ( vince _at_ deater.net, http://www.deater.net/weave )
4
SUPPORTS Linux (most architectures) and some non-Linux OSes
5
5
\*--------------------------------------------------------------------------*/
9
9
Back in the summer of 1997 there was a recurring topic on the linux-kernel
10
list about having a "boot-up" penguin in the kernel. There were many
11
arguments back and forth, but eventually the primary consensus was that
12
this would be better done in user-space. [though with the advent
13
of GGI, etc, a graphical approach may become standard. Patches did
14
float around of a Vga-font hack to get a penguin...]
10
list about having a "boot-up" penguin on all architectures. There
11
were many arguments back and forth, but eventually the primary consensus
12
was that this would be better done in user-space. [Eventually the fbcon
13
people snuck it in anyway]. In any case, those of us running on text
14
consoles wanted a penguin too, and barring some attempts to use a vga-font
15
hack to get one displayed, the best way to get this was a user-space
16
So using a ppm to ansi converter from Rasterman [www.rasterman.com],
17
a trial version of THEDRAW under DosEmu, and just some talents left
18
over from my Ansi-art BBS days I hacked together a rough likeness
19
of Ewing's Linux Penguin. I added some system info from /proc, and
18
I used a ppm of the Linux penguin and a ppm2ansi converter from
19
Rasterman [www.rasterman.com], and then touched it up with a trial
20
version of THEDRAW under DosEmu. Dredging up some talents left
21
over from my Ansi-art BBS days I eventually hacked together a rough
22
likeness of Ewing's Linux Penguin. I added some system info from
23
/proc, and linux_logo was born.
22
25
The program itself has grown more "feature-full" as people around the
23
world sent in their patches. The newer versions are primarily minor
26
world send in their patches. The newer versions are primarily minor
24
27
cosmetic fixes. But I get a lot of positive feedback from this tiny
25
28
little program I created one summer day........
32
35
hidden file .linux_logo in your home directory] and
33
36
/etc/linux_logo.conf before parsing the command line options.
35
The format of the config files is a bit of a "hack". Basically,
36
just stick in the files the command line options you want to run.
38
The format of the config files is a bit of a hack. Just put in the
39
file the command line options you want passed to linux_logo.
38
41
Thus if you put in ~/.linux_logo
40
43
-a -c -F "Linux Logo on a #M Mhz Machine"
57
60
----------------------------------------------------------------------->
59
62
untar and uncompress the file
60
tar -xzvf linux_logo-4.14.tar.gz
63
tar -xzvf linux_logo-5.0.tar.gz
62
65
enter the directory
65
edit the Makefile and be sure everything is set up the way you want.
66
[on stock Linux systems it should work without any changes]
68
71
compile the program
71
74
install (you'll probably want to do this as root) with
75
78
-------------------------------------------------------------------------->
76
79
ADVANCED LINUX_LOGO Installation
77
80
-------------------------------------------------------------------------->
82
Destination directory:
84
By default linux_logo is installed under /usr/local/
86
To change this, run configure with
87
"./configure --prefix=/usr"
88
Where you can replace /usr with any location you want.
108
118
This can be turned off by changing the USE_I18N option at the top
109
119
of the defaults.h file.
123
If you are using linux_logo on an embedded system you might
124
want to cross compile. I tried to make this as easy as possible.
126
For example, to cross-compile for avr32 on x86 (assuming you
127
have all of the avr32 cross-compile tools installed) I do this:
129
env CROSS=avr32-linux- ./configure
130
make CROSS=avr32-linux- LDFLAGS=-static ARCH=avr32
132
And the result is a working avr32 version of linux_logo
134
On non-Linux architectures:
136
You'll have to use GNU make. This is often called "gmake".
112
140
--------------------------------------------------------------------------->
113
141
COMMAND LINE OPTIONS
203
231
This is useful if for whatever reason you don't want to see the
206
[-L num | list | random_xy]: This option is used to manipulate compiled-in
234
[-L num | NAME | list | random_xy]: This option is used to manipulate compiled-in
207
235
custom logos. As of linux_logo 3.9 you can compile in an
208
236
arbitrary amount of logos, although the default is to just have
209
237
the original and banner logos.
211
239
"-L list" will list all of the logos available
240
"-L NAME" will display the logo with name NAME.
241
the names available can be seen with the "-L list" command
212
242
"-L num" will display logo number num, where the number is
213
243
obtained using the "-L list" command
214
244
"-L random_xy" will pick a logo at random, with criteria xy.
added
removed
README
