• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
Author Topic: sheeva/dream 3.2.13 new kernel available  (Read 2263 times)
cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« on: March 23, 2012, 03:51:37 PM »

3.2.13 is now available.

For everything besides Dreamplugs:
sudo ./README-PLUG-UPDATE.sh 3.2.13 --nandkernel (installs to nand)
or:
sudo ./README-PLUG-UPDATE.sh 3.2.13 --rootkernel (installs to /boot)

For Dreamplugs:
sudo ./README-DREAM-UPDATE.sh 3.2.13 (installs to /boot)

Kernel and modules are available from the following locations:

http://www.plugapps.com/mirror/with-linux/
http://www.xilka.com/sheeva/

Features systemd, e-sata, dmcrypt, IPV6, CIFS, NFS4, EXT3, EXT4, JFS, XFS, FUSE(for ntfs-3g), UBIFS, usb-serial, uvcvideo, iptables, appletalk, bluetooth, v4l and ppp.

The kernel source is available on the plugapps mirror (it syncs once a day, so it may be up to 24 hours late).
Logged

entropy
Newbie
*

Karma: 0
Posts: 12


View Profile
« Reply #1 on: March 25, 2012, 09:10:24 AM »

You might want to update your README-PLUG-UPDATE.sh script to check for /lib being linked to /usr/lib (like in Fedora 17+).  Currently the script will overwrite the /lib link and make any system that relies on this unbootable.  The safest thing would probably be to check if /lib is a symlink, follow it, and untar there.
Logged

Anon
Newbie
*

Karma: 0
Posts: 7


View Profile
« Reply #2 on: March 25, 2012, 02:17:07 PM »

This kernel incorporates the latest linuxtv drivers?
Logged

cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #3 on: March 26, 2012, 12:42:41 AM »

You might want to update your README-PLUG-UPDATE.sh script to check for /lib being linked to /usr/lib (like in Fedora 17+).  Currently the script will overwrite the /lib link and make any system that relies on this unbootable.  The safest thing would probably be to check if /lib is a symlink, follow it, and untar there.

ok, it's done.  BTW on my systemd systems I decided NOT to make /lib, /bin and /sbin symlinks to /usr/? for this exact reason.  It's much safer to make the items inside the directory links when necessary.  In any case the scripts should handle this problem effectively now.
Logged

entropy
Newbie
*

Karma: 0
Posts: 12


View Profile
« Reply #4 on: April 11, 2012, 10:38:34 PM »


ok, it's done.  BTW on my systemd systems I decided NOT to make /lib, /bin and /sbin symlinks to /usr/? for this exact reason.  It's much safer to make the items inside the directory links when necessary.  In any case the scripts should handle this problem effectively now.


Not quite.  I get this error:
Extracting modules
tar: usr: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now

Logged

entropy
Newbie
*

Karma: 0
Posts: 12


View Profile
« Reply #5 on: April 11, 2012, 10:45:19 PM »


tar: usr: Cannot open: No such file or directory


# readlink /lib; ls -l lib
usr/lib
lrwxrwxrwx 1 root root 7 Dec 31  1969 lib -> usr/lib
#
Logged

cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #6 on: April 25, 2012, 12:40:23 AM »


tar: usr: Cannot open: No such file or directory


# readlink /lib; ls -l lib
usr/lib
lrwxrwxrwx 1 root root 7 Dec 31  1969 lib -> usr/lib
#


It's fixed now.
Logged

Pages: [1]
Print
Jump to: