Tiny Core Linux
Off-Topic => Archive / Obsolete => Topic started by: Jason W on June 03, 2015, 03:30:43 PM
-
Ubuntu Vivid Vervet is available, I will commence work on a ub-dCore-vivid. ub-dCore-trusty is based on a long term release and will remain.
-
ub-dCore-vivid is now released to the release candidate status. All seems to work well here, let me know if anything is not.
-
Uploaded a new release candidate. References of loadsce have been changed to sce-load in /etc/init.d/tc-config.
-
If I hear no issues regarding ub-dCore-vivid I will move to release in the coming days.
-
trying today to move from trysty to vivid:
- boot option waitusb=5:UUID= doesn't work, waitusb=5 only works
- during boot while loading extension I see this error:
error opening usb device 'descriptors' file
- X doesn't start is sayng that libdrm.so.2 is missing, importing it fixes the problem
- connmand doesn't start:
Couldn't load target `standard':No such file or directory
googling for the error I found:
Looks like you miss the support for the xtables in kernel's netfilter.
http://comments.gmane.org/gmane.linux.network.connman/16197 (http://comments.gmane.org/gmane.linux.network.connman/16197)
-
Ok, I will look into the issues. There was some udev and other updates that meant more deps to bring in, perhaps something is missing.
-
Hi
some more differences and bugs since trusty to vivid upgrade:- X is on the first console
- wifi ipw2200 doesn't work: tried wifi.sh since connman doesn't start, the AP is showed but after inserting the passphrase it doesn't get the ip, while an rtl8187 based wifi works
- mount/unmount via enlightenment doesn't work
Thanks
-
I think the X-on-first-tty is intentional, because it speeds up boot by a tiny amount when you don't change the tty.
-
On the connman and netfilter issue, below is the part of the README that deals with what needs to be enabled in the kernel config, and all exists in the current kernel build as either builtin or modules:
Kernel configuration
====================
In order to support tethering, the following kernel configuration options
need to be enabled either as modules (m) or builtin (y):
CONFIG_BRIDGE
CONFIG_IP_NF_TARGET_MASQUERADE
In order to enable CONFIG_IP_NF_TARGET_MASQUERADE, the following options need
to be enabled also as modules (m) or builtin (y):
CONFIG_NETFILTER
CONFIG_NF_CONNTRACK_IPV4
CONFIG_NF_NAT_IPV4
-
Was X on a different console with ub-dCore-trusty? Nothing has been changed in the base files that would cause a different behavior.
As for mount, I truecrypt can't set up a loop device though I only have one loop mounted. So something affecting mounting is broken somewhere since the kernel has not changed nor the truecrypt package.
-
The mount issue with truecrypt was resolved by adding libsmartcols1 to the deps of the mount package.
I have a hunch it will fix the mount issue in enlightenment as well. Please re-import and test.
-
Hi
I forgot to say that I'm using "multivt" boot option. On "trusty" X is on tty7 while on "vivid" is on the first console.
-
Hi
re-imported mount and after changing
<allow_any>
<allow_inactive>
<allow_active>
from auth_admin to yes
in /usr/share/polkit-1/actions/org.freedesktop.udisks2.policy
section
org.freedesktop.udisks2.filesystem-mount-other-seat
enlightenment is able to mount
-
Hi
connman works installing iptables, maybe it should be added as dep.
Thanks
-
Great!
I have read that newer Xorg builds use the login tty as it's own, I am not well experienced in the Xorg/tty subject but it seem like it is expected behavior. Is it causing any issues?
I will see if I can add some startup script function to take care of the /usr/share/polkit-1/actions/org.freedesktop.udisks2.policy file.
-
For the file in package udisks2, /usr/share/polkit-1/actions/org.freedesktop.udisks2.policy, those lines are set to auth_admin in Trusty just like in Vivid. Was mounting successful in trusty with auth_admin in those fields?
I am working on a startup script to change them to yes, I am just curious what the difference might be.
-
Hi
In vivid it was also working with modification as already written in the past in this forum.
in the URL below are the 2 files
http://ge.tt/5B5oDKJ2 (http://ge.tt/5B5oDKJ2)
-
but I want to add that to me this policykit modifications seems like an hack, indicating that something is wrong elsewhere, consolekit maybe?
-
Yeah, I am wondering why the mod is needed in vivid and not in trusty. Which sounds like it is somethig else than that file mentioned, since essentially those files are the same in trusty and vivid. I will look into it more.
-
Please re-import and test. I have added the command "pam-auth-update --force" to the startup script of udisks and udisks2.
-
Ok i'll test. i just want to correct my previous post. The mod was also used in trusty
-
Hi
still cannot mount without the hack on the policy file. Strange that the following command works without the modification:
jls@box:~$ udisksctl mount -b /dev/sdb1
==== AUTHENTICATING FOR org.freedesktop.udisks2.filesystem-mount-other-seat ===
Authentication is required to mount Verbatim STORE N GO (/dev/sdb1)
Authenticating as: root
==== AUTHENTICATION COMPLETE ===
Mounted /dev/sdb1 at /mnt/sdb1.
-
ub-dCore-vivid updated to support the use of the /cde directory on an ISO image. Details are in this thread:
http://forum.tinycorelinux.net/index.php/topic,18527.msg113514.html#msg113514
-
Hi. Waitusb boot code it seems not to be considered infact the message doesn't appear on the screen during boot
-
Ok, I will look into that today.
Oh, are we seeing this issue also in ub-dCore-trusty or ub-dCore-utopic? I will check them out as I remember a udev rule that had to be in /etc/udev/rules.d.
-
In dCore-trusty waitusb works
-
I think I have it fixed, I tested all the ports besides dCore-wheezy. Uploaded. Note the name change to dCore-vivid.
-
yes Jason, fixed ;D thanks
-
Great!
The file that needs to exist is /etc/udev/rules.d/60-persistent-storage.rules, somehow did not get put in.
-
dCore-vivid has been moved to release.