Next version of Slackware?

ReaperX7 · 03-19-2015, 03:33 AM

Yes, but cute-bartender-40d.24.36-x86_64-1.txz has a better output in interoperability with libjackdaniels, libcola, libjosecuervo, libgrenadine, and libbeer, and is able to function as a dynamic interpreter for libbacardi and libbeefeater which have some incompatibilities with other barlibs from time to time. We have noticed the output of the mixed-drink binary is cleaner and the instances of error:hangover in drinks.log are fewer, plus the new cute-bartender package is able to output instance::adiosmotherfucker, instance::jackncoke, instance::longislandiceatea, and instance::happiness has increased dramatically. Plus it works better in the new bar-shell system quite high stability.

This one didn't have any injection patches. This version was created as such. Pure vanilla code baby.

bartgymnast · 03-19-2015, 06:32 AM

my cute-bartender files where overwritten by a package called: pretty-wife-1.0-x86_64-1.txz a few years ago

allend · 03-19-2015, 07:09 AM

Congratulations on your successful uptake of pretty-wife-1.0-x86_64-1.txz! The benefits are great, although there is potential for spawning of child processes, that can be resource hungry with significant loss of system idle time.
Also, some users who have experienced failure with pretty-wife-1.0-x86_64-1.txz have reported a rocky upgrade path to pretty-wife-2.0-x86_64-1.txz and beyond.

ReaperX7 · 03-19-2015, 10:25 AM

Quote:

Originally Posted by allend

Congratulations on your successful uptake of pretty-wife-1.0-x86_64-1.txz! The benefits are great, although there is potential for spawning of child processes, that can be resource hungry with significant loss of system idle time.
Also, some users who have experienced failure with pretty-wife-1.0-x86_64-1.txz have reported a rocky upgrade path to pretty-wife-2.0-x86_64-1.txz and beyond.

About squirted orange juice out my nose allend... LOL

Just be advised pretty-wife-1.0-x86_64-1.txz will seek to gain control of life-1.0-noarch-1.txz as PID1. Just be aware to scan pretty-wife-1.0 for mother-in-law-1.0 also in the package which could have malware like behaviors.

WiseDraco · 03-20-2015, 06:05 AM

where there be a thread "must be included in next slackware version" ?
Cannot find.
Strange, slackware installation does not include acpi util, not iotop, nor also very useful ncdu...

Didier Spaier · 03-20-2015, 06:34 AM

Quote:

Originally Posted by WiseDraco

Strange, slackware installation does not include acpi util, not iotop, nor also very useful ncdu...

All these are available @ http://slackbuilds.org.

Alien Bob · 03-20-2015, 07:22 AM

Quote:

Originally Posted by WiseDraco

where there be a thread "must be included in next slackware version" ?
Cannot find.

Here: http://www.linuxquestions.org/questi...ad-4175526322/

rmarquet · 03-20-2015, 02:06 PM

You guys are cracking me up.

The new server hardware is up and running, just have to get some stuff working, as always. Thanks for the help and laughs.

ReaperX7 · 03-20-2015, 05:36 PM

Having fun is part of the Slackware way. If we didn't joke around, it just wouldn't be LQ or Slackware now would it? Laughter fills the soul with joy and light, just like Slackware lights the way of learning with joy.

rmarquet · 03-20-2015, 08:24 PM

This isn't Slackware related but I figure asking a bunch of Slackware people is most likely to work...

I use an old intrusion detection program called fcheck that appears to be unsupported. It's a perl program, but I'm not a perl programmer. Unfortunately I'm getting this warning:

Quote:

Use of assignment to $[ is deprecated at /usr/local/sbin/fcheck line 638.

What did that assignment do?

Here's the top of the function that does it; the offending code is in the second line of code within the function:

Quote:

###############################################################################
# $x=&ctime($y); #
# This support routine will return the converted time to human readable format#
# Basically, I'm trying to get away from any functions that may not be in any #
# very minimal PERL distribution. #
###############################################################################
sub ctime
{
local($time) = @_;
local($[) = 0;
local($sec, $min, $hour, $mday, $mon, $year, $wday);

@WeekDay = ('Sun','Mon','Tue','Wed','Thu','Fri','Sat');
@Month = ('Jan','Feb','Mar','Apr','May','Jun',
'Jul','Aug','Sep','Oct','Nov','Dec');

($sec, $min, $hour, $mday, $mon, $year, $wday) = ($TZ) ? gmtime($time) : localtime($time);

Thanks! I'm sure I could figure it out if I spent the time on it, but someone who is fluent in perl can probably look at it and tell me in a few seconds...

ReaperX7 · 03-20-2015, 09:46 PM

Deprecated means it's using an older function command, path, or library that is still around, but isn't exactly optimal to use. It doesn't mean it still isn't useful on some level however.

rmarquet · 03-21-2015, 08:09 AM

Quote:

Originally Posted by ReaperX7

Deprecated means it's using an older function command, path, or library that is still around, but isn't exactly optimal to use. It doesn't mean it still isn't useful on some level however.

I know. My question is, as someone who doesn't know perl, what was that line of code doing so that I can rewrite it to avoid the warning message? I've programmed in a number of languages, but I haven't seen a construct like that before. I know I can surpress warning too, but I'd rather fix the code.

Thanks.

55020 · 03-21-2015, 09:33 AM

I know no Perl whatsoever, but I can google. Add this as the second line of /usr/local/sbin/fcheck

Code:

no warnings 'deprecated';

References: http://perldoc.perl.org/perl5120delt...arn-by-default ; http://perldoc.perl.org/perldiag.html ; http://perldoc.perl.org/perlvar.html#%24[

(As a learning point, btw, threadjacking is a suboptimal way of getting answers (even when it's your own thread that you're threadjacking). New question => new thread)

Alien Bob · 03-21-2015, 09:51 AM

Quote:

Originally Posted by rmarquet

This isn't Slackware related but I figure asking a bunch of Slackware people is most likely to work...

I'm sure I could figure it out if I spent the time on it, but someone who is fluent in perl can probably look at it and tell me in a few seconds...

Code:

$[
The index of the first element in an array, and of the first character in a substring. Default is 0, but you could theoretically set it to 1 to make Perl behave more like awk (or Fortran) when subscripting and when evaluating the index() and substr() functions. (Mnemonic: [ begins subscripts.)
As of release 5 of Perl, assignment to $[ is treated as a compiler directive, and cannot influence the behavior of any other file. Its use is highly discouraged.

From the looks of it, that whole line "local($[) = 0;" could be omitted because the default is already zero.

GazL · 03-21-2015, 10:58 AM

I believe $[ is one of those things that you used to set just to be sure of no nasty surprises, much like setting IFS in shell-scripts. $[ used to have global scope within the perl file so you couldn't rely on it being set to a default value on entry to your routine. Later they changed it to local scope, and then I guess just decided it better to deprecate its use completely (presumably because it confused people).

I always liked the pascal approach of doing arrays, where you define each array with an explicit index range such as [1..10] rather than having a fixed 0 or 1 base for all arrays. Seems the $[ perl feature was something in between the two.