Off-Topic > Off-Topic - Tiny Core Lounge
Tiny core on Eden ulv 500MHz cpu
mocore:
--- Quote from: Stefann on August 12, 2024, 07:44:00 AM --- I have to completely disable boot from internal drive (to disallow the baseline damn small Linux to boot) to het tiny core booting from usb.
The inconvenience is that this requires to hookup monitor and keyboard which is inconvenient as the computer is in a crammed utility area.
Any advice is welcome but I can live with it.
--- End quote ---
begging the question....
what (loader) / how - exactly dose the the " damn small Linux" boot ?
fwiw
with this info it might be possible to add an option to *whatever* loader's configuration
which boots from the usb-device/partition-uuid ...
and (if that works) set that ( in the loader cfg) as default and dsl as a fallback ( if usb-part-uuid is not found)
Stefann:
--- Quote from: mocore on August 12, 2024, 09:46:50 AM ---
--- Quote from: Stefann on August 12, 2024, 07:44:00 AM --- I have to completely disable boot from internal drive (to disallow the baseline damn small Linux to boot) to het tiny core booting from usb.
The inconvenience is that this requires to hookup monitor and keyboard which is inconvenient as the computer is in a crammed utility area.
Any advice is welcome but I can live with it.
--- End quote ---
begging the question....
what (loader) / how - exactly dose the the " damn small Linux" boot ?
fwiw
with this info it might be possible to add an option to *whatever* loader's configuration
which boots from the usb-device/partition-uuid ...
and (if that works) set that ( in the loader cfg) as default and dsl as a fallback ( if usb-part-uuid is not found)
--- End quote ---
DSL boots with syslinux3.70. later versions bring problems.
I don't know whether that supports uuid. t.b.h. I had never heard from uuid until last week.
the tiny core core does not fit on the boot-partition: that partition is just big enough for dsl.
And I sure want to fully setup a new p1 partition. Want a clean start. This time a BIG boot partition that includes the ice folder.
Thanks for the suggestion.
mocore:
--- Quote from: Stefann on August 12, 2024, 11:12:52 AM ---DSL boots with syslinux3.70. later versions bring problems.
--- End quote ---
what dose the tiny core usb boot (syslinux/grub/ect) ?
if its also using syslinux
this post might have some relevant perspective
"Is it possible to use Syslinux to boot another drive?" @ https://bbs.archlinux.org/viewtopic.php?id=224923
in summery
ether chain-load the (syslinux)loader on the usb
or create an entry in the internal 'dsl' syslinux config , to set/select the usb partition and boot the linux/initrd from it .
the process would be conceptually similar for other loaders , the cfg syntax would differ ..
Stefann:
--- Quote from: mocore on August 12, 2024, 11:42:55 AM ---
--- Quote from: Stefann on August 12, 2024, 11:12:52 AM ---DSL boots with syslinux3.70. later versions bring problems.
--- End quote ---
what dose the tiny core usb boot (syslinux/grub/ect) ?
if its also using syslinux
this post might have some relevant perspective
"Is it possible to use Syslinux to boot another drive?" @ https://bbs.archlinux.org/viewtopic.php?id=224923
in summery
ether chain-load the (syslinux)loader on the usb
or create an entry in the internal 'dsl' syslinux config , to set/select the usb partition and boot the linux/initrd from it .
the process would be conceptually similar for other loaders , the cfg syntax would differ ..
--- End quote ---
tiny core also uses syslinux.
My existing DSL backup USB had a very small boot-partition, just enough for DSL image, I did not want to erase that to make place for tiny Core Image because "if something went wrong I sure wanted to have my DSL baseline and backup".
Indeed I got my 1st tiny core loaded by creating a bootable USB stick using the notes I got from DSL. Using the syslinux-3.70 (it's now at version 6). Mind you... basically using a process with tools from 2008...
From there I created multiple "pristine" USB-sticks using the tiny core built-in install tool.
It runs like a charm from USB now.
Yes... One can hobby around... but I'm setting this up with the idea that it will be a reliable base for multiple years. So really want to do this good. Want to use "as much non-modified tools as possible".
So... I'm n ow very well able to boot from USB and setup bootable internal drive... but... bit hindered by the refusal of the computer to obey the bios-boot-sequence. It boots from internal drive even now I set bootsequence to usb first. Internal drive is a CF-card that I can easily eject, but than I cannot write it. So... need to hookup monitor/keyboard. This is very possible, just a bit crammed in the utility room.
but.. now hobbying with un-setting the boot-flag:
- booting from internal drive into DSL
- unset boot-flag from the internal drive I just booted from
- reboot should than go from USB
we'll see....
I'll get it sorted out one way or the other.
mocore:
the syslinux "*LOCALBOOT" config option might be of interest
https://git.kernel.org/pub/scm/boot/syslinux/syslinux.git/tree/txt/syslinux.cfg.txt#n292
--- Quote from: Stefann on August 12, 2024, 11:12:52 AM ---DSL boots with syslinux3.70. later versions bring problems.
I don't know whether that supports uuid. t.b.h.
I had never heard from uuid until last week.
--- End quote ---
fwiw just happened to read
--- Quote from: roberts on June 06, 2011, 12:53:52 PM ---f you are going to run Tiny Core from a pendrive, or any removal device, you should be using UUID or LABEL, to properly identify the device. The installation program for pendrives included with Tiny Core up to v3.6 provides an automatic setup with such features. You will also need a waitusb for slow removal devices to be detected. This is also provided with the install program.
--- End quote ---
in this case uuid is a command line option passed to the kernel/modules & (i assume ??... [1] ) init scripts
see also proc/cmdline
--- Quote ---The kernel parses parameters from the kernel command line up to “–”; if it doesn’t recognize a parameter and it doesn’t contain a ‘.’, the parameter gets passed to init: parameters with ‘=’ go into init’s environment, others are passed as command line arguments to init. Everything after “–” is passed as an argument to init..
--- End quote ---
[1] https://www.kernel.org/doc/html/v4.14/admin-guide/kernel-parameters.html
[2] https://raspberrypi.stackexchange.com/questions/113645/what-is-the-difference-between-adding-ro-to-boot-cmdline-txt-vs-etc-fstab#comment220872_128206
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version