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.
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.
...
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.
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.
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
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).
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"
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.