Tiny Core Linux
Tiny Core Base => TCB Talk => Topic started by: manit123 on September 04, 2012, 08:34:21 AM
-
I have been able to install tiny core on second partition(ext2) of my USB stick(16GB , first being fat 32 to be read on windows and linux OS).
Here is what I did
mounted coreplus.iso to /tinycorecd
gave /tinycorecd/boot folder for core.gz
selected frugal , existing partition , install boot loader , mark partition active bootable
waitusb=9 option
core and x desktop - nothing else selected
When I boot from USB , I get a 'tiny core' entry which on entering drops me to a prompt with $. no X window.
-
Is the tce folder present and populated with extensions on your second partition?
What happens when you enter "startx"?
-
try do a df and see if any real disks are mounted presumably not sounds like it cant find the tce directory, try adding boot code tce=sda2 or what ever partition you installed it on
-
This is an example how I'm using my USB sticks.
Partitions:
1) Small, 64MByte FAT - primary 1
2) 1-2GByte LINUX Ext4 - primary 2 - Yes, journaling. USB stick is cheap and last long enough. YOr lost data and time due to non-journaling (ext2) file system is more valuable
3) Depending on the size, additional Ext4 partion(s)
First, TC installed on the FAT partition with core2usb, than tce directory is moved from the first partition to the LINUX partition. Reboot.
That's all. No any change in config files needed. Make sure no other tce directories on other TC readable partitions.
-
Make sure you don't forget the 'waitusb=5' ( Or one of the LABEL/UUID versions ) boot option.
-
'waitusb=9' helped
bmarkus , you don't have any bigger partition of fat or fat32 .
You cannot copy much from computer with windows OS (hosting your USB) ?
Can I have multiple onboot.lst on same partition ?
Because I want one with ALSA while other with OSS .
I know , there is alsa-oss oss_alsa for emulating one over another .
-
Hi manit123
'waitusb=9' helped
Don't just use the lowest value that works. Add a couple of seconds to allow for variations in boot time. Or better
yet, use one of the following:
waitusb=30:LABEL= or
waitusb=30:UUID= and identify your device by label or UUID.
-
Yes, you can have multiple extension lists, use the lst bootcode.
-
if i write lst=with-oss.lst
where the mentioned file is present in tce folder of USB . Will that work ?
-
that worked.
-
i wonder , is it possible to add an entry in onboot.lst that says 'alsa/alsa.tcz' ?
I mean , will it take that file from 'alsa' folder present in 'folder containing onboot.lst'
-
Hi manit123
No, extensions are loaded from the tce directory.
-
Having a distinct "tce=" dir altogether would be a valid approach.
-
In my case , I have all tcz files in tce/optional folder on USB stick which get loaded as written in tce/onboot.lst
I meant , can I create folder inside 'optional' and write entry in onboot.lst as 'something/something.tcz' and expect tiny core to load files by going into folders present in tce/optional .
Will that work ?
Also , I will try it myself ASAP.
-
Hi manit123
That might work since tc-config calls tce-load which uses a path to load the extension. Make sure the entry
does not contain a leading /
-
I will try that and report 'whatever happens' here.
EDIT
That went well .
I created a folder named 'orig' in optional and added to onboot.lst entries like
orig/something.tcz
ALSo , OS used the dep file in 'orig' to load dependency .
-
That is not a good idea.
The auditing scripts will not look for these files.