Off-Topic > Off-Topic - Tiny Core Lounge

Remastering Core does not work, prints stacktrace

<< < (2/3) > >>

Rich:
Hi nim108

--- Quote ---should make no difference if it's a VM or not though
--- End quote ---
I wouldn't know, I work in a real world, not a virtual one.

curaga:
Do try to do it from within TC; that is where the official images are done from, using busybox tools.

tinypoodle:
Besides from already mentioned recommendations, I would suggest you experiment with dynamic remasters - while leaving core.gz untouched.

nim108:

--- Quote from: tinypoodle on November 09, 2012, 12:33:45 PM ---Besides from already mentioned recommendations, I would suggest you experiment with dynamic remasters - while leaving core.gz untouched.

--- End quote ---
Actually, this is what we originally had (an untouched core.gz and customize.gz which includes remaster content, which load just fine from SysLinux), but we later discovered we also have to kexec another variation of TC and I am fairly certain kexec does not allow multiple initrds.

I will have to go with curaga's recommended solution of setting up a TinyCore build environment and doing all these remasters in there with the proper versions of the BusyBox tools.

coreplayer2:
All my x86 remaster's are build on VirtualBox VM's  whilst x64 builds are built in the  always booted to tc

With flawless remastered copies at the rate of on average of one each week, I have to say all the issues i experienced in the early days were of my own doing.   ::)

I use ezremaster exclusively for all x86 builds, and custom frugal based builds for x64 remasters.  Which are usually deployed ass images for USB thumb drives.

YOu'll find the ezremaster script a vital source of information if you're rolling your own..

Navigation

[0] Message Index

[#] Next page

[*] Previous page