dCore Import Debian Packages to Mountable SCE extensions > dCore X86

building my own dCore-Image

<< < (2/2)

curaga:
/tmp/builtin IIRC, but I don't know if that applies to dcore.

Jason W:
/tmp/builtin is the correct  location to place already imported SCEs and they will be loaded into RAM and installed. 

Did you use dCore-usbinstall to install to the usb stick?  It does a good job of setting up a TCE directory on the stick and it is located by filesystem label.  And also sets a waitusb command so the TCE directory on the stick is always found.  But placing SCEs in /tmp/builtin loads them the same except is more resource consuming of course. 

For those who don't know how to remaster dCore, below are the scripts I use to pack and unpack images. 

Run with root privileges the following as "dCoreunpack.sh dCore-stretch.gz" or another image name, in the same directory as the gz image:

--- Code: ---#!/bin/sh

CORE="$1"

if [ ! -d rootfs ]; then
mkdir rootfs
else
rm -r rootfs/*
fi

cd rootfs

zcat ../"$CORE" | cpio -i -H newc -d
 
cd -


--- End code ---

Run with root privileges the following as "dCorepack.sh dCore-stretch.gz" , in the same directory as the rootfs directory:

--- Code: ---#!/bin/sh

CORE="$1"
REPO=`cat rootfs/usr/share/doc/tc/repo.txt`
RELEASE=`echo dCore-"$REPO":$(date "+%Y.%m.%d.%H.%M")`
echo "$RELEASE" > rootfs/usr/share/doc/tc/release.txt
echo "$RELEASE" > dCore-"$REPO".latest
cd rootfs

find | cpio -o -H newc | gzip -2 > ../"$CORE"
cd ..
md5sum "$CORE" > "$CORE".md5.txt

cd -


--- End code ---

minnten:
I have to thank you many times, without you I would probably still search in the depths of the WWW.

It worked, thanks

@ Jason W: Keep it up, great project

mocore:

I dont think i understand the meaning of

--- Quote from: minnten on October 01, 2018, 06:30:22 AM ---Now I have done tests with an installation on sticks, but they do not work as intended, because I do not get the tce folder cleanly bound.

--- End quote ---

Do you mean you have aproblem using the "tce=" bootcode ?
eg that  "tce=sdb3"  fails some how ??.

Jason W:
Actually, device naming among USB drives can change across reboots, so using the format "tce=sdb3" may not work every time.  Better to use filesystem label or UUID. 

dCore-usbinstall uses label, and you specify a label for the USB drive in the dCore-usbinstall process and the USB is given that label and it is added to the boot command line.  Very easy and no chance for error in creating the entries in the boot command line.  Below is the entry in the boot file when I just made a dCore-stretch USB, and choosing the name dCore for the label:

append initrd=/dCorestretch.gz quiet waitusb=30:LABEL=dCore rd.udev.log-priority=0 net.ifnames=0 tce=LABEL=dCore/dCore-stretch

Navigation

[0] Message Index

[*] Previous page