Tiny Core Linux
General TC => General TC Talk => Topic started by: aus9 on February 06, 2010, 07:55:17 PM
-
culled as major test a fail
page 2 has relevance to grub2 users only.
Pls ignore if you do not have grub2 installed
thanks
-
culled as major test a fail
-
I don't understand.
TCL on cd has no need for GRUB2.
A machine that already is running GRUB2 has no need for a TCL iso with GRUB2.
What exactly are you trying to accomplish?
-
gerald_clark
hi
I am attempting to accomplish
1) a backup of my hard drive grub2 files onto a cd....................................................done
2) build a bootable cd that has grub2 as the bootloader to get extra benefits. .....done
3) provide a script or 2 so others can do their backup..............................................in progress
4) provide a true rescue cd .....of all of the above......................................................not done
Sorry to hijack my own thread......but I have tested a ext4...vbox system and um hitting a brick wall atm.
It appears I need some kind of TCE extension that supports ext4?
well I am not sure as I have already stated I am new to TC
at this stage I am back to thinking mode
-----------------
any iso I build needs to be really small as I am both impatient and my upload speed is terrible.
Thats why I chose microcore but a combination of oldish kernel...toolchain built with oldish gcc etc means if I want to truly update this distro I have to read more and learn more......did I tell you I am impatient?.....lol
regards
-
Ext4 mounting is supported with the filesystems-2.6.29.1-tinycore.tcz extension. You can add it inside the initrd (this is the procedure for current 2.9rc2, won't work with rc1):
# Assume initrd is extracted into /tmp/ex
mkdir -p /tmp/ex/opt/tce/optional
cp filesystems*.tcz /tmp/ex/opt/tce/optional
echo filesystems*.tcz > /tmp/ex/opt/tce/onboot.lst
Currently we don't have fsck / other ext4 tools, but we also don't recommend using ext4 in production with the .29 kernel.
-
Ext4 mounting is supported with the filesystems-2.6.29.1-tinycore.tcz extension. You can add it inside the initrd (this is the procedure for current 2.9rc2, won't work with rc1):
Hm... Someone wrote in a topic that ext4 is not adviced with 2.6.29 kernel as that time it was not matured and changed a lot in later 2.6.3x kernels :) :
Note there have been many changes to ext4 since 2.6.29, I wouldn't recommend running ext4 with TC 2.x.
-
If you read Phoronix, you'll notice they recently had ext4 data loss with 2.6.32. In the event of a crash, yes, but still a situation other filesystems might have coped better.
-
If you read Phoronix, you'll notice they recently had ext4 data loss with 2.6.32. In the event of a crash, yes, but still a situation other filesystems might have coped better.
By default I'm using ext3 always as a safe filesystem which is common through all LINUX distributions.
BTW, this is an interesting article:
Google upgrading to Ext4, hires former Linux Foundation CTO (http://arstechnica.com/open-source/news/2010/01/google-upgrading-to-ext4-hires-former-linux-foundation-cto.ars)
-
curaga
sorry if I am wasting your time but, do you think I might be better off trying out TC to utulise your TCE extension or do you know a
wget command for microcore that will grab filesystems-2.6.29.1-tinycore.tcz extension?
BTW, since this is general talk......I also tried to mount a vbox ext4 hard drive using slitaz and currently failed with same error suggesting that my stable and cooking slitaz distros lack ext4 support as well.
The problem I had with slitaz is my repack was way too big.....I did something wrong and ended up with about 60 Megs. But maybe I will revisit it and not use lzma compression but advancecomp compression?
But it is pointless me repacking slitaz if I have the same ext4 issue.
bmarkus
I agree with you....my hard drive is ext3.....but I also use partimage for imaging my system partition and ext4 is too new for me to trust it.
-
The "CLI way" to download (and install) extensions is the 'tce-load' command
(e.g. tce-load -wi filesystems-2.6.29.1-tinycore.tcz).
I somehow get the impression that you try to walk before you have learned to crawl (with respect to understanding the way TC/MC works). You might benefit in spending a bit more time reading the FAQ, the Wiki and this forum here.
Please bear in mind that some aspects of the documention are not always reflecting the latest changes. TC enjoys a fair amount of frequent improvements, but sometimes documentation is not updated.
In my view a remastered ISO only makes sense after you have really understood what you are trying to achieve (which I'm currently not so sure for that to be the case).
-
maro
Thats very astute of you...heh heh
I was looking at this page...before you replied
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/tcz_2x.html
so I might try a wget with that page if your way does not work for me.
2) but my issue...my problem....is to pursue TC or MC if if offers ext4 support.....if it does not offer true support I do not want to waste my time or yours having to give me advice.
let me try a few things as suggested and don't bother replying unless I reply to save each other 's time?
regards
-
culled as major test a fail
-
culled as major test a fail
-
culled as major test a fail
-
hi
ok major test after installing teenpup as advertised at DW.
it uses inode 128 and grub-legacy.
my attempt at grub2 rescue cd....fails to fix restoration back to grub2.
2) In trying out various setup chroot commands...I had some issues with my fstab and found grub2 apparently needs access to the locale file.
Why I do not know....it is irrelevant as I am now dismissing this build as a bad idea.
thanks
-
hi
My earlier major fail was not due purely to inode 128 issue but also to a not so good chroot I was setting up.
therefore here is the chroot commands assuming one partition system
mkdir /z
mount /dev/sda1 /z
mount -t proc proc /z/proc
mount -t sysfs sys /z/sys
mount -o bind /dev /z/dev
chroot /z
Unlike other chroots I have tried....once you do the last command all commands are intuitively off your hard drive
FWIW
2) Rather than submit my iso link here.....I submit my scripts which anyone should be able to work out as I am a script novice.
link removed as it is stale
balance of text removed as now irrelevant