Off-Topic > Release Candidate Testing

microcore_v2.8rc4

<< < (2/4) > >>

vitex:

--- Quote from: roberts on January 20, 2010, 01:51:43 PM ---
--- Quote from: vitex on January 20, 2010, 12:30:02 PM ---Could you please clarify your plans for extensions placed in /opt/tce[/optional]?

When booting, the current implementation of tce-setup


* does not load extensions listed in /opt/tce/onboot.lst,
* does not load *.core.gz components in /opt/tce, and
* does load extensions with links from /opt/tce to /opt/tce/optional.
Is this the long-term behavior?

--- End quote ---
...

Now, instead of making does not work proclamations perhaps you can share your specific setup so that progress can be made.

--- End quote ---

The following output was generated by booting a remastered version of
the microcore_2.8.rc4 ISO:


--- Code: ---$ version
microcore_2.8rc4

$ showbootcodes
initrd=/boot/microcore.gz xvesa=800x600x16 vga=788 quiet max_loop=255 BOOT_IMAGE=/boot/bzImage

$ ls -lR /opt/tce
/opt/tce:
-rw-r--r--    1 root     root      3003728 Jan 20 14:15 Xlibs.core.gz
-rw-r--r--    1 root     root           48 Jan 20 14:15 Xlibs.core.gz.md5.txt
-rw-r--r--    1 root     root       660805 Jan 20 14:16 Xprogs.core.gz
-rw-r--r--    1 root     root           49 Jan 20 14:16 Xprogs.core.gz.md5.txt
-rw-r--r--    1 root     root       322694 Jan 20 14:16 Xvesa.core.gz
-rw-r--r--    1 root     root           48 Jan 20 14:16 Xvesa.core.gz.md5.txt
-rw-r--r--    1 root     staff          13 Jan 20 19:42 onboot.lst
drwxr-sr-x    2 root     staff          80 Jan 20 20:46 optional

/opt/tce/optional:
-rw-r--r--    1 root     root        94208 Jan 20 15:02 dropbear.tcz
-rw-r--r--    1 root     root           47 Jan 20 15:02 dropbear.tcz.md5.txt

$ cat /opt/tce/onboot.lst
dropbear.tcz

$ df
Filesystem           1K-blocks      Used Available Use% Mounted on
tmpfs                   112956     12308    100648  11% /
tmpfs                    62752         0     62752   0% /dev/shm

--- End code ---

This output demonstrates my first two points.  The third point is
evident from the following code in tce_setup:


--- Code: ---if [ "$(ls -A /opt/tce)" ]; then
TCEDIR=/opt/tce
FILELIST=`ls "$TCEDIR"/*.tcz`
for FILE in $FILELIST; do process; done
fi

--- End code ---

roberts:
Thanks for the clue that you are running a remaster!
I am going walk before I run. I want to get the bugs out before I try testing remastered versions.
As much as I try to avoid having multiple locations for everything it keeps coming up!

roberts:
Since you are making a remaster, it would seem to me to make more sense to place those extra initramfs images *.core.gz with the bzImage and mircocore.gz. That is the preferred location.

vitex:

--- Quote from: roberts on January 20, 2010, 04:50:11 PM ---Since you are making a remaster, it would seem to me to make more sense to place those extra initramfs images *.core.gz with the bzImage and mircocore.gz. That is the preferred location.

--- End quote ---

Are you planning to keep /opt/tce?  Tce-setup currently loads .tcz files from /opt/tce and from the directory to which /opt/.tce_dir points.  Tce-setup loads .core.gz files from the directory to which /opt/.tce_dir points but not from /opt/tce.  If you are going to keep /opt/tce, then its seems natural to add the few lines of code to tce-setup so it also loads .core.gz files from /opt/tce.

Remastering seems to be easier for me if the .core.gz files are in /opt/tce, but I can do it either way. It is your choice.

curaga:
Just a thought, if one plans to include all three core.gz always loaded in /opt/tce, wouldn't it be simpler to start with the TC iso?

Navigation

[0] Message Index

[#] Next page

[*] Previous page