Off-Topic > Off-Topic - Tiny Tux's Corner
Tiny Core get much ratings at distroratings top-10
newbody:
--- Quote from: yoshi314 on December 29, 2011, 06:33:09 AM ---
i think the simple way to do it is :
1. grab coreplus iso
2. unpack it somewhere (or you can browse the iso file with mc and copy files out)
3. replace kernel and initrd with new ones ( vmlinuz and core.gz ). you might to alter your bootloader config, or rename files, as tinycore.gz is now named core.gz. either rename core.gz or fix the syslinux config file on your usb
4. copy extensions from cde directory to your tce directory on usb
5. add contents of onboot.lst to your onboot.lst, just to be sure you do not miss any required extensions (especially the X related ones)
...
or, you can backup your mydata.tgz and extensions, reinstall tc from scratch and copy them back over, adding them from apps audit tool.
--- End quote ---
this one sounds interesting
--- Quote ---you can backup your mydata.tgz and extensions, reinstall tc from scratch and copy them back over, adding them from apps audit tool.
--- End quote ---
Yes and a Big No! I usually end up with a big black screen with a prompt that does not even know cd or ls
but do understand sudo reboot which is a blessing
But the mydata.tgz I do already have one such on the usb I will boot again to see if all works okay and then try out what you suggest. What fails me seems to be to know what files to include in the onboot.lst
When RobertS and others describe what I need to add then my brain go haywire. Too many choices
that I don't understand. I do trust I only use xvesa now so that is what I should be using.
Can I move from the 4.1 then or do I have to dowload later ones that are especially made for 4.2
and the repo seems to very many extra files and not only the tcz files.
should be easy but each time I try then it fails. But why give up. I will try again now when I can
reuse the mydata.tgz if it screw up. That would restore everything.
Here is my current grub4dos menu.lst on the usb formatted to fat32
title TinyCore 3.4.1 tce=sdb1/boot/TinyCore TinyCore tce=sdb1 opt=sdb1 home=sdb1
find --set-root /boot/tinycore.gz
kernel /boot/vmlinuz TinyCore waitusb=6 tce=sdb1 opt=sdb1 home=sdb1 showapps dmraid=on kmap=qwerty/fi-latin9
initrd /boot/tinycore.gz /boot/ntfs-3g.gz
Seems the initrd /boot/tinycore.gz /boot/ntfs-3g.gz make it fail to boot? Not sure why.
It boot good on tcl4.1 but when I change to core or coreplus then it fails.
Juanito. Thanks I will try to follow your advice too. I get back with a report to both of you
will take some time. I need to get everythign in place first
newbody:
Not sure what goes wrong. It looks very okay but still fails.
Ask for username and password when I try to start the flwm.
I am 4.1 now on the usb and try to edit the onbootlist and so on.
Now I ahve the menu.lst as this.
title CorePlus 3.4.2 tce=sdb1/boot/TinyCore desktop=jwm
find --set-root /boot/tinycore.gz
kernel /boot/vmlinuz TinyCore waitusb=6 cde showapps desktop=flwm_topside showapps dmraid=on kmap=qwerty/fi-latin9
initrd /boot/core.gz /boot/ntfs-3g.gz
I've also tested to take away this part /boot/ntfs-3g.gz but that does not help.
Maybe I need to change cde to tce? Because it is not a CD so maybe it goes wrong there?
But then I have two tce so how do I keep them apart? It already now try to load from the tce dir
but fail at it. Them marked as belonging to tcl4.1 maybe? Why else would them fail. What am I missing?
this part fails due to never reaching the desktop
4. Use apps audit to edit onboot to include Xprogs, Xvesa, flwm, wbar
So I will go back to what Joshi wrote to see if that explains how to get to desktop.
newbody:
Yoshi
Why would I need the uuid now? have never needed that one ever before? Is that something demanded now?
Re these two
4. copy extensions from cde directory to your tce directory on usb
5. add contents of onboot.lst to your onboot.lst, just to be sure you do not miss any required extensions (especially the X related ones)
Ah that would allow me to add the needed files to the existing optional dir hm I tried that someday before and
failed at that too but can give it a new try. Okay I try
yoshi314:
--- Quote from: newbody on December 29, 2011, 08:03:38 AM ---Yoshi
Why would I need the uuid now? have never needed that one ever before? Is that something demanded now?
Re these two
4. copy extensions from cde directory to your tce directory on usb
5. add contents of onboot.lst to your onboot.lst, just to be sure you do not miss any required extensions (especially the X related ones)
Ah that would allow me to add the needed files to the existing optional dir hm I tried that someday before and
failed at that too but can give it a new try. Okay I try
--- End quote ---
cde parameter only scans cdrom drives for "cde" directory with extensions. or special usb sticks which contain special isohybrid bootloader. which means it will most likely fail to find your extensions (and mydata.tgz)
you need to replace cde with specific tce= parameter.
Juanito:
--- Quote from: newbody on December 29, 2011, 07:57:53 AM ---this part fails due to never reaching the desktop
4. Use apps audit to edit onboot to include Xprogs, Xvesa, flwm, wbar
--- End quote ---
Maybe I misunderstood - I thought you had a working install of tc-4.1 that booted all the way to the desktop. If so, the instructions were given to start from the tc-4.1 desktop
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version