Tiny Core Base > Release Candidate Testing

tinycore_1.0rc4

(1/3) > >>

roberts:
Release Candidate 4 now posted.

* Updated Xvesa kdrive server.
* Updated busbox v1.12.3 and changed applet selection based on recent changes (mount & losetup).
* Changed default lang to C.
* New cpu/mem/swap meter for .jwmrc-tray (currently commented out).
* Dropped unused lzma, lzmacat, and xload.
* General cleanup.

Thanks to all for continued feedback.

^thehatsrule^:
Also included is the udevtrigger change in tc-config
Reference thread: http://forum.tinycorelinux.net/index.php?topic=145.msg914#msg914

It seems to have the modules for the NIC loaded, but is not configured automatically (for network access).
As compared to rc3, these modules also are now loaded on boot on this system: parport_pc, parport, ac

EDIT:
- it might be due to the boot going too fast(?)
- using waitusb= was a workaround that allowed the network be configured automatically

roberts:
Thanks for the reminder. I had updated the image with the trigger change but not my journal.
My too parport_pc and parport are now auto loaded, before I had them in /opt/bootlocal.sh.

curaga:
The evidence supporting the change so far is good :)

Anyone who had their netcard module not autoload, does it do that now?

Also, has anyone tested terminal server after the busybox change?

curaga:
Tested. Parport autoloaded on all comps, on one comp iee1394 (firewire) got loaded too. :)

The busybox update did break TC-terminal-server. Ash previously worked the correct way, keeping backgrounded processes running after the script itself had closed, but now it closes them with the script. A patch for this new behavior in storage.

Navigation

[0] Message Index

[#] Next page