Slackware 13.1 BETA1

chess · 05-13-2010, 11:37 AM

Quote:

Originally Posted by hitest

The most simple way to install Slackware 13.1 BETA would be to install from scratch using Alien Bob's -current build script. Download his script and run it after activating it (chmod +x nameofscript). His script will by default create three -current ISOs for you. You can also edit his script so that it creates one DVD. Alien Bob's script will compute the md5 sums for the -current ISOs so you will know that your -current CDs will work. Back-up all your software before you do the clean install.

And if you'd rather not mirror the entire -current tree, you can also use this script to create a 'MINI' iso (see the -o options in the script) which is a small CD for installing via HTTP/FTP/NFS. It will only download a few files (about 40MB) needed to make the bootable CD. Sort of like a Debian 'netinstall' iso.

Or, you can download the USB installer, dd it to a usb stick, and boot from that.

http://slackware.oregonstate.edu/sla...xe-installers/

Lots of options.

I just used the usb installer to do a fresh install of -current on a laptop. I have a full mirror of both 32 and 64 bit versions, so I used this usb installer to start an install over NFS. It took all of 8 minutes.

Josh000 · 05-14-2010, 12:59 AM

I've been following this with interest.

I note that Slackware 13.1 does not seem to have changed to drastically.

I normally keep my kernel up to date, and most of the software I use on a daily basis doesn't ship with slack, so I kept it updated independently.

I also make sure to apply security patches when necessary.

So I wonder, would anything necessarily be gained by upgrading my entire system to 13.1?

sahko · 05-14-2010, 07:00 AM

Quote:

Originally Posted by Josh000

I note that Slackware 13.1 does not seem to have changed to drastically.

Thats wrong. Theres many many stuff that could be mentioned.
Shadow was updated after 8 years, libpata switch, the libpng/libjpeg rebuild which required many packages to be rebuilt (many of which hadnt on the 32bit version for quite some time), the inclusion of *kit's due to the inclusion of the 4.4.3 KDE version (which IMO feels worst than 4.3.5, maybe due to the kits im not really sure), changed kernel settings resulting to inclusion of powetop in ap/ etc etc etc

Josh000 · 05-14-2010, 07:57 AM

Quote:

Originally Posted by sahko

Thats wrong. Theres many many stuff that could be mentioned.
Shadow was updated after 8 years, libpata switch, the libpng/libjpeg rebuild which required many packages to be rebuilt (many of which hadnt on the 32bit version for quite some time), the inclusion of *kit's due to the inclusion of the 4.4.3 KDE version (which IMO feels worst than 4.3.5, maybe due to the kits im not really sure), changed kernel settings resulting to inclusion of powetop in ap/ etc etc etc

I suppose I should have said it does not seem to have changed drastically in a way that will affect me.

I don't use KDE so any of that stuff doesn't affect me, and I run my own kernels so the rest didn't either.

Didn't know about the libpng/jpeg rebuild though, which is interesting.

henkees · 05-14-2010, 05:31 PM

LAST CHANGELOG:
Fri May 14 19:37:13 UTC 2010
Good hello! We will call this update Slackware 13.1 RC1. With this, the
kernel, compiler, and glibc versions are "golden", and everything is
pretty much ready to release. Last call for bug reports...

It is almost there....

Ahmed · 05-14-2010, 05:43 PM

Awesome

Can't wait to make the jump. After updating to -current regularly, things got a bit hairy with HAL and Xorg, so I stopped updating. A new Slackware release is always a great start!

-A

Ilgar · 05-19-2010, 02:13 AM

Quote:

Originally Posted by rworkman

hitest pointed you to my libata-switchover link, and that's good -- however, please let me know if it needs some further clarification and such; I wrote that mostly from a theoretical viewpoint (as in, rather than actually *doing* the upgrade, I wrote what I *think* will occur)

There was some feedback from several other people involved (including actual error messages and such), and I made some edits based on that feedback, but to make a long story short, that howto might not be perfect. Since it *needs* to be perfect before 13.1 is released, any pushes in that direction will be appreciated.

Hi Robby,

Could the following be a reliable way of guessing the new device names: Instead of doing upgradepkg right away, you first reboot with the installation CD and do fdisk -l, read dmesg output or something similar to see what devices you have, then you boot back to the original system, do the upgrade and use these names in fstab. When booted from the HDD, the devices should get the same names they did with the installation CD, shouldn't they?

dive · 05-19-2010, 02:23 AM

Another way to do it is to find device ids with 'blkid' and then use UUID lines in fstab.

Ilgar · 05-19-2010, 02:30 AM

Quote:

Originally Posted by dive

Another way to do it is to find device ids with 'blkid' and then use UUID lines in fstab.

True (and the howto already mentions that), but I was just wondering if there was another way for those who are not that familiar with those methods.

rworkman · 05-19-2010, 04:23 PM

Quote:

Originally Posted by Ilgar

Hi Robby,

Could the following be a reliable way of guessing the new device names: Instead of doing upgradepkg right away, you first reboot with the installation CD and do fdisk -l, read dmesg output or something similar to see what devices you have, then you boot back to the original system, do the upgrade and use these names in fstab. When booted from the HDD, the devices should get the same names they did with the installation CD, shouldn't they?

Probably (and in practice, they do here), but there's no guarantee.