Tiny Core Base > Release Candidate Testing

tinycore_v2.7rc2

<< < (2/3) > >>

roberts:
bmarkus. Thanks for the kind words and. Merry Christmas!

In just over one year from going public, my desire to create a tiny base Linux system has come along way. I have indeed selected a great team to help and support this project. But it is also the community, I wish to thank.

It gives me inspiration and motivation to see the efforts put forward by the team and community. The saying "built it and they will come". I have had great joy in building it and well to see the results is amazing. Thank you for contributions especially XFCE and LXDE. From Tiny Core to fully integrated desktop and all stops between. Awesome!

roberts:

--- Quote from: maro on December 18, 2009, 10:03:17 PM ---Just a minor suggestion for the "ondemand" script to use in line 31 "mkdir -p ..." (instead of "mkdir ...").

On that thought, I wonder whether there is a reason not to use in pretty much all cases the "-p" option. This way one script does not have to rely on the fact that another process has already created all parent directories.

--- End quote ---

OK. Will do. Thanks.

philip:
I had no end of trouble with 2.7rc2, especially the wireless, on my Acer Aspire One netbook. Until I powered the thing off, counted to 0xA, and rebooted from scratch. Then everything worked! Google says this is a known feature of the Atheros wireless chips: if they get confused (I'm not sure how), nothing but a nice power-off nap will make them perform as expected. This is the kind of loopy undocumented experience that may help somebody else, so I mention it here.

Also, I wanted to get in on the general celebration of TinyCore and how sweet it is. I have four thin clients (2 home-made, 2 rescued from Windows) running pretty minimal TC. Each one is always on and getting lots of use. Not to mention my peppy, instant-on, bloat-free netbook now running the latest release candidate. Hearty thanks and warm greetings to Robert and Team TC!

bmarkus:
Just few minor notes.

In /etc/sysconfig/cdroms drive ( /dev/hdd ) is listed twice in one line.

Theres is an ampty file, /etc/sysconfig/newlibs. What is it inteded for?

Feature request for 2.8:

Record boot media, partition system was booted from in /etc/sysconfig/bootmedia or something like this.

Implement priority on multiple /tce dirs. Booting from USB on a system with HDD and /tce on both HDD and USB, HDD dir is used. /tce on the boot USB would be more practical.

roberts:

--- Quote from: bmarkus on December 19, 2009, 04:27:27 AM ---Just few minor notes.

In /etc/sysconfig/cdroms drive ( /dev/hdd ) is listed twice in one line.

Theres is an ampty file, /etc/sysconfig/newlibs. What is it inteded for?

Feature request for 2.8:

Record boot media, partition system was booted from in /etc/sysconfig/bootmedia or something like this.

Implement priority on multiple /tce dirs. Booting from USB on a system with HDD and /tce on both HDD and USB, HDD dir is used. /tce on the boot USB would be more practical.

--- End quote ---

re: cdroms
It is probably listed twice because the system identified it as a cdrom and then again as a dvd. My guess is that your hdd is therefore a dvd. I use the list when I tightened up the rules in rebuildfstab to eliminate those extra devices. rebuildfstab is quite different from early 2.x.

re: newlibs
ldconfig is called after every extension load. However during booting I did not want to do such. So I  use newlibs as a flag. The flag is really no longer needed in 2.7 as it is always be set . A single call to ldconfig after booting should always be performed. I will remove the flag.

re: tce priority
You can always specify which device to use for your tce directory via the tce boot code.

Navigation

[0] Message Index

[#] Next page

[*] Previous page