Boot Core with ntfs-3g extension

[casey]

hello Maro,
thank you very much for your help,

I'm sorry for saying this forum died, but in the past I have asked for help in forums such as Ubuntu and Mandriva, and I always receive immediate help, with many users always ready to help me,
but of course I realize that tiny core has not the spread of ubuntu and mandriva

I am Italian, and I have trouble understanding the English language,
I read your answer, but I did not understand everything 100%

can you upload your Core-current.iso with changes for ntfs-3g on a hosting site such as Mega, mediafire, rapidshare, etc and send me the link?

you can also add in ISO kmaps.tcz and in the line "append" lang=it kmaps=qwerty/it
for my Italian keyboard?

thanks

[maro]

Hmm, I'm not too keen to do all the work for you as it takes away your opportunity to learn something.

Nevertheless I've uploaded the ISO image I've produced yesterday to here (it will be there for the next five days). This should allow you to re-trace my steps and therefore (I hope) guide you in what is needed to customise TC for your particular use case.

[mocore]

tone keep it oscillating frequently!

but I must say that this forum is dead

"it's not dead it's just resting"  
( Monty Python - Dead Parrot - youtube.com/watch?v=Ldk5DWLd9KU `Sottotitoli italiano.` )




UltraISO virtualbox hmm 
it seems like you'r coming from a m$windows perspective

you want to  "Boot Core with ntfs-3g extension"
however to do this you need to know at least

 - boot loader (sysliinux in your case )
 - how syslinux menu starts linux
 - core specific file paths boot options within syslinux menu 

only the last item is specific to core , any way
 an alternative (and more windows centered )
 place to find more about bootloader's ect  you could try
reboot.pro/forum/140-boot-methods-tools
in the past i have found the forum usefull .
 & fyi
reboot.pro/forum/46-italiano/
i think you could  find 'molto aiuto' 

I don't have to do this you know! I'm a qualified brain surgeon! I only do this because I like being my own boss.

[casey]

Hmm, I'm not too keen to do all the work for you as it takes away your opportunity to learn something.

Nevertheless I've uploaded the ISO image I've produced yesterday to here (it will be there for the next five days). This should allow you to re-trace my steps and therefore (I hope) guide you in what is needed to customise TC for your particular use case.

thanks for the help

I asked you to load the iso on a hosting site because I wanted to study and learn as you had solved the problem,

I wrote ntfs-3g.tcz without leaving a space before the next line
and did not work,
instead leaving a space after ntfs-3g.tcz (so "ntfs-3g.tcz "), this works
this was my mistake,
and it was impossible to know, if I had not seen on your file onboot.lst

probably by editing the file onboot.lst from windows with notepad or notepad++ is not a space is left,
while the editor linux most likely be added to the decisive character


I ask two more help?
1) how do i automatically mount all drives at boot time?
(I mean all ntfs, fat32, ext3, ext4)

2) How can I add the ServerX to ISO and boot only from the command line when I need it?

EDIT: correction my error

[gerald_clark]

1. Core does not automatically mount anything.
Mount what you want in /opt/bootlocal.sh

2. This is what you need to learn.  As far as booting in text mode, add another boot stanza to your boot loader config file that has the text boot option.

[casey]

1)
in my bootlocal.sh there is only:
#!/bin/sh

what is the command to be added so that the kernel finds and automatically mounts all the drives in the computer in which you start?

2) in my iso Core_current.iso is not present ServerX,
which file TCZ I need to add to get the ServerX?

there is a command to start the ServerX only when you need it?

[bmarkus]

1)
in my bootlocal.sh there is only:
#!/bin/sh

what is the command to be added so that the kernel finds and automatically mounts all the drives in the computer in which you start?

There are no such command, it is not the Kernel 's jobs.

Tiny Core scans drives at boot time and creates mounting points in /mnt for FAT and EXT3/EXT4 type partitions, but doesn' mount them, except the first found with /tce directory. It is what you have to do in your program.

[casey]

but if I put in the file bootlocal.sh the commands for mount drives my pc, then if I then boot the ISO in another PC with a different drive, then it does not work properly,

how can I fix?

[bmarkus]

Describe expected functionality, what do you want to achive. Without details can't be answered.

[casey]

I would like to create an ISO to boot on any PC automatically mounts all drives

[gerald_clark]

Write a script that tries to mount all mountpoints in /mnt.  Call this script from or include it in /opt/bootlocal.sh.

Core is a tool set.   Honestly, it is not our job to build your system for you, or write these scripts.
You need to spend a lot of time reading the wiki, and experimenting until you understand how core works and
what you need to do to make it work the way you want it.

[casey]

I am not able to write a script that mounts all drives,
I ask someone who knows how to write the script, to help

[maro]

...
I wrote ntfs-3g.tcz without leaving a space before the next line
and did not work,
instead leaving a space after ntfs-3g.tcz (so "ntfs-3g.tcz "), this works
this was my mistake,
and it was impossible to know, if I had not seen on your file onboot.lst

probably by editing the file onboot.lst from windows with notepad or notepad++ is not a space is left,
while the editor linux most likely be added to the decisive character
...

Just to clarify: The space character found in my 'cde/onboot.lst' is insignificant (it was rather an "accident"), what is significant is the new-line character (i.e. '\n') to terminate the line. In my (rather rushed) test I did not eyeball the file created in a Windows editor, as things were working as expected. I therefore overlooked the trailing space character (as well as the surplus carriage return).

Note: In an 'onboot.lst' file each extension name needs to appear on a line terminated with a newline character. Space or carriage return characters are seemingly being ignored. Likewise it is optional to terminate an extension name with '.tcz' (i.e. "NAME" will work as well as "NAME.tcz").

[casey]

the problem was that \n was missing in my onboot.lst
and adding space and then pressing enter was added \n

you can help me solve the other problems?

thanks

[gerald_clark]

What is your purpose for creating this CD?
You don't appear to have enough linux knowledge make use of it once you are done.
Perhaps user oriented distro would be more suitable.