Tiny Core Linux
Tiny Core Base => TCB Q&A Forum => Topic started by: casey on October 20, 2013, 10:45:27 PM
-
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
-
Because that is what it is supposed to do. That menu selection does not read cde/onboot.lst.
-
we can solve this problem?
-
You are booting your remastered CD, right?
Look at your isolinux.cfg file.
-
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
-
The coreplus ISO includes ezremaster.
-
I also tried with remaster,
but the changes works on the server x, but do not work by starting the command line
-
Show us your isolinux.cfg file.
-
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?
-
Try it on real iron with a real CD.
-
I have tried, but not works
-
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
-
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.
-
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?
-
@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 (http://www.catb.org/esr/faqs/smart-questions.html#intro) 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
-
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
-
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 (http://rghost.net/49814811) (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.
-
tone keep it oscillating frequently!
but I must say that this forum is dead
"it's not dead it's just resting" :D
( 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' ;D
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.
-
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 (http://rghost.net/49814811) (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
-
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.
-
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?
-
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.
-
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?
-
Describe expected functionality, what do you want to achive. Without details can't be answered.
-
I would like to create an ISO to boot on any PC automatically mounts all drives
-
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.
-
I am not able to write a script that mounts all drives,
I ask someone who knows how to write the script, to help
-
...
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").
-
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
-
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.
-
I'm an old programmer (since the days of dos)
I need a basic command line to start my software from a CD or pen drive, on all computers directly through the bios, without needing Windows or other operating systems
also using a distro oriented should modify it to make it a command line with ntfs support and mount all drives
and use tiny core because preparing it with your help, will help me to learn a lot about Linux
I know many linux commands, use the command line very well, but I do not know how to configure/prepare and compile, for this I would like to learn
-
What software is it you want to run?
Why do you need ntfs?
Why do you want to mount all drives?
Without a clear definition of the goal, it is difficult to give recommendations.
-
I'm designing a software that boots from CD to repair a windows system not functioning properly, and to make backups of personal data on external hdd
I need to see all the drives and access to drive ntfs
-
There are CDs for this already. To name a few:
System Rescue CD
Recovery is Possible
Ultimate Boot CD
And by the way, automounting your damaged filesystem is a really bad idea.
-
If you want to edit files for UNIX-like operating systems under windows, then you must always run 'dos2unix' on them, this is not even particular to Linux.
-
Gerald_clark
I have to create this program, which will be fully automated for my clients,
linux distro for recovery are another matter, that have nothing to do with my program
I asked for help to mount all drives and add the ServerX to my mini-iso
you're making me the third degree without help
-
If you want to edit files for UNIX-like operating systems under windows, then you must always run 'dos2unix' on them, this is not even particular to Linux.
thanks for the advice
-
The third degree was to attempt to help you find something ready made you could use.
Good luck with your custom programming.
-
@maro
can you help me for solve other problems?
thanks
-
Not sure what you refer to as "other problems", but the intended indiscriminate force mounting of filesystems at boot has a high potential to create serious problems in general, and more particularly so with ntfs in read-write mode.
-
no problem,
I ask only one command line prompt and with all the mounted drives,
I'll take that responsibility on the potential consequences to the file system,
15 years ago based my low-level software on DOS,
which gave me access to all drives and a command line,
DOS is now obsolete, does not read ntfs, does not support LBA48, does not support AHCI, reads only a few dozen mb of ram, does not support long file names,
for this I am trying to build me a replacement based on a linux operating system that is very good, in some respects the best
-
Hi casey
Read this thread:
http://forum.tinycorelinux.net/index.php/topic,12356.msg66630.html#msg66630
You will find knowing how to write a script (batch file) is a very useful skill to have when working under Linux.
-
Hi casey
Read this thread:
http://forum.tinycorelinux.net/index.php/topic,12356.msg66630.html#msg66630
You will find knowing how to write a script (batch file) is a very useful skill to have when working under Linux.
thanks for reporting,
I will study the topic given to you, and I will try to create a working script,
can you help me to enter the ServerX in my Core-current.iso?
and let me know how to start it when I need it?
I need that in ServerX appear only the command line, without the bar style application Mac OS