LinuxQuestions.org
Review your favorite Linux distribution.
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 12-30-2017, 02:43 PM   #31
USUARIONUEVO
Senior Member
 
Registered: Apr 2015
Posts: 2,296

Rep: Reputation: 916Reputation: 916Reputation: 916Reputation: 916Reputation: 916Reputation: 916Reputation: 916Reputation: 916

what happen arround enchant 2.x branch ?

Here is enchant-2.2.0
https://github.com/AbiWord/enchant/r...t-2.2.0.tar.gz
 
Old 12-30-2017, 03:30 PM   #32
dugan
LQ Guru
 
Registered: Nov 2003
Location: Canada
Distribution: distro hopper
Posts: 11,193

Rep: Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307
Quote:
Originally Posted by arcctgx View Post
How common is it to play media from SMB shares over the network?
I'd imagine that a single Windows media server serving media for an entire household (including the Linux users in that household) is an extremely common setup.

Last edited by dugan; 12-30-2017 at 03:33 PM.
 
Old 12-30-2017, 04:01 PM   #33
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,559

Original Poster
Rep: Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351
Quote:
Originally Posted by USUARIONUEVO View Post
what happen arround enchant 2.x branch ?

Here is enchant-2.2.0
https://github.com/AbiWord/enchant/r...t-2.2.0.tar.gz
Go back and read the first post in this thread.
 
Old 12-30-2017, 04:05 PM   #34
USUARIONUEVO
Senior Member
 
Registered: Apr 2015
Posts: 2,296

Rep: Reputation: 916Reputation: 916Reputation: 916Reputation: 916Reputation: 916Reputation: 916Reputation: 916Reputation: 916
@rworkman

Sorry , i no see is considering arround plasma5 , waiting then.

Thanks !!
 
Old 12-30-2017, 05:19 PM   #35
janhe
Member
 
Registered: Jul 2007
Location: Belgium
Distribution: slackware64 14.2, slackware 13.1
Posts: 371

Rep: Reputation: 54
IPv6 and VLAN, yay!

Quote:
Originally Posted by rworkman View Post
...
TODO items:
* Jakub Jankowski has a seems-to-be-working patch for vlan support in network-scripts; see the "vlan" branch here: https://git.rlworkman.net/slacknetsetup/
* if anyone has some free time and wants a challenge, figure out a way to do ipv6 support such that it integrates nicely and works well; good luck. :-)
I have a slackware box that I have configured as an ipv6 router/tunnel endpoint. I've just finished installing a laptop that is an ipv6 network client.
What do you mean by:
- ipv6 support
- integrates nicely?

The client is configured with one sysctl connfiguration file (and including the ipv6 module in the initrd).
The server (Slackware 13.1) has an extra file in rc.d that sets up the routing (it is called from rc.local):
- open an ipv6 in ipv4 tunnel
- set an ipv6 address on my end of the tunnel
- add an ipv6 address on eth0
- start radvd (router advertisement deamon, from SBo) with its own rc.* script

TLDR: I have a laptop client that already has an ipv6 configuration that IMO integrates nicely, and a server/router whose configuration could be adapted to integrate nicer. I don't know if it would cover all scenarios that you want.

Also, the router has a VLAN that terminates on eth0. I got away with configuring that using only rc.netdevice and rc.inet1.conf. I guess the "vlan" branch will do away with the need for changes in rc.netdevice? I don't see my specific setup in the test scenarios, so if you want I can try if my scenario also works... Scenario is static IP on eth0 and static IP on eth0.4 (eth0 is parent of eth0.4).

I've been away from this forum for a long time, so please forgive (and educate) me if I am missing something obvious.
 
1 members found this post helpful.
Old 12-30-2017, 06:49 PM   #36
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,716
Blog Entries: 3

Rep: Reputation: 483Reputation: 483Reputation: 483Reputation: 483Reputation: 483
The editor Geany in the extra directory.
 
2 members found this post helpful.
Old 12-30-2017, 07:05 PM   #37
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,716
Blog Entries: 3

Rep: Reputation: 483Reputation: 483Reputation: 483Reputation: 483Reputation: 483
Quote:
Originally Posted by arcctgx View Post
I was always wondering about this: why is MPlayer binary dynamically linked with libsmbclient.so? Do we really need this dependency? How common is it to play media from SMB shares over the network?

I don't know if other people consider it a problem. But for me it's inconvenient, because I don't need Samba at all, so I uninstall the package (or don't install it in the first place). But then it's necessary to recompile MPlayer, because it fails to start.

Could this dependency be avoided in MPlayer package shipped with the next Slackware release?
If I remember right we are using pulseaudio and 14.2 and current build the mplayer with pulseaudio. and that would bring in samba client because you need it for many things.
It is actually a server and works with data bases over the internet. I see a huge reason why it should be a must. With or without pulseaudio. Think of Mplayer it does a ton of stuff like rtmpdump. the sambaclient works direct with mariadb. So many cool things you can do with it and the media now.
 
1 members found this post helpful.
Old 12-30-2017, 09:00 PM   #38
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,792

Rep: Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656
I know this has been discussed before, but would we be able to change the default output of removepkg to just display the errors of removing files/folders rather than showing every attempt at removing a file and folder? Right now it is extremely difficult to catch any errors while removing a package unless you look over it later or pipe the output to another command. I would love to only see the errors rather than have them mixed in with the rest of the files that were removed as expected. It would make it much easier to clean up any remnants from removed packages.

Right now, you'd have to hope you have a big enough console buffer and scroll up, pipe the output to grep, or save it to a file to comb through it later.

For those who wish to keep the "verbose" output, a -verbose option could remain.

I did a quick patch of -current's removepkg adding this ability. I enabled support for -v, -verbose, or --verbose. See below or attached.

Code:
diff --git a/removepkg b/removepkg
index 127e518..ae5de0a 100755
--- a/removepkg
+++ b/removepkg
@@ -216,7 +216,9 @@ delete_files() {
      echo "WARNING: $ROOT/$FILE changed after package installation."
     fi
     if [ ! "$WARN" = "true" ]; then
-     echo "  --> Deleting $ROOT/$FILE"
+     if [ "$VERBOSE" = "true" ]; then
+      echo "  --> Deleting $ROOT/$FILE"
+     fi
      preserve_file "$FILE" && rm -f "$ROOT/$FILE"
     else
      echo "  --> $ROOT/$FILE would be deleted"
@@ -235,7 +237,9 @@ delete_links() {
  while read LINK ; do
   if [ -L "$ROOT/$LINK" ]; then
    if [ ! "$WARN" = "true" ]; then
-    echo "  --> Deleting symlink $ROOT/$LINK"
+    if [ "$VERBOSE" = "true" ]; then
+     echo "  --> Deleting symlink $ROOT/$LINK"
+    fi
     rm -f "$ROOT/$LINK"
    else
     echo "  --> $ROOT/$LINK (symlink) would be deleted"
@@ -252,7 +256,9 @@ delete_dirs() {
   if [ -d "$ROOT/$DIR" ]; then
     if [ ! "$WARN" = "true" ]; then
       if [ $(ls -a "$ROOT/$DIR" | wc -l) -eq 2 ]; then
-        echo "  --> Deleting empty directory $ROOT/$DIR"
+        if [ "$VERBOSE" = "true" ]; then
+          echo "  --> Deleting empty directory $ROOT/$DIR"
+        fi
         rmdir "$ROOT/$DIR"
       else
         echo "WARNING: Unique directory $ROOT/$DIR contains new files"
@@ -269,7 +275,9 @@ delete_cats() {
  while read FILE ; do
    if [ -f "$ROOT/$FILE" ]; then
      if [ ! "$WARN" = "true" ]; then
-       echo "  --> Deleting $ROOT/$FILE (fmt man page)"
+       if [ "$VERBOSE" = "true" ]; then
+         echo "  --> Deleting $ROOT/$FILE (fmt man page)"
+       fi
        rm -f $ROOT/$FILE
      else
        echo "  --> $ROOT/$FILE (fmt man page) would be deleted"
@@ -362,6 +370,7 @@ remove_packages() {
      mv $ADM_DIR/scripts/$PKGNAME $ADM_DIR/removed_scripts
     fi
    fi
+   echo "Package $PKGNAME removed."
   else
    echo "No such package: $ADM_DIR/packages/$PKGNAME. Can't remove."
   fi
@@ -369,7 +378,7 @@ remove_packages() {
 }

 if [ "$#" = "0" ]; then
-  echo "Usage: $(basename $0) [-copy] [-keep] [-preserve] [-warn] packagename ..."; exit 1
+  echo "Usage: $(basename $0) [-copy] [-keep] [-preserve] [-verbose] [-warn] packagename ..."; exit 1
 fi

 while : ; do
@@ -377,8 +386,9 @@ while : ; do
   -copy | --copy) WARN=true; PRESERVE=true; shift;;
   -keep | --keep) KEEP=true; shift;;
   -preserve | --preserve) PRESERVE=true; shift;;
+  -verbose | --verbose | -v) VERBOSE=true; shift;;
   -warn | --warn) WARN=true; shift;;
-  -* | --*) echo "Usage: $(basename $0) [-copy] [-keep] [-preserve] [-warn] packagename ..."; exit 1;;
+  -* | --*) echo "Usage: $(basename $0) [-copy] [-keep] [-preserve] [-verbose] [-warn] packagename ..."; exit 1;;
   *) break
  esac
 done
Also, there are two minor grammar mistakes that will show if you enable the preserve option. Patch is below (patch is for the unmodified removepkg) and attached.

Code:
diff --git a/removepkg b/removepkg
index 127e518..4c1e49a 100755
--- a/removepkg
+++ b/removepkg
@@ -386,14 +386,14 @@ done
 if [ "$WARN" = "true" ]; then
  echo "Only warning... not actually removing any files."
  if [ "$PRESERVE" = "true" ]; then
-  echo "Package contents is copied to $PRES_DIR."
+  echo "Package contents are copied to $PRES_DIR."
  fi
  echo "Here's what would be removed (and left behind) if you"
  echo "removed the package(s):"
  echo
 else
  if [ "$PRESERVE" = "true" ]; then
-  echo "Package contents is copied to $PRES_DIR."
+  echo "Package contents are copied to $PRES_DIR."
  fi
 fi
Attached Files
File Type: txt removepkg-verbose.patch.txt (2.7 KB, 98 views)
File Type: txt removepkg-preserve.patch.txt (616 Bytes, 49 views)
 
1 members found this post helpful.
Old 12-30-2017, 09:09 PM   #39
chrisretusn
Senior Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 2,943

Rep: Reputation: 1526Reputation: 1526Reputation: 1526Reputation: 1526Reputation: 1526Reputation: 1526Reputation: 1526Reputation: 1526Reputation: 1526Reputation: 1526Reputation: 1526
Quote:
Originally Posted by bassmadrigal View Post
I know this has been discussed before, but would we be able to change the default output of removepkg to just display the errors of removing files/folders rather than showing every attempt at removing a file and folder? Right now it is extremely difficult to catch any errors while removing a package unless you look over it later or pipe the output to another command. I would love to only see the errors rather than have them mixed in with the rest of the files that were removed as expected. It would make it much easier to clean up any remnants from removed packages.

Right now, you'd have to hope you have a big enough console buffer and scroll up, pipe the output to grep, or save it to a file to comb through it later.

For those who wish to keep the "verbose" output, a -verbose option could remain.

I did a quick patch of -current's removepkg adding this ability. I enabled support for -v, -verbose, or --verbose. See below or attached.
I like this idea. For me it matters not what is default but I do like just a displaying errors option, be it default or as an option. Right now I tee the output of upgradepkg, removepkg and slackpkg (when I remember too at least).
 
Old 12-30-2017, 09:58 PM   #40
orbea
Senior Member
 
Registered: Feb 2015
Distribution: Slackware64-current
Posts: 1,950

Rep: Reputation: Disabled
I don't like that solution. A better way is to use this function which will redirect any errors/warnings to stderr which can then be filtered out or redirected by the user.

Code:
die () {
  ret="$1"; shift
  printf %s\\n "$@" >&2
  case "$ret" in
    : ) return 0 ;;
    * ) exit "$ret" ;;
  esac
}
It can then be used like this.

Code:
die 1 "This is an error message"
die 0 "This is an exit message"
die : "This is a warning message"
Instead of this.
Code:
echo "This is an error message"; exit 1

Last edited by orbea; 12-30-2017 at 09:59 PM.
 
1 members found this post helpful.
Old 12-30-2017, 11:29 PM   #41
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,727

Rep: Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247
Quote:
Originally Posted by Drakeo View Post
The editor Geany in the extra directory.
Just wait for That Ugly Lady to enter in the building.

Because the Kate from Plasma 5 is really, but really good (for developing).

Last edited by Darth Vader; 12-30-2017 at 11:31 PM.
 
Old 12-31-2017, 03:48 AM   #42
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559

Rep: Reputation: 8104Reputation: 8104Reputation: 8104Reputation: 8104Reputation: 8104Reputation: 8104Reputation: 8104Reputation: 8104Reputation: 8104Reputation: 8104Reputation: 8104
Quote:
Originally Posted by Darth Vader View Post
Because the Kate from Plasma 5 is really, but really good (for developing).
Do I hear a grudging approval of Plasma 5?
 
2 members found this post helpful.
Old 12-31-2017, 04:24 AM   #43
gmgf
Senior Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 2,185

Rep: Reputation: 985Reputation: 985Reputation: 985Reputation: 985Reputation: 985Reputation: 985Reputation: 985Reputation: 985
xterm-331:

http://invisible-island.net/xterm/xterm.log.html
ftp://ftp.invisible-island.net/xterm/xterm-331.tgz
 
Old 12-31-2017, 04:25 AM   #44
DarkVision
Member
 
Registered: Jul 2007
Posts: 199

Rep: Reputation: Disabled
I think this was already mentioned: xfce4-pulseaudio-plugin-0.3.4

I applied a short patch to fix auto-detection of *bz2 tarballs.
Quote:
Binary files xfce4-pulseaudio-plugin.orig/xfce4-pulseaudio-plugin-0.2.5.tar.xz and xfce4-pulseaudio-plugin/xfce4-pulseaudio-plugin-0.2.5.tar.xz differ
Binary files xfce4-pulseaudio-plugin.orig/xfce4-pulseaudio-plugin-0.3.4.tar.bz2 and xfce4-pulseaudio-plugin/xfce4-pulseaudio-plugin-0.3.4.tar.bz2 differ
diff -U3 -d -r -N xfce4-pulseaudio-plugin.orig/xfce4-pulseaudio-plugin.SlackBuild xfce4-pulseaudio-plugin/xfce4-pulseaudio-plugin.SlackBuild
--- xfce4-pulseaudio-plugin.orig/xfce4-pulseaudio-plugin.SlackBuild 2017-04-26 22:00:48.000000000 +0200
+++ xfce4-pulseaudio-plugin/xfce4-pulseaudio-plugin.SlackBuild 2017-12-31 11:06:59.674000000 +0100
@@ -58,7 +58,7 @@
mkdir -p $TMP $PKG
cd $TMP
rm -rf $PKGNAM-$VERSION
-tar xvf $CWD/$PKGNAM-$VERSION.tar.xz || exit 1
+tar xvf $CWD/$PKGNAM-$VERSION.tar.?z* || exit 1
cd $PKGNAM-$VERSION || exit 1
chown -R root:root .
find . \
Attached Thumbnails
Click image for larger version

Name:	VirtualBox_slackware64-current_025-vs-035.png
Views:	211
Size:	35.5 KB
ID:	26649  
 
2 members found this post helpful.
Old 12-31-2017, 04:27 AM   #45
shastah
Member
 
Registered: Dec 2017
Posts: 52

Rep: Reputation: Disabled
When kernel 4.14 lands in main tree eventually, I suggest putting a note in ChangeLog.txt/UPGRADE.TXT/CHANGES_AND_HINTS.TXT about the fact that "cciss" driver is now removed in favor of "hpsa" (which supports all boards cciss did and is actually a module alias for cciss now). Disks connected to previously-cciss will still be visible, but if one refers to them as /dev/cciss/... (ie. in /etc/fstab) it will no longer work. Also smartctl/smartd needs some tuning, you need to know which scsi generic device your controller is at (lsscsi -g), and then point smartd there:
Code:
$ lsscsi -g
[0:1:0:0]    disk    HP       LOGICAL VOLUME   7.24  /dev/sda   /dev/sg0 
[0:1:0:1]    disk    HP       LOGICAL VOLUME   7.24  /dev/sdb   /dev/sg1 
[0:3:0:0]    storage HP       P400i            7.24  -          /dev/sg2 
$
$ grep sg2 /etc/smartd.conf 
/dev/sg2 -d cciss,0 -I 190 -a -m root
/dev/sg2 -d cciss,1 -I 190 -a -m root
/dev/sg2 -d cciss,2 -I 190 -a -m root
/dev/sg2 -d cciss,3 -I 190 -a -m root
/dev/sg2 -d cciss,4 -I 190 -a -m root
$
This may affect people running Slackware on HP servers.
 
3 members found this post helpful.
  


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
[SOLVED] Requests for -current (20151216) rworkman Slackware 3441 12-28-2017 03:50 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 11:40 PM.

Main Menu
Advertisement
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
Open Source Consulting | Domain Registration