SlackwareThis 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.
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.
Awesome! I appreciate you clearing that up Alien. I have been sitting on my hands wondering LOL. I had no intentions of misleading anyone or giving false witness if it was taken the wrong way.
Perl v5.22.2 (currently in RC1) fixes several bugs present in v5.22.1 (some relevant to security).
If it's not too late in the Slackware dev cycle, and if v5.22.2 final is released soon, might it be possible to upgrade Slackware's perl to v5.22.2, please?
Calls to the placeholder &PL_sv_yes used internally when an import() or unimport() method isn't found now correctly handle scalar context.
In some cases, failing to parse a here-doc would attempt to use freed memory.
If a here-doc was found while parsing another operator, the parser had already read end of file, and the here-doc was not terminated, perl could produce an assertion or a segmentation fault.
Perl 5.22.0 added support for the C99 hexadecimal floating point notation, but sometimes misparsed hex floats.
Certain regex patterns involving a complemented posix class in an inverted bracketed character class, and matching something else optionally would improperly fail to match.
Fixed an issue with pack() where < pack "H" could read past the source when given a non-utf8 source and a utf8 target.
Fixed some cases where perl would abort due to a segmentation fault, or a C-level assert.
Perl now correctly raises an error when trying to compile patterns with unterminated character classes while there are trailing backslashes.
NOTHING regops and EXACTFU_SS regops in make_trie() are now handled properly.
As an optimization (introduced in Perl 5.20.0), uc(), lc(), ucfirst() and lcfirst() sometimes modify their argument in-place rather than returning a modified copy. The criteria for this optimization has been made stricter to avoid these functions accidentally modifying in-place when they should not, which has been happening in some cases, e.g. in List::Util.
I've just gotten myself a bluetooth dongle, and in trying to understand the bluez ecosystem I discovered on line 40 of rc.bluetooth:
Code:
/usr/bin/rfcomm -f /etc/bluetooth/rfcomm.conf bind all > /dev/null 2>&1 || :
This does not work, since the undocumented -f switch has been removed after the 3.x bluez series. And a quick look at the source reveals that neither "bind all" is supported anymore. I'm not sure what the right thing to do is wrt the rfcomm command and rfcomm.conf file. Hopefully someone who knows more about bluetooth can figure it out..
I'd like to encourage Intel graphics owners to test the driver version with git head f2a4645 and report the results here. f2a4645 has resolved important issue with SNA and seem to be a good candidate for entering -current. It is also many commits ahead of d167280 and brings new hardware support and features "improvements" (pun intended).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.