WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: tinycore_1.0rc4  (Read 4494 times)

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
tinycore_1.0rc4
« on: December 13, 2008, 09:24:13 PM »
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.
10+ Years Contributing to Linux Open Source Projects.

Offline ^thehatsrule^

  • Administrator
  • Hero Member
  • *****
  • Posts: 1726
Re: tinycore_1.0rc4
« Reply #1 on: December 13, 2008, 09:51:03 PM »
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
« Last Edit: December 13, 2008, 10:03:16 PM by ^thehatsrule^ »

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_1.0rc4
« Reply #2 on: December 13, 2008, 11:21:45 PM »
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.
10+ Years Contributing to Linux Open Source Projects.

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10050
Re: tinycore_1.0rc4
« Reply #3 on: December 14, 2008, 03:59:27 AM »
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?
The only barriers that can stop you are the ones you create yourself.

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10050
Re: tinycore_1.0rc4
« Reply #4 on: December 14, 2008, 06:38:54 AM »
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.
The only barriers that can stop you are the ones you create yourself.

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 11068
Re: tinycore_1.0rc4
« Reply #5 on: December 14, 2008, 07:09:54 AM »
modules loaded with rc3 (and all previous versions):
Code: [Select]
Module                  Size  Used by
battery                11268  0
ac                      5124  0

modules loaded with rc4:
Code: [Select]
Module                  Size  Used by
ohci_hcd               19076  0
scsi_wait_scan          2176  0
sg                     24500  0
pcmcia                 23272  0
firmware_class          7424  1 pcmcia
parport_pc             28440  0
parport                29012  1 parport_pc
ohci1394               25392  0
ieee1394               68488  1 ohci1394
yenta_socket           21388  4
rsrc_nonstatic         10240  1 yenta_socket
pcmcia_core            28948  3 pcmcia,yenta_socket,rsrc_nonstatic
tg3                    98948  0
battery                11012  0
ac                      4996  0

there's no parallel port on this machine, but the big news is that the netcard module (tg3) loads itself and connects to the network during boot without any waitusb (and the boot goes quickly).

curaga's display gadget shows (for eg) "2.0%C 9.5%M nan%S" - does "nan" mean no swap?

I tried the timeserver with the boot codes noutc tz=Asia/Dubai - now that the netcard connects on boot, I get the timeserver but, depending on when files were created in the boot process, I get a time/date format of either:
Code: [Select]
$ ls -l /tmp
drwxrwxr-x    2 root     staff           0 Dec 14 19:14 tce
which is good, or:
Code: [Select]
$ ls -l .jwmrc
-rw-r--r--    1 tc       staff        3763 Dec 14  2008 .jwmrc
which is less good

..no big deal, one day I'll have a laptop that I don't have to share with windows and I can set the time to UTC  :)
« Last Edit: December 14, 2008, 07:24:25 AM by Juanito »

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10050
Re: tinycore_1.0rc4
« Reply #6 on: December 14, 2008, 07:22:49 AM »
Could you upload your /proc/meminfo to storage? It should be 0, not nan
The only barriers that can stop you are the ones you create yourself.

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 11068
Re: tinycore_1.0rc4
« Reply #7 on: December 14, 2008, 07:27:28 AM »
Code: [Select]
$ cat /proc/meminfo
MemTotal:      1033920 kB
MemFree:        842320 kB
Buffers:         14556 kB
Cached:          76268 kB
SwapCached:          0 kB
Active:          48508 kB
Inactive:        75368 kB
HighTotal:      129688 kB
HighFree:        19520 kB
LowTotal:       904232 kB
LowFree:        822800 kB
SwapTotal:           0 kB
SwapFree:            0 kB
Dirty:               0 kB
Writeback:           0 kB
AnonPages:       33068 kB
Mapped:          15572 kB
Slab:             6120 kB
SReclaimable:     3628 kB
SUnreclaim:       2492 kB
PageTables:        476 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
WritebackTmp:        0 kB
CommitLimit:    516960 kB
Committed_AS:    89264 kB
VmallocTotal:   114680 kB
VmallocUsed:      3584 kB
VmallocChunk:   110068 kB

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10050
Re: tinycore_1.0rc4
« Reply #8 on: December 14, 2008, 07:33:16 AM »
The new busybox is not suid, so normal user can't ping anymore ;)
The only barriers that can stop you are the ones you create yourself.

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10050
Re: tinycore_1.0rc4
« Reply #9 on: December 14, 2008, 10:52:45 AM »
Since some network cards are slow, and we don't want to wait for 'em, I separated the dhcp portion out.  In that separate, backgrounded script, we first wait for all devices, and then do the dhcp loop. All in another thread from the main, to keep the boot fast for all.
See separated-dhcp.tgz in storage.
The only barriers that can stop you are the ones you create yourself.

Offline ^thehatsrule^

  • Administrator
  • Hero Member
  • *****
  • Posts: 1726
Re: tinycore_1.0rc4
« Reply #10 on: December 14, 2008, 11:55:45 AM »
I don't think busybox was ever suid before though.

FYI, nan is "not a number"

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_1.0rc4
« Reply #11 on: December 14, 2008, 12:08:20 PM »
busybox was not suid.
10+ Years Contributing to Linux Open Source Projects.

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_1.0rc4
« Reply #12 on: December 14, 2008, 02:37:02 PM »
I didn't see Curaga's patches in time for rc5.
I will have them in for rc6,

Glad it's only 10MB to download.
10+ Years Contributing to Linux Open Source Projects.