Hi all
In the first attempt to insytall SLitaz rolling on a hard disk and after tazpkg up, the command lsmod returned nothing and the command depmod complain about /lib/modules/linux-3.2-slitaz
For the second time I've just installed Slitaz rolling on a hard disk. Now the commands lsmod and depmod ok.
Now the command slitaz returns
Release cooking
Kernel 3.2-slitaz
The command uname -r returns 3.2-slitaz
However in tazpanel I can see the package linux 3.2.53 (the Linux kernel and modules) installed and /lib/modules/3.2.53-slitaz is a link to /lib/modules/3.2-slitaz
And the icon of /boot/vmlinuz-3.2-slitaz is the Windows flag !
I'm a little puzzled with all that.
Would you be so nice to answer my question : may I type tazpkg recharge && tazpkg up with no risk ?
PS : happily I've Slitaz stable on an other part of my disk !

Problem with rolling/cooking
(6 posts) (3 voices)-
Posted 11 years ago #
-
Hi yves04
regarding the 3.2/3.2.53 issue,look here:
http://forum.slitaz.org/topic/problem-installing-slitaz-rolling-version#post-27495
The windows-flag-icon...lol...nice gag..;-)
--"tazpkg recharge && tazpkg up with no risk ?"--I wouldn't do that, or expect
that it will crash.
All in all I wouldn't take it too seriously, it's rolling....Posted 11 years ago # -
Hi
The kernel has been fixed now by Christophe: http://hg.slitaz.org/wok/rev/db5b03f42dd9
Updating should be OK, but a newer rolling release could be better for the users?: http://mirror.slitaz.org/iso/rolling/
Posted 11 years ago # -
@Paul
really good news...thanks
and yes, a newer rolling release would be great, preventing the trouble to get
the old version running before One can update.
(because I'm always testing with a CD-RW and real Hardware)Posted 11 years ago # -
Thanks @sixofeight and @paul for your answers. For a while I think to keep the kernel 3.2 so with the command tazpkg block linux and tazpkg block linux-*
After that I've been able to use tazpkg up
I think change for the new Rolling one day.
Have a nice day.Posted 11 years ago # -
Thanks @sixofeight and @Paul for your answers. For a while I think to keep the kernel 3.2 So I used the command tazpkg block linux and tazpkg block linux-* ; after that I've been able to use tazpkg up
I think change for the new Rolling one day.
Have a nice day.Posted 11 years ago #
Reply
You must log in to post.