Core v4.5.2

[bmarkus]

Hmmm, reviving old thread on virt.machines :
could we have/do we already have, lxc ready kernel for last TCL version? (now 4.5.2.
and extra question : any one, then, able to build a tcz extension with the tcl toys^Wtools?
thanks a lot for the fine work.
clu
(also posting in the news thread)

Please do not double post.

[coreplayer2]

It's my understanding that waitusb=10 provides only a maximum time to wait for detection, meaning that after after USB device detection the boot process continues regardless if the process only took 5 seconds to detect the hardware.

That's my understanding, however if the config file is specifically set to say waitusb=20 you'll sit waiting for the exact full 20 seconds after the line " Starting udev daemon....." is displayed before boot process continues.

Is that right??

[gerald_clark]

You have to specify the device if you don't want to wait the full 20 seconds.

[coreplayer2]

Thanks, I think the only device we would be interested in is sdb1 so for example:  waitusb=20 tce=sdb1,  then why not waitusb=20 tce=sd?    by defining the usb are we only specifying the obvious, effectively is there really a choice?

While I think about the process, I'm assuming this will be adequate?  waitusb=20 tce=sdb1

[gerald_clark]

Because that is not the proper syntax. Read the wiki.
http://wiki.tinycorelinux.net/wiki:install_hd?s[]=waitusb

[coreplayer2]

Thanks, unfortunately after looking at the WAITUSB script I noticed the blkid -lt options.  Since I have only limited control over these two parameters; LABEL and UUID    I guess I'll have to either replace blkid -lt  with blkid  to accept /dev/sdb1   or set waitusb=15 to avoid the "Call Trace" errors we are seeing frequently, because 10 seconds is not always a sufficient timeout period.

 


PS maybe I'm reading the -t option wrong..?    perhaps we can specify waitusb=5:/dev/sdb1  ??

[Rich]

Hi coreplayer2
This is not right place for that discussion, TCB Talk would be more appropriate.

[coreplayer2]

lol I know but it's kinda hard to move once you've begun the discussion..   Thought it may have been a change in this release but was wrong about that.