Thanks for the best Boot Code ever

[coreplayer2]

I have to say, thanks for this boot code 

waitusb=5:LABEL=TINYCORE

this, this above boot code has decreased my USB boot process tremendously, cut to a fraction of the previously used waitusb=5.   Another benefit of this boot code is seen when the Label has been corrupted (renamed etc) where a countdown will be presented, providing system feedback (beside the obvious accidental Label rename).

I know bmarkus is a heavy supporter of Labels, am sad to say I never gave enough respect to Labels before.  However all that has changed, now I understand the importance of Labels. 


Thanks again

[genec]

waitusb=5:LABEL=TINYCORE

Impressive.  I wonder if other "mountable targets" like UUIDs are valid.

[Rich]

Hi genec
Yes, you can replace  LABEL  with  UUID

[netnomad]

I have to say, thanks for this boot code 

waitusb=5:LABEL=TINYCORE
 

great contribution!
on my old 1,6ghz-one-core-notebook i could decrease the boot-time from 8,6s to 3,9s now.
that's a noticeable speed improvement.

thanks.

[aus9]

hi

sorry but best boot code ever?
Not if you are filesystem is on normal hard drives, meaning not USB drives.

but I would say, that a candidate for most unique bootcode ever.....one that AFAIK no other Linux distro can offer.....is a bootcode that allows you to choose which sound device you have enabled at boot up.

As you can see this too is subjective because most people do not have 2 sound devices to choose from eh?

http://wiki.tinycorelinux.net/wiki:alsa_part2#choose_sound_devices_at_boot

and it goes without saying but will say it,

thanks for this bootcode as well.

[hiro]

You can do this on other distros, too.
What if your 2 devices use the same driver?

[coreplayer2]

OMG. A spinning hard drive?  That's archaic... 

But I'll give you that if you have a rare PC with two audio cards then that boot code might be a contender.. 

[aus9]

What if your 2 devices use the same driver?

quite possible, true....but then you would probably be using a model=string to differentiate between them, I hope

[Lee]

I have to say, thanks for this boot code

waitusb=5:LABEL=TINYCORE
 

I use 30 seconds on my USB sticks -and- on my hard drives.  That way I can use an almost identical menu.lst (for grub4dos) on whatever I boot from.

The wait time is cancelled as soon as the device is recognized, so it doesn't cost me any time.  But if something is seriously fouled up, and the device never comes on line, 30 seconds gives me plenty of time to notice something is going on and take control of the situation.

FWIW, I rarely see it count down even one second before recognizing a USB stick and cancelling the wait time, though it wasn't always so.

And yeah, that's the coolest boot code ever because I can specify a subdirectory on the device:

Code: [Select]

waitusb=5:LABEL=cruzr0/boot/core4.6.2/tce
or

Code: [Select]

waitusb=5:LABEL=cruzr0/boot/core4.7rc3/tce

for two entirely separate distributions on the same usb stick.  -That- is cool!

[Lee]

OMG. A spinning hard drive?  That's archaic...

If you spin those old things too fast, all your bits will fly off the edges.  That's why there's more data on the outer tracks than the inner ones. 

[tinypoodle]

but I would say, that a candidate for most unique bootcode ever.....one that AFAIK no other Linux distro can offer.....is a bootcode that allows you to choose which sound device you have enabled at boot up.

As you can see this too is subjective because most people do not have 2 sound devices to choose from eh?

http://wiki.tinycorelinux.net/wiki:alsa_part2#choose_sound_devices_at_boot

I think such a bootcode might be sound system specific, when core has no sound system in base and offers 2 different sound systems treated equally as extensions...

[coreplayer2]

LEE  that is cool too 

Never occurred to me that you could combine the two,  I use a similar boot code to specify two separate versions of core via separate tce directories, am going to try your method thanks 

[gerald_clark]

Lee, I think you are confusing waitusb= with tce=.

[Lee]

Lee, I think you are confusing waitusb= with tce=.

You're right.  Looks like one of those "senior moments".  I can use that excuse now that I'm old enough that the AARP wants me. 

[curaga]

This highlights a lack in our docs, I believe

Core is not even close to being as complicated as many other distros, but it does have many nice tricks like that. If even experienced users like coreplayer2 find new old things, that to me says docs aren't up to snuff.

If only there was enough time I've had this idea of writing a book on Core, fully current for one release, with chapters describing the internals, some on projects to use Core for, some focusing on boot time etc. I was thinking both the pdf and ascii sources would be freely available online, dead tree version available at some cost.

Sadly, at least 'til christmas uni is taking all of my time, weekends too.