Boot Core with ntfs-3g extension

[casey]

hello guys

I have downloaded the ISO core (Core-current.iso) of 9mb

and I added the extension ntfs-3g.tcz (downloaded from the "Browse TCZs) in the folder /cde/optional in ISO (Core-current.iso)
in /cde I created the file onboot.lst (with text: ntfs-3g.tcz)
and I added the text "cde" in the lines "append" in /boot/isolinux/isolinux.cfg

why the extension ntfs-3g.tcz is not loaded at boot?


if I do this procedure to TinyCore (TinyCore-current.iso) of 15mb, and then start choosing the menu "Boot TinyCore" will start the X server with ntfs-3g.tcz,
but choosing the menu "Boot Core (command line only) starts the command line but not ntfs-3g.tcz

why??


please help,

thanks

[gerald_clark]

Because that is what it is supposed to do.  That menu selection does not read cde/onboot.lst.

[casey]

we can solve this problem?

[gerald_clark]

You are booting your remastered CD, right?
Look at your isolinux.cfg file.

[casey]

I modified the ISO manually with software UltraISO,
and I have also modified the file isoconfig.cfg adding text cde in the append line

the version I use is the Core 9mb

[gerald_clark]

The coreplus ISO includes ezremaster.

[casey]

I also tried with remaster,
but the changes works on the server x, but do not work by starting the command line

[gerald_clark]

Show us your isolinux.cfg file.

[casey]

display boot.msg
default microcore
label microcore
   kernel /boot/vmlinuz
   initrd /boot/core.gz
   append loglevel=3 cde lang=it kmaps=qwerty/it

label mc
   kernel /boot/vmlinuz
   append initrd=/boot/core.gz loglevel=3 cde lang=it kmaps=qwerty/it
implicit 0   
prompt 1   
timeout 300
F1 boot.msg
F2 f2
F3 f3
F4 f4


I added the text "cde" at line "append",
and I created a folder "cde" in the root of the ISO that contains the ntfs-3g.tcz
but during the boot does not load this extension

I use Virtualbox for test

how can I fix?

[gerald_clark]

Try it on real iron with a real CD.

[casey]

I have tried, but not works

[casey]

Gerald_clark thank you for your answers,

but I must say that this forum is dead,
one week after my question, no one has been able to respond and give me the help I needed,

Tiny Core had the potential to be a big project, but it really is not supported

this forum is really a cemetery,

unthinkable to continue my project to use Tiny Core as the basis for a powerful software that I'm planning, which had to be booted from a CD via the bios

I have to rely on another mini distribution, which is fully supported,
you must rely on a community to overcome their limitations

thanks

[gerald_clark]

The Wiki covers remastering quite thoroughly.
As I said before, try ezremaster.
It is not rocket science,
Read the wiki until you understand how core works.

[casey]

I tried with ezremaster, but it does not work,
only works by starting the x server, but does not work from the command line

I have also read the wiki, but I have not found the solution,

but in this forum you only answer?
there are other experts who understand the problem?

[maro]

@casey: First up, IMHO you should be a bit more careful with the tone of your statements (in particular as a new member). In my view when a highly experienced member chooses to spent his time to answer your questions it pays for you to also take care how you phrase your postings. I found it helps to be mindful of what Eric Raymond wrote about this matter. In the end, I don't think one can expect the same kind of responses from a community forums as you would get when paying mega-bucks for a 24/7 support contract.

That said, I've now re-tested what you describe in the OP: using 'Core-current.iso' as the basis (and ISO Master to manipulate it) I've added the 'ntfs-3g.tcz' and 'ntfs-3g.tcz.md5.txt' files to a newly created 'cde/optional' directory. I then created a 'cde/onboot.lst' file which only had the single entry of: 'ntfs-3g'. Finally, I added the 'cde' boot code to the 'append' line of the 'microcore' stanza (i.e. line 6) in 'boot/isolinux/isolinux.cfg'.

I found that it is easy to add the correct boot code to the wrong (e.g. a non-default) stanza (e.g. the 'mc' one) in this boot loader configuration file. Having done all this, the new ISO image booted with the 'ntfs-3g' extension loaded after boot (just like I'd expected).

BTW, to confirm what boot codes are handed over to the kernel just run: cat /proc/cmdline