LinuxQuestions.org
Share your knowledge at the LQ Wiki.
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 09-21-2013, 06:24 PM   #46
AlleyTrotter
Member
 
Registered: Jun 2002
Location: Coal Township PA
Distribution: Slackware64-14.1 (3.17.3) UEFI enabled
Posts: 357

Rep: Reputation: 77

Quote:
Originally Posted by solarfields View Post
...Grub2 is offered for those who want it and people complain that it is there. I don't get it. ...
Didn't mean to offend. You know "teaching an old dog new tricks" and all that.
I'm all in with whatever PV decides on for Slackware's new boot loader.
Already studying grub2 manual. I hope it solves the initial efi boot problem.
It looks like it may be able to boot into setup from the install dvd while in UEFI mode.
That would be great news.
John
 
1 members found this post helpful.
Old 09-21-2013, 06:30 PM   #47
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 875

Rep: Reputation: 1823Reputation: 1823Reputation: 1823Reputation: 1823Reputation: 1823Reputation: 1823Reputation: 1823Reputation: 1823Reputation: 1823Reputation: 1823Reputation: 1823
Quote:
Originally Posted by AlleyTrotter View Post
Didn't mean to offend. You know "teaching an old dog new tricks" and all that.
I'm all in with whatever PV decides on for Slackware's new boot loader.
LILO won't be going anywhere. GRUB was added purely because it's a nice option for UEFI (and LILO doesn't work there at all). So use it if you like (for UEFI or BIOS)... otherwise, don't.
 
5 members found this post helpful.
Old 09-21-2013, 06:44 PM   #48
rkfb
Member
 
Registered: Oct 2003
Location: Guildford, England
Distribution: slackware
Posts: 303

Rep: Reputation: 41
Quote:
Originally Posted by Habitual View Post

[...]

Scarey too. Skype, Thunderbird, and rainlendar2 all quit working.

Fortunately, It was only for a minute.
There is a 64-bit Skype at Slacky with the 32-bit libraries built in.

http://www.slacky.eu/asche64/pkgs/in...er=16&pkg=2111
 
1 members found this post helpful.
Old 09-21-2013, 06:48 PM   #49
astrogeek
Senior Member
 
Registered: Oct 2008
Distribution: Slackware: 12.1, 13.1, 14.1, 64-14.1, -current, FreeBSD-10
Posts: 2,031

Rep: Reputation: 804Reputation: 804Reputation: 804Reputation: 804Reputation: 804Reputation: 804Reputation: 804
Quote:
Originally Posted by volkerdi View Post
LILO won't be going anywhere. GRUB was added purely because it's a nice option for UEFI (and LILO doesn't work there at all). So use it if you like (for UEFI or BIOS)... otherwise, don't.
Very reassuring! Thanks!
 
Old 09-22-2013, 03:05 AM   #50
solarfields
Member
 
Registered: Feb 2006
Location: Outer Shpongolia
Distribution: Slackware
Posts: 483

Rep: Reputation: 126Reputation: 126
Quote:
Didn't mean to offend.
No offense taken, man
 
Old 09-22-2013, 08:18 AM   #51
jostber
Member
 
Registered: Jul 2001
Location: Skien, Norway
Distribution: Slackware 14.0 64-bit
Posts: 228

Rep: Reputation: 41
http://ostatic.com/blog/slackware-14-1-on-its-way
 
Old 09-22-2013, 08:59 AM   #52
ppencho
LQ Newbie
 
Registered: Jan 2004
Location: Bulgaria
Distribution: Slackware64-current
Posts: 27

Rep: Reputation: 3
Grub2 command-line freeze

I configured Grub2 with:
Code:
grub-install /dev/sda
grub-mkconfig -o /boot/grub/grub.cfg
It works fine. But if in GrubMenu I enter the grub command-line (by 'c') then any of the following commands makes it to freeze:
Code:
help sleep
help linux
help usb
help exit
exit
If I run 'sleep 1' then 'help sleep' does not cause a freeze.

Freeze means that only the power button (in case of 'exit' command also ctrl-alt-del helps) heals it.
 
Old 09-22-2013, 09:11 AM   #53
jtsn
Member
 
Registered: Sep 2011
Location: Europe
Distribution: Slackware
Posts: 896

Rep: Reputation: 425Reputation: 425Reputation: 425Reputation: 425Reputation: 425
Quote:
Originally Posted by volkerdi View Post
LILO won't be going anywhere. GRUB was added purely because it's a nice option for UEFI (and LILO doesn't work there at all). So use it if you like (for UEFI or BIOS)... otherwise, don't.
Is ELILO not a suitable LILO replacement?

BTW: Today I tried grubx64.efi with 14.0: It seems to load the kernel (still 3.8.13 which works fine with ELILO) + initrd and then crashes the machine without further notice. Currently I have no idea how to debug this...
 
Old 09-22-2013, 12:10 PM   #54
Skaperen
Senior Member
 
Registered: May 2009
Location: WV, USA
Distribution: Slackware, CentOS, Ubuntu, Fedora, Timesys, Linux From Scratch
Posts: 1,777
Blog Entries: 20

Rep: Reputation: 116Reputation: 116
Quote:
Originally Posted by volkerdi View Post
LILO won't be going anywhere. GRUB was added purely because it's a nice option for UEFI (and LILO doesn't work there at all). So use it if you like (for UEFI or BIOS)... otherwise, don't.
And syslinux is still in there. I know because I've been using it (literally, extlinux) for a few years, and have been with -current. I wanted more than what I could do in LILO, didn't want to have to re-run the lilo command every time I changed something, and ended up hating grub almost as soon as I tried it (installed from source back then).

While I can install syslinux from source (I have done so to test out new versions), I'd like to see it stay in Slackware.
 
1 members found this post helpful.
Old 09-22-2013, 09:41 PM   #55
TommyC7
Member
 
Registered: Mar 2012
Distribution: Slackware, CentOS, OpenBSD, FreeBSD
Posts: 438

Rep: Reputation: Disabled
Will -current keep following newer versions of Firefox or is -current also staying on 24.*-esr?
 
Old 09-22-2013, 09:48 PM   #56
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 875

Rep: Reputation: 1823Reputation: 1823Reputation: 1823Reputation: 1823Reputation: 1823Reputation: 1823Reputation: 1823Reputation: 1823Reputation: 1823Reputation: 1823Reputation: 1823
Quote:
Originally Posted by TommyC7 View Post
Will -current keep following newer versions of Firefox or is -current also staying on 24.*-esr?
After 14.1 is released, -current will probably follow the latest versions of Firefox.
 
1 members found this post helpful.
Old 09-23-2013, 12:50 AM   #57
TommyC7
Member
 
Registered: Mar 2012
Distribution: Slackware, CentOS, OpenBSD, FreeBSD
Posts: 438

Rep: Reputation: Disabled
Okay, thank you for letting us know Pat.
 
Old 09-23-2013, 01:52 AM   #58
jaycee4
Member
 
Registered: Aug 2009
Posts: 42

Rep: Reputation: 7
I just upgraded a fresh install of Slackware 14.0 to -current today, following the instructions provided on SlackDocs. The upgrade went without any issues. Not that I would expect otherwise... It therefore seems highly likely that an up-to-date version of Slackware 14.0 would also upgrade to -current without issue. No doubt upgrades to the future release of Slackware 14.1 would similarly be flawless.
I'll prepare alpha releases of updated mirror lists for slackpkg this week. This time I'll additionally look for rsync mirrors for the mirrors.slackware.com website, and also include armedslack in addition to the x86 and x86_64 architectures for slackpkg. I think I'm correct in saying that Slackware releases aren't available for S/390 anymore, so I'll encourage Pat to remove that list from the slackpkg package. Hopefully I'll finalise the lists within a few weeks so that it doesn't interfere with the Slackware 14.1 release date (so to speak). I'll bump the relevant thread I created last year and post the pre- and final releases of the updated lists there. Anyway, happy Slacking!
 
Old 09-23-2013, 06:49 AM   #59
rvdboom
Member
 
Registered: Jul 2007
Distribution: Slackware
Posts: 186

Rep: Reputation: 23
Quote:
Originally Posted by hitest View Post
Yeah, I am also more comfortable with lilo and like how it works. When 14.1 comes out I may try GRUB on one of my boxes just for the novelty.
As always, use whatever works for you. I moved to grub because now and then I appreciate that I can just modify the boot command line, especially the kernel options or the run level, at boot time. Very handy when for some reason I want to boot on runlevel 3 (I usually go directly to 4) or when I run into a buggy kernel (I tend to compile my own kernels to test newer ones).
Funily, grub seems a bit more complicated in its 2.0 version than what it was in the legacy one, but there are enough tutorials on the web to quickly get the hand of it. It's rather simple.
Well, both works, happy to see grub in Slack since I use it.
What I did, to avoid having many entries called "Slackware 14" as someone told, is to go into /etc/grub.d, created one script per kernel I want to boot, as "0*_slackware_perso_*" and using the following syntax :

Code:
#!/bin/sh -e
cat << EOF
menuentry "Slackware Linux 3.11.1-vdb" {
  set root=(hd0,1)
  linux /boot/3.11.1-vdb root=/dev/sda1 ro resume=/dev/sda2 radeon.dpm=1
}
EOF
I numbered them in the order of apparence that I wanted, then removed execution rights (chmod -x) to the "10_linux", "20_linux_xen" and "30_os-prober" scripts, which do the autodetection I want to avoid.
Then a simple "grub-mkconfig -o /boot/grub/grub.cfg" compiles the changes and with the reboot, I just have the entries I created by myself.
It was actually much simpler to upgrade from grub legacy than I feared. Once the package was upgraded, a simple "grub-install /dev/sda" was enough to install the new grub on the MBR and set up the various files, then I did my configuration as above.
 
Old 09-23-2013, 08:05 AM   #60
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad T61 6457-4XG
Posts: 4,546

Rep: Reputation: 1191Reputation: 1191Reputation: 1191Reputation: 1191Reputation: 1191Reputation: 1191Reputation: 1191Reputation: 1191Reputation: 1191
Quote:
Originally Posted by rvdboom View Post
[..] I moved to grub because now and then I appreciate that I can just modify the boot command line, especially the kernel options or the run level, at boot time. Very handy when for some reason I want to boot on runlevel 3 (I usually go directly to 4) [...]
At boot time, when you see lilo's screen hit [Tab], and complete your command line, e.g.
Code:
Linux 3
Of course you can set any kernel or modules parameters that way.

Last edited by Didier Spaier; 09-23-2013 at 08:08 AM.
 
  


Reply

Tags
current


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
Hey folks unkilbeeg LinuxQuestions.org Member Intro 1 01-26-2012 11:41 AM
Hey folks... FP! spool32 LinuxQuestions.org Member Intro 1 06-30-2011 02:01 PM
[SOLVED] Hey Folks! chroot/jail Linux - Newbie 8 01-10-2011 08:19 PM
Hey folks! vstrabello LinuxQuestions.org Member Intro 1 11-02-2009 06:07 AM
Hey Folks WinterOrbit LinuxQuestions.org Member Intro 1 11-27-2004 05:13 AM


All times are GMT -5. The time now is 04:13 PM.

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