LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 03-09-2010, 04:55 PM   #1
linus72
Guru
 
Registered: Jan 2009
Location: Gordonsville-AKA Mayberry-Virginia
Distribution: PocketWriter/MinimalX
Posts: 5,059

Rep: Reputation: 330Reputation: 330Reputation: 330Reputation: 330
Can/Should I upgrade to Current?


I wanna upgrade one of my 13 installs to current and was wanting any tips, etc
and whether I should do it?

thanks
 
Old 03-09-2010, 05:08 PM   #2
GrapefruiTgirl
Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550
Hey Linus

My advice is, since you seem to have a pretty fair bit of experience in general, then:

if you can live with the prospect of potentially running into problems as some of us have ( *ahem* probably from not reading the changelogs/instructions <pointing at myself>), and you're not depending on that machine for life & death, then by all means, if you want to see what -current does for you, and maybe help identify and report problems, go for it. BUT READ THE CHANGELOG & UPGRADE.TXT if applicable and follow any instructions therein, before proceeding.

You may have noticed a number of threads around here detailing various issues people have had with the upgrade, so *definitely* search and read about these issues first (I'm not sure which ARCH you run, nor if any reported issues are ARCH specific).

All in all, -current is working well for me, though due to *I think* my own doing, I have yet to upgrade my Xorg because when I do, it won't start up. I believe this is NOT the fault of Xorg or Slackware, but my own fault for mangling my first attempt at upgrading.

Last thoughts: If you have no compelling reason to run -current other than to see, play, test, etc., and don't want to risk any instability, then do not try it.

Best regards,
Sasha
 
Old 03-09-2010, 05:11 PM   #3
linus72
Guru
 
Registered: Jan 2009
Location: Gordonsville-AKA Mayberry-Virginia
Distribution: PocketWriter/MinimalX
Posts: 5,059

Original Poster
Rep: Reputation: 330Reputation: 330Reputation: 330Reputation: 330
thanks grapefruitgirl

I actually have a current install via Alien's mirror-slackware-current.sh
and then installed it

I have a (many) 13 install I wanna see if a upgrade will take

I noticed after installing current that it sees my drives as sda/sdb, etc
and 13 sees them as hda/hdb
this may be a issue.....
 
Old 03-09-2010, 05:16 PM   #4
GrapefruiTgirl
Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550
Doing it via the DVD method (installing) like by using Robby's scripts, was the first way I moved to 13.0 when it was still in "-current" stage, and it worked perfect. Probably that method is better than manually upgrading using pkgtools or Slackpkg, because the system is not `live`.

As far as the HDD's being seen as HDA or SDA, the Slack kernels are set up like that, yes, but if you make your own kernels, then you can still have the old behavior if you like (this is how I keep it -- hda, hdb etc..). I haven't actually installed a Slack-provided kernel in a long time; I just migrate my own kernel.

I cannot recall right off, what exact kernel CONFIG options make the HDD's become HD* or SD* but there was a fairly recent thread on that subject... And someone will probably know

Sasha
 
Old 03-09-2010, 05:18 PM   #5
dive
Senior Member
 
Registered: Aug 2003
Location: UK
Distribution: Slackware
Posts: 3,211

Rep: Reputation: 292Reputation: 292Reputation: 292
Quote:
Originally Posted by linus72 View Post
I noticed after installing current that it sees my drives as sda/sdb, etc
and 13 sees them as hda/hdb
this may be a issue.....
http://rlworkman.net/howtos/libata-switchover

You may want to consider installing current on a box that isn't mission critical - ie it doesn't matter to you if it goes down, breaks etc

Good luck

Last edited by dive; 03-09-2010 at 05:20 PM.
 
Old 03-09-2010, 05:35 PM   #6
linus72
Guru
 
Registered: Jan 2009
Location: Gordonsville-AKA Mayberry-Virginia
Distribution: PocketWriter/MinimalX
Posts: 5,059

Original Poster
Rep: Reputation: 330Reputation: 330Reputation: 330Reputation: 330
OH
both my big PC's are testbeds
heres' my 2 grub.conf's for my HP and Emachines

HP a810n 1GB RAM 180GB HDD 2.4Ghz AMD Athlon64 3300+
Code:
menuentry "Ubuntu, Linux 2.6.31-20-generic" {
        recordfail=1
        if [ -n ${have_grubenv} ]; then save_env recordfail; fi
	set quiet=1
	insmod ext2
	set root=(hd0,7)
	search --no-floppy --fs-uuid --set 9a3a9fca-1add-4643-8312-a6c3e306f79a
	linux	/boot/vmlinuz-2.6.31-20-generic xforcevesa root=UUID=9a3a9fca-1add-4643-8312-a6c3e306f79a ro splash vga=788  quiet splash
	initrd	/boot/initrd.img-2.6.31-20-generic
}
menuentry "Ubuntu, Linux 2.6.31-20-generic (recovery mode)" {
        recordfail=1
        if [ -n ${have_grubenv} ]; then save_env recordfail; fi
	insmod ext2
	set root=(hd0,7)
	search --no-floppy --fs-uuid --set 9a3a9fca-1add-4643-8312-a6c3e306f79a
	linux	/boot/vmlinuz-2.6.31-20-generic xforcevesa root=UUID=9a3a9fca-1add-4643-8312-a6c3e306f79a ro single splash vga=788
	initrd	/boot/initrd.img-2.6.31-20-generic
}
menuentry "Ubuntu 9.04, kernel 2.6.28-18-generic (on /dev/sda1)" {
	insmod ext2
	set root=(hd0,1)
	search --no-floppy --fs-uuid --set 0b07e554-9083-4467-a1a8-94cb88ee6c6f
	linux /boot/vmlinuz-2.6.28-18-generic xforcevesa root=UUID=0b07e554-9083-4467-a1a8-94cb88ee6c6f ro quiet splash
	initrd /boot/initrd.img-2.6.28-18-generic
}
menuentry "Ubuntu 9.04, kernel 2.6.28-18-generic (recovery mode) (on /dev/sda1)" {
	insmod ext2
	set root=(hd0,1)
	search --no-floppy --fs-uuid --set 0b07e554-9083-4467-a1a8-94cb88ee6c6f
	linux /boot/vmlinuz-2.6.28-18-generic xforcevesa root=UUID=0b07e554-9083-4467-a1a8-94cb88ee6c6f ro single
	initrd /boot/initrd.img-2.6.28-18-generic
}
menuentry "slack13 (on /dev/sda10)" {
	insmod ext2
	set root=(hd0,10)
	search --no-floppy --fs-uuid --set c3e727e0-2bed-490f-8898-4b93698eb311
	linux /boot/vmlinuz root=/dev/hda10 ro  vt.default_utf8=0 vga = 788
	initrd /boot/initrd.gz
}
menuentry "Debian GNU/Linux, kernel 2.6.26-2-686 (on /dev/sda2)" {
	insmod ext2
	set root=(hd0,2)
	search --no-floppy --fs-uuid --set 164d8b87-a312-4852-98f4-2eb07f1ae655
	linux /boot/vmlinuz-2.6.26-2-686 xforcevesa root=UUID=164d8b87-a312-4852-98f4-2eb07f1ae655 ro
	initrd /boot/initrd.img-2.6.26-2-686
}
menuentry "Debian GNU/Linux, kernel 2.6.26-2-686 (single-user mode) (on /dev/sda2)" {
	insmod ext2
	set root=(hd0,2)
	search --no-floppy --fs-uuid --set 164d8b87-a312-4852-98f4-2eb07f1ae655
	linux /boot/vmlinuz-2.6.26-2-686 xforcevesa root=UUID=164d8b87-a312-4852-98f4-2eb07f1ae655 ro single
	initrd /boot/initrd.img-2.6.26-2-686
}
menuentry "ClutchOS-13 (on /dev/sda5)" {
	insmod ext2
	set root=(hd0,5)
	search --no-floppy --fs-uuid --set 82b7c2c1-3710-4c00-adce-3ef7aec76186
	linux /boot/vmlinuz root=/dev/hda5 ro  vt.default_utf8=0 vga = 788
}
menuentry "ClutchOS (on /dev/sda8)" {
	insmod ext2
	set root=(hd0,8)
	search --no-floppy --fs-uuid --set 743e0940-aa50-46b4-a0cf-4257186cbf1c
	linux /boot/vmlinuz root=/dev/hda8 ro  vt.default_utf8=0 vga = 788
}
menuentry "iceslack (on /dev/sda9)" {
	insmod ext2
	set root=(hd0,9)
	search --no-floppy --fs-uuid --set 63571c10-02e5-4591-892c-a59825d83feb
	linux /boot/vmlinuz root=/dev/sda9 ro vga = 788
}

Emachines noname 768MB ram 80GB and 160GB HDD 1.8Ghz AMD AthlonXP 2400++

Code:
menuentry "Debian GNU/Linux, with Linux 2.6.32-trunk-486" {
	insmod ext2
	set root=(hd0,4)
	search --no-floppy --fs-uuid --set fc8f064d-319a-40f3-91b2-be2addc3ea53
	echo	Loading Linux 2.6.26-2-686 ...
	linux	/boot/vmlinuz-2.6.32-trunk-486 root=UUID=fc8f064d-319a-40f3-91b2-be2addc3ea53 ro  quiet
	echo	Loading initial ramdisk ...
	initrd	/boot/initrd.img-2.6.32-trunk-486
}
menuentry "Debian GNU/Linux, with Linux 2.6.32-trunk-486 (recovery mode)" {
	insmod ext2
	set root=(hd0,4)
	search --no-floppy --fs-uuid --set fc8f064d-319a-40f3-91b2-be2addc3ea53
	echo	Loading Linux 2.6.26-2-686 ...
	linux	/boot/vmlinuz-2.6.32-trunk-486 root=UUID=fc8f064d-319a-40f3-91b2-be2addc3ea53 ro single 
	echo	Loading initial ramdisk ...
	initrd	/boot/initrd.img-2.6.32-trunk-486
}
menuentry "PLOP" {
	linux16	/boot/plpbt
}
menuentry "ArchBang! (on /dev/hda3)" {
	insmod ext2
	set root=(hd0,3)
	search --no-floppy --fs-uuid --set 78f05dc2-d2c5-4454-b249-05e2735d03c3
	linux /boot/vmlinuz26 root=/dev/sda3 ro
        initrd /boot/kernel26.img
}
menuentry "Ubuntu 9.04, kernel 2.6.28-18-generic (on /dev/hda6)" {
	insmod ext2
	set root=(hd0,6)
	search --no-floppy --fs-uuid --set 7fe055ba-c753-4616-8b3a-36fe0aeef4d2
	linux /boot/vmlinuz-2.6.28-18-generic root=UUID=7fe055ba-c753-4616-8b3a-36fe0aeef4d2 ro quiet splash vga=792
	initrd /boot/initrd.img-2.6.28-18-generic
}
menuentry "Ubuntu 9.04, kernel 2.6.28-18-generic (recovery mode) (on /dev/hda6)" {
	insmod ext2
	set root=(hd0,6)
	search --no-floppy --fs-uuid --set 7fe055ba-c753-4616-8b3a-36fe0aeef4d2
	linux /boot/vmlinuz-2.6.28-18-generic root=UUID=7fe055ba-c753-4616-8b3a-36fe0aeef4d2 ro single
	initrd /boot/initrd.img-2.6.28-18-generic
}
menuentry "SalixOS (on /dev/hda7)" {
	insmod ext2
	set root=(hd0,7)
	search --no-floppy --fs-uuid --set f3ce1f9d-28d0-4fc0-bd91-92c67cc5dca3
	linux /boot/vmlinuz root=/dev/hda7 ro quiet  vt.default_utf8=1 vga = 788
}
menuentry "IceFinal (on /dev/hda8)" {
	insmod ext2
	set root=(hd0,8)
	search --no-floppy --fs-uuid --set 19a929c8-868e-41ce-a4f1-935a642ac0bd
	linux /boot/vmlinuz root=/dev/sda8 ro vga = 788 vt.default_utf8=1
	initrd /boot/initrd.gz
}
menuentry "Slack13 (on /dev/hda9)" {
	insmod ext2
	set root=(hd0,9)
	search --no-floppy --fs-uuid --set 6b01081d-09d8-416b-8749-f27ed3f11e78
	linux /boot/vmlinuz root=/dev/hda9 ro  vt.default_utf8=0 vga = 788
}
menuentry "Ice9" {
	insmod ext2
	set root=(hd1,3)
	search --no-floppy --fs-uuid --set 3c420d10-c6df-4298-868b-1e5fd03f172b
	linux /boot/vmlinuz root=/dev/sdb3 ro quiet vga=788 vt.default_utf8=1
	initrd /boot/initrd.gz
}
menuentry "SlimSlack (on /dev/hdb2)" {
	insmod ext2
	set root=(hd1,2)
	search --no-floppy --fs-uuid --set 86ccdbff-ee45-4628-ba43-8f09fadcff69
	linux /boot/vmlinuz root=/dev/sdb2 ro quiet  vt.default_utf8=1 vga = 788
}
thats 9 slack'ish installs altogether
including a SalixOS, 12.2, current, some 13's and a couple Absolute's

I already broke my Squeeze install and have to fix that sooner or later...

EDIT: see the differences in how the Slack's recognize my drives

SlimSlack is current and sees it as sda, while 13 sees it as hda,etc
the Ice named ones are Absolute 13.0.9, ClutchOS and ClutchOS-13 are 12.2/13 respectively

I have *buntu 9.04/9.10, ArchBang, some Debian Lenny/Squeeze and many Slack's
Gonna try SoulMage soon...

Last edited by linus72; 03-09-2010 at 05:44 PM.
 
Old 03-09-2010, 08:19 PM   #7
linus72
Guru
 
Registered: Jan 2009
Location: Gordonsville-AKA Mayberry-Virginia
Distribution: PocketWriter/MinimalX
Posts: 5,059

Original Poster
Rep: Reputation: 330Reputation: 330Reputation: 330Reputation: 330
OK

well my Upgrade to Current was flawless and thus far have noticed NO problems

This was my procedure....

1st)
I edited my /etc/slackpkg /mirrors list and commented 13 mirror and uncommented current mirror.

I edited /etc/inittab and put it back to runlevel 3 ( I use Slim from SlackBuilds at level 4)
I put it back to 3 so I could only go to 3 both pre and post upgrade

I rebooted into runlevel 3 and ran

Code:
slackpkg update && slackpkg upgrade-all
I upgraded everything, kernel, etc
I had a 4.5+GB install with jwm,xfce4, and icewm
lots of sbopkg's and some slacky stuff too

It took about an hour to do the upgrade

2nd) as soon as it upgraded I rebooted and booted into my Debian(any linux, livecd,etc) setup
I edited /etc/fstab and made hda into sda
as new current kernel sees my drive as sda now

I edited /etc/lilo.conf and changed hda to sda

I edited my Debian grub2 config manually and changed hda to sda

I edited /etc/rc.d/rc.4 and added my Slim entry as it overwrote the old one

I edited /etc/inittab and made it runlevel 4 again

3rd) I rebooted into New, shiny Slackware Current and Slim started
and then JWM started and here I am!
EDIT: I then ran /sbin/lilo to recognize changes I made to lilo.conf
and rebooted


So, no problems yet, no firefox crashing,,etc

we'll see....

EDIT: to elaborate
here is Old grub2 entry for slack13 on Emachines PC

Code:
menuentry "Slack13 (on /dev/hda9)" {
	insmod ext2
	set root=(hd0,9)
	search --no-floppy --fs-uuid --set 6b01081d-09d8-416b-8749-f27ed3f11e78
	linux /boot/vmlinuz root=/dev/hda9 ro  vt.default_utf8=0 vga = 788
}
and new one

Code:
menuentry "Slack13 (on /dev/hda9)" {
	insmod ext2
	set root=(hd0,9)
	search --no-floppy --fs-uuid --set 6b01081d-09d8-416b-8749-f27ed3f11e78
	linux /boot/vmlinuz root=/dev/sda9 ro  vt.default_utf8=0 vga = 788
}

Last edited by linus72; 03-09-2010 at 08:24 PM.
 
Old 03-10-2010, 06:40 AM   #8
linus72
Guru
 
Registered: Jan 2009
Location: Gordonsville-AKA Mayberry-Virginia
Distribution: PocketWriter/MinimalX
Posts: 5,059

Original Poster
Rep: Reputation: 330Reputation: 330Reputation: 330Reputation: 330
Mornin Gang

Well, I also upgraded my ClutchOS-13 on my HP to current last night
and this mornin upgraded some other stuff

everything works fine

I may have solved the firefox crashing too

After uninstalling/reinstalling several times
I found out that some folders like /etc/mozilla /usr/share/mozilla were not being
deleted when removing seamonkey/mozilla
I deleted those, all the .mozilla folder in /root and anything else I could find related to firefox/seamonkey

I rebooted, installed firefox and seamonkey again
and they haven't crashed yet

EDIT: Seamonkey started crashing...uninstalled..
Firefox isn't crashing though...

Last edited by linus72; 03-10-2010 at 06:51 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Upgrade from 12.0 to -current Yalla-One Slackware 2 06-13-2009 06:30 AM
DISCUSSION: Upgrade to Slackware -current without a -current CD truthfatal LinuxAnswers Discussion 0 09-19-2006 01:42 PM
What first upgrade kernel or upgrade slack 10.0 to current Kelean Slackware 7 01-16-2005 06:54 PM
Is there a way to upgrade to current? trey85stang Debian 9 04-10-2004 10:43 PM
swaret upgrade from 8.0 to current. carboncopy Slackware 14 04-05-2004 11:05 AM


All times are GMT -5. The time now is 08:47 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration