Need help with gfxboot install to PCLinuxOS Education remaster

[melodie]

Hi,

I got issues with that since the pclinuxos theme update. I have succeeded in putting the plymouth splashboot back, with the command lines, but I feel like I don't have the hand on the Grub side of the theme.

I have a file "message" which contains the file back.jpg, as well as a bunch of other files. I extracted them with cpio, and with the whole bunch redid a gfxmenu file. →

Code:

ls | cpio  -o --io-size=502784 > gfxmenu

in /usr/share/gfxboot/theme/pclosedu_gdm there are the directories boot/ and install/

In "boot" I put the file "message" which contains everything : the back.jpg and other files, and in "install" I put the content of the archive "message", without "message" itself.

In /boot I replaced the gfxmenu by the one created with the files contained in the original "message" archive provided to me by Timeth.

Up to now I can't get an iso with the gfxmenu chosen for this version although I could see it at work in the installed version. I have done 4 versions in a row, not one with the right gfxmenu and the last one does not even find it and does not boot.

I would like advices and the right methods for a Grub splash install strongly sticked.

Thanks,
Mélodie

[melodie]

Hi,

I compared the content of the PCLinuxOS gfxboot theme and the pclosedu gdm, did some changes. I also started Lxde mini and compared with what Neal did, in the LXDE gfxboot theme, and got some conclusions.

I am now starting a new Edu remaster in Vbox, it now seems ok. I'll try Neal's way in a next and maybe last Edu... depending on what the testers will tell me at the forum, once uploaded.

Bye the way, I found a trick with cpio, for the "message" archive. To avoid getting "message" in the "message" archive, send the new "message" file elsewhere than in the current directory.

ie, in the "install" directory which goes under /usr/share/gfxboot/themes/Theme-name/install:

Code:

# ls
af.hlp*    el.hlp*       gu.hlp*  lt.hlp*         pt.hlp*       welcome.jpg*
ar.hlp*    en.hlp*       hr.hlp*  mr.hlp*         ro.hlp*       xh.hlp*
back.jpg*  es.hlp*       hu.hlp*  nb.hlp*         ru.hlp*       zh_CN.hlp*
bootlogo*  et.hlp*       it.hlp*  nl.hlp*         sk.hlp*       zh_TW.hlp*
ca.hlp*    fi.hlp*       ja.hlp*  pa.hlp*         sv.hlp*
cs.hlp*    fr.hlp*       ko.hlp*  pclinuxos.pcx*  text.jpg*
da.hlp*    gfxboot.cfg*  ky.hlp*  pl.hlp*         timer_a.jpg*
de.hlp*    gl.hlp*       langs*   pt_BR.hlp*      uk.hlp*

Code:

# ls | cpio -o > /home/guest/Desktop/message

instead of:

Code:

# ls | cpio -o > message

Then the new archive "message", created elsewhere than in the current directory, does not contain itself.

I have one question about the gfxboot directories structure : what is the symlink "PCLinuxOS → /usr/share/themes/PCLinuxOS", which is under /usr/share/gfxboot/themes/PCLinuxOS, (besides the directories "boot" and "install") meant for ? What is exactly it's use ?

Regards,
Mélodie

[timeth]

Bye the way, I found a trick with cpio, for the "message" archive. To avoid getting "message" in the "message" archive, send the new "message" file elsewhere than in the current directory.

Yes, after you "unzip" the message archive and make changes, you must delete the original message archive before compressing it again, or, take the original message file out before compressing.

I have one question about the gfxboot directories structure : what is the symlink "PCLinuxOS → /usr/share/themes/PCLinuxOS", which is under /usr/share/gfxboot/themes/PCLinuxOS, (besides the directories "boot" and "install") meant for ? What is exactly it's use ?

Strange. This file links to itself infinitely. I've often wondered what the purpose of this is but have never asked.

[melodie]

Bye the way, I found a trick with cpio, for the "message" archive. To avoid getting "message" in the "message" archive, send the new "message" file elsewhere than in the current directory.

Yes, after you "unzip" the message archive and make changes, you must delete the original message archive before compressing it again, or, take the original message file out before compressing.

Hi Tim,

It seems that it is created even if it's not anymore in the directory with the other files. When I have sent the "message" elsewhere it did not anymore.

ie:
$ su
passwd //we want to be root to get/setup/keep the right ownership on the files
# ls
(lots of files)

Code:

# ls | cpio -o /home/user/Desktop/message

gave a good result.

I have one question about the gfxboot directories structure : what is the symlink "PCLinuxOS → /usr/share/themes/PCLinuxOS", which is under /usr/share/gfxboot/themes/PCLinuxOS, (besides the directories "boot" and "install") meant for ? What is exactly it's use ?

Strange. This file links to itself infinitely. I've often wondered what the purpose of this is but have never asked.

I tried to remove the symlink, next remaster the bootloader could not find it's gfxboot and didn't boot at all. Just saying :

boot_
could not find gfxboot

boot_
could not find gfxboot (or something like that).

I restored the symlink, next remaster booted ok. So I still don't know how that works.

[timeth]

It seems that it is created even if it's not anymore in the directory with the other files. When I have sent the "message" elsewhere it did not anymore.

ie:
$ su
passwd //we want to be root to get/setup/keep the right ownership on the files
# ls
(lots of files)

Code:

# ls | cpio -o /home/user/Desktop/message

Oh I see.    It does re-create itself. Thanks.

This command doesn't work for me.  # ls | cpio -o /home/user/Desktop/message

I must insert ">" like this   # ls | cpio -o > /home/user/Desktop/message

Also, I found this tutorial which is helpful. http://www.cyberciti.biz/faq/how-do-i-use-cpio-command-under-linux/

[melodie]

I must insert ">" like this   # ls | cpio -o > /home/user/Desktop/message

Also, I found this tutorial which is helpful. http://www.cyberciti.biz/faq/how-do-i-use-cpio-command-under-linux/

Sorry I forgot the ">" !! That happens to me while I type the command too, but as I get an error message I correct it on the fly...