Tiny Core Linux
Tiny Core Base => TCB Q&A Forum => Topic started by: wurstbrot on February 02, 2009, 06:53:40 PM
-
TC 1.0, boot with 'norestore'. I tried the following mirrors:
ftp.nluug.nl/pub/os/Linux/distr/tinycorelinux/tce/ [ftp]
distro.ibiblio.org/pub/linux/distributions/tinycorelinux/ [http]
but appbrowser always says: "error connecting. try again later." What to do about it?
-
The tce/tcz parts are left for the 'Repository' field, so it should be
URL: ftp.nluug.nl/pub/os/Linux/distr/tinycorelinux
Protocol: ftp
Repository: tce
The other one (default) looks fine - so if it cannot connect there could be something going wrong on your end or temporarily on the server side.
-
Wow! Thx a ton!
ibiblio had a problem today, and your tip for ftp.nluug.nl did the trick! Great experience! I already got annoyed with dependencies.
Other topic: my grub kernel line reads:
kernel (hd0,2)/tc_10/bzImage norestore.
but it seems mydata.tgz gets restored anyway?! Is this cheatcode correct?
-
There isn't supposed to be a period, if it's there.
-
Here's what i did. Booted with:
kernel (hd0,2)/tc_rc9b/bzImage home=hda3 nodhcp
Created the folder /opt/.backgrounds/so and backed it up in mydata.tgz.
Then booted with
kernel (hd0,2)/tc_10/bzImage norestore
...and /opt/.backgrounds/so gets restored.
-
Does it say "skipping restore..." during boot? (If it goes by too quickly, add the "pause" bootcode)
-
No. It says: Restoring backup ... blabla Done.
-
What does `cat /proc/cmdline` say?
It might be a problem with your bootloader - post your configuration?
-
tc@box:~$ cat /proc/cmdline
norestore
This is GNU GRUB version 0.97
menu.lst
title tiny core 1.0
kernel (hd0,2)/tc_10/bzImage norestore
initrd (hd0,2)/tc_10/tinycore.gz
boot
-
Seems you are missing quiet
kernel (hd0,2)/tc_10/bzImage quiet norestore
-
Looks like some of the cmdline parsing explicitly check for a space before the bootcode, specifically those that use functions in /etc/init.d/tc-functions
grub seems to strip away the rest of the line unlike isolinux, so just having "norestore" will fail detection.
As a workaround, you can either put something else before norestore, such as the suggested "quiet". However, if you still want verbose kernel messages during boot, you can just use any other 'filler' text, such as kernel (hd0,2)/tc_10/bzImage filler norestore
-
...grub seems to strip away the rest of the line unlike isolinux, so just having "norestore" will fail detection.
That's an interesting comment - I have grub-0.97 set up to boot several os on a desktop and it completely ignores the kernel/boot parameters on an lfs build and dsl and only follows those of tc. Note that for each os I have several kernel/boot parameters entered...
-
Is not necessary to put "tinycore" between quit and any tinycore boot command?
kernel (hd0,2)/tc_10/bzImage quiet tinycore norestore
I have created a boot menu in syslinux.cfg and works great:
display boot.msg
default tinycore
label tinycore
kernel /boot/bzImage
append initrd=/boot/tinycore.gz quiet tinycore tce=sda1 restore=sda1 waitusb=5 laptop
label 2
kernel /boot/bzImage
append initrd=/boot/tinycore.gz quiet tinycore tce=sda1/tce/optional/gparted restore=sda1/tce/optional/gparted waitusb=5 laptop
label 3
kernel /boot/bzImage
append initrd=/boot/tinycore.gz quiet tinycore base norestore waitusb=5 laptop
prompt 1
timeout 300
F1 boot.msg
F2 f2
F3 f3
the menu is appended to boot.msg:
Tinycore menu:
1 - Tinycore complete <Enter>
2 - Tinycore gpart-image
3 - Tinycore base
Select option or <Enter>
Hope is useful, to me is
-
Onyarian: that is needed for syslinux/isolinux/etc if you want to use that label, but it is different for grub
-
I tried
kernel (hd0,2)/tc_10/bzImage pause norestore
and both arguments worked.
However with
kernel (hd0,2)/tc_10/bzImage norestore pause
only pause is working.
I don't know about the GRUB spacing issue, but an empty space before the first argument... might be stripped - if it is really there. Strange anyway. Must be different handling of arguments in the functions that use 'pause' and 'norestore'.
-
Yes, indeed. Good find. Will be fixed in the next RC, v1.1RC3.
-
Wow, that was quick. Works here, tc_1.1rc3. Nice colours, too.
Was it a GRUB thing?