Tiny Core Linux
Tiny Core Extensions => TCE Talk => Topic started by: aswjh on September 29, 2011, 12:24:32 AM
-
If i want to tc load extenssions on the partition(ntfs),i must add tce=hd(x).
-
Where is TC booted, CD, USB, HDD, ??
-
usb boot
-
Do not use NTFS. My advice is to have a small FAT partition, say 64Mbyte to make moving files between TC and Windows easy. Create a 2nd partition with ext4 partition, make a /tce directory and use as your TC drive. It is my setup used.
One can argue against ext4 and advice ext2. No!
- ext4 journaling will protect you against corruption which happens frequently and save you
- lifetime of USB stick today is long enough not to afraid using journaling
- USB sticks are cheap
- your time and data are more costly
-
ok,thanks.
-
At aswjh - you said "If i want to tc load extenssions on the partition(ntfs),i must add tce=hd(x)."
Can you elaborate - exactly where I might put that command?
At bmarkus - I agree USB is cheap and probably a great way to go for folks who have them. However the reality is that many people "only have a laptop" with an NTFS drive - so making this "easy and painless" for them entails:
a) loading TCE files - optional - everything to C:\TCE C:\OPTIONAL etc. and
b) having it work right out of the hole - WITHOUT having to muck around with bootlocal.sh
Then later - when they have time and money and access to a store that carries USB drives - they can set up a FAT32 USB drive, since that device is easily accessed by both Windows and Linux.
The advantages of EXTx are well documented, but still impractical and not well loved by those folks who have to switch back and forth between Win and Lin.
Ideally TCE's boot process would a) look for a \TCE folder on an EXTx partition, b) try to find it on a FAT32 part, c) fallback (quarterback scramble baby) and look on any drive - NTFS - or anything else - and try to boot.
Once booted to TC - things could be "logged" (last successful boot) and the same process becomes much faster the next time around.
The students I work with do NOT have a USB drive - many live in countries where they are NOT easily available - they share laptops 5 - 10 students per machine - and complain constantly about the problems with Windows and related APs. Windows does NOT allow creating a new FAT32 partition without self-destruct - and having TC solve these problems by working easily - seamlessly - from an NTFS \tce folder (ideally on C: drive) is - to me - essential.
I've said this for about a year now - and as a teacher - I have faith that eventually ya'all will get it.
-
Core is a tool kit. You are welcome to make it anything you want.
.
-
At aswjh - you said "If i want to tc load extenssions on the partition(ntfs),i must add tce=hd(x)."
Can you elaborate - exactly where I might put that command?
At bmarkus - I agree USB is cheap and probably a great way to go for folks who have them. However the reality is that many people "only have a laptop" with an NTFS drive - so making this "easy and painless" for them entails:
a) loading TCE files - optional - everything to C:\TCE C:\OPTIONAL etc. and
b) having it work right out of the hole - WITHOUT having to muck around with bootlocal.sh
Then later - when they have time and money and access to a store that carries USB drives - they can set up a FAT32 USB drive, since that device is easily accessed by both Windows and Linux.
The advantages of EXTx are well documented, but still impractical and not well loved by those folks who have to switch back and forth between Win and Lin.
Ideally TCE's boot process would a) look for a \TCE folder on an EXTx partition, b) try to find it on a FAT32 part, c) fallback (quarterback scramble baby) and look on any drive - NTFS - or anything else - and try to boot.
Once booted to TC - things could be "logged" (last successful boot) and the same process becomes much faster the next time around.
The students I work with do NOT have a USB drive - many live in countries where they are NOT easily available - they share laptops 5 - 10 students per machine - and complain constantly about the problems with Windows and related APs. Windows does NOT allow creating a new FAT32 partition without self-destruct - and having TC solve these problems by working easily - seamlessly - from an NTFS \tce folder (ideally on C: drive) is - to me - essential.
I've said this for about a year now - and as a teacher - I have faith that eventually ya'all will get it.
Now i make a package named ntfs-3g.gz to append when booting ,and add these lines into /etc/init.d/rcS:
for stra0 in \
' fi ' \
' 2>/dev/null read UMOUNT< /tmp/find-tce/UMOUNT.f' \
' 2>/dev/null read MOUNTED< /tmp/find-tce/MOUNTED.f' \
' 2>/dev/null read TCE_DIR< /tmp/find-tce/TCE_DIR.f' \
' 2>/dev/null read MOUNTPOINT< /tmp/find-tce/MOUNTPOINT.f' \
' . /usr/local/bin/cmds/find-tce' \
' if [ "${MOUNTPOINT}" == "/tmp" ];then '
do
sed -i '/MOUNTPOINT=\"\/tmp\"/a\'"$stra0"'' /usr/bin/tce-setup;
done
. /etc/init.d/tc-config
this is my "find-tce" placed at /usr/local/bin/cmds/:
#! /bin/sh
ttt="nonetce";
for i in `cat /proc/cmdline`; do
if [ "${i:0:4}" == "tce=" ]; then ttt=${i:4:20};fi;
done
[ ! -d /tmp/find-tce ]&&mkdir -p /tmp/find-tce;
if [ ${ttt} = "nonetce" ]; then
for chedsk in `cat /etc/fstab | grep -i /mnt/ | awk '{print $2}'`;do
mount ${chedsk};
[ -d ${chedsk}/tce ]&&
echo "${chedsk}" >/tmp/find-tce/MOUNTPOINT.f&&
echo "tce" >/tmp/find-tce/TCE_DIR.f&&
echo "yes" >/tmp/find-tce/MOUNTED.f&&
echo "yes" >/tmp/find-tce/UMOUNT.f&&
ls -la "${chedsk}" >/tmp/find-tce/ls.f&&
ls -la "${chedsk}"/tce >>/tmp/find-tce/ls.f&&
break;
umount ${chedsk};
done
fi;