LinuxQuestions.org
Help answer threads with 0 replies.
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 06-25-2012, 09:47 AM   #16
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,485

Rep: Reputation: 856Reputation: 856Reputation: 856Reputation: 856Reputation: 856Reputation: 856Reputation: 856

Eric, my thanks for the update. I feel that having a standardised way of handling bridging in Slackware will be a big bonus.
I have already studied your guides on QEMU and VDE which allowed me to get a virtual machine running on my little intranet at work. I also wish to say thankyou on behalf of my colleagues! It has been a boon for productivity.
 
Old 06-25-2012, 10:57 AM   #17
SpelledJ
Member
 
Registered: Jun 2006
Location: Birmingham, AL
Distribution: Slackware64-13.1, 12.1
Posts: 119

Rep: Reputation: 20
Quote:
Originally Posted by GazL View Post
BTW, Anyone else notice Pat's use of "slackware-next" in the comments for the kernel package? Far more descriptive name than "slackware-current" which has always seemed a bit of a misnomer. I like it.
I saw that and wasn't sure how to interpret it. Does he mean slackware-current will be called "slackware-next" after 14 is released? Was he just using it a placeholder for "Slackware 14" (i.e. the next release number)? Or did he mean slackware-current after 14 is released, not to be confused with -current prior to 14's release?

I took it to just be a placeholder to mean "Slackware 14": "Systems older than that can still be upgraded to -current (or the next release of Slackware) and will work fine using megaraid.ko . . ."
 
Old 06-25-2012, 11:15 AM   #18
GazL
Senior Member
 
Registered: May 2008
Posts: 3,475

Rep: Reputation: 1013Reputation: 1013Reputation: 1013Reputation: 1013Reputation: 1013Reputation: 1013Reputation: 1013Reputation: 1013
Perhaps you're right, though at this stage he knows he's going to number it 14
Quote:
Bumped slackware-version to 14.0.
... so why use a placeholder at all.

Changing the name would require coordination with the mirrors and tools though so I wouldn't assume he's planning to change it unless he says so explicitly. It just struck me that slackware-next was a better name than slackware-current considering its role.

Last edited by GazL; 06-25-2012 at 11:17 AM.
 
Old 06-25-2012, 11:24 AM   #19
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,474

Rep: Reputation: 901Reputation: 901Reputation: 901Reputation: 901Reputation: 901Reputation: 901Reputation: 901Reputation: 901
Quote:
Originally Posted by CTM View Post
I really appreciate the built-in bridge support in rc.inet1 - it'll replace my own, probably brittle, shell script implementation. Thanks, Eric
I quote all of this
 
Old 06-25-2012, 11:59 AM   #20
sycamorex
LQ Veteran
 
Registered: Nov 2005
Location: London
Distribution: Slackware64-current
Posts: 5,578
Blog Entries: 1

Rep: Reputation: 1033Reputation: 1033Reputation: 1033Reputation: 1033Reputation: 1033Reputation: 1033Reputation: 1033Reputation: 1033
It seems that rsync.osuosl.org has just been synced. Thanks
 
Old 06-25-2012, 12:10 PM   #21
CTM
Member
 
Registered: Apr 2004
Distribution: Slackware64 14.0 / 14.1
Posts: 131

Rep: Reputation: 50
Speaking of networking: any chance of a bump for NetworkManager to 0.9.4 in -current? I've been using it with the associated bits and pieces (nm-applet, VPN plugins) for a few months on 13.37 and it works fine. It'd be great to see it in 14.
 
1 members found this post helpful.
Old 06-25-2012, 01:48 PM   #22
SpelledJ
Member
 
Registered: Jun 2006
Location: Birmingham, AL
Distribution: Slackware64-13.1, 12.1
Posts: 119

Rep: Reputation: 20
Quote:
Originally Posted by GazL View Post
... so why use a placeholder at all.
Maybe he wrote the note for kernel-huge before updating aaa_base and writing the note for it, then didn't go back and just say "Slackware 14" in the kernel-huge note. Either way, it's still a bit of a cryptic reference. I also considered the mirror problem of changing the name of current to "next". Probably unlikely due to tradition and inertia.
 
Old 06-25-2012, 03:26 PM   #23
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,332

Rep: Reputation: Disabled
People running my KDE 4.9-beta2 for Slackware-current, please note that the upgrade to attica-0.4.0 in -current broke a great deal of my packages.

Read http://alien.slackbook.org/blog/test...kde-4-9-beta2/ if you need a fix.

Eric
 
Old 06-25-2012, 03:34 PM   #24
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,332

Rep: Reputation: Disabled
Quote:
Originally Posted by SpelledJ View Post
Maybe he wrote the note for kernel-huge before updating aaa_base and writing the note for it, then didn't go back and just say "Slackware 14" in the kernel-huge note.
That's exactly what happened. The kernel package was originally compiled on june 22nd, and we deciced only later on the next release version number.

The kernel is always first target, followed by glibc, when the gcc has been upgraded. The kernel packages were rebuilt just before going public with this batch, to add
Code:
CONFIG_FB_EFI=y
(it was off at first but I read a post by ruario yesterday, stating that this was needed to get visible framebuffer text on EFI boot).

Eric
 
Old 06-25-2012, 03:57 PM   #25
Darth Vader
Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 625

Rep: Reputation: 115Reputation: 115
Quote:
Originally Posted by Alien Bob View Post
People running my KDE 4.9-beta2 for Slackware-current, please note that the upgrade to attica-0.4.0 in -current broke a great deal of my packages.

Read http://alien.slackbook.org/blog/test...kde-4-9-beta2/ if you need a fix.

Eric
Too late!

I solved the problem in the hard way: recompiling the KDE-4.8.90's kdelibs and kdebase packages group.

And thank you, AlienBOB, for the excellent KDE build-system!

Last edited by Darth Vader; 06-25-2012 at 03:58 PM.
 
Old 06-25-2012, 04:11 PM   #26
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,332

Rep: Reputation: Disabled
Quote:
Originally Posted by Darth Vader View Post
Too late!

I solved the problem in the hard way: recompiling the KDE-4.8.90's kdelibs and kdebase packages group.

And thank you, AlienBOB, for the excellent KDE build-system!
Thank you Darth Vader. And, good to see you're still using Slackware! I thought you had moved darkstarlinux away from its Slackware parent and were no longer slacking.

Cheers, Eric
 
Old 06-25-2012, 05:18 PM   #27
BroX
Member
 
Registered: Oct 2003
Location: Sweden
Distribution: Slackware64-current
Posts: 755

Rep: Reputation: 65
Thanks for the quick fix Eric!

Should have come here first before upgrading, but it was nice to use lynx once again

Cheers.
 
Old 06-25-2012, 05:57 PM   #28
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,893

Rep: Reputation: 948Reputation: 948Reputation: 948Reputation: 948Reputation: 948Reputation: 948Reputation: 948Reputation: 948
Quote:
Originally Posted by Alien Bob View Post
The kernel is always first target, followed by glibc, when the gcc has been upgraded. The kernel packages were rebuilt just before going public with this batch, to add
Code:
CONFIG_FB_EFI=y
(it was off at first but I read a post by ruario yesterday, stating that this was needed to get visible framebuffer text on EFI boot).
Cool, that'll should it much nicer when using EFI based systems, though I was really just repeating what rwebber had discovered.

Edit: Offering an EFI capable bootloader would also be nice.

P.S. If anyone wants to test EFI booting and doesn't have the hardware, VirtualBox can simulate an EFI system as rwebber also pointed out.

Last edited by ruario; 06-25-2012 at 06:02 PM. Reason: Added the request for an EFI bootloader
 
Old 06-25-2012, 06:03 PM   #29
hitest
Senior Member
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 4,240

Rep: Reputation: 570Reputation: 570Reputation: 570Reputation: 570Reputation: 570Reputation: 570
Upgrade went smooth as silk today. Many thanks to Patrick J. Volkerding and the entire Slackware Team. It is all good, man.
 
Old 06-25-2012, 07:36 PM   #30
ReaperX7
Senior Member
 
Registered: Jul 2011
Location: California
Distribution: LFS-7.6, Slackware 14.1, FreeBSD 10.1
Posts: 3,635
Blog Entries: 15

Rep: Reputation: 1104Reputation: 1104Reputation: 1104Reputation: 1104Reputation: 1104Reputation: 1104Reputation: 1104Reputation: 1104Reputation: 1104
Most of the packages have been updated, but not everything. While the base of 14.0 has been set, the real true remaining updates have yet to be made yet, such as the new version of XFce, the newest kernel, and various other library packages to name a few.

You can tell the next release is near, but it's not here yet. Plenty of work left to be done, so until then, keep your eye's pealed on the Slackware.com webpage and the Changelog.

The best is yet to come.
 
  


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
LXer: Massive updates in slackware-current LXer Syndicated Linux News 0 03-12-2009 04:31 AM
After massive updates new BE is unbootable hscast Solaris / OpenSolaris 5 11-21-2008 06:54 PM
Slackware current updates today! neo Slackware 2 04-22-2005 06:32 PM
VMWare on Slackware Current: massive display corruption senorsnor Slackware 4 02-24-2005 01:30 PM
Why haven't there been any updates to slackware current lately? moger Slackware 18 07-21-2004 11:21 AM


All times are GMT -5. The time now is 01:19 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