cbxbiker61
Global Moderator
Sr. Member
   
Karma: 37
Posts: 488
|
 |
« on: February 23, 2010, 04:29:17 PM » |
|
2.6.32.9 is now available. Kernel and modules are available from the following location: http://sheeva.with-linux.com/sheeva/Features dmcrypt, IPV6, CIFS, NFS4, EXT3, EXT4, JFS, XFS, FUSE(for ntfs-3g), UBIFS, usb-serial, uvcvideo, iptables, appletalk, bluetooth, v4l and ppp.
|
|
|
|
|
Logged
|
|
|
|
|
xoxox
Newbie
Karma: 0
Posts: 7
|
 |
« Reply #1 on: February 24, 2010, 04:01:30 AM » |
|
Thanks for your work :-) For future releases, would it be possible to activate the "ppp_mppe" and "ppp_filter" options? I need them for the poptop VPN Server. diff .config sheeva-2.6.32.9.config 1216,1217c1216,1217 < CONFIG_PPP_MULTILINK=y < CONFIG_PPP_FILTER=y --- > # CONFIG_PPP_MULTILINK is not set > # CONFIG_PPP_FILTER is not set
1219c1219 < CONFIG_PPP_SYNC_TTY=m --- > # CONFIG_PPP_SYNC_TTY is not set
1222c1222 < CONFIG_PPP_MPPE=m --- > # CONFIG_PPP_MPPE is not set
1709c1709 < # CONFIG_FB_CFB_IMAGEBLIT is not set --- > CONFIG_FB_CFB_IMAGEBLIT=m
1749a1750 > CONFIG_FB_UDLFB=m
|
|
|
|
|
Logged
|
|
|
|
|
|
|
 |
« Reply #2 on: February 25, 2010, 07:57:56 AM » |
|
I have just discovered that for this release the command 'su' does not work. Also, even after creating a new user (adduser) it is impossible for that user, or any user other than root to login, either from a serial terminal or remotely.
I have done some testing
Kernel 2.6.30.1 su <user> works OK . . . Kernel 2.6.31 su <user> Fails Kernel 2.6.32.8 su <user> Fails Kernel 2.6.32.9 su <user> Fails
So presumably something broke between 30.1 and 31. I am in severe doubt about this as I cannot imagine somebody else has not noticed it, but it is definitely what is happening to me.
|
|
|
|
|
Logged
|
|
|
|
|
|
|
 |
« Reply #3 on: February 25, 2010, 09:42:44 AM » |
|
Further investigation reveals that su "stopped working" between 2.6.30.1 and 2.6.30.2. However, it was not fully working on version 2.6.30.1.
On 2.6.30.2 " su <user>" Does nothing, no error, no request for password, nothing
On 2.6.30.1 you can login as root and " su <user>"
This does as it should, correctly logging you in as that user, without asking for a password. BUT it is then impossible to use su to get back to root or to su to any other user. It does ask for a password but entering the correct password gives
su: Authentication failure
|
|
|
|
|
Logged
|
|
|
|
|
restamp
Global Moderator
Sr. Member
   
Karma: 4
Posts: 273
|
 |
« Reply #4 on: February 25, 2010, 02:28:40 PM » |
|
I just created a password for another user on my Plug, which is running cbxbiker61's 2.6.32.5 kernel, and I can su at will: $ uname -a Linux sheeva 2.6.32.5 #1 PREEMPT Sat Jan 23 04:10:40 MST 2010 armv5tel GNU/Linux $ su x10 Password: $ id uid=1099(x10) gid=1099(x10) groups=1099(x10) $ ^D $ id uid=1100(res) gid=1100(res) groups=1100(res) $ su Password: root@sheeva:/home/res# su x10 $ id uid=1099(x10) gid=1099(x10) groups=1099(x10) $ ^D root@sheeva:/home/res# id uid=0(root) gid=0(root) groups=0(root) root@sheeva:/home/res# exit $ id uid=1100(res) gid=1100(res) groups=1100(res) $ FWIW, I'm using the root filesystem that came with the alpha-6 SheevaPlug installer.
|
|
|
|
|
Logged
|
|
|
|
|
cbxbiker61
Global Moderator
Sr. Member
   
Karma: 37
Posts: 488
|
 |
« Reply #5 on: February 25, 2010, 03:27:53 PM » |
|
I have just discovered that for this release the command 'su' does not work. Also, even after creating a new user (adduser) it is impossible for that user, or any user other than root to login, either from a serial terminal or remotely.
From the README: ####### change vm security settings # Due to changes in vm security a change must be made in /etc/sysctl.d/10-process-security.conf. # vm.mmap_min_addr should be set to 32768 (This change is safe for any kernel version). # If this is not done it is likely that you will not be able to login remotely. # Although you should still be able to login as root on the main console.
cat /proc/sys/vm/mmap_min_addr 32768 If it's not set to 32768 you need to get it set to 32768.
|
|
|
|
|
Logged
|
|
|
|
|
|
|
 |
« Reply #6 on: February 26, 2010, 08:07:09 AM » |
|
Hi, Im trying to dial a 3G USB modem attached to the sheeva, starting PPPd i see this : "kernel does not support PPP filtering" before the modem hangs up, So i guess I need ppp_filter support in the kernel too, if possible. Thanks in advance! Thanks for your work :-)
For future releases, would it be possible to activate the "ppp_mppe" and "ppp_filter" options? I need them for the poptop VPN Server.
|
|
|
|
|
Logged
|
|
|
|
|
cbxbiker61
Global Moderator
Sr. Member
   
Karma: 37
Posts: 488
|
 |
« Reply #7 on: February 26, 2010, 01:23:58 PM » |
|
Thanks for your work :-)
For future releases, would it be possible to activate the "ppp_mppe" and "ppp_filter" options? I need them for the poptop VPN Server.
Ok. 2.6.32.9 has been re-released with the ppp changes.
|
|
|
|
|
Logged
|
|
|
|
|
|
|
 |
« Reply #8 on: February 26, 2010, 04:24:10 PM » |
|
 Your a star thanks!
|
|
|
|
|
Logged
|
|
|
|
|
xoxox
Newbie
Karma: 0
Posts: 7
|
 |
« Reply #9 on: February 27, 2010, 04:41:33 PM » |
|
Ok. 2.6.32.9 has been re-released with the ppp changes. [/quote] Thank you 
|
|
|
|
|
Logged
|
|
|
|
|
|
|
|
|
 |
« Reply #11 on: March 02, 2010, 02:06:02 AM » |
|
Thanks for your work !!!
For future releases, would it be possible to activate the this options? CONFIG_TASKSTATS=y CONFIG_TASK_DELAY_ACCT=y CONFIG_TASK_XACCT=y CONFIG_TASK_IO_ACCOUNTING=y
I need them for use iotop.
Could not run iotop as some of the requirements are not met: - Python >= 2.5 for AF_NETLINK support: Found - Linux >= 2.6.20 with I/O accounting support: Not found
|
|
|
|
|
Logged
|
|
|
|
|
cbxbiker61
Global Moderator
Sr. Member
   
Karma: 37
Posts: 488
|
 |
« Reply #12 on: March 02, 2010, 10:44:37 AM » |
|
Thanks for your work !!!
For future releases, would it be possible to activate the this options? CONFIG_TASKSTATS=y CONFIG_TASK_DELAY_ACCT=y CONFIG_TASK_XACCT=y CONFIG_TASK_IO_ACCOUNTING=y
I need them for use iotop.
Could not run iotop as some of the requirements are not met: - Python >= 2.5 for AF_NETLINK support: Found - Linux >= 2.6.20 with I/O accounting support: Not found
There are two "testing" kernels available in the testing directory that have task accounting enabled. I don't plan on adding task accounting to the "standard" kernels. http://sheeva.with-linux.com/sheeva/index.php?dir=testing
|
|
|
|
|
Logged
|
|
|
|
|
|
|
 |
« Reply #13 on: March 02, 2010, 10:56:21 AM » |
|
I seem to have missed the README but I am sorry to say this does not help. cat /proc/sys/vm/mmap_min_addr 32768 If it's not set to 32768 you need to get it set to 32768.
I am sure this is good advice BUT Sadly no such file "10-process-security.conf" exists anywhere on my filesystem. Any more suggestions? From the README ####### change vm security settings # Due to changes in vm security a change must be made in /etc/sysctl.d/10-process-security.conf. # vm.mmap_min_addr should be set to 32768 (This change is safe for any kernel version). # If this is not done it is likely that you will not be able to login remotely. # Although you should still be able to login as root on the main console.
|
|
|
|
|
Logged
|
|
|
|
|
cbxbiker61
Global Moderator
Sr. Member
   
Karma: 37
Posts: 488
|
 |
« Reply #14 on: March 02, 2010, 11:31:23 AM » |
|
I seem to have missed the README but I am sorry to say this does not help. cat /proc/sys/vm/mmap_min_addr 32768 If it's not set to 32768 you need to get it set to 32768.
I am sure this is good advice BUT Sadly no such file "10-process-security.conf" exists anywhere on my filesystem. Any more suggestions? From the README Did you cat /proc/sys/vm/mmap_min_addr ?? What does it say?
It doesn't really matter if 10-process-security.conf exists. What matters is what /proc/sys/vm/mmap_min_addr says. If it's wrong you can just do a "echo 32768 > /proc/sys/vm/mmap_min_addr" in your startup scripts. ####### change vm security settings # Due to changes in vm security a change must be made in /etc/sysctl.d/10-process-security.conf. # vm.mmap_min_addr should be set to 32768 (This change is safe for any kernel version). # If this is not done it is likely that you will not be able to login remotely. # Although you should still be able to login as root on the main console.
|
|
|
|
|
Logged
|
|
|
|
|
|