Tiny Core Linux

Tiny Core Base => TCB Q&A Forum => Topic started by: Det on May 16, 2010, 01:47:32 PM

Title: [Solved] Creating 64-bit TC iso
Post by: Det on May 16, 2010, 01:47:32 PM
So how would I do this with the tinycore64.gz (http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/3.x/release_candidates/distribution_files/tinycore64.gz) and bzImage64 (http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/3.x/release_candidates/distribution_files/bzImage64)?

Will it be as easy as to just:


- Oh, and thanks 8)
Title: Re: Creating 64-bit TC iso
Post by: curaga on May 16, 2010, 05:02:16 PM
Yes, nothing more complicated than that.

Do note that Xvesa doesn't work on 64 bits; it's Xorg or text mode.
Title: Re: Creating 64-bit TC iso
Post by: maro on May 16, 2010, 05:22:53 PM
That looks about right (mind you I have not tried it).

One thing I'm not clear is how you deal with the fact that 'bzImage64' is a different name than 'bzImage' (and likewise 'tinycore64.gz' is not 'tinycore.gz'). You could rename the copied files, but that would be IMHO a bad idea since you loose the ability to distinguish between the 32-bit vs. the 64-bit ISO image. So a change in the boot loader configuration (e.g. '/boot/isolinux/isolinux.cfg) would be required.

Furthermore I'm not sure what you try to achieve with "then dd to a partition/set grub". An ISO image should not be "cloned" to a hard disk, there are many reasons why that would not work. I assume you mean to use the files from the '/boot' directory of this 64-bit ISO image when following the installation (http://tinycorelinux.com/install.html) instructions.
Title: Re: Creating 64-bit TC iso
Post by: curaga on May 16, 2010, 05:35:51 PM
grub4dos can boot iso images, and an isohybrid (part of syslinux) handled iso image can be dd'd to a disk, usually an usb one. At least these come to my mind at first for the mentioned things.
Title: Re: Creating 64-bit TC iso
Post by: Det on May 17, 2010, 06:54:15 AM
Jesus, I thought this process in the way that I would clone the "setup" to the partition instead of actually just installing it there.

But a question came to my mind which is that what is the difference between genisoimage, mkisofs, mkhybrid and isohybrid?

Which I guess would be a question of: what is the difference between iso image and a hybrid?
Title: Re: Creating 64-bit TC iso
Post by: bmarkus on May 17, 2010, 07:02:04 AM
Quote from: Det on May 17, 2010, 06:54:15 AM
Jesus, I thought this process in the way that I would clone the "setup" to the partition instead of actually just installing it there.

But a question came to my mind which is that what is the difference between genisoimage, mkisofs, mkhybrid and isohybrid?

Which I guess would be a question of: what is the difference between iso image and a hybrid?

It may help a bit

http://wiki.geteasypeasy.com/Hybrid_ISO/IMG_format

Title: Re: Creating 64-bit TC iso
Post by: Det on May 17, 2010, 10:09:33 AM
Yeah, that made the perfect sense.
Title: Re: [Solved] Creating 64-bit TC iso
Post by: sird on August 25, 2010, 10:34:14 AM
Hi all,

I've created a microcore usb stick the way described in the first post.
Code: [Select]
uname -r suggest that I have a 64 bit kernel.
Code: [Select]
file (after istalled) however cannot find any 64-bit elfs in the sbin folder.. what gives?

In addition I cannot run downloaded 64-bit software <http://www.luxrender.net (http://www.luxrender.net)> the 32 bit versions run fine.

I'm trying to make a 64 bit usb stick that allows me to run render slaves in my 32bit WinXP office by booting into microcore over night. (dont' worry I'm allowed)

Any one successfully running a 64 bit microcore system? Any ideas what might be wrong?

Tiny/Microcore is great by the way incredible fast and straightforward!

cheers
Title: Re: [Solved] Creating 64-bit TC iso
Post by: curaga on August 25, 2010, 10:41:29 AM
It's only the kernel currently, to allow all ram and capabilities of HW to be addressed.
Title: Re: [Solved] Creating 64-bit TC iso
Post by: sird on August 25, 2010, 11:15:40 AM
Quote from: curaga on August 25, 2010, 10:41:29 AM
It's only the kernel currently, to allow all ram and capabilities of HW to be addressed.

Alright, thanks for the quick response!