Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
|
10-24-2013, 08:53 AM
|
#46
|
LQ Addict
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,284
Rep:
|
Can't connect to wifi through NetworkManager
[wrongly posted as a reply, opened new thread instead, sorry]
Last edited by Didier Spaier; 10-24-2013 at 09:01 AM.
|
|
|
10-24-2013, 09:19 AM
|
#47
|
Member
Registered: Mar 2009
Distribution: Slackware
Posts: 121
Rep:
|
Quote:
Originally Posted by mattallmill
I have also pre-ordered the Slackware release. I cannot think of money that is better spent.
|
Wouldn't a donation be even better, as most of it would go straight to the developers? When buying the disks, a good portion of the money goes towards multiplying and shipping them.
|
|
|
10-24-2013, 09:40 AM
|
#48
|
Senior Member
Registered: Dec 2008
Posts: 1,191
|
Is it possible to add label / uuid support for swap partition in the initrd? This should not be much different than supporting label / uuid for the root partition.
|
|
|
10-24-2013, 08:46 PM
|
#49
|
Member
Registered: Aug 2004
Distribution: Debian
Posts: 443
Rep:
|
Quote:
Originally Posted by LukenShiro View Post
I've noticed a tiny problem: slackpkg package's version and shell script's version are not aligned:
/var/log/packages/:
slackpkg-2.82.0-noarch-12
but:
# slackpkg
slackpkg - version 2.81.1
[..]
Quote:
Originally Posted by afreitascs
even here ...
|
|
just for the record, is the version of the manual slackpkg which is version 12.1 ....
forgiveness lords
|
|
|
10-24-2013, 08:51 PM
|
#50
|
Member
Registered: Nov 2009
Location: Kansas, USA
Distribution: Slackware64-15.0
Posts: 865
|
Quote:
Originally Posted by chicken76
Wouldn't a donation be even better, as most of it would go straight to the developers? When buying the disks, a good portion of the money goes towards multiplying and shipping them.
|
A very good suggestion. I will consider it for the next release.
|
|
|
10-25-2013, 06:20 AM
|
#51
|
Senior Member
Registered: Dec 2008
Posts: 1,191
|
|
|
|
10-25-2013, 10:01 AM
|
#52
|
LQ Newbie
Registered: Oct 2013
Posts: 2
Rep:
|
xterm #296 -> #297, contains changes to handling the xft fontName/Size. Checks for missing bitmaps cells and other...
ChangeLog
[edit]
If there is no known issues with --enable-double-buffer, maybe add it to avoid text "flickering" on slower hardware. That would be nice.
Last edited by esodax; 10-25-2013 at 06:09 PM.
|
|
|
10-26-2013, 07:02 AM
|
#53
|
LQ Veteran
Registered: May 2008
Posts: 7,099
|
rc.M contains this:
Code:
# If we're using udev, make /dev/cdrom and any other optical drive symlinks
# if some udev rule hasn't made them already:
if grep -wq sysfs /proc/mounts && grep -q tmpfs /proc/filesystems; then
if ! grep -wq nohotplug /proc/cmdline ; then
if [ -x /lib/udev/rc.optical-symlinks -a -x /etc/rc.d/rc.udev ]; then
/bin/sh /lib/udev/rc.optical-symlinks
fi
fi
fi
My first thought was shouldn't that be grep -q devtmpfs /proc/mounts, but then I found that there is no rc.optical-symlinks file to run, so can this entire snippet go?
Last edited by GazL; 10-26-2013 at 07:04 AM.
|
|
|
10-26-2013, 07:39 AM
|
#54
|
LQ Veteran
Registered: May 2008
Posts: 7,099
|
Also, while we're on the subject of rc.M. These seem like they belong on the end of rc.S so that they take effect when booting into single-user mode:
Code:
# Load a custom screen font if the user has an rc.font script.
if [ -x /etc/rc.d/rc.font ]; then
. /etc/rc.d/rc.font
fi
# Load a custom keymap if the user has an rc.keymap script.
if [ -x /etc/rc.d/rc.keymap ]; then
. /etc/rc.d/rc.keymap
fi
I was going to suggest calling rc.font as early as possible (boot messages can be a little small on a high dpi screen before setfont is called, plus setfont also seems to wipe out the console history so scroll back doesn't work), but I've just thought of a better way:
Code:
test@rc2:~$ cat /etc/modprobe.d/nouveau.conf
install nouveau /sbin/modprobe --ignore-install nouveau $CMDLINE_OPTS && /usr/bin/setfont -m 8859-15 ter-132b.psf.gz
(not suggesting stock slackware should do that mind you, but I think I'm going to use it in place of rc.font).
update: Been playing around with this a little more, and moving the call for rc.font to the end of rc.S also has the advantage of setting the font on all 6 terminals. When it's left to rc.M it only goes on the first (which I'm assuming is because terminals 2-6 will have a getty process established on them by the time rc.M normally runs rc.font.
Last edited by GazL; 10-26-2013 at 01:18 PM.
|
|
1 members found this post helpful.
|
10-26-2013, 04:30 PM
|
#55
|
Member
Registered: May 2004
Distribution: Slackware
Posts: 215
Rep:
|
If it's not too late, can I suggest this patch for grub?
Fix for Bug#37280
This fixes a problem that evidently crops up on some hardware in which grub fails to terminate the EFI environment and thus won't boot successfully:
http://savannah.gnu.org/bugs/?37280
and which I encountered leading to my rash of posts in the last 24 hours in Slackware on UEFI.
This afternoon I applied that patch to grub, rebuilt the efi images and burned a new installer DVD, and now it boots as it should.
Thanks,
Dave
|
|
1 members found this post helpful.
|
10-26-2013, 06:13 PM
|
#56
|
Senior Member
Registered: Oct 2005
Distribution: Slackware 14.1
Posts: 3,482
|
Quote:
Also, while we're on the subject of rc.M. These seem like they belong on the end of rc.S so that they take effect when booting into single-user mode:
|
I like that suggestion.
|
|
|
10-26-2013, 08:22 PM
|
#57
|
Member
Registered: Apr 2009
Location: Oz
Distribution: slackware64-14.0
Posts: 875
|
Quote:
Originally Posted by GazL
Also, while we're on the subject of rc.M. These seem like they belong on the end of rc.S so that they take effect when booting into single-user mode:
|
Only one problem, what if some problem occurs with the system and that command causes the console to become unusable and you need to drop to single user mode to fix it?
|
|
1 members found this post helpful.
|
10-26-2013, 08:27 PM
|
#58
|
Member
Registered: Oct 2011
Distribution: Slackware64
Posts: 364
Rep:
|
I think GazL's idea of moving rc.font and rc.keymap invocation to rc.S makes good sense.
wildwizard's point seems important. Too bad there isn't a script in between the two.
Isn't rc.K for going to runlevel 1, not rc.S?
Last edited by j_v; 10-26-2013 at 08:37 PM.
|
|
|
10-26-2013, 08:49 PM
|
#59
|
Slackware Maintainer
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 2,930
|
Quote:
Originally Posted by GazL
update: Been playing around with this a little more, and moving the call for rc.font to the end of rc.S also has the advantage of setting the font on all 6 terminals. When it's left to rc.M it only goes on the first (which I'm assuming is because terminals 2-6 will have a getty process established on them by the time rc.M normally runs rc.font.
|
Hmmm... rc.font sets the font on all 6 terminals here.
I can see possibly getting rid of the stale code for the optical-symlinks script, but I'm inclined to say this isn't the time to rearrange much else.
|
|
|
10-27-2013, 04:54 AM
|
#60
|
LQ Veteran
Registered: May 2008
Posts: 7,099
|
Quote:
Originally Posted by volkerdi
Hmmm... rc.font sets the font on all 6 terminals here.
|
edit: I've just restored them to stock and it seems that you're right. Perhaps it only does the one when you run it from the command-line and I'm getting confused... But I'm sure I had to use a for loop in rc.font in the past to work around this.
Quote:
Originally Posted by volkerdi
I can see possibly getting rid of the stale code for the optical-symlinks script, but I'm inclined to say this isn't the time to rearrange much else.
|
Yep, that's understandable. I appreciate I was a little last-minute here. It was just something I spotted while poking around looking for bugs.
I'll mention them again sometime after the post-release circus has died down: along with a few other suggestions I've been holding-back for the next cycle.
Last edited by GazL; 10-27-2013 at 07:42 AM.
|
|
|
All times are GMT -5. The time now is 01:34 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|