Tiny Core Linux

Tiny Core Base => TCB News => Release Candidate Testing => Topic started by: roberts on February 12, 2010, 06:56:51 PM

Title: tinycore_v2.9rc3
Post by: roberts on February 12, 2010, 06:56:51 PM
The Third Release Candidate of v2.9 (tinycore_2.9rc3.iso), is now posted and ready for testing
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/2.x/release_candidates

tinycore_2.9rc3.iso
tinycore_2.9rc3.iso.md5.txt

Change log for Tiny Core v2.9

Release Candidate 1

* Updated appbrowser - added "Provides" to search for "What provides", also speed improvements.
* Updated appsaudit - added "Display All Not Depends On".
* Updated tce-load - added support for recursive dependencies.
* Updated tc-config - persistent home and/or opt, changed ext only support to not Microsoft file system support.
* Updated ab to use tmp work files.
* Improved language support by auto loading locale support extension(s) when both "lang=  " and the "-locale.tcz" extension(s) are available in tce/optional.
* Renamed *.core.gz to simply *.gz for ISO9660 compliance.
* Clean up of reported relics and empty directories.
* Updated f2 & f3 boot message screens.
* Fixed bug in tce-update easy mode.
* Dropped the embedded help file.

Notes:

Attention extension makers, please test the new recursive dependency process, but hold in abeyance until v2.9 is final.

Since the embedded help file has been dropped, your system menu, likely in your backup will need to be adjusted. Edit/remove such entry.


Release Candidate 2

* Upgraded busybox to stable 1.15.3
* Upgraded udev to 151.
* New "Set TCE Drive" in control panel to setup TCE directory, optional and mydata.tgz from cloud mode.
* Upgraded tce-load and appsaudit to support copy2fs flag and list in the base tce directory.
* Updated OnDemand to also support re-launching applicatons. Now one can always use the OnDemand menu section.
* Updated support for easy mode remastering /opt/tce now uses onboot.lst
* Updated tc-config to also make, if necessary, optional directory when tce= boot code is used.
* Added cache, .logo.xpm, and stats.txt to default /opt/.xfiletool.lst
* Updated  /opt/.xfiletool.lst to persist OnDemand menu item across reboots via normal backup.


Notes: Files likely in your backup that need updating:
The following have been added to the default /opt/.xfiletool.lst:

cache
home/tc/.wmx/Applications
home/tc/.logo.xpm
home/tc/stats.txt

Release Candidate 3
* Fixed new udev firmware issue.
* Fixed easy mode remaster to support copy2fs flag and list in static /opt/tce.
* Updated Control Panel, label change TCE Update to Update Apps.
* Purged system menu Tools section with item already present in Control Panel.

Items likely in your backup or persistent store that need to be updated
/home/tc/.wmx/Tools/

   
Title: Re: tinycore_v2.9rc3
Post by: gerald_clark on February 12, 2010, 10:30:40 PM
As reported for rc2 and still in rc3:

Quote
rebuildfstab[2685]: segfault at 8 ip 0806f590 sp bffd8510 error 4 in busybox[8048000+7c000]

I see these only when I have wireless_tools in onboot.
Title: Re: tinycore_v2.9rc3
Post by: Juanito on February 13, 2010, 12:44:49 AM
I do not see any errors with
Code: [Select]
$ sudo rebuildfstab /etc/fstab
Title: Re: tinycore_v2.9rc3
Post by: Juanito on February 13, 2010, 05:49:41 AM
I first though this was something between tc-1.x and tc2.x, but in fact things work as expected in tc-1.x and tc-2.8.1 - the issue is with tc-2.9rc3 - something to do with udev?

I've recently tried updating my old kayak xu from tc-1.x to tc-2.x

For some reason no usb devices show up in tc-2.9rc3 - I've played around for a while without much progress.

On both tc-1.x and tc-2.9rc3, I get this:
Code: [Select]
$ lspci
...
00:07.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01)
...
00:10.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
00:10.1 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
00:10.2 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
00:10.3 USB Controller: ALi Corporation USB 2.0 Controller (rev 01)

On tc-1.x, I get this:
Code: [Select]
$ lsmod
Module                  Size  Used by
usblp                  11264  0
ohci_hcd               19076  0

On tc-2.9rc3 (with usb ohci, ehci compiled in), I get this:
Code: [Select]
$ lsmod
...
usblp                   6556  0

On tc-1.x, I get this:
Code: [Select]
$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0424:a700 Standard Microsystems Corp.
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 03f0:0211 Hewlett-Packard OfficeJet G85

..but on tc-2.9rc3, "lsusb" doesn't show anything, but I do get this:
Code: [Select]
$ lsusb -t
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/2p, 12M
    |__ Port 1: Dev 2, If 0, Class=print, Driver=usblp, 12M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/2p, 12M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/2p, 12M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/6p, 480M
    |__ Port 3: Dev 2, If 0, Class=hub, Driver=hub/4p, 480M

..and on tc-2.9rc3:
Code: [Select]
$ dmesg | grep usb
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
usb usb1: configuration #1 chosen from 1 choice
usb usb2: configuration #1 chosen from 1 choice
usb usb3: configuration #1 chosen from 1 choice
usb usb4: configuration #1 chosen from 1 choice
usb usb5: configuration #1 chosen from 1 choice
usbcore: registered new interface driver usb-storage
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
usb 1-3: new high speed USB device using ehci_hcd and address 2
usb 1-3: configuration #1 chosen from 1 choice
usb 4-1: new full speed USB device using ohci_hcd and address 2
usb 4-1: configuration #1 chosen from 1 choice
usblp0: USB Bidirectional printer dev 2 if 0 alt 0 proto 3 vid 0x03F0 pid 0x0211
usbcore: registered new interface driver usblp
usbcore: registered new interface driver oss_usb

Title: Re: tinycore_v2.9rc3
Post by: Juanito on February 13, 2010, 05:53:53 AM
Also on tc-2.8.1 compared to tc-2.9rc3...

This works in .xsession tc-2.8.1:
Code: [Select]
/usr/bin/Xvesa -br -screen 1280x1024x16 -shadow -mouse /dev/psaux,5 -nolisten tcp -I >/dev/null 2>&1 &
waitforX
...

..but in tc-2.9rc3, I get a message about the screen mode requested not being supported - however, if I run xsetup.sh and chose the same thing - i.e. "1280x1024x16", then things work??
Title: Re: tinycore_v2.9rc3
Post by: roberts on February 13, 2010, 06:31:41 AM
I would agree that the udev upgrade is the bane of 2.9.
It probably should have been delayed until Core v3.0.
 I may have to pull it.
Title: Re: tinycore_v2.9rc3
Post by: meo on February 13, 2010, 06:49:56 AM
Hi there!
Thank you Robert for your work to improve tinycore. Unfortunately I still get the following boot message:

Starting sound driver: snd-nm256
amixer: Mixer attach defaulterror: No such file or directory

finishing the boot sequence. Is there a way to pass around this problem and get the sound to work? I use alsa and have it started by the bootlocal.sh. I have never had any problem with my somewhat troublesome neomagic sound chip in tinycore before, neither in DSL by the way. Other huge distributions that come with everything but the kitchen sink (read SuSE linux, Mandriva and Ubuntu) have given me problems during the years associated with the sound chip.

Have fun constantly improving this wonderful distro,
meo
Title: Re: tinycore_v2.9rc3
Post by: roberts on February 13, 2010, 06:51:32 AM
Meo, Does it work in v2.8.1 ?
Title: Re: tinycore_v2.9rc3
Post by: curaga on February 13, 2010, 07:00:51 AM
Juanito, is it possible the device has changed paths? find /dev -name "*lp*"

I have only usb sticks available, but those work fine in rc3.

Robert, I do agree it's a rough ride; but this is why I hoped for it to be over before the other major changes in 3.0. Changing a lot at once it becomes much harder to pinpoint where things broke.

Meo, sorry if I've asked this already, but is your alsa.tcz up to date?
Title: Re: tinycore_v2.9rc3
Post by: sci_fi on February 13, 2010, 07:08:16 AM
Confirming.

I am having similar problems to Meo with alsa. The problems were present in rc2 and continue in rc3, although seemed not present in rc1 (I am currently using rc1 with skype for example). Alsa works fine for me in 2.8.1 as well.  My alsa module is up to date, per appsedit.

Also continuing to see segfaults ala busybody and rebuildfstab during boot. These problems did not occur in rc1 but are present in both rc2 and rc3.

The firmware fix in rc3 is working fine for me.

Best regards,

sci_fi
Title: Re: tinycore_v2.9rc3
Post by: curaga on February 13, 2010, 07:14:05 AM
Also on tc-2.8.1 compared to tc-2.9rc3...

This works in .xsession tc-2.8.1:
Code: [Select]
/usr/bin/Xvesa -br -screen 1280x1024x16 -shadow -mouse /dev/psaux,5 -nolisten tcp -I >/dev/null 2>&1 &
waitforX
...

..but in tc-2.9rc3, I get a message about the screen mode requested not being supported - however, if I run xsetup.sh and chose the same thing - i.e. "1280x1024x16", then things work??
Is the same line generated by xsetup? I wonder what does it change.
Title: Re: tinycore_v2.9rc3
Post by: Juanito on February 13, 2010, 07:17:43 AM
Juanito, is it possible the device has changed paths? find /dev -name "*lp*"

I have only usb sticks available, but those work fine in rc3.

in tc-1.x:
Code: [Select]
$ find /dev -name "*lp*"
/dev/.udev/names/usb\x2flp0
/dev/.udev/names/usb\x2flp0/\x2fdevices\x2fpci0000:00\x2f0000:00:10.2\x2fusb5\x2f5-1\x2f5-1:1.0\x2fusb\x2flp0
/dev/.udev/names/par0/\x2fdevices\x2fpci0000:00\x2f0000:00:10.2\x2fusb5\x2f5-1\x2f5-1:1.0\x2fusb\x2flp0
/dev/.udev/db/\x2fdevices\x2fpci0000:00\x2f0000:00:10.2\x2fusb5\x2f5-1\x2f5-1:1.0\x2fusb\x2flp0
/dev/usb/lp0

In tc-2.9rc3 on a different machine, the above does not give anything and lsusb does not give anything (even though the usb stick I booted from is there)

Do you see your usb sticks with lsusb in 2.9rc3?
Title: Re: tinycore_v2.9rc3
Post by: Juanito on February 13, 2010, 07:22:03 AM
I didn't pay attention to all of .xsession, but the "1280x1024x16" bit did not change...
Title: Re: tinycore_v2.9rc3
Post by: curaga on February 13, 2010, 07:23:10 AM
Everybody with udev problems, or suspected ones, please enable syslog, and:

Quote
cd /var/log

sudo udevadm control --log-priority=err
sudo udevadm trigger

grep -i udev messages* > /tmp/udev-err-logs

sudo udevadm control --log-priority=info
sudo udevadm trigger

grep -i udev messages* > /tmp/udev-info-logs
Then, please upload those two log files from /tmp somewhere, and post links here. This should help debug the issue.

pastebin.ca is a good text upload service.

edit: Had old info there, should have been "log-priority" with a dash instead of an underscore.
Title: Re: tinycore_v2.9rc3
Post by: Juanito on February 13, 2010, 07:35:54 AM
I get:
Code: [Select]
$ sudo udevadm control --log_priority=err
control: unrecognized option '--log_priority=err'
unrecognized command
..same thing with =debug, but =info works

info log attached
Title: Re: tinycore_v2.9rc3
Post by: curaga on February 13, 2010, 07:46:41 AM
Just tested a fresh boot, and to be sure manually removed existing /dev/sd*. The device node for my stick appeared as it should.

Lsusb didn't show a thing, but it seems not to be a bug:
http://lkml.indiana.edu/hypermail/linux/kernel/0705.3/1225.html

I'll add that udev rule for testing.

edit: Confirmed, lsusb works with one added rule.
Title: Re: tinycore_v2.9rc3
Post by: meo on February 13, 2010, 08:19:54 AM
Hi Robert!

Yes, the sound works just fine in tinycore 2.8.1. It also works just fine in tinycore 2.9rc1 which I'm running right now.

Have fun continuing your excellent work,
meo
Title: Re: tinycore_v2.9rc3
Post by: sci_fi on February 13, 2010, 08:32:16 AM
Hi curaga,

here are some urls of the log files I tried to collect. Too big so I broke into two parts. info only. The error log only had a few bytes of complaints about wanting to change the command syntax in a later release. So not included.

http://pastebin.ca/1795391

http://pastebin.ca/1795392

Not sure I did everything properly here.
What commands should I run before doing the grep to extract the files. I did alsamixer only.

Best regards

sci_fi

Title: Re: tinycore_v2.9rc3
Post by: curaga on February 13, 2010, 09:01:12 AM
Thanks sci_fi. Your logs were very useful.

Seems the alsa startup script somehow did not reload udev rules. Can you post the following:
- cat /usr/local/tce.installed/alsa
- ls -l /etc/udev/rules.d
Title: Re: tinycore_v2.9rc3
Post by: gerald_clark on February 13, 2010, 09:21:44 AM

Also continuing to see segfaults ala busybody and rebuildfstab during boot. These problems did not occur in rc1 but are present in both rc2 and rc3.


I am also getting these errors, but only if I include wireless_tools in the boot?
Have you tried identifying which extension is triggering these errors on your system?
Title: Re: tinycore_v2.9rc3
Post by: sci_fi on February 13, 2010, 10:59:41 AM
Hi curaga,

Here are the logs you requested.

http://pastebin.ca/1795521
http://pastebin.ca/1795522

Hope it helps.

sci_fi
Title: Re: tinycore_v2.9rc3
Post by: sci_fi on February 13, 2010, 11:01:02 AM
Hi gerald_clark,

I have not tried to isolate the problems to a specific extension. I will try booting wo wireless tools to see if I can duplicate your results.

sci_fi
Title: Re: tinycore_v2.9rc3
Post by: sci_fi on February 13, 2010, 11:11:15 AM
Follow up.

I removed wireless_tools.tcz and wireless-2.6.29.1-tinycore.tcz from my boot up. The segfaults and alsa problems still occurred.

sci_fi
Title: Re: tinycore_v2.9rc3
Post by: curaga on February 13, 2010, 11:14:01 AM
Looks like your alsa.tcz is the one from Oct 2009 - before the -config split and the two updates for supporting the new udev. Are you perhaps using a mirror?

Here's the md5sum of the latest alsa.tcz:
75af7f641bac0be51dd53b6ac2aa7c14  alsa.tcz

If the app updater is reporting an older one as the latest, there's something amiss here.

Edit: s/appsaudit/app updater/
Title: Re: tinycore_v2.9rc3
Post by: sci_fi on February 13, 2010, 11:20:01 AM
Thanks for the tip. I will check again and respond.

Also, fwiw I have gotten a warning all the way back to rc1 during extension loading as follows:

touch: usr/local/tce.installed/libusb: permission denied.
libusb is present belonging to tc staff rw  r r
Never seemed to cause a problem so I did not mention before.

Perhaps not important.

I will now double check alsa.

sci_fi
Title: Re: tinycore_v2.9rc3
Post by: sci_fi on February 13, 2010, 11:27:24 AM
Hi Curaga,

When I do Appsaudit->Update->Check for updates the return is only that I need to upgrade firefox. Nothing else is mentioned.

The checksum does not match the checksum I have on alsa-config.tcz.md5 which is the only alsa related checksum in my optional older.

I will now uninstall alsa and reboot and reinstall.

sci_fi
Title: Re: tinycore_v2.9rc3
Post by: sci_fi on February 13, 2010, 11:48:56 AM
Hi curaga,

Re-installing alsa on rc3 works. Skype and audio works.
Do check out appsaudit because it certainly gave me no indication that I was not current. Wonder what else may be old.

This did not help all the segfaults, however. Still, one more down.

Thanks,

sci_fi
Title: Re: tinycore_v2.9rc3
Post by: curaga on February 13, 2010, 12:47:31 PM
Hi curaga,

Re-installing alsa on rc3 works. Skype and audio works.

Good to hear :)
Title: Re: tinycore_v2.9rc3
Post by: jur on February 13, 2010, 06:04:55 PM
Code: [Select]
I have problems with chromium. Chromium won't load web pages, it reports
[code]
[2458:2463:677390998:ERROR:base/shared_memory_posix.cc(192)] Creating shared memory in /dev/shm/org.chromium.o3QTBj failed: No such file or directory
There are about 4 such lines, all same but with the number stuff different.

tc2.8.1 has no problem.

Also when booting, when the extensions are loaded I get a whole string of repeated messages, something about
Code: [Select]
/init.d/rcS (sp?) line 415: usleep: Text file busy
I haven't reproduced it exactly, but from memory.[/code]
Title: Re: tinycore_v2.9rc3
Post by: curaga on February 14, 2010, 02:31:18 AM
On rc3, /dev/shm is mounted tmpfs as it should, and is world writable. If "touch /dev/shm/test" works as user tc, this is a chromium bug, as you can clearly use the area with user privileges then.
Title: Re: tinycore_v2.9rc3
Post by: Jason W on February 14, 2010, 06:43:37 AM
Chromium works fine here with booting as "base norestore" and loading chromium from ibiblio.

Posting from it now.
Title: Re: tinycore_v2.9rc3
Post by: jur on February 14, 2010, 06:37:27 PM
If I chown /dev/shm to tc.staff chromium works, but it boots up as root.root, both on usb stick and hard drive.
Title: Re: tinycore_v2.9rc3
Post by: jur on February 14, 2010, 11:59:02 PM
Besides the issue of /dev/shm ownership, there is also the string of messages I get when the onboot extensions are loading. I wonder if this might be some race condition, as the number of those messages is not always the same. But they do not appear to have any negative effect that I can see.
Title: Re: tinycore_v2.9rc3
Post by: curaga on February 15, 2010, 12:31:04 AM
The ownership should not matter with 1777 permissions.
Title: Re: tinycore_v2.9rc3
Post by: jur on February 15, 2010, 02:16:32 AM
Of course, I should have said it boots up with 755 permissions.
Title: Re: tinycore_v2.9rc3
Post by: jur on February 15, 2010, 02:33:49 AM
Here's another thing:

I have only a few things in .filetool.lst, such as /etc/X11/xorg.conf and a few other setup files. I have persistent /opt and /home. I don't have bootlocal.sh and .filetool.lst in there.

rc3 trashes my bootlocal.sh and filetool.lst files, overwriting what was in persistent /opt with the default ones. There may be other files that would be affected; these are the ones I know of.
Title: Re: tinycore_v2.9rc3
Post by: Juanito on February 15, 2010, 02:40:00 AM
Could you cut & paste the boot codes you're using?
Title: Re: tinycore_v2.9rc3
Post by: jur on February 15, 2010, 03:00:29 AM
Code: [Select]
tc@box:~$ showbootcodes
quiet tce=sda7 opt=sda7 home=sda7 max_loop=255 tz=EST,M10.1.0/2,M4.1.0/2 noicons
Title: Re: tinycore_v2.9rc3
Post by: curaga on February 15, 2010, 05:27:27 AM
Hmm, on a pristine MC 2.9rc3 boot I get 1777 permissions. Could it be it doesn't get mounted for some reason on your system? It could be the buggy busybox version.

Please post the output of mount.
Title: Re: tinycore_v2.9rc3
Post by: helander on February 15, 2010, 10:21:31 AM
I was browsing the code in tce-load and from what I understood the recursive load would not work as I would have expected. I then made this simple test:

   I created four extensions having the following dependency chain:

        A.tcz -> B.tcz -> C.tcz -> D.tcz     ( x -> y means that x.dep contains y)

When I installed A.tcz, only B.tcz was not installed. I would have expected all four extensions to be installed due to dependency chain.

The recursive scan of the dependency chain only operates on the .dep files available in tce/optional and when that is done none of B.tcz.dep, C.tcz.dep have yet been loaded and are not considered in the scan.

/Lars
Title: Re: tinycore_v2.9rc3
Post by: roberts on February 15, 2010, 01:46:07 PM
Load Local never tries to acces the repository for further downloads.
Since only a "local load" request is being made it would imply that a previous download from a repository was completed and the supporting files are available in tce/optional. Or is this going to be supporting partial broken downlooads while in the midst of a recursive download chain.



Title: Re: tinycore_v2.9rc3
Post by: jur on February 15, 2010, 04:12:20 PM
mount output on my usb stick:
Code: [Select]
rootfs on / type rootfs (rw)
tmpfs on / type tmpfs (rw,size=689208k)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,mode=600)
tmpfs on /dev/shm type tmpfs (rw)
/dev/sdb1 on /mnt/sdb1 type vfat (rw,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1)
/dev/loop0 on /tmp/tcloop/cairo type squashfs (ro)
/dev/loop1 on /tmp/tcloop/expat2 type squashfs (ro)
/dev/loop2 on /tmp/tcloop/fontconfig type squashfs (ro)
/dev/loop3 on /tmp/tcloop/glib2 type squashfs (ro)
/dev/loop4 on /tmp/tcloop/graphics-libs-1 type squashfs (ro)
/dev/loop5 on /tmp/tcloop/libglade type squashfs (ro)
/dev/loop6 on /tmp/tcloop/libxml2 type squashfs (ro)
/dev/loop7 on /tmp/tcloop/pango type squashfs (ro)
/dev/loop8 on /tmp/tcloop/pixman type squashfs (ro)
/dev/loop9 on /tmp/tcloop/tint2 type squashfs (ro)
/dev/loop10 on /tmp/tcloop/915resolution type squashfs (ro)
/dev/loop11 on /tmp/tcloop/atk type squashfs (ro)
/dev/loop12 on /tmp/tcloop/gtk2 type squashfs (ro)
/dev/loop13 on /tmp/tcloop/libstartup-notification type squashfs (ro)
/dev/loop14 on /tmp/tcloop/ttf-bitstream-vera type squashfs (ro)
/dev/loop15 on /tmp/tcloop/Xlibs_support type squashfs (ro)
/dev/loop16 on /tmp/tcloop/libxcb type squashfs (ro)
/dev/loop17 on /tmp/tcloop/libxcb-util type squashfs (ro)
/dev/loop18 on /tmp/tcloop/openbox type squashfs (ro)
/dev/loop19 on /tmp/tcloop/file type squashfs (ro)
/dev/loop20 on /tmp/tcloop/shared-mime-info type squashfs (ro)
/dev/loop21 on /tmp/tcloop/rox-filer type squashfs (ro)
I can't check my hard disk frugal install ATM but I konw it exhibits rw on /dev/shm as well.
Title: Re: tinycore_v2.9rc3
Post by: roberts on February 15, 2010, 05:11:11 PM
Quote
/dev/sdb1 on /mnt/sdb1 type vfat
  google "chromium on vfat" ...
Title: Re: tinycore_v2.9rc3
Post by: jur on February 15, 2010, 05:16:13 PM
Quote
/dev/sdb1 on /mnt/sdb1 type vfat
  google "chromium on vfat" ...
Did you miss where I said I get exactly the same behaviour on my hard drive install as well? Well that is not vfat, it's ext3.
Title: Re: tinycore_v2.9rc3
Post by: helander on February 15, 2010, 09:59:27 PM
Load Local never tries to acces the repository for further downloads.
Since only a "local load" request is being made it would imply that a previous download from a repository was completed and the supporting files are available in tce/optional. Or is this going to be supporting partial broken downlooads while in the midst of a recursive download chain.






You assumed for some reason that a "local load" wa being made. That assumption was wrong.

Goodbye
Title: Re: tinycore_v2.9rc3
Post by: curaga on February 16, 2010, 12:31:58 AM
@jur

Please try if manually forcing that helps, and post the output:

Quote
ls -lhd /dev/shm
sudo sed -i '/shm/ s@defaults@&,mode=1777@' /etc/fstab
sudo umount /dev/shm
sudo mount /dev/shm
ls -lhd /dev/shm
Title: Re: tinycore_v2.9rc3
Post by: jur on February 16, 2010, 02:57:47 AM
Yep forcing it worked:

Code: [Select]
tc@box:~$ ls -lhd /dev/shm
drwxr-xr-x    2 root     root           40 Feb 16 21:54 /dev/shm/
tc@box:~$ sudo umount /dev/shm
tc@box:~$ sudo mount /dev/shm 
tc@box:~$ ls -lhd /dev/shm
drwxrwxrwt    2 root     root           40 Feb 16 21:56 /dev/shm/

(I edited fstab manually using a text editor between the 2 ls statements.) Posting from Chromium in rc3 now.
Title: Re: tinycore_v2.9rc3
Post by: jls on February 16, 2010, 11:58:51 PM
for robert, I'm attanching the file as robert requested me
Title: Re: tinycore_v2.9rc3
Post by: roberts on February 17, 2010, 07:28:10 AM
Thanks. Nothing unusal. Looks typical.
Title: Re: tinycore_v2.9rc3
Post by: curaga on February 17, 2010, 09:18:12 AM
I found out why busybox 1.15.3 segfaults in rebuildfstab; when it's called while the first instance is running, the code reading the pid file segfaults.

This is a bug in busybox ash, as 1.14.3 works fine, as does bash.

edit: Correction, also segfaults when file exists.
Title: Re: tinycore_v2.9rc3
Post by: roberts on February 17, 2010, 12:54:24 PM
Falling back to busybox v1.14.3