Tiny Core Linux
Tiny Core Base => TCB Talk => Topic started by: newbody on February 07, 2011, 12:01:57 PM
-
I tested to follow the description again and now I have the one from Finland going again. Such a pain spending this many hours just to get the åäö chars right.
I still fail to get a AltGr which I did have just a few hours ago. Have no idea how that happen. Now I am back in Finland keyboard though which luckily have enough of what I am used to.
Okay Firefox works and getflash10 works and iptables as far as I know works too.
So that is some comfort.
But NTFS-3g fails. I want to play my music on the HDD. Where is the description how to accomplish this as easy as possible?
I have been at this for some 5 hours so have failed and failed and failed and makes more and more mistakes obviously. Phew
-
Have you read the FAQ? There's an entry just about the altgr keys with Xvesa.
-
Thanks I did not know it was related to xvesa even. I am a newbie. So altgr and xvesa will find that text? I give it a try
You refer to this text?
If the altgr symbols do not work in the browser or openoffice then modify the .xsession file by adding:
sleep 3 && xmodmap -e "clear Mod4" -e "add Mod5 = Mode_switch" &
Just before
exec "${DESKTOP:=jwm}"
Or, in later versions, right after waitforX.
Do I have a later version most likely then this being teh current
I should open Editor and the file .xsessions file and add sleep 3 && xmodmap -e "clear Mod4" -e "add Mod5 = Mode_switch" &
right after waitforX
Right on that did work.
Now I only need to learn how to activate that ntfs-3g thing I downloaded. I've read and read and seems not so easy is it?
Don't you guys have NTFS HDD on many of your computers?
And if you visit a neighbor he certainly very often have only MsWindows on his gear so to help him save the files it is of great help to let him see which one to save.
-
Do you have ntfs-3g in OnBoot?
-
Guy how do I know if I have it in onboot?
I trust that I used onboot when I did download it but how does one check after that?
I usually go to appbrowser adn then look in local is that what you refers to? I have the Gpicview there and Firefox and gcheeky something and kmaps and iptables and so on.
So hopefully that is what you talk about but I take a look I am in puppy now so I reboot into the usb instead. And try to see if I have a onboot folder or something. Thanks for wanting to help me.
I've come rather far for being me. But I started at 7 AM and now it is 7PM so it is a slow process to get around doing things.
Edit I am in TCL now but lost swedish again despite me doing backup. So this is much more difficult than what I expected .
Okay Now I look in appbrowser for that ntfs-3g thing.
It says this when I load it.
/mnt/sdb1/boot/TinyCore/optional/ntfs-3g is already installed!
So have no idea if it is in onboot, it is in local is that same as onboot?
-
Open Apps Audit, Click OnBoot, then Maintenance.
Those on the right side, are in OnBoot. If what you want is not there, click on it in the left side.
-
I finally got Swedish åäö now. Was the most difficult thing me have tried in many monthes. :) Took me some 12 hours?
I did not understand your advice about the maintenance thing. all of it looks okay for me.
The ntfs-3g is there in onboot what am I supposed to do next?
I must have given wrong code in menu.lst because it give an error message but too fast to noiced what it says but something that it ignore the request to do persistence.
title TinyCore 3.4.1
find --set-root /boot/tinycore.gz
kernel /boot/bzImage waitusb=6 tce=sdb1/boot/TinyCore home=tce showapps dmraid=on kmap=qwerty/fi-latin9
initrd /boot/tinycore.gz
What should I change there so I get persistence?
-
If you install it using the HD/USB Install, everything should just work.
You can add additional things, like your keyboard.
-
I must have given wrong code in menu.lst because it give an error message but too fast to noiced what it says but something that it ignore the request to do persistence.
title TinyCore 3.4.1
find --set-root /boot/tinycore.gz
kernel /boot/bzImage waitusb=6 tce=sdb1/boot/TinyCore home=tce showapps dmraid=on kmap=qwerty/fi-latin9
initrd /boot/tinycore.gz
What should I change there so I get persistence?
please read
http://forum.tinycorelinux.net/index.php?topic=8619.msg46673#msg46673
again.
Having /home scattered on NTFS is looking for trouble.
-
Tinypoodle, but now I am using TCL current installed on a USB formatted to FAT32 and that works for TCL as far as I know?
I am not on NTFS at all. Where did you get that idea?
In the tread you referred to was about a remix and I am not using that one at all now because I was told to use official TCL instead for to be able to ask here in the main part of the forum.
so why do you drag up that old thread now?
I do back up now what code in teh menu.lst should I use for to get persistence on Fat32?
You link was not on my level of getting such from your text there. Too technical or grammatically abstract.
-
Regarding FAT32, I have already clarified here:
http://forum.tinycorelinux.net/index.php?topic=8619.msg46675#msg46675
in every detail.
-
You seem to mix up a lot of things due to not thoroughly reading basic documentation first...
1. Frugal installs are supported out of the box on FAT* and ext* filesystems.
That is a choice of the developers made about specific filesystems, not at all about a linux partition or not, as neither FAT* are linux filesystems nor are any UNIX /Linux filesystems beyond ext* supported.
2. A UNIX filesystem would be required for any - even partial - "hybrid" type install approach (scatter mode), and that is not particular to TC in the slightest, but is valid for any Linux system.
"You seem to mix up a lot of things due to not thoroughly reading basic documentation first..."
My English and my ability to grasp your intention with that text is way above my level of experience on what you talk about. But now after reading your request several times I suddenly guessed that what you say is that it can boot but not use it for saving. So I should make a ext2 for to be able to save on it from TCE. The reason me did not make ext2 was that I plan to ahve NTFS-3g which puppy use and one save in a Squash file so no need to have it in Ext2 or 3. Knoppix save that way too. So TCL should also be able to?
Your text are written on a too abstract level for some one on my level to grasp.
Fat32 allow me to boot a Linux but Fat32 don't allow TCE to use the boot codes that I used. That I mixed up these two things as you say.
Have I finally get what you tried to say?
I give it a try tomorrow. Some 12 hour from now.
-
I repeat:
If you install it using the HD/USB Install, everything should just work.
-
But now after reading your request several times I suddenly guessed that what you say is that it can boot but not use it for saving.
That is more or less correct.
For booting, PPR (tce= ) and to save/restore backup; but not for any other way to save scattered files, e.g. home=.
So I should make a ext2 for to be able to save on it from TCE.
No such need to save extensions and backup, unless you insist on saving scattered files.
The reason me did not make ext2 was that I plan to ahve NTFS-3g which puppy use and one save in a Squash file so no need to have it in Ext2 or 3. Knoppix save that way too. So TCL should also be able to?
1. Puppy may have a capability to use NTFS, but such is certainly not a requirement.
2. AFAIK, Puppy is creating persistence in frugal install mode with a ext2/3 loop file, so it still uses a Linux filesystem, even if that is located on top of a non-native filesystem. I could imagine that Knoppix could have a similar approach.
AFAIK a loop file used to be supported by TC, but it escapes me if that is still the case currently, someone else might know.
Fat32 allow me to boot a Linux but Fat32 don't allow TCE to use the boot codes that I used. That I mixed up these two things as you say.
Have I finally get what you tried to say?
Yes, any frugal Linux install can be booted from FAT32, but files can not be stored directly on FAT*, which those boot codes would do.
I wonder why you do not just use the default mode with backup/restore and PPR (tce=) as described in documentation; that works perfectly well to achieve persistence with one single FAT* filesystem.
-
TinyPoodle wrote:
Some Other Linux" are... creating persistence in frugal install mode with a ext2/3 loop file, so it still uses a Linux filesystem, even if that is located on top of a non-native filesystem. I could imagine that Knoppix could have a similar approach.
AFAIK a loop file used to be supported by TC, but it escapes me if that is still the case currently, someone else might know.
That is how I remember that Puppy and Knoppix and a few more. Nimblex, Vector, maybe Slitas?
Yes I had TCL 2.7 something working for me one year ago and that was also on a NTFS and it was no remix or anything. Standard official TCL.
So it used to work? Unless I fail to remember. The Fan is acting up on that computer so I will not use it. Gets too hot.
This PPR? Using tce=sdb1 or similar code? I should read up some FAQ or wiki on that one then?
How I can activate it? But maybe TCL 2.7 and 3.4 are so different from each other that they fail to use from each others tcz files? I saw some files that simply failed to get used. Don't remember what name but nothing did happen when I tried to activate them. Maybe they work only in one year old versions then?
-
This PPR? Using tce=sdb1 or similar code? I should read up some FAQ or wiki on that one then?
How I can activate it? But maybe TCL 2.7 and 3.4 are so different from each other that they fail to use from each others tcz files? I saw some files that simply failed to get used. Don't remember what name but nothing did happen when I tried to activate them. Maybe they work only in one year old versions then?
Most of your questions would be answered in following all the links from TC main page.
Particularly kernel modules of 2.x vs. 3.x are not compatible.
-
They use different kernels, so packages that provide or depend on kernel modules are not compatible between the versions.
Just use the correct repository.
-
@Guy: In reply #6 one of his boot settings reads "tce=sdb1/boot/TinyCore home=tce".
Does that trailing "=tce" belong there?
-
@Guy: In reply #6 one of his boot settings reads "tce=sdb1/boot/TinyCore home=tce".
Does that trailing "=tce" belong there?
Good catch!
Even though I had replied as to the "home=" as being wrong when using a non UNIX filesystem, I had totally overlooked how wrong "home=tce" would be under any circumstances. :P
-
Guys thanks indeed for catchin my sloppy copy of others menu entries me not realizing it would only work on ext2 or ext3.
So I will try to edit these part.
I use Backup/Restore now as the way to save changes and it works very well so that is a good thing.
Suppose I make a new boot entry in grub4dos boot2 and have same official TCL iso files in tehre on the HDD NTFS and then make a Backup/Restore and use onBoot to download things and so on.
Would that not work. Or would it not even boot on NTFS? Sorry my ADHD makes me a very poor reader of texts. I get easily distracted and forget what I just was reading.
-
Already answered here...
http://forum.tinycorelinux.net/index.php?topic=8619.msg46675#msg46675
-
Thanks tinypoodle, yes it is if one are on that level.
Took me a long time to get what you say and I am not 100% sure still.
But I have done practical experiments and you are right. I am way too slow to get things. :)
So now I know.
1. TCL do boot on NTFS but in reality it is grub4dos that boot the TCL OS in RAM and all that happens is in RAM and get lost when I do reboot.
That was what took me so long to realize.
2. BackUp and Restore can save on Fat32 and Ext2 etc but not on NTFS.
A TCE can not be made pesistent on NTFS and not on Fat32 either only on Ext2.
3. Linux distros like Slax can use a save file that internally have ext2 but that can be saved due to them loopmounted in NTFS but for to get that one need NTFS-3g already going in TCL?????
Have I got it right now?
4. Puppy have Vbox and Vbox can create a virtual install of TCL on Ext2 formatted virtual HDD within the sandbox of Vbox.
Could I then use Puppy and Vbox on Puppy to get to learn TCL using the ext2 formatted HDD in Vbox?
Could I there learn how to use home=tce home=hda1 or what the Manual says one should use?
Hope I am a bit more structured this post so you guys don't lose trust in me. I truly want to learn how to use TCL.
Why else would I spend 12 hours testing and testing until I learned it did not work the way I thought.
-
Getting closer...
Thanks tinypoodle, yes it is if one are on that level.
Took me a long time to get what you say and I am not 100% sure still.
But I have done practical experiments and you are right. I am way too slow to get things. :)
So now I know.
1. TCL do boot on NTFS but in reality it is grub4dos that boot the TCL OS in RAM and all that happens is in RAM and get lost when I do reboot.
That was what took me so long to realize.
2. BackUp and Restore can save on Fat32 and Ext2 etc but not on NTFS.
A TCE can not be made pesistent on NTFS and not on Fat32 either only on Ext2.
3. Linux distros like Slax can use a save file that internally have ext2 but that can be saved due to them loopmounted in NTFS but for to get that one need NTFS-3g already going in TCL?????
Have I got it right now?
4. Puppy have Vbox and Vbox can create a virtual install of TCL on Ext2 formatted virtual HDD within the sandbox of Vbox.
Could I then use Puppy and Vbox on Puppy to get to learn TCL using the ext2 formatted HDD in Vbox?
Could I there learn how to use home=tce home=hda1 or what the Manual says one should use?
Hope I am a bit more structured this post so you guys don't lose trust in me. I truly want to learn how to use TCL.
Why else would I spend 12 hours testing and testing until I learned it did not work the way I thought.
Getting closer... ;)
1. Booting from and achieving persistence on any other filesystem than FAT* or ext* (incl. NTFS) is not supported by default, but might be subject to - unofficial - modifications (e.g. remaster).
2. For any mode of persistence including scattered files - with exception from tce= and backup/restore - a linux filesystem is required.
For any questions regarding virtualization please prefer to peruse the "Tiny Core on Virtual Machines" subforum.