dCore Import Debian Packages to Mountable SCE extensions > dCore X86

remastering dCore ?

(1/3) > >>

bernhard:
I would like to remaster dCore for being able to use my german Keyboard and/or having the ISO on an usb stick, but I am failing miserably, when I try to follow my own instructions created some time ago for CorePlus (see wiki: http://wiki.tinycorelinux.net/wiki:remastering_kmap_iso). ezremaster complains about a wrong ISO.

Any help appreciated.

--
  Bernhard

Jason W:
Posting ISO images of dCore I have yet to do, and this reminds me I need to get it going.  I will do that now.

I have not used ezremaster in a long time, I personally have been playing with Unetbootin to make bootable usb's so I can't really help troubleshoot ezremaster at this point.   I will put up some ISOs and we can go from there.

Misalf:
As an alternative to EZremaster, if there is no need to add or change files that are specifically related to Tiny Core (i.e. just editing boot loader config), ISO Master (isomaster.tcz) has been a quick and easy solution for me.

Jason W:
I am using an ISO of dCore that has been put to a bootable usb via unetbootin.  I have one 100mb fat32 partition that unetbootin places the boot files, and about 7.9 gigs of ext4 space for the tce directory and data.  Before, dCore was basically to use the grub boot loader of an existing Linux install.  Being able to install it on a bootable usb along with a data partition makes it much more nomadic.  And once installed to usb, the syslinux.cfg file is editable so the boot parameters can be changed without having to further remaster.

I will create the ISO creating routine for the x86 dCore ports tomorrow and upload them.

Just make sure to use the "importsce -r " option when using a usb partition as the tce directory to prolong the life of the usb drive.

EDIT: Just saw Misalf's post while posting this one.  That is another option also.

Misalf:
I usually use the first partition (so Windows can see it) of my bootable USB drive for regular data storage (FAT) without any sensitive OS data on it.
The second one contains boot loader files and several .ISOs (+ f.e. persistant TC data) for booting via grub2. I love that Core is using the most reasonable boot code for that: "iso=...".
You'll take care of that, right? (:

Navigation

[0] Message Index

[#] Next page