[ turncoat @ 14.12.2003. 01:51 ] @
Kako vam se svidja ovaj boot screen? U paketu su boot.bmp i lilo.conf pa ih mozete koristiti... |
[ turncoat @ 14.12.2003. 01:51 ] @
[ MMX @ 14.12.2003. 12:06 ] @
Veoma zanimljivo. Sviđa mi se :)
[ E.N.I.A.C @ 14.12.2003. 12:58 ] @
Pf, meni se ne svidjaju ove boje... Nije lose ali moze i bolje...
[ kUdtiHaEX @ 14.12.2003. 15:04 ] @
Bas je bzvz :(
[ L I L I T @ 14.12.2003. 19:31 ] @
pa možda neko nema windous ;)
kao što reče čovek,može i lepše [ anon676 @ 14.12.2003. 22:45 ] @
Simpatično jeste, ali se može nacrtati mnogo, mnogo lepši bootscreen... :-) Ja sam crtao pre za svoju mini floppy distribuciju. Ako iskopam img fajl okačiću.
[ manca @ 15.12.2003. 23:42 ] @
Citat: turncoat: Kako vam se svidja ovaj boot screen? U paketu su boot.bmp i lilo.conf pa ih mozete koristiti... kako si se samo toga setio, bas je dobra ideja, zasedam da napravim i ja jedan primerak :)) Super. [ misa vranje @ 07.01.2004. 01:43 ] @
Kako si napravio ovaj boot screen ,uz pomoc nekog programa ili si samo nacrtao sliku?
Molim te da mi odgovoris samo jos kako da ga ubacim [ MMX @ 07.01.2004. 08:03 ] @
Pogledaj fajl lilo.conf koji se nalazi u Markovom paketu. Mislim da će ti posle biti sve jasno što se tiče ubacivanja LILO boot screen-a.
[ Miroslav Strugarevic @ 07.01.2004. 14:29 ] @
Eve nesto od mene.
[ misa vranje @ 07.01.2004. 18:53 ] @
Ali nisi mi odgovorio kako se pravi.Da li mi je dovoljno da promenim ovu markovu bmp sliku i da upotrebim njegov lilo.conf ili mi treba neki program koji pravi taj boot screen?
[ vilyu @ 08.01.2004. 11:32 ] @
Ćao. Preko man lilo.conf sam zaključio da ta bitmapa mora da ima 16 boja, ne više od toga. Ja se ne bavim grafikom, pa me interesuje kako se to postiže? Tj, gde se npr. u Gimp-u nalazi opcija da crtam sa samo 16 boja? Hvala.
[ NLO @ 08.01.2004. 18:45 ] @
Citat: Notes on the use of Bitmap boot screens LILO 22.3 -- 11-Apr-2002 SUMMARY OF CHANGES (LILO 22.3) ============================== LILO 22.3 no longer requires placement parameters in the configuration file (/etc/lilo.conf). Instead, text menu size, placement, and colors may be edited into the bitmap file header using "lilo -E file.bmp". The parameters may also be saved from the bitmap file header to a companion configuration file, "file.dat", as an option to the edit command. Param- eters may be transferred from the companion '.dat' file to the bitmap file header using the command "lilo -E file.dat". LILO 22.3 still rec- ognizes bitmap file formating commands in '/etc/lilo.conf'. This change allows bitmap graphics to be exchanged among users without the tedious need to exchange the color/positioning information separately. MOTIVATION ========== The makers of several Linux distributions which include LILO as the boot loader have issued patched versions which support graphical screens for kernel selection. However, each distribution seems to have chosen a different screen resolution, and different file-type to implement the graphical (bitmapped) background. In order to try to bring some order to this array of different implementations, and to support common code across all Linux distributions, I submit the following implementation of a graphical background and menu driven interface (cursor keys only) for kernel selection. The choice then was to have the implementation run on the widest array of graphics hardware in use today. VGA is the common standard, and this dictates a choice of two color modes: 320x200x256 and 640x480x16. The VGA/VESA standard extends the modes to add 640x400x256, 640x480x256, and 800x600x256 as possible choices. However, most high-end graphics cards provide graphics acceleration through other means than the VESA standard; and, in actual fact, are moving away from supporting the full spectrum of VESA modes. Older VGA systems often do not have VESA extensions in ROM BIOS, so the choice narrows to the two modes in the original IBM VGA BIOS. Character generation in the 320x200x256 mode is generally limited to an 8x8 character cell, and is not visually appealing. The 640x480x16 mode uses an 8x16 character cell, and is acceptable. The question was the limitations to 16 colors. This is less of a restriction than one might think it is. There are the 16 EGA-compatible colors, which are the BIOS defaults on all systems; but the VGA palette is programmable with 6 bits alloted to each primary color. Some experimentation with graphics images convinced me that very appealing logos could easily be generated, as long as the graphics editor in use would allow ANY 16 colors to be chosen from among the 256K available. Good dithering algorithms exist, and the screens that I produced with dithered 16-color images, in my opinion, were more acceptable than 256-color images. In these latter cases, as a color area transitions from one shade to another, the stepping effect is more notice- able, and more objectionable, than a good dither. With this said, the choice of VGA 640x480x16 (mode 0x12) was settled upon. Then the choice of a graphics screen file format had to be settled. It had to be universally supported, be well documented, allow for image compression, and allow for easy decompression. File formats considered included PCX, GIF, and BMP. The last was chosen because it is understand- able, and the run-length compression is very easy to expand. USAGE ===== Update (22.3): The three keywords 'bmp-table', 'bmp-colors', and 'bmp-timer' are now primarily to be used in the configuration file used as a companion to a bitmap file. The bitmap file must have the filename extension ".bmp", and the companion configuration file must have the filename extension ".dat". Four keywords are added to 'lilo.conf' to allow the usage of bitmap screens: bitmap = #specifies the bitmap file to be used as #a background bmp-table = #specifies the location of the table of #image/other names, and its layout bmp-colors = #specifies the color attributes of the table #entries, normal & highlighted bmp-timer = #specifies the position and color attributes #of the timeout timer install = /boot/boot-bmp.b #specify the boot loader with bitmap #graphics capability 'bitmap=' specifies the graphic file to be used as a background screen. It must be 640 x 480 x 16 colors, and may be saved as an uncompressed bitmap file (153718 bytes), run-length encoded (compressed) bitmap file, or an OS2 bitmap file (153674 bytes). It is suggested that you use the smallest, which will probably be the RLE (compressed) file. When a 'bitmap=' file is in use, 'message=' may not be used, and vice versa. In order to display the graphic file, you will also have to specify a boot loader with graphic capabilities. The LILO Makefile will make the new boot loader, "boot-bmp.b", and the shell command "make install" will install it to the default directory '/boot'. 'lilo.conf' will require the 'install=' line above to make use to this boot loader. 'bmp-table=<list>' specifies the position and table layout of the boot selection menu. The list is a series of up to 5 decimal values, separated by commas, and containing no spaces. Values may be omitted in order to use default values, but the comma separators are required as placeholders. In designing the bmp-table layout, consideration must be given to the upper limit on kernel image/other names. LILO guarantees that up to 16 may be specified, and the current implementation allows up to 19. It is suggested that the table layout design allow for 18 entries. bmp-table = [x],[y],[ncol],[nrow],[xspc],[spill] [x] specifies the column position [1..80] of the first column of the table. Character addressing is assumed, unless the coordinate is suffixed with 'p', in which case pixel ad- dressing will be used [0p..632p]. [y] specifies the row position [1..30] of the top row of the table. All screen text is placed on a 30 row grid. Pixel addressing [0p..464p] is allowed. [ncol] specifies the number of columns used for the display of the kernel image/other entries. The current implementation requires the number of columns to be in the range [1..4]. [nrow] specifies the number of rows in each column; i.e., the height of each column in the table. [xspc] specifies the column spacing from the beginning of one column to the beginning of the next column. Since names in the table are up to 15 characters, plus 2 spacers, 17 is an absolute minimum for this value. The column spacing increases as this value is increased. Too large a value may spill characters beyond the edge of the screen. Pixel addressing is allowed, if the value is suffixed with a 'p'. [spill] specifies the number of entries which may fill a column before the column spills to the next column. The default value for this is 4 entries. (LILO 22.3) 'bmp-colors=<list>' specifies a list of six color numbers, each in the range [0..15]. The first three specify the color attributes of normal text in the boot selection table, and the second three specify the color attributes of the highlighted text in the menu. The list is comma or semicolon separated, with no spaces. However, default values may be indicated by omitting a numerical value altogether. Each of the two triples consists of a fore- ground color, background color, and a shadow color. The foreground color is the color used to display the letter or numeral. The background color is the fill-color of the 8x16 box which encloses the character. If the back- ground color value is omitted from the list, then "transparent" is assumed. The shadow color is the color used to display a character shadow displaced one pixel in both X & Y toward the lower right. If shadows are used, they generally specify a color of low luminance. bmp-colors = [fg],[bg],[sh];[h-fg],[h-bg],[h-sh] [fg] specifies the foreground color for normal text. [bg] specifies the background color for normal text. If omitted, the background is taken to be transparent, and the underlying bitmap color shows through. [sh] specifies the shadow color for the character. If omitted, no shadow is displayed. [h-fg] specifies the foreground color for the line of highlighted text. [h-bg] specifies the background color for highlighted text. If omitted, the highlighted background is taken to be transparent. [h-sh] specifies the shadow color for highlighted text. If omitted, no shadow is displayed. Note: in the list specification above, the semicolon has no special significance; it could have been a comma. Its use is suggested merely for distinguishing the two triples, as spaces (blanks) are not allowed in the list. 'bmp-timer=<list>' specifies the position at which the 'timeout=' timer will be displayed, as well as the color attributes of the characters in the display. If the line 'bmp-timer=' is not used, then no timer will be displayed. If the <list> is specified as "none", then no timer (as speci- fied in the bitmap file header) will be displayed. bmp-timer = [tx],[ty];[t-fg],[t-bg],[t-sh] [tx] specifies the column at which the first of five characters in the timer display will be positioned. It must be in the range [1..80], or [0p..632p] if pixel addresses are used. [ty] specifies the character row position of the timer display. It must be in the range [1..30], or [0p..464p] if pixel addresses are used. [t-fg] specifies the foreground color of the timer characters. If omitted, the normal foreground text color will be used. [t-bg] specifies the background color of the timer character display. If omitted, color '0' will be used. It is not possible to have a transparent timer background. [t-sh] specifies the shadow color for timer display characters. If omitted, no shadow is displayed. Note: the semicolon in the list specification is for readability only; a comma could have been used as well. EXAMPLE ======= The following is excerpted from 'bmp.conf', a LILO configuration file which has been used during the development of the bitmap-capable boot loader. File: bmp.conf (substitute for 'lilo.conf'): ... # # The following parameters select appropriate colors # and proper screen positions for the 'logo64a.bmp' graphic. # bitmap=logo64a.bmp bmp-colors=6,9,0;15,9,0 bmp-table=59,5,1,19, bmp-timer=66,28,6,8,0 ... Update (22.3): If the color information and screen positions specified on the last three lines above have been transferred to the LILO sub-header in the bitmap file "logo64a.bmp", then the entry in 'lilo.conf' can be shortened to: ... # # Select the bitmap file to display. Text positioning information # is in the LILO subheader in the bitmap file. # bitmap=logo64a.bmp ... ... # # The following parameters select appropriate colors # and proper screen positions for the 'ins64a.bmp' graphic. # bitmap=ins64a.bmp bmp-colors=14,11,;15,9,0 # omit this line for lilo 22.3 bmp-table=21,287p,2,4,175p # ditto bmp-timer=73,29,12,8,0 # ditto ... Both bitmap files are available in the source code tarball at: http://lilo.go.dyndns.org/pub/linux/lilo They are located in the 'sample' subdirectory, along with companion '.dat' configuration files. USAGE COMMAND ============= With version 22.3, '/sbin/lilo' becomes, in addition to the boot installer, the bitmap file header editor. A single switch, '-E' is added to accomplish this new task. It has two uses: lilo -E filename.bmp or lilo -E filename.dat In the first case, if the bitmap file is fresh out of a graphics editor, it will have no LILO sub-header. The first edit command is used to alter the default values for color and positioning information, and to save the new values to the LILO sub-header in the bitmap file. The editor is interactive, and allows you to change one parameter at a time. When you write out the updated bitmap file, you are given the chance to create a companion text configuration file, 'filename.dat', which contains a readable copy of all of the text color and positioning information in the header. In the second case, the abbreviated configuration file, 'filename.dat', contains only the commands: "bitmap=", "bmp-table=", "bmp-colors=", or "bmp-timer="; all are optional. If "bitmap=" is omitted, then 'filename.dat' is taken to correspond to the bitmap file 'filename.bmp'; i.e., same name, diffenent file extension. Otherwise, the configuartion file corresponds to the bitmap file specified by the "bitmap=" option. The color, positioning, and timer information in the configuration file is transferred to the LILO header in the bitmap file. If no such header exists, one is created. The primary use for the '.dat' file is to save the LILO header information, so that the bitmap graphic may be edited with a graphics editor. No graphichs editor recognizes the LILO header, so an updated bitmap graphic file will be without the LILO header. The second form of the edit command allows the header to be recreated very quickly, exacltly as it was before. TRADEMARKS ========== Windows is a trademark of Microsoft Corporation. OS/2 and OS2 are trademarks of IBM Corporation. (end) written 05/07/2001 -- John Coffman <[email protected]> updated 05/10/2001 -- John Coffman updated 11/25/2001 -- John Coffman (typos corrected) updated 04/11/2002 -- John Coffman (update to LILO 22.3) sad cemo pokushamo neshto da napravimo :) [ Miroslav Strugarevic @ 08.01.2004. 18:47 ] @
Prekopiraj sliku u /boot/boot.bmp i dodaj u lilo.conf-u linije:
Code: # Lilo Boot Splash vga = 790 bitmap = /boot/splash.bmp I pokreni lilo kao root. **** A sto se tice kreiranja slike. U gimpu ima opcija Image > Mode > Indexed. U polju Max. Number of Colors unesi 8. Tako sam ja uradio. Samo moram da napomenem da je moguce i sa 256 boja. [ NLO @ 08.01.2004. 20:46 ] @
veruj mi da sam sad to provalio i hteo ovde da napishem :)
mozesh i vishe boja da stavish: Image > Mode > Indexed > Generate Optimal Pallete: stavio sam 20 000 i radilo je.... i snimish kao rle encoded bitmap... nego el neko provalio one brojeve za pozicioniranje i boje slova? to koritim od onog prvog lika koji je postovao samo sam ga malo spustio... ne mogu da provalim shta je shta, ako neko provali nek napishe.... [ stalker @ 08.01.2004. 21:01 ] @
Pa postovao si objasnjenje dve poruke iznad
[ NLO @ 08.01.2004. 22:29 ] @
vidi stvarno :)
el zna neko koje su to boje od 0 do 15, mislim koji je broj za koju boju, i dali mogu da napravim da mi budu veca slova? znam da se to sve moze provaliti al mrzi me vishe da reboot-ujem komp :) [ stalker @ 14.01.2004. 12:00 ] @
Evo kako da vidis koje su boje (mozda postoji i laksi nacin, ali posluzice i ovaj). Otvoris u Gimp-u tvoju sliku (ako nije ona od onih standardnih, moras valjda lilo -E imebitmape), pa otvoris prozor Indexed Pallete ili tako nesto, Tu se prikazuje 16 boja koje su u tvojoj slici, pa kad kliknes na neku, reci ce ti broj indexa.
[ manca @ 14.01.2004. 12:11 ] @
Citat: Miroslav Strugarevic: Prekopiraj sliku u /boot/boot.bmp i dodaj u lilo.conf-u linije: Code: # Lilo Boot Splash vga = 790 bitmap = /boot/splash.bmp I pokreni lilo kao root. **** A sto se tice kreiranja slike. U gimpu ima opcija Image > Mode > Indexed. U polju Max. Number of Colors unesi 8. Tako sam ja uradio. Samo moram da napomenem da je moguce i sa 256 boja. ramm, ja sam tako i uradio, i opet mi iskace onaj crveni, linuxov lilo. [ Miroslav Strugarevic @ 14.01.2004. 14:25 ] @
Cek, znaci sve prodje bez problema. Ne prijavi ti nikakvu gresku pri #lilo.
[ Miroslav Strugarevic @ 14.01.2004. 14:34 ] @
Uff. Ja sam ovde pogresio. Izvinjavam se. Treba ovako.
Code: # Lilo Boot Splash vga = 790 bitmap = /boot/boot.bmp Moguce da je to izazvalo zabunu :) Znaci vodi racuna o nazivu slike. Ako je boot.bmp onda u config ide boot.bmp.. Ako si mozda skinuo moj splash onda ide splash.bmp jer sam ja tako nazvao sliku :) [ manca @ 14.01.2004. 19:36 ] @
naravno, naravno.
Evo sad cu da probam sa ovim sto si sad dao. Pa cemo da vidimo ![]() [ manca @ 14.01.2004. 20:19 ] @
Ok je sad.
Ovo radi, lepo. Nego evo da iskoristim priliku da postavim jos jedno pitanje, trenutno sam u Unixu, ali nema veze. Naime, kad pokusam da udjem u Linux, kad se podigne boot, i izaberem linux, on pre pocetka unkompresovanja kernela, me pita: "You passed an undefined mode number, please press <SPACE> or wait 30sec, or press <ENTER> to see all mode numbers" Zasto, sta je sa njim? I da, jos, kad se dize linux, nije mi graficka konzola sa pingvinom u levom gornjem uglu, kao sto je nekad bilo, vec j u txt. obliku, zasato(napominjem da ovo nema veze sa ovim sto sam dodao onu slicku u boot loaderu, vec je bilo to i ranije, samo sam iskoristio sad tu da pitam).Da li neko mozda ideju, zasto se pojavljuje You passed...i zasto mi nije graficki podizanje kernela(i samim tim linuxa)? Evo mog lilo.conf fajla: Code: # LILO configuration file # generated by 'liloconfig' # # Start LILO global section boot = /dev/hda3 #compact # faster, but won't work on all systems. prompt timeout = 300 # Lilo Boot Splash vga = 790 bitmap = /boot/boot.bmp # VESA framebuffer console @ 800x600x32k # vga=787 # Normal VGA console # vga = normal # VESA framebuffer console @ 1024x768x64k # vga=791 # VESA framebuffer console @ 1024x768x32k # vga=790 # VESA framebuffer console @ 1024x768x256 # vga=773 # VESA framebuffer console @ 800x600x64k # vga=788 # VESA framebuffer console @ 800x600x32k # vga=787 # VESA framebuffer console @ 800x600x256 # vga=771 # VESA framebuffer console @ 640x480x64k # vga=785 # VESA framebuffer console @ 640x480x32k # vga=784 # VESA framebuffer console @ 640x480x256 # vga=769 # ramdisk = 0 # paranoia setting # End LILO global section # Linux bootable partition config begins image = /boot/vmlinuz root = /dev/hda3 label = Linux append = "hdc=ide-scsi" read-only # Non-UMSDOS filesystems should be mounted read-only for checking image = /unix/boot/vmlinuz root = /dev/hdb3 label = Unix read-only # Non-UMSDOS filesystems should be mounted read-only for checking # Linux bootable partition config ends # DOS bootable partition config begins other = /dev/hda1 label = Windows table = /dev/hda [ VRider @ 14.01.2004. 21:24 ] @
U vezi ne aktiviranja frame-buffera, milslim da je problem u tome sto nisi nigde ukljucio.
append linija treba da sadrzi i video=vesa. Barem kod mene sadrzi, i radi. ![]() [ caiser @ 14.01.2004. 22:17 ] @
Pa sta te sprecava da stavis i video=vesa u append linuju? :)
Sto se tice prvog pitanja. Mislim da te nisam bas najbolje razumeo tako da je moj predlog long_shot sto bi se reklo. :) Pogledaj u /etc/inittab-u u koji init level se dize linux.pa izmeni ako ne valja. [ VRider @ 14.01.2004. 22:51 ] @
Citat: pa kod mene je u append liniji inicializacija scsi, uredjaja, a to je cdrom, koji mora da se ponasa kao scsi, jer da bih mogao da rezem diskove, ova linija je NEOPHODNA. I ajde ako neko zna, sta je stvarno neka javi. Slucajno znam odavno cemu sluzi to sto se kod tebe nalazi u toj liniji, ali znam da mozes jos mnogo toga da dodas. To je linija u kojoj se prosledjuju parameri (mnozina) kernelu. Dodaj ovo sto sam ti rekao i c'est ce! [ manca @ 14.01.2004. 23:29 ] @
Citat: caiser: Pa sta te sprecava da stavis i video=vesa u append linuju? :) Sto se tice prvog pitanja. Mislim da te nisam bas najbolje razumeo tako da je moj predlog long_shot sto bi se reklo. :) Pogledaj u /etc/inittab-u u koji init level se dize linux.pa izmeni ako ne valja. caiser, evo mog innitab, fajla, pa kazi sta i gde da menjam: Code: # # inittab This file describes how the INIT process should set up # the system in a certain run-level. # # Version: @(#)inittab 2.04 17/05/93 MvS # 2.10 02/10/95 PV # 3.00 02/06/1999 PV # 4.00 04/10/2002 PV # # Author: Miquel van Smoorenburg, <[email protected]> # Modified by: Patrick J. Volkerding, <[email protected]> # # These are the default runlevels in Slackware: # 0 = halt # 1 = single user mode # 2 = unused (but configured the same as runlevel 3) # 3 = multiuser mode (default Slackware runlevel) # 4 = X11 with KDM/GDM/XDM (session managers) # 5 = unused (but configured the same as runlevel 3) # 6 = reboot # Default runlevel. (Do not set to 0 or 6) id:4:initdefault: # System initialization (runs when system boots). si:S:sysinit:/etc/rc.d/rc.S # Script to run when going single user (runlevel 1). su:1S:wait:/etc/rc.d/rc.K # Script to run when going multi user. rc:2345:wait:/etc/rc.d/rc.M # What to do at the "Three Finger Salute". ca::ctrlaltdel:/sbin/shutdown -t5 -r now # Runlevel 0 halts the system. l0:0:wait:/etc/rc.d/rc.0 # Runlevel 6 reboots the system. l6:6:wait:/etc/rc.d/rc.6 # What to do when power fails. pf::powerfail:/sbin/genpowerfail start # If power is back, cancel the running shutdown. pg::powerokwait:/sbin/genpowerfail stop # These are the standard console login getties in multiuser mode: c1:12345:respawn:/sbin/agetty 38400 tty1 linux c2:12345:respawn:/sbin/agetty 38400 tty2 linux c3:12345:respawn:/sbin/agetty 38400 tty3 linux c4:12345:respawn:/sbin/agetty 38400 tty4 linux c5:12345:respawn:/sbin/agetty 38400 tty5 linux c6:12345:respawn:/sbin/agetty 38400 tty6 linux # Local serial lines: #s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100 #s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100 # Dialup lines: #d1:12345:respawn:/sbin/agetty -mt60 38400,19200,9600,2400,1200 ttyS0 vt100 #d2:12345:respawn:/sbin/agetty -mt60 38400,19200,9600,2400,1200 ttyS1 vt100 # Runlevel 4 used to be for an X window only system, until we discovered # that it throws init into a loop that keeps your load avg at least 1 all # the time. Thus, there is now one getty opened on tty6. Hopefully no one # will notice. ;^) # It might not be bad to have one text console anyway, in case something # happens to X. x1:4:wait:/etc/rc.d/rc.4 # End of /etc/inittab znaci da dodam jos jedno append liniju u lilo.conf fajlu? [ caiser @ 15.01.2004. 11:45 ] @
Ma nista. Sve je ok. Rekoh da je long shot. :)
[ misa vranje @ 17.01.2004. 23:41 ] @
Moze li takav boot screen da se napravi za GRUB i kako.
[ aster @ 06.02.2004. 07:13 ] @
Dali dali neko moze da mi kaze kako da uradim upravo suprotno o ulepsavanja lilo boot-a. Po default-u pojavljuje mi se lilo boot prompt sa crvenim kvadratom unutar kojeg biram koji OS da pokrenem. Kako da promenim lilo.conf da mi ne prikazuje isti, vec samo tekstualanu prompt liniju bez boja, kvadrata itd.?
[ nemesis @ 07.02.2004. 01:23 ] @
Citat: aster: Dali dali neko moze da mi kaze kako da uradim upravo suprotno o ulepsavanja lilo boot-a. Po default-u pojavljuje mi se lilo boot prompt sa crvenim kvadratom unutar kojeg biram koji OS da pokrenem. Kako da promenim lilo.conf da mi ne prikazuje isti, vec samo tekstualanu prompt liniju bez boja, kvadrata itd.? nadji liniju Code: message=/boot/message onda je remuj tako shto cesh ubaciti # ispred :0 i to je to :) potom prozivash komandi lilo i trebalo bi da ti je odradio posao :) [ nemesis @ 07.02.2004. 01:52 ] @
Citat: manca: Code: # c3:12345:respawn:/sbin/agetty 38400 tty3 linux c4:12345:respawn:/sbin/agetty 38400 tty4 linux c5:12345:respawn:/sbin/agetty 38400 tty5 linux c6:12345:respawn:/sbin/agetty 38400 tty6 linux mislim da ovo mozesh da izbacish :) [ aster @ 08.02.2004. 01:47 ] @
Citat: nemesis: Citat: aster: Dali dali neko moze da mi kaze kako da uradim upravo suprotno o ulepsavanja lilo boot-a. Po default-u pojavljuje mi se lilo boot prompt sa crvenim kvadratom unutar kojeg biram koji OS da pokrenem. Kako da promenim lilo.conf da mi ne prikazuje isti, vec samo tekstualanu prompt liniju bez boja, kvadrata itd.? nadji liniju Code: message=/boot/message onda je remuj tako shto cesh ubaciti # ispred :0 i to je to :) potom prozivash komandi lilo i trebalo bi da ti je odradio posao :) Hvala sto si se potrudio da mi odgovoris, ali nije to. Naime, message je samo poruka koja se pojavljuje ispod menija (kod mene je npr. bilo message=/boot/boot_mesage.txt, koji je ispisivao pozdrav pri boot-u, ispod pomenutog menija). Medjutim nasao sam resenje, ako jos nekoga zanima, u pitanju je komanda install, koja instalira jedan od tri UI: text (ono sto je meni trebalo), menu (ono sto je vec bilo) i bmp (ono sto su ostali u ovoj temi postavljali). Novije verzije lilo-a po default-u postavljaju UI menu. [ nemesis @ 08.02.2004. 08:16 ] @
Citat: aster: Hvala sto si se potrudio da mi odgovoris, ali nije to. Naime, message je samo poruka koja se pojavljuje ispod menija (kod mene je npr. bilo message=/boot/boot_mesage.txt, koji je ispisivao pozdrav pri boot-u, ispod pomenutog menija). Medjutim nasao sam resenje, ako jos nekoga zanima, u pitanju je komanda install, koja instalira jedan od tri UI: text (ono sto je meni trebalo), menu (ono sto je vec bilo) i bmp (ono sto su ostali u ovoj temi postavljali). Novije verzije lilo-a po default-u postavljaju UI menu. mu ? ako sam ja tebe drobro razumeo tebi je trebalo da izbacish onu slikicu iz lilo boot-a ? pa kad remujesh liniju ostane bez slichice ... tako je bar na RH ... [ aster @ 08.02.2004. 11:52 ] @
Moguce da je taj fajl korisitio umesto bmp. Kod mene je stajalo:
Code: a u tom fajlu se nalazila tekstualna poruka koja se ispise kao dodatni help ispod menija: message = /boot/boot_message.txt Code: Welcome to the LILO Boot Loader! Please enter the name of the partition you would like to boot at the prompt below. The choices are: DOS - DOS or Windows (FAT/FAT32 partition) Linux - Linux (Linux native partition) [ random @ 08.02.2004. 14:35 ] @
Citat: misa vranje: Moze li takav boot screen da se napravi za GRUB i kako. Može. http://ruslug.rutgers.edu/~mcgrof/grub-images/ [ u_m @ 17.02.2004. 15:42 ] @
ovo samo za vreme biranja OS-a
da li se ovakvo nesto moze postaviti i za vreme dizanja sistema(dok prolaze ona slova), ja sam naso neke slike ali ne znam kako se postavlja. [ Miroslav Ranković @ 12.03.2004. 20:31 ] @
[ RAIN--SONG @ 14.03.2004. 00:09 ] @
Citat: NLO: vidi stvarno :) el zna neko koje su to boje od 0 do 15, mislim koji je broj za koju boju, i dali mogu da napravim da mi budu veca slova? znam da se to sve moze provaliti al mrzi me vishe da reboot-ujem komp :) Eto i ja sam malo uljepsao svoj boot screen al ne znam koja je koja tablica mrsko mi vise rebootat da pogodim a i boje slova su gadne. Copyright (C) 2001-2025 by www.elitesecurity.org. All rights reserved.
|