Slackware 13.1 BETA1

acummings · 05-07-2010, 10:12 AM

Quote:

and 'swim' in NTFS room

ntfs-3g (native on the systemrescuecd) has done excellently lately for me at mounting and writing to NTFS volumes.

<grin>

But, I *do* see your logic, sir.

--
Alan.

acummings · 05-07-2010, 10:27 AM

Quote:

For the new user to get '-current' or this 'Slackware 13.1 BETA1' I suggest that you use Alien_Bob's-script-mirror-slackware-current.sh.

I'm an old user (my age: 59) <grin> I use Alien Bob's as per above. Here's some aliases I already had in my .bashrc

Code:

alias makdvdslackcurr='sh ~/bin/mirror-slackware-current.sh -l /mnt/sda_8/slackware -i -o DVD'

alias mirr64slackcurr='sh ~/bin/mirror-slackware-current.sh -l /mnt/sda_8/slackware -a x86_64 -o NONE -m slackware.mirrors.tds.net::slackware/slackware64-current'

alias mirrslackcurr='sh ~/bin/mirror-slackware-current.sh -l /mnt/sda_8/slackware -o NONE -m slackware.mirrors.tds.net::slackware/slackware-current'

BTW, silly Windows. <grin> but it does have value for some people but the only value it has for me is I repair/rescue/de_virus/de_spyware *other people's* (Windows XP) computers.

I learn Win 7 only enough for me to fix other people's Win 7, not mine.

I'm hooked on Slackware.

--
Alan.

a4z · 05-07-2010, 10:43 AM

did the update this morning
now every time I start kontakt kmail starts akonadi
I have to wait while the "start akonadi prograssbar is on the screen
and then I get the the default Akonadi Server Self-Test Report

how can I turn this off?

slackpkg reports md5 errors like it did by others, however I have upgraded all packages, was this a bad idea?

also I would like to re point to this
http://www.linuxquestions.org/questi...ml#post3805717

problems like this
http://www.linuxquestions.org/questi...tem-mt-805905/
and others (I do not whant to research the threads) could be avoid in future by providing a useful boost build that does not eliminate the -mt versions.

I will rebuild boost for me with 1.42 or 1.43 this weekend (hope so), if anyone is interest I can post the buildscript here

damgar · 05-07-2010, 10:53 AM

Quote:

Originally Posted by a4z

did the update this morning
now every time I start kontakt kmail starts akonadi
I have to wait while the "start akonadi prograssbar is on the screen
and then I get the the default Akonadi Server Self-Test Report

how can I turn this off?

With Eric's KDE packages I've just removpkg'd Akonadi. I haven't seen any ill effects. The stock 13 KDE packages as well as the 4.3.x packages I'm using now on my stock 13 don't appreciate that. It's easy enough to just reinstall it though if it doesn't work, provided you have a copy of the package.

linus72 · 05-07-2010, 11:13 AM

After upgrades this morning xfce4 wont load on 2 of my installs

heres xsession errors as X crashes

Code:

<stdin>:1:3: error: invalid preprocessing directive #Those
<stdin>:2:3: error: invalid preprocessing directive #or
<stdin>:3:3: error: invalid preprocessing directive #Xft
<stdin>:4:3: error: invalid preprocessing directive #Xft
xrdb:  "Xft.hinting" on line 9 overrides entry on line 6
xrdb:  "Xft.hintstyle" on line 11 overrides entry on line 7
/etc/X11/xinit/xinitrc.xfce: line 134: ck-launch-session: command not found

anyone else get this?

rg3 · 05-07-2010, 11:39 AM

Just upgraded and no problems here, but I don't use KDE on this computer. Huge thanks and congratulations to the Slackware team. This ugprade proves the fantastic work they're doing together with upstream projects, getting them to support Slackware itself by adding features such as shadow support to essential components for the distribution. This ensures we get the best possible experience envisioned by the team. Congratulations again.

ponce · 05-07-2010, 11:53 AM

@linus: I think it's because by default it tries to run with consolekit/policykit and you are probably missing them in your install: you can try modifying line 134 of /etc/X11/xinit/xinitrc.xfce deleting the ck-launch-session command (but leave there the $xfcesm).
you can also copy it to your home as ~/.xinitrc and edit that copy if you need it for one user only.

I don't know if you will miss any functionality not running if in a policykit session: I'm not a xfce user, you know it surely better than me, so you will discover if something is missing trying

sjampoo · 05-07-2010, 01:43 PM

Love you guys. ( no really! )

Got atleast the boxes running again... with the 13 dvd I chroot into the borked /dev/sda2. couldn't get to my ftp mirror, got eth0 up, restarted the slackpkg sequence to go to -current... and voila. 13.1(b) up and running, without any flaws!
got sbopkg going, nvidia kernel + driver installed.. wow.. KDE looks really slick.

Now the slacktop needs an update.

PS: booting from the 13.1 DVD (thanks @ ponce), the installer welcomes me (us) to 13.1.. without any comments on the \ beta / status... so as a note to myself I wrote a big ' -current' on the disk for future reference (Although it will turn into a coaster within months from now).

BobNutfield · 05-07-2010, 04:17 PM

Just did the upgrade and all is well, except my laptop runs 10-12 degrees hotter! It is averaging 70 degrees c. Does it turn off cpufreq or something? Never seen this with just an upgrade.

Bob

damgar · 05-07-2010, 04:36 PM

Quote:

Originally Posted by slackass

I've never used gslapt or slapt-get.
I used gftp to get GSB 2.28 and installed it with:
upgradepkg --install-new *?/*.t?z

Thanks for this. I used lftp to create the mirror and upgradepkg handled the move from 2.26 to 2.28 well. Now I'm trying to figure out what to do about the versions of policykit and consolekit provided from GSB and the new current before updgrading to the 13.1 beta.

Did you do anything special regarding these two packages?

lumak · 05-07-2010, 04:40 PM

We waited 3+ months for an update that we were told was not going to come for 13.1 and automatically gets put into beta status when it is?

On a positive note, it seems Slackware was a major driving force to fixing polkit to support shadow. Nice that something as old as Slackware still has relevance and pull in the direction of things.

onebuck · 05-07-2010, 06:13 PM

Hi,

Quote:

Originally Posted by lumak

We waited 3+ months for an update that we were told was not going to come for 13.1 and automatically gets put into beta status when it is?

Where did you get that information?

Quote:

Originally Posted by lumak

On a positive note, it seems Slackware was a major driving force to fixing polkit to support shadow. Nice that something as old as Slackware still has relevance and pull in the direction of things.

Slackware has always had relevance!

She maybe the oldest but still the best and strongest distribution hands down.

andrew.46 · 05-07-2010, 07:16 PM

Hi onebuck,

Quote:

Originally Posted by onebuck

She maybe the oldest but still the best and strongest distribution hands down.

Hmmm.... I have always thought of Slackware as being masculine...

Andrew

damgar · 05-07-2010, 07:22 PM

For anyone interested: upgrading slackpkg prior to the rest seems to stop the md5sum errors, at least for me, and the Gnome Slackbuild Project 2.28 seems to coexist with the 13.1 beta quite nicely.

storkus · 05-07-2010, 07:25 PM

Does anyone know if the "policy" on a mixed 32/64 bit install has changed or not? That is, to do a 13.1 32/64 install would I have to apply Bob's patches like with 13.0 or will there be an actual ISO released where this is all included? This is from a former SlamD64'er.

Also, can't wait for 13.1 pre-ordering to show on the Slack Store so I can send in my support!!

Thanks again to Pat and the gang from this long-time (15 years/since 2.x) Slacker!

Mike