[opensuse-factory] christmas screen
just a question: is the install christmas screen just related to the system date, or is it to be the install screen for all the 8 mont release duration? thanks jdd -- http://www.dodin.net http://dodin.org/mediawiki/index.php/GPS_Lowrance_GO --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Wednesday, 6. December 2006 10:32, jdd wrote:
just a question: is the install christmas screen just related to the system date, or is it to be the install screen for all the 8 mont release duration?
Change your system date to find out? :-) Bye, Steve --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 2006/12/06 10:32 (GMT+0100) jdd apparently typed:
just a question: is the install christmas screen just related to the system date, or is it to be the install screen for all the 8 mont release duration?
I have about 5 10.2s. Only the least recently updated retains the Christmas theme. :-( -- "Let your conversation be always full of grace." Colossians 4:6 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Wed, Dec 06, 2006 at 08:55:05AM -0500, Felix Miata wrote:
On 2006/12/06 10:32 (GMT+0100) jdd apparently typed:
just a question: is the install christmas screen just related to the system date, or is it to be the install screen for all the 8 mont release duration?
I have about 5 10.2s. Only the least recently updated retains the Christmas theme. :-(
Yes, we marked the ISO specifically for this one. Well just kidding, there like is randonmness and specific days involved. Ciao, Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Mittwoch, 6. Dezember 2006 14:59 schrieb Marcus Meissner:
On Wed, Dec 06, 2006 at 08:55:05AM -0500, Felix Miata wrote:
On 2006/12/06 10:32 (GMT+0100) jdd apparently typed:
just a question: is the install christmas screen just related to the system date, or is it to be the install screen for all the 8 mont release duration?
I have about 5 10.2s. Only the least recently updated retains the Christmas theme. :-(
Yes, we marked the ISO specifically for this one.
Well just kidding, there like is randonmness and specific days involved.
But it seems to depend on the BIOS, too. On one of my testmachines, I get the christmas-screen all the time. Only 1 of 10 is the normal blue bootscreen. -- Mit freundlichen Grüßen, Marcel Hilzinger Linux New Media AG Süskindstr. 4 D-81929 München Tel: +49 (89) 99 34 11 0 Fax: +49 (89) 99 34 11 99 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Wed, 6 Dec 2006, Marcel Hilzinger wrote:
Am Mittwoch, 6. Dezember 2006 14:59 schrieb Marcus Meissner:
On Wed, Dec 06, 2006 at 08:55:05AM -0500, Felix Miata wrote:
On 2006/12/06 10:32 (GMT+0100) jdd apparently typed:
just a question: is the install christmas screen just related to the system date, or is it to be the install screen for all the 8 mont release duration?
I have about 5 10.2s. Only the least recently updated retains the Christmas theme. :-(
Yes, we marked the ISO specifically for this one.
Well just kidding, there like is randonmness and specific days involved.
But it seems to depend on the BIOS, too. On one of my testmachines, I get the christmas-screen all the time. Only 1 of 10 is the normal blue bootscreen.
It is random (check the sources) and depends on the date. And today in particular you will get it all the time. BTW, the online help mentions how to configure it. Steffen --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 2006/12/06 15:53 (GMT+0100) Steffen Winterfeldt apparently typed:
It is random (check the sources) and depends on the date. And today in particular you will get it all the time.
Funny, I just booted to test on a box I thought it was permanently gone from, but it came up.
BTW, the online help mentions how to configure it.
It says: "Like it or hate it? Edit gfxboot.cfg in /boot/message to have it always or get rid of it." /boot/message is apparently a binary file, and 379,904 bytes. How do you suggest to edit it? -- "Let your conversation be always full of grace." Colossians 4:6 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Mittwoch, 6. Dezember 2006 17:17 schrieb Felix Miata:
On 2006/12/06 15:53 (GMT+0100) Steffen Winterfeldt apparently typed:
It is random (check the sources) and depends on the date. And today in particular you will get it all the time.
Funny, I just booted to test on a box I thought it was permanently gone from, but it came up.
BTW, the online help mentions how to configure it.
It says:
"Like it or hate it? Edit gfxboot.cfg in /boot/message to have it always or get rid of it."
/boot/message is apparently a binary file, and 379,904 bytes. How do you suggest to edit it?
cpio -i /boot/message -- Mit freundlichen Grüßen, Marcel Hilzinger Linux New Media AG Süskindstr. 4 D-81929 München Tel: +49 (89) 99 34 11 0 Fax: +49 (89) 99 34 11 99 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 2006/12/06 17:27 (GMT+0100) Marcel Hilzinger apparently typed:
Am Mittwoch, 6. Dezember 2006 17:17 schrieb Felix Miata:
On 2006/12/06 15:53 (GMT+0100) Steffen Winterfeldt apparently typed:
BTW, the online help mentions how to configure it.
It says:
"Like it or hate it? Edit gfxboot.cfg in /boot/message to have it always or get rid of it."
/boot/message is apparently a binary file, and 379,904 bytes. How do you suggest to edit it?
cpio -i /boot/message
All that has done is removed my shell prompt from the screen. What next? -- "Let your conversation be always full of grace." Colossians 4:6 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2006-12-06 at 12:04 -0500, Felix Miata wrote:
cpio -i /boot/message
All that has done is removed my shell prompt from the screen. What next?
I'm not familiar with cpio options, but I think that should have extracted the files in the archive to the current directory. You can also copy the archive somewhere else, rename to message.cpio, start "mc", and click or press enter into the archive to see its contents. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFdxXWtTMYHG2NR9URAq7XAJ9lfe0zInPBstkHAhjkusYqIPA3OQCfaZi1 4FeRS5PRXTzI0YCUXsusbzs= =C+6f -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Wednesday 06 December 2006 09:04, Felix Miata wrote:
On 2006/12/06 17:27 (GMT+0100) Marcel Hilzinger apparently typed:
Am Mittwoch, 6. Dezember 2006 17:17 schrieb Felix Miata:
On 2006/12/06 15:53 (GMT+0100) Steffen Winterfeldt apparently typed:
BTW, the online help mentions how to configure it.
It says:
"Like it or hate it? Edit gfxboot.cfg in /boot/message to have it always or get rid of it."
/boot/message is apparently a binary file, and 379,904 bytes. How do you suggest to edit it?
cpio -i /boot/message
CPIO in input mode reads from the standard input. The lack of prompt indicates it's waiting for you to type a CPIO stream. Kill it (^C) and redirect from the CPIO file you want to unpack:: % cpio -i </boot/message On my system, this yields: % mkdir /tmp/boot-message % cd /tmp/boot-message % cpio -i </boot/mesage 250 blocks % ls -l total 168 -rw-r--r-- 1 rschulz users 37860 2006-12-06 11:27 16x16.fnt -rw-r--r-- 1 rschulz users 7500 2006-12-06 11:27 back.jpg -rw-r--r-- 1 rschulz users 3129 2006-12-06 11:27 en.hlp -rw-r--r-- 1 rschulz users 1099 2006-12-06 11:27 en.tr -rw-r--r-- 1 rschulz users 2862 2006-12-06 11:27 head_a.jpg -rw-r--r-- 1 rschulz users 1894 2006-12-06 11:27 head.jpg -rw-r--r-- 1 rschulz users 67222 2006-12-06 11:27 init -rw-r--r-- 1 rschulz users 6 2006-12-06 11:27 lang -rw-r--r-- 1 rschulz users 3 2006-12-06 11:27 languages -rw-r--r-- 1 rschulz users 983 2006-12-06 11:27 ldots_a.jpg -rw-r--r-- 1 rschulz users 797 2006-12-06 11:27 ldots.jpg -rw-r--r-- 1 rschulz users 1755 2006-12-06 11:27 rdots_a.jpg -rw-r--r-- 1 rschulz users 356 2006-12-06 11:27 rdots.jpg -rw-r--r-- 1 rschulz users 326 2006-12-06 11:27 translations.en -rw-r--r-- 1 rschulz users 961 2006-12-06 11:27 vdots_a.jpg -rw-r--r-- 1 rschulz users 308 2006-12-06 11:27 vdots.jpg CPIO is definitely a horse of a different color in the Unix archive tool world. Apart from the fact that it is the basis of the RPM format, it's really an archaic standard, having been supplanted by TAR in the large majority of uses. Naturally, "cpio --help" and "man cpio" will give you the information you need.
All that has done is removed my shell prompt from the screen. What next?
Randall Schulz --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2006-12-06 at 11:29 -0800, Randall R Schulz wrote: ...
CPIO is definitely a horse of a different color in the Unix archive tool world. Apart from the fact that it is the basis of the RPM format, it's really an archaic standard, having been supplanted by TAR in the large majority of uses.
I read once that the cpio archive is more solid. If the tar.gz archive is broken, all of it is broken. The backup program that claimed this explained that instead they used cpio, compressing each file separately: thus only one file would be irretrievable, not the whole archive.
Naturally, "cpio --help" and "man cpio" will give you the information you need.
I tried - info cpio, actually, man is almost empty - and I almost run away. It is difficult to understand, and it has no examples. I didn't realize the redirection was needed. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFdymFtTMYHG2NR9URAr5AAJsHkrO2IfbNyaLBR7yq2eOpcQI5mACgh/pw FAf4aTIbXs0QNrh15J4e6O8= =mNt0 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Wednesday 06 December 2006 12:35, Carlos E. R. wrote:
The Wednesday 2006-12-06 at 11:29 -0800, Randall R Schulz wrote:
...
CPIO is definitely a horse of a different color in the Unix archive tool world. Apart from the fact that it is the basis of the RPM format, it's really an archaic standard, having been supplanted by TAR in the large majority of uses.
I read once that the cpio archive is more solid.
If the tar.gz archive is broken, all of it is broken. The backup program that claimed this explained that instead they used cpio, compressing each file separately: thus only one file would be irretrievable, not the whole archive.
But the tradeoff with per-file compression is that you typically get rather poor compression for archives that contain many small files.
Naturally, "cpio --help" and "man cpio" will give you the information you need.
I tried - info cpio, actually, man is almost empty - and I almost run away. It is difficult to understand, and it has no examples.
I wish I could make "info" go away. I hate it. In addition to the atrocious tools used to access it, having the information I seek as fragmented as it is in the typical set of info pages is a disagreeable experience. Just try to figure out how to do something non-trivial with "sed" based on its info pages. You'll be pulling your hair out soon enough.
I didn't realize the redirection was needed.
As I said, it's a horse of a different color. RRS --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2006-12-06 at 12:45 -0800, Randall R Schulz wrote:
I read once that the cpio archive is more solid.
If the tar.gz archive is broken, all of it is broken. The backup program that claimed this explained that instead they used cpio, compressing each file separately: thus only one file would be irretrievable, not the whole archive.
But the tradeoff with per-file compression is that you typically get rather poor compression for archives that contain many small files.
Yes, the compression ratio is a bit worse, but that's something I will happily sacrifice for safety where backups are concerned. I have some backups of an entire HD done using nearly a hundred floppies - you can imagine when - and the whole backup is still fully retrievable, although some floppies have errors. They were made with PCBackup (dos version). It had compression with a data recovery algorithm that seems to work well after the years; the data recovery feature had a lower compression ratio, of course. I wish we had something similar for Linux - with current media, obviously :-)
I wish I could make "info" go away. I hate it. In addition to the atrocious tools used to access it,
Try "pinfo" instead. It doesn't make the contents better, of course, just easier to navigate ;-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFd4vvtTMYHG2NR9URAhQ/AJ9phbE57Bcgi0SCQ4gH/PqmAw5GuACeOR2h z6DfaehDxkDCl/URONNZJnE= =PpZs -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Wednesday 06 December 2006 19:35, Carlos E. R. wrote:
...
But the tradeoff with per-file compression is that you typically get rather poor compression for archives that contain many small files.
Yes, the compression ratio is a bit worse, but that's something I will happily sacrifice for safety where backups are concerned.
But what is this "safety" we're talking about? Usually if a file is corrupted, it's massively corrupted and if it's intact, then it's intact. It's a specious safety you get with the CPIO approach. Either you back-ups are intact or they're not.
I have some backups of an entire HD done using nearly a hundred floppies - you can imagine when - and the whole backup is still fully retrievable, although some floppies have errors.
Yes. Thank god we're now far beyond the floppy era. There is nothing that can meaningfully be done with a diskette as far as archiving or back-ups are concerned. And any "sneaker-net" style application is far better handled with a USB flash drive.
...
I wish I could make "info" go away. I hate it. In addition to the atrocious tools used to access it,
Try "pinfo" instead. It doesn't make the contents better, of course, just easier to navigate ;-)
Spoken like a true advocate of quasi-GUIs like Midnight Commander. Yuck. Gross. Eesh. No thank you. It's a bad and wholly unnecessary model. Konqueror's "info:" scheme presents them fine, but they're awful in their essence. RRS --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2006-12-06 at 21:12 -0800, Randall R Schulz wrote:
But the tradeoff with per-file compression is that you typically get rather poor compression for archives that contain many small files.
Yes, the compression ratio is a bit worse, but that's something I will happily sacrifice for safety where backups are concerned.
But what is this "safety" we're talking about? Usually if a file is corrupted, it's massively corrupted and if it's intact, then it's intact.
It's a specious safety you get with the CPIO approach. Either you back-ups are intact or they're not.
No, that's not the point. A single error in a tar.gz archive renders the whole archive useless, with all its contents - because it is the tar archive that is compressed. On the other hand, if the files are first compressed and then archived with cpio, a single media error will only inutilize the single file affected, not the whole. That's way safer, IMO. And not only IMO.
I have some backups of an entire HD done using nearly a hundred floppies - you can imagine when - and the whole backup is still fully retrievable, although some floppies have errors.
Yes. Thank god we're now far beyond the floppy era. There is nothing that can meaningfully be done with a diskette as far as archiving or back-ups are concerned.
You seem to not read the complete paragraph and then jump to the wrong conclusions too fast. I mentioned disquetes only because that application was able to make reliable backups with unreliable media, and thus I would like to have a modern app in linux able to do the same thing with modern media - not disquetes. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFeBw9tTMYHG2NR9URAnXeAJwNFEYZOpMPo8SqCJYJAcykgPfTcQCgkJCW Fl+ngkoE2Wijsheuf3q/tuU= =4Fcd -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Wednesday 06 December 2006 14:35, Carlos E. R. wrote:
I tried - info cpio, actually, man is almost empty - and I almost run away.
If you're using KDE, you can go to Konqueror and type in "info:cpio", it's not quite as painful. -- Glenn Holmer (Q-Link: ShadowM) http://www.lyonlabs.org/commodore/c64.html --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 2006/12/06 11:29 (GMT-0800) Randall R Schulz apparently typed:
On Wednesday 06 December 2006 09:04, Felix Miata wrote:
Naturally, "cpio --help" and "man cpio" will give you the information you need.
"Naturally" to you maybe. To me, they are like most man pages, lucid as mud. I changed gfxboot.cfg with s/-1/99/, but my output file only ever comes out to 512 bytes. -- "Let your conversation be always full of grace." Colossians 4:6 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Wednesday 06 December 2006 13:16, Felix Miata wrote:
On 2006/12/06 11:29 (GMT-0800) Randall R Schulz apparently typed:
On Wednesday 06 December 2006 09:04, Felix Miata wrote:
Naturally, "cpio --help" and "man cpio" will give you the information you need.
"Naturally" to you maybe. To me, they are like most man pages, lucid as mud. I changed gfxboot.cfg with s/-1/99/, but my output file only ever comes out to 512 bytes.
I don't know what that has to do with cpio, but if you're going go build kernels and change your boot configuration or do pretty much anything at such a low level of system adminsitration, then you're just going to have to deal with the command-line tools and their documentation. I can tell you that when cpio writes 0 files in output mode (-o), the result is always exactly 512 bytes (one block, where block has the old half-kilobyte definition). Randall Schulz --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Wed, 6 Dec 2006, Felix Miata wrote:
On 2006/12/06 17:27 (GMT+0100) Marcel Hilzinger apparently typed:
Am Mittwoch, 6. Dezember 2006 17:17 schrieb Felix Miata:
On 2006/12/06 15:53 (GMT+0100) Steffen Winterfeldt apparently typed:
BTW, the online help mentions how to configure it.
It says:
"Like it or hate it? Edit gfxboot.cfg in /boot/message to have it always or get rid of it."
/boot/message is apparently a binary file, and 379,904 bytes. How do you suggest to edit it?
cpio -i /boot/message
All that has done is removed my shell prompt from the screen. What next?
*sigh* # mkdir foo # cd foo # cpio -i </boot/message # edit something # find | cpio -H newc -o >/boot/message Steffen --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thu, 7 Dec 2006, Steffen Winterfeldt wrote:
# mkdir foo # cd foo # cpio -i </boot/message
# edit something
# find | cpio -H newc -o >/boot/message
Sorry, must be # find | cpio -o >/boot/message of course. Steffen --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 2006/12/07 12:27 (GMT+0100) Steffen Winterfeldt apparently typed:
On Thu, 7 Dec 2006, Steffen Winterfeldt wrote:
# mkdir foo # cd foo # cpio -i </boot/message
# edit something
# find | cpio -H newc -o >/boot/message
Sorry, must be
# find | cpio -o >/boot/message
of course.
Thank you. I had tried the syntax in the first example from cpio --help, and got nowhere figuring out how name-list works. I also tried the -O syntax, but got only 512 bytes file output each time. -- "Let your conversation be always full of grace." Colossians 4:6 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 2006/12/06 14:59 (GMT+0100) Marcus Meissner apparently typed:
On Wed, Dec 06, 2006 at 08:55:05AM -0500, Felix Miata wrote:
On 2006/12/06 10:32 (GMT+0100) jdd apparently typed:
just a question: is the install christmas screen just related to the system date, or is it to be the install screen for all the 8 mont release duration?
I have about 5 10.2s. Only the least recently updated retains the Christmas theme. :-(
Yes, we marked the ISO specifically for this one.
Well just kidding, there like is randonmness and specific days involved.
Is there a way to preserve it through future updates? -- "Let your conversation be always full of grace." Colossians 4:6 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (9)
-
Carlos E. R. -
Felix Miata -
Glenn Holmer -
jdd -
Marcel Hilzinger -
Marcus Meissner -
Randall R Schulz -
Steffen Winterfeldt -
Stephan Binner