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.
1. I am agree with Lockywolf why is not have nss-mdns?
2. How about to fix cups-filters for the latest changes?
open /source/ap/cups-filters/cups-filters.SlackBuild and find
Code:
--with-browseremoteprotocols=cups \
replace with
Code:
--with-browseremoteprotocols="dnssd cups" \
or remove this line coz
Quote:
--with-browseremoteprotocols=value
Set which protocols to listen for in cups-browsed
(default: dnssd cups)
+
Code:
sed -i 's|BrowseRemoteProtocols cups|BrowseRemoteProtocols dnssd cups|' /.../etc/cups/cups-browsed.conf
# I am not sure about this line coz
# Only CUPS is actually supported, as DNSSD is done by CUPS itself (we ignore
# DNSSD in this directive).
# probably here is must to be only BrowseLocalProtocols cups or # BrowseLocalProtocols none by default
sed -i 's|# BrowseLocalProtocols none|BrowseLocalProtocols dnssd cups|' /.../etc/cups/cups-browsed.conf
sed -i 's|# BrowseProtocols none|BrowseProtocols dnssd cups|' /.../etc/cups/cups-browsed.conf
and probably for cups config
Code:
sed -i 's|Browsing Yes|Browsing On|' /.../etc/cups/cupsd.conf
sed -i 's|BrowseLocalProtocols dnssd|BrowseLocalProtocols dnssd cups|' /.../etc/cups/cupsd.conf
Thanks.
Last edited by TurboBlaze; 02-23-2024 at 04:25 AM.
I am a bit confused with the most recent -current.
Avahi was added, but not nss-mdns.
What is the use for avahi, if not for resolving .local domain?
Maybe I am missing something?
Code:
nss-mdns provides client functionality only, which means
that you have to run a mDNS responder daemon seperately
from nss-mdns if you want to register the local host name
via mDNS. I recommend Avahi.
nss-mdns provides client functionality only, which means
that you have to run a mDNS responder daemon seperately
from nss-mdns if you want to register the local host name
via mDNS. I recommend Avahi.
nss-mdns provides client functionality only, which means
that you have to run a mDNS responder daemon seperately
from nss-mdns if you want to register the local host name
via mDNS. I recommend Avahi.
By default nss-mdns tries to contact a running avahi-daemon for
resolving host names and addresses and making use of its
superior record cacheing.
And also
Code:
Please note that due to security reasons from this release
on the minimal mDNS stack included in nss-mdns
(dubbed "legacy") is no longer built by default.
Thus, nss-mdns will not work unless Avahi is running!
That makes Avahi essentially a hard dependency of nss-mdns.
nss-mdns is not a replacement for avahi but a bridge between avahi and glibc name resolver, and a very useful one.
It kind of feels like pam at this point. Is there a distro without avahi? (There was something I needed avahi for, but didn't want to build it myself because it seemed like a total pain in the ass.)
--- run-parts.8.orig 2009-05-30 01:25:07.000000000 +0000
+++ run-parts.8 2024-02-23 17:04:57.595702859 +0000
@@ -7,7 +7,7 @@
.ie \\n(.$=0:((0\\$1)*2u>(\\n(.lu-\\n(.iu)) .TP
.el .TP "\\$1"
..
-.TH RUN-PARTS 8 "14 Apr 2002" "Slackware Version 8.1.0
+.TH RUN-PARTS 8 "23 Feb 2024" "Slackware Version 15.0
.SH NAME
run-parts \- run scripts found in a directory
.SH SYNOPSIS
@@ -27,7 +27,7 @@
.B run-parts
automatically skips files with certain suffixes that are generally associated
with backup or extra files. Any file that ends in one of these will be silently
-ignored: ~ ^ , .bak .new .rpmsave .rpmorig .rpmnew .swp
+ignored: ~ ^ , .bak .new .orig .rpmsave .rpmorig .rpmnew .swp
.SH AUTHOR
Patrick J. Volkerding <volkerdi@slackware.com>, with ideas borrowed from the
Red Hat and Debian versions of this utility.
It kind of feels like pam at this point. Is there a distro without avahi? (There was something I needed avahi for, but didn't want to build it myself because it seemed like a total pain in the ass.)
There are devices (I'm looking at you, Linksys wifi APs), which do not work without a .local hostname.
That is, their internal net web-configuration interfaces listen on ServerName linksys-0123.local, and don't respond to bare IP address requests.
Yes, you "can" add an IP of those access points to /etc/hosts, if you know them, but maintaining overly long /etc/hosts is a pain too.
I pesonally never had problems with avahi, in the sense that I don't really notice it beyond .local domains resolving, having avahi and nss-mdns from SBo for years. I don't think it ever broke any of my scripts.
--- run-parts.8.orig 2009-05-30 01:25:07.000000000 +0000
+++ run-parts.8 2024-02-23 17:04:57.595702859 +0000
@@ -7,7 +7,7 @@
.ie \\n(.$=0:((0\\$1)*2u>(\\n(.lu-\\n(.iu)) .TP
.el .TP "\\$1"
..
-.TH RUN-PARTS 8 "14 Apr 2002" "Slackware Version 8.1.0
+.TH RUN-PARTS 8 "23 Feb 2024" "Slackware Version 15.0
.SH NAME
run-parts \- run scripts found in a directory
.SH SYNOPSIS
@@ -27,7 +27,7 @@
.B run-parts
automatically skips files with certain suffixes that are generally associated
with backup or extra files. Any file that ends in one of these will be silently
-ignored: ~ ^ , .bak .new .rpmsave .rpmorig .rpmnew .swp
+ignored: ~ ^ , .bak .new .orig .rpmsave .rpmorig .rpmnew .swp
.SH AUTHOR
Patrick J. Volkerding <volkerdi@slackware.com>, with ideas borrowed from the
Red Hat and Debian versions of this utility.
I'll have to be more careful what I ask for
If you're going to change this again, might as well add '#' to the list in order to exclude emacs autosave files (#foo#)
Distribution: Slackware64 {15.0,-current}, FreeBSD, stuff on QEMU
Posts: 460
Rep:
man pages
Two semi-related items about man pages:
Somewhere between man-db-2.9.4 and man-db-2.12.0, whatis started picking up the ksh93 man page for "man sh" and "whatis sh." Since bash is the default sh, would it be appropriate to create a sh.1.gz symlink, or maybe keep the POSIX sh.1p page from man-pages-posix-2017-a?
man-pages.SlackBuild still refers to man-pages-posix-2013-a, so the POSIX pthread pages are no longer installed.
Last edited by pghvlaans; 02-24-2024 at 05:48 AM.
Reason: typo
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
