I have an [old printer](http://support.lexmark.com/index?page=product&locale=en&productCode=1100_COLOR_JETPRINTER&segment=SUPPORT&userlocale=EN_UK#1) which requires the LSB package in order to install the OpenPrinting driver in Debian: [Preparation of LSB-compliant distributions](https://wiki.linuxfoundation.org/openprinting/database/driverpackages) However, the current version of Debian no longer support LSB: [Debian discontinued LSB support in 2015](https://wiki.debian.org/LSB) Therefore, I'm not able to install the OpenPrinting driver of this printer on Debian Buster. Any idea how to solve that? *** # Follow-up Following some advices, I tried to install the LSB package from Ubuntu. So, I downloaded the LSB package from Ubuntu 19.04 available at https://pkgs.org/ Then I tried to install via the following command: dpkg -i lsb_10.2019031300ubuntu1_all.deb However, some dependencies were missing: dpkg: dependency problems prevent configuration of lsb: lsb depends on lsb-core (>= 10.2019031300ubuntu1); however: Package lsb-core is not installed. lsb depends on lsb-printing (>= 10.2019031300ubuntu1); however: Package lsb-printing is not installed. Then I've downloaded the lsb-core package and tried to install it: dpkg -i lsb-core_10.2019031300ubuntu1_amd64.deb Again, dependencies issues: dpkg: dependency problems prevent configuration of lsb-core: lsb-core depends on libncurses5; however: Package libncurses5 is not installed. lsb-core depends on lsb-invalid-mta (>= 10.2019031300ubuntu1) however: Package lsb-invalid-mta is not installed. lsb-core depends on at; however: Package at is not installed. lsb-core depends on binutils; however: Package binutils is not installed. lsb-core depends on ed; however: Package ed is not installed. lsb-core depends on libc6-dev | libc-dev; however:Package libc6-dev is not installed. Package libc-dev is not installed. lsb-core depends on cups-bsd | lpr; however: Package cups-bsd is not installed. Package lpr is not installed. lsb-core depends on m4; however: Package m4 is not installed. lsb-core depends on mailx | mailutils; however: Package mailx is not installed. Package mailutils is not installed. lsb-core depends on make; however: Package make is not installed. lsb-core depends on patch; however: Package patch is not installed. lsb-core depends on pax; however: Package pax is not installed. lsb-core depends on rsync; however: Package rsync is not installed. lsb-core depends on alien (>= 8.36); however: Package alien is not installed. lsb-core depends on lsb-security (>= 10.2019031300ubuntu1); however: Package lsb-security is not installed. lsb-core depends on time; however: Package time is not installed. It seems that this is not the way to go. Any idea?

When I'm trying to run lmgrd it shows the follwing:

lmgrd: cannot execute: required file not found

Searching on the Internet I found out that it requires LSB (linux standard base) package support. But at the same time I found out that Ubuntu 23.04 doesn't support LSB anymore. How am I supposed to run lmgrd now? Is there a way to work this around?

I have an Epson ET-2600 printer at home. I tried configuring it using CUPS, but the printing is very slow and constantly in a very high quality (which results in a lot of ink being wasted). I tried to download the .deb packages from here , but **it requires the lsb package** which I cannot retrieve. I currently have Debian 10 installed. I tried to put in my /etc/apt/sources.list the link for Debian Jessie and running sudo apt install lsb, but it did not work. Any ideas on how I can get a better working open driver or the lsb package to install the official Epson driver? Thanks in advance.

When I boot my Debian system, its startup hangs for approximately 2 minutes on the line: Loading, please wait... [ 5.191043] systemd-fsck: /dev/mmcblk0p2: clean, 234192/873120 files, 2335263/3491328 blocks [ 6.645242] intel_rapl: no valid rapl domains found in package 0 [ 6.643682] systemd-fsck: fsck.fat 3.0.27 (2014-11-12) [ 6.664844] intel_rapl: no valid rapl domains found in package 0 [ 6.660702] systemd-fsck: /dev/mmcblk0p1: 3 files, 33/130812 clusters [ **] A start job is running for LSB: Raise network interf...38s / no limit) Eventually, it gives up on raising the network interface and continues booting. **Question:** How can I change the timeout used in systemctl, so that after 15 seconds it stops trying to raise the network interface? **Additional info:** the source of the problem is the use of a wifi USB dongle on this machine. Sometimes the dongle is there, sometimes it's not. When the dongle is not plugged in, I expect the network interface to not be raised, and I just don't want to wait for too long.

[This question](https://askubuntu.com/questions/795226/how-to-list-all-enabled-services-from-systemctl) asks: "How to list all enabled services from systemctl?" Answers on that page include: systemctl list-unit-files | grep enabled systemctl list-unit-files --state=enabled At least as of systemd version 229 (on Ubuntu 16.04), systemctl list-unit-files will not include "LSB" services that are launched via legacy init scripts. Therefore, the original question seems to remain unanswered: Can systemd display a list of ALL the services (and other unit types) that it will try to start at boot, including legacy services? Consider: $ systemctl list-units | grep LSB | grep grub grub-common.service loaded active exited LSB: Record successful boot for GRUB $ systemctl list-unit-files | grep enabled | grep grub || echo 'nothing found' nothing found $ systemctl is-enabled grub-common grub-common.service is not a native service, redirecting to systemd-sysv-install Executing /lib/systemd/systemd-sysv-install is-enabled grub-common enabled systemctl knows about grub-common, and if you ask explicitly systemctl will tell you it is enabled. So... is there a way to get systemd to display a list of ALL the services it will attempt to run at boot, including legacy scripts?

on Debian, the init script /etc/init.d/umountnfs.sh has default stop in runlevel 0 and 6. # Default-Stop: 0 6 but there is no symlink in /etc/rc0.d/ or /etc/rc6.d/ on my system. I am trying to enable the script in these runlevels, but chkconfig does not create the symlink chkconfig umountnfs.sh on I could create the symlink manually, but I believe the chkconfig script does more than just symlink. I think it also calculates dependencies and modifies the .depend.* files **How can I enable umountnfs.sh script on shutdown ?**

recently I switched from **zorin os** to **deepin 20** for it's outstanding UI and eases of use for daily operations. it's almost OK but if I need some newer packages which are not listed in official deepin repositories, I have to use some community installer scripts that rely on this command to obtain the correct linux LSB version :

-c

the problem is : **the return value is "n/a"** that consequently, breaks down the installation process. how can I fix this ?

Let us say, an application - JDK, which is compiled against certain the linux version - say 4.18, available for the download. How can the same application can be run on different linux version - say 3.10? When there is no ABI compatibility guaranteed by Linux between major releases. ABI compatibility is guaranteed between user program and kernel only when their binaries are generated for the same kernel version as seen from this below picture - If my above understanding is correct about the ABI incompatibility between linux versions, then why don't the application developer mention about the linux version on which the binary was generated on. Just like the hardware architecture - x86, x64, ARM, they mention along with the application, which it is compatible with.

I am creating a startup script for my Ubuntu 14.04.1 LTS server. The script needs to be run after the Rabbit MQ server. The Rabbit MQ startup script says it provides "rabbitmq-server". So I put this string in the "Required-Start" list of my startup script headers (see below). However, after installing my script with update-rc, both the Rabbit MQ script and my script are at the "S20" level, i.e., I don't think the dependency has worked. My script is also not starting correctly, but does start if I run it manually after bootup. Any ideas as to what could be wrong? ### BEGIN INIT INFO # Provides: amqp_receive # Required-Start: $local_fs $network rabbitmq-server # Required-Stop: # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Script to provide start/stop/status of the amqp_receive program ### END INIT INFO lrwxrwxrwx 1 root root 22 Aug 17 00:29 S20amqp-receive -> ../init.d/amqp-receive lrwxrwxrwx 1 root root 25 Aug 13 18:14 S20rabbitmq-server -> ../init.d/rabbitmq-server lrwxrwxrwx 1 root root 15 Apr 16 18:26 S20rsync -> ../init.d/rsync lrwxrwxrwx 1 root root 24 Apr 16 18:26 S20screen-cleanup -> ../init.d/screen-cleanup lrwxrwxrwx 1 root root 23 Apr 16 18:26 S38open-vm-tools -> ../init.d/open-vm-tools lrwxrwxrwx 1 root root 26 Apr 16 18:26 S45landscape-client -> ../init.d/landscape-client lrwxrwxrwx 1 root root 19 Apr 16 18:26 S70dns-clean -> ../init.d/dns-clean lrwxrwxrwx 1 root root 18 Apr 16 18:26 S70pppd-dns -> ../init.d/pppd-dns lrwxrwxrwx 1 root root 21 Apr 16 18:26 S99grub-common -> ../init.d/grub-common lrwxrwxrwx 1 root root 18 Apr 16 18:25 S99ondemand -> ../init.d/ondemand lrwxrwxrwx 1 root root 18 Apr 16 18:25 S99rc.local -> ../init.d/rc.local

i am trying to set up a headless minecraft server using debian. So far everything is working save for hamachi (portforwarding is coming later). I installed the .deb file from https://secure.logmein.com/labs and i get this on install: Traceback (most recent call last): File "/usr/lib/lsb/remove_initd", line 46, in headers = initdutils.scan_initfile(initfile) File "/usr/lib/lsb/initdutils.py", line 79, in scan_initfile inheaders = RFC822Parser(strob=headerlines) File "/usr/lib/lsb/initdutils.py", line 24, in __init__ fileob = StringIO(strob) TypeError: initial_value must be unicode or None, not str however the install completes "successfully". If i type hamachi i get no feedback for 20s, then Hamachi does not seem to be running. Run '/etc/init.d/logmein-hamachi start' to start daemon. starting the service reports no errors, but the above happens again. hamachi --help reports proper output, but any hamachi [command] does not work Having a look at syslog i see: Nov 19 11:53:03 Server avahi-daemon: Registering new address record for 25.29.60.87 on ham0.IPv4. Nov 19 11:53:03 Server avahi-daemon: Withdrawing address record for 25.29.60.87 on ham0. Nov 19 11:53:03 Server avahi-daemon: Withdrawing workstation service for ham0. Nov 19 11:53:03 Server avahi-daemon: Joining mDNS multicast group on interface ham0.IPv4 with address 25.29.60.87. Nov 19 11:53:03 Server avahi-daemon: IP_ADD_MEMBERSHIP failed: No such device Last thing: when i first installed it, hamachi returned something like the expected output. I am vague since this was over 2000 lines of shell ago. Any help will be appreciated

Both POSIX and SUS (Single UNIX Specification) define a line as > A sequence of zero or more non-` characters plus a terminating ` character. Many distributions are more oriented towards LSB than POSIX. LSB includes a lot of POSIX/SUS standards but not all exactly. Must lines also be terminated with a NEWLINE character in regards to LSB v4.1 ?

I was taking a look at the Linux standard base (lsb) and could not find much interesting info on the kernel. Does the LSB specify anything at all about the kernel or kernel interface? Is it kernel agnostic? By interface I mean things like: - where does a bootloader look for the kernel? How does the bootloader load the kernel? - system calls - kernel module API - proc and sys filesystems. As @jofel mentioned, there has been some [discussion](https://wiki.linuxfoundation.org/en/LSB_Kernel_Interfaces) , but it does not seem to be implemented. If it did specifies things like that, then it would be possible to plug in different kernels without problem. Of course, maybe it is too early to thing about those things, since the Linux Kernel dominates LSB systems and sets a de facto standard anyway.

I wrote an LSB init script that can manage multiple instances of my daemon: rcfoo start starts all the instances (which are found in some /etc configuration file), rcfoo stop stops all the instances, rcfoo status displays the status of all instances, and rcfoo reload reloads updates the daemon with a changed configuration. First I wonder how to detect the instances to work on with some foo@.service systemd unit file. AFAIK I must specify all the instances like foo@A, foo@B, and so on. Second my LSB script can report an extended status, meaning it can display whether a service reload is needed (and my reload actually optimizes to only reload the services that need it). How can I make a custom status report? I think a script has to use systemd-notify for custom status messages. Fortunately my final extension to the LSB script, namely manipulating single instances by adding single (like in rcfoo start single A), is supported out-of-the-box with systemd. So my basic question is the first one.

When I install this "Taurus Blazemeter 'bzt'" program with pip, it ends up being installed into ~/.local/bin folder. mkdir ~/bzt && cd ~/bzt sudo apt-get install python default-jre-headless python-tk python-pip python-dev libxml2-dev libxslt-dev zlib1g-dev sudo pip install bzt Does anyone know what use this ~/.local folder is for and why a Python program like this one would install there?

Just installed Linux Mint 18.2 Cinnamon yesterday and am now trying to get Wine installed but everything I do results in this same error. Somehow my codename must not match to Linux Mint Cinnamon and have no idea how to fix this or how to get Wine installed. Running on Kernel 4.14.1-041401-generic. Any help would be great! Thanks! sudo add-apt-repository ppa:wine/wine-builds LSB codename: 'Traceback (most recent call last): File "/usr/bin/lsb_release", line 95, in main() File "/usr/bin/lsb_release", line 59, in main distinfo = lsb_release.get_distro_information() File "/usr/lib/python3/dist-packages/lsb_release.py", line 383, in get_distro_information distinfo = guess_debian_release() File "/usr/lib/python3/dist-packages/lsb_release.py", line 281, in guess_debian_release get_distro_info(distinfo['ID']) File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in get_distro_info RELEASES_ORDER.sort(key=lambda n: float(n)) File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in RELEASES_ORDER.sort(key=lambda n: float(n)) ValueError: could not convert string to float: '14.04 LTS''. Version of base-files: '18.2.1'. Your LSB codename isn't a valid Linux Mint codename.

I'm just curious to know how to best check if a program exists. I've seen solutions with * test * command * hash * type * which * [ Which is the best method, is there a *right* answer? What does the POSIX and LSB specs say about this?

I've got node.js and pm2 installed on a Pi (Raspbian). PM2 was configured to start via pm2 startup and the init scripts it creates. Sometimes when I reboot, shutdown hangs for a few minutes on: A stop job is running for LSB: PM2 init script (... / 5min) Every once in a while1 what I'm assuming is PM2 doesn't shut down properly and hangs for the full 5 minutes. On this system, I know exactly what apps PM2 is managing and I really don't care if they shutdown properly. My question is: How do I reduce the timeout from 5 minutes to, say, 15 seconds or so? Where is this configured? I read on a forum that it was the DefaultTimeoutStopSec key in */etc/systemd/system.conf*, so I tried setting that to "15s" but it had no effect. I tried the same thing in */etc/systemd/user.conf*, too, but no change. The timeout is still set to 5 minutes. --- 1 I actually do know specifically what triggers this, but the details aren't important and the effect is unavoidable.

I am using Debian Stretch with systemd version 231-9. I need to run some shell scripts and non-daemon programs in background even when I logout. I used to make simple init.d scripts with LSB header and then case with start option that simply executes "my_script.sh >> /var/log/my_script.log 2>&1 &" to run my_script.sh in background but now Systemd kills them once I close the terminal no matter what I try: &, nohup, setsid, disown. Can you help me to give a recipe for a proper init.d script that makes any script or non-daemon program run as daemon? Thank you.

I run Debian 8 jessie. I have activated a daemon's debugging facility, which causes the daemon to print debugging info to stdout and/or stderr. How can I persuade start-stop-daemon(8), as invoked by /lib/lsb/init-functions, to redirect the daemon's stdout and stderr to my debugging log file /root/log? It appears that >/root/log 2>&1 is ineffective. I suppose that this makes sense, since start-stop-daemon(8) is not a shell. At any rate, how shall I redirect the daemon's stdout and stderr? [The daemon happens to be exim4(8), but this is not relevant to my question as far as I know. LSB evidently delegates the management of the daemon to Systemd; this could be indirectly relevant for all I know.]

In an application, I need to find out where removable media is mounted. On Ubuntu, this happens in /media/username/ . On Arch, it is /run/media/username/ . On other systems, its just /media/ etc. There seems to be no XDG environment variable for this path. So I wonder, is this standardized anywhere? The FHS only specifies that there must be a /media directory, not how to find out that directory.