Boot option iso=sdb1 in TinyCore 4.4

[V.Krishn]

How to use new boot code, e.g., iso=sdb1,
Is this option available in boot options list (F2, etc)?

[roberts]

It is documented here. http://forum.tinycorelinux.net/index.php/topic,12786.msg69982.html#msg69982

Cannot be easily explained/documented as a single "F" line nor is it often required.
As it was documented as above some thought it a boot loader, which it is not!

[V.Krishn]

I could suggest a boot cheatcode text file in /boot dir

[bmarkus]

I could suggest a boot cheatcode text file in /boot dir

See f2, f3, f4 files in the boot directory or press F2, F3 or F4 for boot options.

[vinnie]

As it was documented as above some thought it a boot loader, which it is not!

 

But I think it would be useful to have all features/bootcodes organized in a place to avoid getting lost in the mists of time!

[Rich]

Hi vinnie
Most of them are listed in the FAQs.
A lot of them are listed in   /usr/share/doc/tc/bootOptions.txt.
All of them should be in   /etc/init.d/tc-config.

[maro]

... All of them should be in   /etc/init.d/tc-config.

Hmmm, that might be the case for the majority of TC specific boot codes. But in the Core there are some other scripts that interpret these TC specific boot codes:
    /etc/init.d/rc.shutdown
    /etc/init.d/tc-restore.sh
    /usr/bin/filetool.sh
    /init
    /usr/bin/scm-update
    /usr/bin/tce-setup
    /usr/bin/tce-update
(ignoring for a moment: '/etc/init.d/tc-functions', and '/usr/bin/showbootcodes', plus some executables like '/bin/busybox', '/sbin/udevadm' and '/sbin/udevd' which probably interpret some more generic boot codes)

If adding the default TinyCore extensions (e.g. from the 'cde' directory) there are some more:
    /usr/bin/setupdesktop
    /usr/bin/startx
    /usr/local/bin/appsaudit
    /usr/local/bin/exittc
(and ignoring again '/usr/local/bin/stats')

Please note that these lists are only containing files that directly interpret '/proc/cmdline'. In many cases the result of such an interpretation is stored in a file (e.g. '/etc/sysdir/icons') and several other scripts then use said file. So there are many other "secondary consumers" of TC specific boot codes.

Therefore I'd like to state that whilst I also use '/etc/init.d/tc-config' as my first stop when trying to figure out the treatment of a given boot code, one has to be aware that this is likely to be a necessary, but maybe not a sufficient approach.

[vinnie]

uhm, usefull

[ndrancs]

Hi Robert,
This is feature i waiting for in TC, likes other distro,

[cast-fish]

Hello

THis appears to be a super feature to put into Tinycore....it appears to save a lot of effort on the part of any user.

Also the SCM system appears to be superb feature of TCL 4.4. I Have tried it out and it's simple to understand and simple operate with single clean files.

Would it ever be the case that the "whole" app browser will become SCM styled eventually?

thanks

V.

[cast-fish]

hello

do i understand this new "iso" bootcode right?

1) it is a feature for booting only TCL .iso files  (remastered tcl .iso files..... and such like)
2) it will read the entire contents of the .iso file and you can arrive at the GUI desktop with all extensions
detected and installed..(by using extra commands)


thanks

V.

[gerald_clark]

1. No it does not boot anything. 
2. Not exactly. It loop mounts the ISO so it can be treated like a DVD.

[cast-fish]

Hmm

not sure how to use it.....is this correct below...?

The new ".iso" bootcode assumes your machine is already booted with a TCL cd disc and is at the
boot prompt. Your hard drive contains some arbitrary remastered TCL .iso file with extensiosn in it.

Your point the new bootcode to that arbitrary iso file  (from your TCL boot prompt)

this should then mount that remastered .iso and arrive at a command line version  of that  remastered TCL .iso?

then follow more commands to arrive at the X gui desktop?...

and what about the extensions in that remaster?

V.