Tiny Core Linux
General TC => General TC Talk => Topic started by: ejames82 on May 06, 2013, 11:13:26 AM
-
Hello,
this is the first time I have installed any new tinycore version that starts with a 4
the last version I have used was 3.8.4 it worked nicely.
the version I installed is 4.7.6 I did so by the command-line method. here are the instructions that I follow:
fdisk -l
mkfs.ext3 /dev/sda2
rebuildfstab
mount /mnt/sda2
mkdir -p /mnt/sda2/boot/grub
mount /mnt/sr0
cp -p /mnt/sr0/boot/* /mnt/sda2/boot/
mkdir -p /mnt/sda2/tce
touch /mnt/sda2/tce/mydata.tgz
cp -p /usr/lib/grub/i386-pc/* /mnt/sda2/boot/grub/
vi /mnt/sda2/boot/grub/menu.lst
default 0
timeout -1
title Tiny Core
root (hd0,1)
kernel /boot/vmlinuz quiet tce=sda2
initrd /boot/core.gz
title Windows XP
root (hd0,0)
makeactive
chainloader +1
~
grub
root (hd0,1)
setup (hd0)
quit
umount /mnt/sr0
eject /dev/sr0
reboot
everything I see as I install tinycore appears normal. there is nothing to indicate a problem or error.
as the computer reboots it stops at the screen with the picture of the penguin and text that says this:
tinycore is distributed with ABSOLUTELY NO WARRANTY
tinycorelinux.net
and a terminal prompt below.
I looked in the wiki and found some instruction that said enter "tinycore x setup". I did and received output that said:
-sh: tinycore: not found
how do I get past this screen? did I do something wrong in the install?
thank you.
-
Hi ejames82
You should also copy the cde directory to sda2 and rename it to tce.
-
Hello Rich,
"copy the cde directory to sda2 and rename it to tce."
"cde directory"
I have never seen this directory. I am guessing that it is in the root directory of the boot disk.
I will guess at the command:
cp /mnt/sr0/cde /mnt/sda2/tce
please let me know if this is not correct.
would this cause the bootup to stop at the text screen I explained in reply 1?
thanks for the quick reply
-
tce-load -iw Xvesa Xprogs flwm_topside wbar
-
Hi ejames82
cp /mnt/sr0/cde /mnt/sda2/tce
Try:
cp -a /mnt/sr0/cde /mnt/sda2/tceThere have been many changes since 3.8.4, including the addition of a cde directory for use on read only media and
the GUI has been broken out to be loaded separately.
-
thank you gerald_clark and Rich.
I will try what you advise and report the results.
-
tc@box:~$ tce-load -iw Xvesa Xprogs flwm_topside wbar
Xvesa is already installed!
Xprogs is already installed!
flwm_topside is already installed!
wbar is already installed!
tc@box:~$ sudo cp -a /mnt/sr0/cde /mnt/sda2/tce
tc@box:~$
now I will boot without the disk and see what happens
-
it didn't work.
any other suggestions, I would be glad to hear them.
-
Are you sure that when you boot you have a /mnt/sdb1/tce directory, and that /etc/sysconfig/tcedir points to it?
Is sdb a USB drive? Did you include a waitusb=10 boot code?
Please read the wiki persistence articles.
-
Hi ejames82
I think the command I gave you was incorrect and should have read:
cp -a /mnt/sr0/cde/* /mnt/sda2/tce
-
Tried 'xsetup'?
-
gerald_clark,
Are you sure that when you boot you have a /mnt/sdb1/tce directory
you must mean the tinycore partition. that would be sda2, and yes there is a /mnt/sda2/tce directory.
and that /etc/sysconfig/tcedir points to it?
it definitely does
Is sdb a USB drive? Did you include a waitusb=10 boot code?
no. there is no usb drive. xp is sda1, and tinycore is sda2.
I would be glad to include a waitusb=10 if I knew how to do it. I have tried entering boot codes when the computer boots from cd, I pushed f2 and the screen says to type, but the screen changes no matter what key I type. Is this something I put in the menu.lst?
Rich,
I tried your suggestion and there is bad and good news. the bad news is that when I click on appbrowser I get 'fatal error writable only', so the good news is that I was able to get to the desktop.
tinypoodle,
I tried xsetup. it didn't work.
thanks everybody.
-
You have been telling us sdb1 not sda2.
Does the /etc/sysconfig/tcedir point to /mnt/sda2/tce ?
Again, read the wiki article on persistence, because until you have your tce directory properly setup, you cannot install extensions.
-
gerald_clark,
You have been telling us sdb1 not sda2.
I respectfully disagree. which reply? I have went back through the thread and double-checked and I don't see any referrence made by me to sdb1. I appreciate your help as always, and I would not intentionally do that. if I did, I apologise. my fault.
I went back and checked and /etc/sysconfig/tcdir does point to /mnt/sda2/tce. sda2 is the tinycore partition.
I have been reading the wiki throughout the day, and when I see the thread has a reply, I answer the reply. but I have been reading the wiki. it's great documentation.
-
My mistake. I don't know why I thought you were referring to sdb1.
-
EDIT OP does not have a persistent home so home stuff removed from reply
ahhh I think I can spot some issues as he has a series of commands which I believe he is forced to use root powers
He creates mydata.tgz in the build. It might be better he leaves that out.
ejames82
When you get a chance could you do me a favour and look at your permissions pls,
ls -al /mnt/sda2
(should return drwxr-xr-x 3 root root 4096 Mar 3 08:17 home/)
(should return drwxrwxr-x 4 tc staff 4096 Apr 28 14:04 tce/)
The reason is because tc must have the ability to download TCZs, and they go to tce/optional
IMHO your commands can not complete the process until you boot up to console
suggest you then
sudo su
chown -R tc:staff /mnt/sda2/tce
You may need to check your permissions in tce/optional but one hopes they are good
then try
su tc
startx
-
that's quite alright gerald_clark. you're a good guy. :)
-
One hopes so
I won't edit above now that you have replied so quickly
pls delete mydata.tgz with
sudo -rf /mnt/sda2/tce/mydata.tgz
when you can get a graphical screen up, you can create a backup file by using the control panel
click on mount tool to select sda2
click on backup/restore to backup
-
I am on it aus9. I have commandeered my wifes computer. shuffling between the two.
have that info in a few.
-
/mnt/sda2 ls -la
drwxr-xr-x root root .
drwxrwxr-x root staff ..
drwxr-xr-x root root boot
drwx------ root root lost + found
drwxrwxr-x tc staff tce
should the tce directory be owned by tc?
there is no /mnt/sda2/home
I figured I would let you see this before I go on with the rest of your instructions, aus9.
this is a fresh install. if something goes wrong, I can always reinstall, so not a big deal. it only takes me about 10 minutes to get to where I was before.
-
Hi
boot folder is fine
lost and found is fine
tce folder is fine by me
OOPS I have persistent home and opt.....thats a leakage error from me about home
should the tce directory be owned by tc
yes, this is the reason why as user=tc you can run commands like....tce-load -w something.tcz, if you did not have permission to create new entries there.....the command would bork
Others, feel free to chip in if I am misleading OP
-
/mnt/sda2/tce/optional dr-xrwxr-x
this did not work:
sudo -rf /mnt/sda2/tce/mydata.tgz
but this did:
sudo rm /mnt/sda2/tce/mydata.tgz
is that sufficient?
just to let you know, I am at the desktop now, but I am not able to use appbrowser
fatal error tce directory is not writable
-
I have decided to try core plus 4.7.6
maybe when I am done I will have a better understanding what is supposed to be there and what isn't
jumping from 3.8.4 to 4.7.6 is quite a leap, regardless of how well prepared I thought I was.
thanks to everybody who helped me.
-
sorry I should have asked what you had for tce/optional so your reply
/mnt/sda2/tce/optional dr-xrwxr-x
shows the first string is read (not writeable) execute
if you ever decide to re-investigate this matter, you should be able as user=tc to fix by
chmod -R 775 /mnt/sda2/tce
I have editted my reply at the other thread you know I replied to as well as a result of knowing your current permissions
-
aus9,
not a big deal. I just wanted to have the latest tinycore. I have been using 3.8.4, but firefox is constantly bothering me about update and I can't find a way to stop it. I tried to let firefox update itself once, but it was a huge mess that resulted in me reinstalling tinycore. I thought I would make an effort to use 4.7.6. I found out alot, and that my command-line skills are still not as good as they need to be.
also, my effort to use core plus didn't work. it wouldn't boot up to the OS. I think that was because I was making a dual-boot. I think it would have worked if it was just core plus on the hard drive by itself. I like having many OS's on a system (to a fault). :)
do you know how to enter boot codes? I want stuff in my home and opt to survive a reboot and if I need to do this by entering a boot code, I don't know how.
you mentioned earlier using the console. I am not sure what you mean by this, but I can guess THIS:
explanation of how to get to console in this url below. basically, it is saying press ctrl + alt + f1. if this is the case, when do I press it? when I am on the desktop with no windows or applications running?
http://forum.tinycorelinux.net/index.php/topic,7430.0.html
reply #3
what does the console do?
thanks again aus9
-
ok one thing at a time
edit boot if you are the only user of this computer, I assume your wife won't touch it, the computer...giggles
sudo chown -R tc:staff /mnt/sda2/boot
cp /mnt/sda2/boot/grub/menu.list /mnt/sda2/boot/grub/menu.lst-bak
this is NON-standard but allows us to quickly edit boot codes. Step one.....as per your signature.....create a backup of your existing menu as per last line above
Now duplicate your TC menu so it now reads (you can now use a standard gui text editor----I use leafpad)
title TC nocodes
root (hd0,1)
kernel /boot/vmlinuz quiet tce=sda2
initrd /boot/core.gz
title TC-codes
root (hd0,1)
kernel /boot/vmlinuz quiet tce=sda2 <insert boot codes here>
initrd /boot/core.gz
refer to http://distro.ibiblio.org/tinycorelinux/faq.html#bootcodes
I will show you mine to give you an idea, lots of people have better ideas. I have a very complicated system that allows me to easily swap from vesa graphics to nVidia closed source graphics.....don't focus on that just see you have multiple menu entries
AND
I rename core as 476 for the version=4.7.6 because when the next version comes out, I create extra menus to try out (say) 4.7.7
AND my main bootloader is on sda1 and TC is on sda3 but I prefer labels, and so I don't need a /boot/grub on sda3
as you can tell I am a grubby person....giggles
title NV
kernel /grub/vmlinuz tce=LABEL=partthree home=LABEL=partthree opt=LABEL=partthree waitusb=8:LABEL=partthree snd=/opt/nv.sh lst=nv.lst lang=en_AU.UTF-8
initrd /grub/476.gz
title VESA
kernel /grub/vmlinuz tce=LABEL=partthree home=LABEL=partthree opt=LABEL=partthree waitusb=8:LABEL=partthree snd=/opt/vesa.sh lst=vesa.lst lang=en_AU.UTF-8
initrd /grub/476.gz
title TCB
kernel /grub/vmlinuz base norestore
initrd /grub/476.gz
[/code]
-
if you like the idea of using LABEL then download --as ondemand and load it ---e2fsprogs.tcz while using a live cd not hard drive
sudo su
umount /mnt/sda2
e2label /dev/sda2
(returns current value or blank line)
e2label /dev/sda2 Eric
e2label /dev/sda2
Eric
Choose something in place of Eric, labels can be added to un-mounted partitions
there are other commands that will do it, but I like the simplicity of e2label
---assuming its a linux ext2/3/4 partition
-
aus9,
so the boot code task goes something like this:
sudo chown -R tc:staff /mnt/sda2/boot
we don't want to be blocked from doing this by our own OS.
make a backup copy
cp /mnt/sda2/boot/grub/menu.list /mnt/sda2/boot/grub/menu.lst-bak
ok, so now if I want my firefox and alsa to survive reboot, should my kernel line have this:
kernel /boot/vmlinuz quiet tce=sda2
or this?:
kernel /boot/vmlinuz quiet tce=sda2 tce=home tce=opt
I think I may see the reasoning behind having multiple selections with differing boot codes. the NV selection is probably when you unplug the 19inch monitor and plug in the big screen ultra plasma. you probably have resolution of 5000x3000 enabled. :)
sudo su
umount /mnt/sda2
e2label /dev/sda2
(returns current value or blank line)
e2label /dev/sda2 Eric
e2label /dev/sda2
Eric
here you're verifying that the label 'Eric' took hold
if you like the idea of using LABEL then download --as ondemand and load it ---e2fsprogs.tcz while using a live cd not hard drive
I know how to do this. follow this up with the blkid command to verify.
a label is a sort of 'name', if you will. it takes alot of the confusion away, instead of sda1 or sda2 (most confusing).
I think you can also use gparted to add a label.
what about the console subject? anything to add?
what is that thing for?
thanks aus9. I think I will try that command-line install of 4.7.6 again tomorrow (the one where everything went wrong yesterday). when I do, I'll post about how it goes and I hope to hear your advice when you check into the site.
-
tce=sda2 home=sda2 opt=sda2
-
your "or this" option will give you persistence for home and opt. Please read the wiki and forums on that as I am have to get back to work.
In case you thought I was ignoring you, it was not clear to me, you had succeeded in getting a graphical display up either with this build of TC or the coreplus way.
so if you don't get graphics up, that is called console and means the same as terminal but you can't run any mouse controlled stuff.
like msdos if you are old enough to know such beasts.
some nice person has a wiki entry on alsa so you may elect to read that.
ie what you put into your onboot.lst determines what is REBOOTED if downloaded into tce/optional
--files you changed, means you put that in your .filetool.lst------but drop the leading /
eg if you change /etc/scooby you add etc/scooby to your filetool.lst
------ alsa also needs a daemon so that goes to a boot up script called bootlocal.sh
Please take your time with the wiki and other forum posts.....you will be rewarded, with good looks, karma and skills, once you understand it.
good luck
-
gerald_clark,
tce=sda2 home=sda2 opt=sda2
this is what my kernel line will look like in menu.lst
kernel /boot/vmlinuz quiet tce=sda2 home=sda2 opt=sda2
thanks.
aus9,
if you don't get graphics up, that is called console and means the same as terminal but you can't run any mouse controlled stuff.
then that is the screen I describe in reply #1 with the penguin and ABSOLUTELY NO WARRANTY, then a terminal prompt. so that's the console. can that be invoked by ctrl + alt + f1 ?
before I get started (right away) with a new install, I need to mention that I will be skipping this command:
touch /mnt/sda2/tce/mydata.tgz
unless a reputable member recommends different. the idea here is, we don't want that file, do we?
your "or this" option will give you persistence for home and opt. Please read the wiki and forums on that as I am have to get back to work.
for apps to survive a reboot, it will be this:
kernel /boot/vmlinuz quiet tce=sda2 home=sda2 opt=sda2
In case you thought I was ignoring you, it was not clear to me, you had succeeded in getting a graphical display up either with this build of TC or the coreplus way.
it was after I ran this command, reply #9
cp -a /mnt/sr0/cde/* /mnt/sda2/tce
this command got me to the desktop (I was no longer stuck at the console), but I was no longer able to use appbrowser after that. I got an error 'tce directory is not writable', and I was unable to do anything except run the terminal and send replies to you with another computer. I didn't even have leafpad, so I couldn't transfer text from computer to computer with a flash drive. there probably is a way to send text files to the flash drive with the terminal, but I am not that good.
some nice person has a wiki entry on alsa so you may elect to read that.
I'll bet that's you. :) I think I remember studying that.
that reminds me. every time I restarted tinycore I had to turn alsamixer all the way up. there is a lock icon but it doesn't keep the volume all the way up the way I like it. is there a way to force alsamixer to stay on full volume? maybe even a command to put in bootlocal.
ie what you put into your onboot.lst determines what is REBOOTED if downloaded into tce/optional
--files you changed, means you put that in your .filetool.lst------but drop the leading /
I will have to get in there and have a look.
eg if you change /etc/scooby you add etc/scooby to your filetool.lst
------ alsa also needs a daemon so that goes to a boot up script called bootlocal.sh
right. commands go in bootlocal.
Please take your time with the wiki and other forum posts.....you will be rewarded, with good looks, karma and skills, once you understand it.
understanding it is the hard part.
now on to the install. thanks aus9.
-
aus9,
there has definitely been a change. whether it is for the better is yet to be determined.
the immediate problem was an error I received when clicking on appbrowser 'tce directory is not writable'. I was able to get appbrowser to work with this command (below):
root@box:/mnt/sda2/tce# ls -la
total 28
drwxrwxrwx 4 tc staff 4096 May 8 15:48 .
drwxr-xr-x 5 root root 4096 May 8 15:16 ..
-r--r--r-- 1 tc staff 73 Apr 2 03:36 copy2fs.lst
-rw-rw---- 1 tc staff 0 May 8 15:26 firstrun
-r--r--r-- 1 tc staff 73 Apr 2 03:36 onboot.lst
drwxrwxr-x 2 tc staff 4096 May 8 15:25 ondemand
dr-xr-xr-x 2 tc staff 4096 Apr 2 03:36 optional
-r-xr-xr-x 1 tc staff 57 Apr 2 03:36 xbase.lst
-rw-rw-r-- 1 tc staff 0 May 8 15:25 xwbar.lst
root@box:/mnt/sda2/tce# chmod 777 optional/
root@box:/mnt/sda2/tce# ls -la
total 28
drwxrwxrwx 4 tc staff 4096 May 8 15:48 .
drwxr-xr-x 5 root root 4096 May 8 15:16 ..
-r--r--r-- 1 tc staff 73 Apr 2 03:36 copy2fs.lst
-rw-rw---- 1 tc staff 0 May 8 15:26 firstrun
-r--r--r-- 1 tc staff 73 Apr 2 03:36 onboot.lst
drwxrwxr-x 2 tc staff 4096 May 8 15:25 ondemand
drwxrwxrwx 2 tc staff 4096 Apr 2 03:36 optional
-r-xr-xr-x 1 tc staff 57 Apr 2 03:36 xbase.lst
-rw-rw-r-- 1 tc staff 0 May 8 15:25 xwbar.lst
root@box:/mnt/sda2/tce#
I used the 777 variation just to ensure that there was no permission problem.
you suggested to me this command:
chmod -R 775 /mnt/sda2/tce
I don't see why this would not have worked. what does the -R do? honestly, I don't remember trying it, so I will assume that I didn't (hitting myself in the head with a hammer). I am going to reinstall and now I know exactly where I have to look to investigate the reason for the problem and what exactly would have worked and why. I have to know what permissions the tce/optional had before and after running this command:
cp -a /mnt/sr0/cde/* /mnt/sda2/tce
then see what change to the permissions this command has:
chmod -R 775 /mnt/sda2/tce
I am going to use the OS for a few minutes (I want to make sure everything works) then I will reinstall.
-
Hi ejames82
Entering:
chmod --helpwill tell you that -R means to recurse which means do it to all files and subdirectories in optional.
-
thank you Rich. that reply will help me with my investigation and my next post.
-
here is everything I did for the fresh install, plus my investigation as to the problems getting out of console and the problem with appbrowser not opening.
pardon my inefficiency with the terminal.
fdisk -l
mkfs.ext3 /dev/sda2
rebuildfstab
mount /mnt/sda2
mkdir -p /mnt/sda2/boot/grub
mount /mnt/sr0
cp -p /mnt/sr0/boot/* /mnt/sda2/boot/
mkdir -p /mnt/sda2/tce
cp -p /usr/lib/grub/i386-pc/* /mnt/sda2/boot/grub/
vi /mnt/sda2/boot/grub/menu.lst
default 0
timeout -1
title Tiny Core
root (hd0,1)
kernel /boot/vmlinuz quiet tce=sda2 tce=home tce=opt
initrd /boot/core.gz
title Windows XP
root (hd0,0)
makeactive
chainloader +1
~
grub
root (hd0,1)
setup (hd0)
quit
umount /mnt/sr0
eject /dev/sr0
reboot
cp -a /mnt/sr0/cde/* /mnt/sda2/tce
chmod -R 775 /mnt/sda2/tce
at this point I have already installed grub-splash0.97
root@box:~# mkfs.ext3 /dev/sda2
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
2908160 inodes, 11614995 blocks
580749 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
355 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 37 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
root@box:~# rebuildfstab
root@box:~# mount /mnt/sda2
root@box:~# mkdir -p /mnt/sda2/boot/grub
root@box:~# cp -p /mnt/sr0/boot/* /mnt/sda2/boot/
cp: omitting directory '/mnt/sr0/boot/isolinux'
root@box:~# mkdir -p /mnt/sda2/tce
root@box:~# cp -p /usr/lib/grub/i386-pc/* /mnt/sda2/boot/grub/
root@box:~# vi /mnt/sda2/boot/grub/menu.lst
default 0
timeout -1
title Tiny Core
root (hd0,1)
kernel /boot/vmlinuz quiet tce=sda2 tce=home tce=opt
initrd /boot/core.gz
title Windows XP
root (hd0,0)
makeactive
chainloader +1
~
grub
root (hd0,1)
setup (hd0)
quit
umount /mnt/sr0
eject /dev/sr0
reboot
root@box:~# cd /
root@box:/# ls
bin dev etc home init lib mnt opt proc root run sbin sys tmp usr var
root@box:/# cd mnt
root@box:/mnt# ls
sda1 sda2 sr0 test
root@box:/mnt# cd sda2
root@box:/mnt/sda2# ls
boot lost+found tce
root@box:/mnt/sda2# cd tce
root@box:/mnt/sda2/tce# ls
root@box:/mnt/sda2/tce#
root@box:/mnt/sda2/tce# cd /
root@box:/# ls
bin dev etc home init lib mnt opt proc root run sbin sys tmp usr var
root@box:/# cd mnt/
root@box:/mnt# ls
sda1 sda2 sr0 test
root@box:/mnt# cd sr0/
root@box:/mnt/sr0# ls
boot cde
root@box:/mnt/sr0# cd cde/
root@box:/mnt/sr0/cde# ls
copy2fs.lst onboot.lst optional xbase.lst
root@box:/mnt/sr0/cde# cd optional/
root@box:/mnt/sr0/cde/optional# ls
Xlibs.tcz Xvesa.tcz flwm_topside.tcz
Xlibs.tcz.md5.txt Xvesa.tcz.md5.txt flwm_topside.tcz.md5.txt
Xprogs.tcz fltk-1.1.10.tcz wbar.tcz
Xprogs.tcz.md5.txt fltk-1.1.10.tcz.md5.txt wbar.tcz.md5.txt
root@box:/mnt/sr0/cde/optional# ls -la
total 4087
dr-xr-xr-x 2 root root 2048 Apr 2 03:36 .
dr-xr-xr-x 3 root root 2048 Apr 2 03:36 ..
-r--r--r-- 1 root root 3313664 Apr 2 03:36 Xlibs.tcz
-r--r--r-- 1 root root 44 Apr 2 03:36 Xlibs.tcz.md5.txt
-r--r--r-- 1 root root 131072 Apr 2 03:36 Xprogs.tcz
-r--r--r-- 1 root root 45 Apr 2 03:36 Xprogs.tcz.md5.txt
-r--r--r-- 1 root root 372736 Apr 2 03:36 Xvesa.tcz
-r--r--r-- 1 root root 44 Apr 2 03:36 Xvesa.tcz.md5.txt
-r--r--r-- 1 root root 294912 Apr 2 03:36 fltk-1.1.10.tcz
-r--r--r-- 1 root root 50 Apr 2 03:36 fltk-1.1.10.tcz.md5.txt
-r--r--r-- 1 root root 28672 Apr 2 03:36 flwm_topside.tcz
-r--r--r-- 1 root root 51 Apr 2 03:36 flwm_topside.tcz.md5.txt
-r--r--r-- 1 root root 36864 Apr 2 03:36 wbar.tcz
-r--r--r-- 1 root root 43 Apr 2 03:36 wbar.tcz.md5.txt
root@box:/mnt/sr0/cde/optional# cd ..
root@box:/mnt/sr0/cde# ls
copy2fs.lst onboot.lst optional xbase.lst
root@box:/mnt/sr0/cde# ls -la
total 8
dr-xr-xr-x 3 root root 2048 Apr 2 03:36 .
dr-xr-xr-x 4 root root 2048 Apr 2 03:36 ..
-r--r--r-- 1 root root 73 Apr 2 03:36 copy2fs.lst
-r--r--r-- 1 root root 73 Apr 2 03:36 onboot.lst
dr-xr-xr-x 2 root root 2048 Apr 2 03:36 optional
-r-xr-xr-x 1 root root 57 Apr 2 03:36 xbase.lst
root@box:/mnt/sr0/cde# cp -a /mnt/sr0/cde/* /mnt/sda2/tce
root@box:/mnt/sr0/cde# chmod -R 775 /mnt/sda2/tce
root@box:/mnt/sr0/cde#
root@box:/mnt/sda1# cd /
root@box:/# ls
bin dev etc home init lib mnt opt proc root run sbin sys tmp usr var
root@box:/# cd mnt
root@box:/mnt# ls
sda1 sda2 sr0 test
root@box:/mnt# cd sda2
root@box:/mnt/sda2# ls
boot lost+found tce
root@box:/mnt/sda2# cd tce/
root@box:/mnt/sda2/tce# ls
copy2fs.lst onboot.lst optional xbase.lst
root@box:/mnt/sda2/tce# ls -la
total 24
drwxrwxr-x 3 root root 4096 May 8 19:08 .
drwxr-xr-x 5 root root 4096 May 8 18:50 ..
-rwxrwxr-x 1 root root 73 Apr 2 03:36 copy2fs.lst
-rwxrwxr-x 1 root root 73 Apr 2 03:36 onboot.lst
drwxrwxr-x 2 root root 4096 Apr 2 03:36 optional
-rwxrwxr-x 1 root root 57 Apr 2 03:36 xbase.lst
root@box:/mnt/sda2/tce# cd optional/
root@box:/mnt/sda2/tce/optional# ls -la
total 4128
drwxrwxr-x 2 root root 4096 Apr 2 03:36 .
drwxrwxr-x 3 root root 4096 May 8 19:08 ..
-rwxrwxr-x 1 root root 3313664 Apr 2 03:36 Xlibs.tcz
-rwxrwxr-x 1 root root 44 Apr 2 03:36 Xlibs.tcz.md5.txt
-rwxrwxr-x 1 root root 131072 Apr 2 03:36 Xprogs.tcz
-rwxrwxr-x 1 root root 45 Apr 2 03:36 Xprogs.tcz.md5.txt
-rwxrwxr-x 1 root root 372736 Apr 2 03:36 Xvesa.tcz
-rwxrwxr-x 1 root root 44 Apr 2 03:36 Xvesa.tcz.md5.txt
-rwxrwxr-x 1 root root 294912 Apr 2 03:36 fltk-1.1.10.tcz
-rwxrwxr-x 1 root root 50 Apr 2 03:36 fltk-1.1.10.tcz.md5.txt
-rwxrwxr-x 1 root root 28672 Apr 2 03:36 flwm_topside.tcz
-rwxrwxr-x 1 root root 51 Apr 2 03:36 flwm_topside.tcz.md5.txt
-rwxrwxr-x 1 root root 36864 Apr 2 03:36 wbar.tcz
-rwxrwxr-x 1 root root 43 Apr 2 03:36 wbar.tcz.md5.txt
root@box:/mnt/sda2/tce/optional#
root@box:~# grub
GNU GRUB version 0.97 (640K lower / 3072K upper memory)
[ Minimal BASH-like line editing is supported. For
the first word, TAB lists possible command
completions. Anywhere else TAB lists the possible
completions of a device/filename. ]
grub> root (hd0,1)
Filesystem type is ext2fs, partition type 0x83
grub> setup (hd0)
Checking if "/boot/grub/stage1" exists... yes
Checking if "/boot/grub/stage2" exists... yes
Checking if "/boot/grub/e2fs_stage1_5" exists... yes
Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 16 sectors are embedded.
succeeded
Running "install /boot/grub/stage1 (hd0) (hd0)1+16 p (hd0,1)/boot/grub/stage2
/boot/grub/menu.lst"... succeeded
Done.
grub> quit
root@box:~# umount /mnt/sr0
root@box:~# eject /dev/sr0
root@box:~# reboot
-
Hi
reply 30
can that be invoked by ctrl + alt + f1
Yes and No. The trouble is if you already have graphics running and want to do something with X not running, the correct method is to click on the exit options and choose Exit to prompt......which has designed by the TC team to shutdown graphics.
If you just want to see a console, TC only gives you one, and your action will show it, then change that action to c/a/F2 to get back to X.
your last reply ....sorry its a bit long to give a quick reply but I would like you to understand that it generally frowned upon to weaken your permissions to 777.
find /mnt/sda3/tce/ -perm 775
/mnt/sda3/tce/
/mnt/sda3/tce/optional
/mnt/sda3/tce/ondemand
Above is my sda3 system. If you re-look at your last reply you have a lot of files with r-- r-- r-- that ain't right!
tce/optional has some minor quirks as we have not all built them to the wiki standard but IMHO
664 with tc:staff would be the way to go.
The apps panel must have the abiltiy to over write an older file on update and without the w.....updates will fail
I could waffle on, but I hope you take the time to review your permissions
TCZs are files that are read by the function tce-load or whatever its called in the TC boot up scripts, they are not executables.
As I said, read the wikis.
##########
Alternatively leave those folders as 777, reboot and fix them when you can tell you have a graphical system
good luck
-
Hi ejames82
That's one busy post, but this stands out:
kernel /boot/vmlinuz quiet tce=sda2 tce=home tce=optI think this might work a little better:
kernel /boot/vmlinuz quiet tce=sda2 home=sda2 opt=sda2
-
ahh I am slow witted today
you copied from a cd that is read only, thats why the copy gave your r--
chmod -R 775 /mnt/sda2/tce
ok I have that wrong
try
chmod 775 /mnt/sda2/tce
chmod 775 /mnt/sda2/tce/optional
chmod 644 /mnt/sda2/tce/optional/*
reboot and run .....ls -al /mnt/sda2/tce/optional....no need to post it, just tell us if you now have rw- r-- r--
good luck
-
aus9,
I checked out your reply and will respond categorically tomorrow.
Rich,
you have an eagles eye. I finished the install and tried booting to hard drive and it said kernel is corrupt. a mistake like that one would cause that exactly. to say the least, the OS didn't behave.
it shows I am tired out. I will fix this tomorrow after I recharge. I don't want to make things worse.
thanks for the replies
-
recap:
I do a fresh command-line install and cannot boot past the console, so I boot to the cd and enter this command:
cp -a /mnt/sr0/cde/* /mnt/sda2/tce
but now, my appbrowser won't open. this command fixes it:
chmod 777 /mnt/sda2/tce/optional here are the permissions of /mnt/sda2/tce/optional after the command:
drwxrwxrwx 2 root root 4096 May 9 11:50 optional
here I run other commands and show the permissions after the commands.
root@box:/mnt/sda2/tce# chmod 775 /mnt/sda2/tce/optional
root@box:/mnt/sda2/tce# ls -la
drwxrwxr-x 2 root root 4096 May 9 11:50 optional
appbrowser won't open
root@box:/mnt/sda2/tce# chmod 777 /mnt/sda2/tce/optional
root@box:/mnt/sda2/tce# ls -la
drwxrwxrwx 2 root root 4096 May 9 11:58 optional
now it will
so I know specifically that the third w in the permission line dictates whether or not I am able to open appbrowser
root@box:/mnt/sda2/tce# chmod 775 /mnt/sda2/tce
appbrowser opens
root@box:/mnt/sda2/tce# chmod 775 /mnt/sda2/tce/optional
now it won't open
root@box:/mnt/sda2/tce# chmod 644 /mnt/sda2/tce/optional/*
still won't open
root@box:/mnt/sda2/tce# chmod 777 /mnt/sda2/tce/optional
now it will open
-
aus9,
I was able to get to console by choosing exit>exit to prompt but ctrl + alt + f2 didn't work to return me to X
startx
did.
thanks.
-
Hi ejames82
If the GUI is running, Ctrl-Alt-F1 will get you the console and Ctrl-Alt-F2 will get you back to the desktop.
If you use exit>exit to prompt or Ctrl-Alt-Backspace to get to the console, it kills the GUI, and the only way back is
to restart the GUI with startx.
-
Hello Rich,
ctrl + alt + f1 to get to console and ctrl + alt + f2 to get back to gui is now working for me.
thanks.
-
drwxrwxrwx 2 root root 4096 May 9 11:58 optional
consider changing the ownership
sudo chown -R tc:staff /mnt/sda2/tce
re-look at your /mnt/sda2/tce/optional pls
you no longer need 777 as you are tc and you are already in the first group rwx so now that you own that folder, drop sudo
chmod 755 -R /mnt/sda2/tce
(takes care of folders now do files)
chmod 644 /mnt/sda2/tce/optional/*
and test you can download an app
you are almost there, I can feel it ...
-
aus9,
nice work. :) all of those commands went without a problem and appbrowser still works.
tc@box:/mnt/sda2/tce$ ls -la
drwxr-xr-x 2 tc staff 4096 May 9 21:25 optional/
what's more, I ran appbrowser>apps>maintenance and ran everything listed in there. I haven't received any more prompts from firefox since.
the appsaudit feature seems to be discontinued. it's mentioned in the wiki. little things that are new to tinycore I've discovered in different places. tinycore has always been solid, though, even way back when I first tried it out, version 2.11.1.
everything is working like it's supposed to be. I hope I don't find any more problems.
thanks aus9.
-
I spoke too soon. I opened appbrowser and clicked on apps>cloud>browse and I got an error:
error, check network, mirror or writable extension directory
I am not receiving a list of extension to choose from
-
ahh network their end may be under maintenance, I get similar error
yep this page borks
http://tinycorelinux.net/downloads.html
Nothing to worry about, it happens from time to time.
-
very possible. I tried using the live cd 3.8.4, and also got the same problem.
I will give it a little time, then revisit the issue.
thanks.
-
Also I can not boot CorePlus from another boot loader. I use the following in the menu.lst file:
root (hd0,0)
kernel /tce/boot/vmlinuz
initrd /tce/boot/core.gz
The startup fails at a $
It seems a lot of people have this problem but I can not find the answer on the forum. Im surprised its not in the FAQ.
Is there an answer?
-
Have you read this whole thread from the start?
-
ejames82, I am sure the extension 'TC-Install' could have saved you from all this trouble
-
I read all of the tread but there is no menu.lst that works for me. I sems to make it worse.
I didnt want to use the boot loader because I want to keep the old settings since I also have two other distros on my computer.
Isnt there a kernel line which I can simple put in my menu.lst to get me past the $ promt an start X?
-
Hi Alb
The reason you are getting a command prompt is because you did not install the extensions required for a GUI.
Create a partition for Tinycore. Then, using the install utility included with CorePlus (http://tinycorelinux.net/install.html).
Select Existing Partition
DO NOT Mark Partition Active
DO NOT select Install Bootloader
complete the installation.
In menu.lst, change root (hd0,0) to point to your Tinycore partition.
Open the /boot/extlinux/extlinux.conf file in the Tinycore partition. Copy the initrd and kernel paths to menu.lst. Copy
everything starting from quiet to the end of the line to the kernel line in menu.lst.
Reboot.
-
Hello Rich,
this the kind of answer Ive been looking for!
I already had frugally installed CorePlus to a directory in hda1, but in the directory /boot/extlinux is no file called extlinux.conf, in fact there is no file at all.
rgds Albert
-
Hi Alb
At steps 5 and 6, did you select Core and X/GUI Desktop and Install Extensions?
-
I did not get step 5 (I was surprised) and at step 6 I did indeed install extensions to TDE. I didnt know what it meant but after installation all the CorePlus files were in a directory called TDE.
-
The path to TCE needs to be specified on the command line. Something along the lines of
tce=sda1
maybe
-
Hi Alb
Just reread the install tutorial. Step 5 only shows up when installing from a CorePlus CD. Step 6 only shows up when
installing from a Tinycore CD.
... all the CorePlus files were in a directory called TDE.
Since you only saw step 6 that suggests you used a Tinycore CD, though it still should give you a GUI. Are you sure
about the directory name? It should have created a directory called /tce. You should find it under /mnt/sda1.
-
Im sorry, it is TCE (not TDE).
I installed the CorePlus from the ISO file on a memorystick.
Now I have removed the dir TCE and did the installationprocess again. I did not install Extensions and since I did not get step 5 I assume that should have gone right.
But again no extlinux.conf file in the extlinux directory.
Any suggestions?
-
Now I have completed the frugal installation again using the boot loader and marking the partition bootable.
After a restart Core doesnt boot, again stops at the $ promt.
Then I reinstalled my old bootloader and now found the extlinux.conf file. I made the changes Rich suggested in his reply two days ago but still the boot fails at the $.
I am about to give up on TinyCore unless someone can come with a sollution. Anyone?
-
If you get a $, the boot did not fail.
Make sure /etc/sysconfig/tcedir is pointing at your persistent tce directory and install the GUI extensions.
-
Hi Alb
Now I have removed the dir TCE and ...
The tce directory contains the onboot.lst file that tells the OS which extensions to load. It also contains the subdirectory
optional where the extensions are stored. Without those you won't get a GUI.
-
...I installed the CorePlus from the ISO file on a memorystick.
...I did not install Extensions
The extensions are needed otherwise you'll only boot to a $ prompt. Also a memory stick will almost certainly need the additional " waitusb=5 " boot code
-
Both the onboot.lst file and the directory optional were empty.
Has this something to do with step 6 where I took the second option Dont install Extensions?
I can not find the TCE/CDE directory. Can you explain what is meant by "The extensions you want installed"?
What are Extensions and where can they be found?
-
optional components, e.g. GUI
-
Hi Alb
Has this something to do with step 6 where I took the second option Dont installe Extensions?
Yes, because you chose a text based (command line only) environment rather than a GUI.
-
Agian I tried the installationpocess but no succes.
I do not get step 5 so I can not choose GUI and at step 6 I can not find a TCE directory to point to.
What am I missing here?