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?
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 :rolleyes: <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.
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.....
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 ;)
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 :)
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+
Emachines noname 768MB ram 80GB and 160GB HDD 1.8Ghz AMD AthlonXP 2400++
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...
well my Upgrade to Current was flawless and thus far have noticed NO problems:)
This was my procedure....
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
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
So, no problems yet, no firefox crashing,,etc
EDIT: to elaborate
here is Old grub2 entry for slack13 on Emachines PC
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...
|All times are GMT -5. The time now is 12:37 PM.|