How to know which partition to install on, if I don't see the sizes?

[MrAccident]

ISO - CorePlus; in "blkid" - iso9660; from - http://distro.ibiblio.org/tinycorelinux/downloads.html.
I installed it with the installer. Frugal. Clicked next next etc; other than the "non-US keyboard" option.
TC is installed on partition "sdb1" type ext4
Conf file - /mnt/sdb1/tce/boot/extlinux/ - that's the path in Puppy.

I can't copy the text from the terminal; and there are all the long file names of the partitions; so if some other information is needed - tell me.

[MrAccident]

In the file "extlinux.conf" the text is:
DEFAULT core
LABEL core
KERNEL /tce/boot/vmlinuz
APPEND initrd=/tce/boot/core.gz quiet  waitusb=5:UUID="c16640ef-c0bc-4cff-9245-85615e9d8708" tce=UUID="c16640ef-c0bc-4cff-9245-85615e9d8708"

Puppy is installed on sda1 and TC on sdb1.

gerald_clark - I asked - where can I find this "useful information"?

[Misalf]

Since you're

[...] a newb to Linux.

I can understand that you're not really aware about what info is useful/needed.

Please do this in while Puppy

Code: [Select]

blkid /dev/sdb1

You can just mark anything in the terminal with your mouse (no need to 'copy' but the text needs to still be marked while pasting) and paste it by clicking the mouse wheel. If you're not using a mouse, it can be pasted by pressing "SHIFT"+"INSERT" (not every program understands this, though).

Also, please post your onboot.lst (just in case).
HINT: Use the  [ code ]-your-outup-here-[ /code ]  tags (without the spaces) for such outputs.

[MrAccident]

# blkid
/dev/sdb5: UUID="13FF883D343D1961" TYPE="ntfs"
/dev/sdb3: UUID="fa48b2d0-f9cf-4d42-bdc9-2a3e79a84391" TYPE="swap"
/dev/sdb1: UUID="c16640ef-c0bc-4cff-9245-85615e9d8708" TYPE="ext4"
/dev/sda5: UUID="8C783A62783A4B6A" TYPE="ntfs"
/dev/sda3: UUID="313f00fc-1bad-4f97-9525-32db8a9ac7ef" TYPE="swap"
/dev/sda1: UUID="09cd876b-21ad-4196-9a6a-8b0a04665f20" TYPE="ext4"
/dev/sr0: LABEL="CorePlus" TYPE="iso9660"
/dev/loop1: LABEL="CorePlus" TYPE="iso9660"

OK, now you know all my secrets. :-P

[gerald_clark]

No, you did not show the full path to your extlinux.conf file.
You installed TC to your 2nd drive, but we don't know where you installed the boot loader.

[MrAccident]

Sorry; didn't find "onboot.lst". And "code" and "/code" didn't do anything in the terminal; if that is what I was suppose to do.

gerald_clark - so what can I do about it?

[Misalf]

Nah, the "code" tags are for posting stuff on the forum.

OK, the UUID of

Code: [Select]

/dev/sdb1: UUID="c16640ef-c0bc-4cff-9245-85615e9d8708" TYPE="ext4"
and

Code: [Select]

tce=UUID="c16640ef-c0bc-4cff-9245-85615e9d8708"
are identical. So that was not the problem.

Maybe your downloaded ISO got corrupted.
You can check via

Code: [Select]

md5sum /path/to/your/copy/of/CorePlus-5.3.iso
and compare it with the contents of this file
http://tinycorelinux.net/5.x/x86/release/CorePlus-5.3.iso.md5.txt
which is

Code: [Select]

312a35d769bd61271bfbf6f08eae8492  CorePlus-5.3.iso


[gerald_clark]

You still did not show the full path to your extlinux.conf file you posted.
You may have installed the boot loader and boot files on different drives.
That won't work.

[MrAccident]

By comparing - you mean - comparing those two numbers?:
312a35d769bd61271bfbf6f08eae8492  /mnt/sda5/חדש/CorePlus-current.iso
312a35d769bd61271bfbf6f08eae8492  CorePlus-5.3.iso

gerald_clark - you mean this path? - /mnt/sdb1/tce/boot/extlinux/extlinux.conf

[Misalf]

Oh, I just checked the syslinux install of my dual-booting laptop where I have syslinux installed in the MBR, using a config file on the first partition (FAT) and for Linux, I have another (sys)extlinux installation installed to the Partition Table of /dev/sda3 (ext4) using onother config.

It's chainloading from one boot loader to the other like this:

Code: [Select]

LABEL linux
 MENU LABEL Linux on /dev/sda3
 KERNEL chain.c32
 APPEND hd0 3


[MrAccident]

Misalf - I don't understand if it has something to do with me.

About installing TC on the same partition. I don't have a problem installing it there;
but will TC be in it's own separated folder?
Will I be able to later remove one of them and keep the other, just by deleting it's folders?
And if the same will happen - will I be able to delete TC's folders with Puppy's live-CD; and the problem will go away?
It'll really be a problem if I won't be able to boot into anything, and will have to reinstall and loose all the settings (mostly FireFox).

[Misalf]

It seems boot loaders from the syslinux family aren't able to boot from another drive as the one the boot loader is installed on (I'm not sure; I'm more used to grub2 where it is possible).

About installing TC on the same partition. I don't have a problem installing it there;
but will TC be in it's own separated folder?

Yes. on sda1, it will be /mnt/sda1/tce/.../

Will I be able to later remove one of them and keep the other, just by deleting it's folders?

Yes. But make sure you don't delete the directory which contains additional boot loader files and the config file (either /boot/extlinux/  or  /tce/boot/extlinux/).

And if the same will happen - will I be able to delete TC's folders with Puppy's live-CD; and the problem will go away?

I don't understand. If something doesn't boot, you probably won't be able to fix it by removing stuff. You'd rather make it worse if you're not absolutely sure what can be deleted.

It'll really be a problem if I won't be able to boot into anything, and will have to reinstall and loose all the settings (mostly FireFox).

The good thing about, both, Puppy and Core, is that you can easily backup your settings to an external drive (Flash, CD, whatever) in case something terrible happens. Both distros save the user settings in packages.

For Core it is
/tce/mydata.tgz

For Puppy I'm not sure right now but usually it's something like
/puppysave.sfs

[MrAccident]

If I understand correctly - TC and Puppy have each, their own boot-loader.
So if the same will happen - the fault is in TC's one. So if then I'll delete it - I'll be able to boot into Puppy.
Am I wrong?

Yeah I know the save file. Didn't know exactly how it works. So all the bookmarks, sessions etc - will be saved there?

[Misalf]

Yes, you are wrong. ;^)
The BIOS is configured to boot from a certain drive and it does if that drive has some sort of loader in its MBR (Master Boot Record). The config file of that boot loader can then have several entries for all sorts of linuxes you have installed, pointing to different locations and files (kernel and initrd in sub directories). If you want to boot from another drive or partition while the boot loader from the first drive was already started by the BIOS, you would have to chainload from one boot loader to another (again, I'm not quite sure about that; might be possible even with syslinux but I used chainloading to start a second boot loader from another partition [installed to partition table] - pretty much the same as chainloading to another drive [MBR]).

So if the same will happen [...]

Sorry again, I don't understand.

You won't be able to start one boot loader by deleting another one. The MBR contains the reference to the latest installed bootloader files (stored on the disk in a sub directory; usually /boot/...).
While two Linux installers from different distros have messed with your drive now (it seems), I'd suggest you try find a tutorial on the internet to install extlinux manually (so you can choose the extlinux path) with any live CD (Puppy or CorePlus or anything - doesn't matter) so that you know for sure which bootloader files are actually being used and what can get deleted (to clean up the mess for preventing further confusion with config files all over the place).

[MrAccident]

Alright. Thank you both for all the effort!