piCore-5.2alpha2

[bmarkus]

Second test release of piCore v5.2 available.

http://tinycorelinux.net/5.x/armv6/release_candidates/

alpha2 change log:

* useBusybox in tc-functions changed to eliminate interference with certain installed GNU apps

alpha1 change log:

* rebuildfstab: do not replace fstab entries for a device that does not have "Added by TC" on the line (thanks to Gerald Clark)
* init: increase the default inode count
* ondemand: don't list extensions under subdirs in onboot maintenance
* busybox updated to 1.22.1 and split suid/nosuid for better security
* ldd: Added quotes for binaries with spaces in their names
* /etc/services: modified to suit rpcbind rather than portmap
* tc-functions: Removed the getpasswd stars to allow backspace to work
* added accelerated arm-mem library to spead-up memcmp, memcpy, memmove & memset
* updated Raspberry Pi firmware

[Paul_123]

Loaded the X image.  Worked ok.   Although I'm not sure I'm a fan of X on a linux.

I noticed when installing extensions, the install scripts tries to touch the tce.installed directory.   They all fail.

[Paul_123]

Is it intentional the the X version image is setup for manual configuration of eth0?

[bmarkus]

Is it intentional the the X version image is setup for manual configuration of eth0?

Do you mean no IP address assigned by udhcpc?

[Paul_123]

Is it intentional the the X version image is setup for manual configuration of eth0?

Do you mean no IP address assigned by udhcpc?

When I booted, there was no ip address assigned.   When I opened the network configuration box, it was set as manual.  As soon as I put it as DHCP, it was assigned an address.

I also had a problem that when I unplugged the ethernet cable, the interface was not automatically taken down.

[bmarkus]

Hm.... Will check, it is not intended

[tinypoodle]

I also had a problem that when I unplugged the ethernet cable, the interface was not automatically taken down.

Why would you expect that, and why would you consider it being a problem if not?

[Paul_123]

I also had a problem that when I unplugged the ethernet cable, the interface was not automatically taken down.

Why would you expect that, and why would you consider it being a problem if not?

In my case I added wifi.  After I connected the wifi, I unplugged my ethernet cable.......the system would not route traffic properly until I down'ed the eth0 interface.

I would expect that an interface that starts automatically would stop automatically.   I put wifi on almost every tinycore image, I've never seen that problem before.   Maybe I rebooted in the middle.....but I've just never noticed it on tinycore.

[tinypoodle]

After I connected the wifi, I unplugged my ethernet cable.......the system would not route traffic properly until I down'ed the eth0 interface.

I wouldn't expect anything different.
Just deleting the default gateway associated with interface would do as well.

I would expect that an interface that starts automatically would stop automatically.

Nothing starts automatically by plugging the ethernet cable in.
A script would bring up interface at boot and run udhcpc when boot code "nodhcp" is omitted.

[Paul_123]

Nothing starts automatically by plugging the ethernet cable in.
A script would bring up interface at boot and run udhcpc when boot code "nodhcp" is omitted.

I guess with udev running, I assumed udev managed the hardwire interfaces.   * Wrong assumption *

No big deal