Re: Where'd lsb-compat go?

From	Kent West <westk@acu.edu>
Newsgroups	linux.debian.user
Subject	Re: Where'd lsb-compat go?
Date	2019-07-15 23:00 +0200
Message-ID	<ykgeJ-7C2-3@gated-at.bofh.it> (permalink)
References	(2 earlier) <yka9j-3XI-1@gated-at.bofh.it> <ykeZj-6UP-3@gated-at.bofh.it> <ykf8Z-6Yy-3@gated-at.bofh.it> <ykfsn-7l6-7@gated-at.bofh.it> <ykfC1-7on-5@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On 7/15/19 3:15 PM, Greg Wooledge wrote:
> On Mon, Jul 15, 2019 at 03:09:28PM -0500, Kent West wrote:
>> Well, in this particular case, the Quest SMA is a Systems Management
>> Appliance, which provides management and data-collection capabilities of
>> devices on a network. When a sysadmin wants to use the SMA to find out about
>> PCs on the network, particularly Linux PCs, particularly Debian PCs,
>> particularly Debian PCs of a certain version, that SMA itself must first
>> know that information. That's part of what the SMA does; it goes and and
>> collects information about the devices.
> And yet it can't even figure out how to see the version number of a
> Debian GNU/Linux system.  Are you sure you want to continue using this
> product?  It doesn't sound very capable.
>

- Wasn't my choice.

- Every product has short-comings (and many support far fewer platforms; 
I'm thankful Quest works with Linux at all).

- They plainly state that they support Ubuntu 18.04, but not Debian. It 
worked fine on Debian until Debian changed with Buster. Had I stuck with 
Stretch, there would have been no problem. When they support the next 
version of Ubuntu, there will probably again be no problem. As it is, it 
still works; it just took some effort from me to get their product to 
work with an up-front-stated unsupported Debian.


-- 

Kent

Thread

Where'd lsb-compat go? Kent West <westk@acu.edu> - 2019-07-11 20:50 +0200
  Re: Where'd lsb-compat go? Dominic Knight <dominicknight@gmx.com> - 2019-07-12 05:10 +0200
    Re: Where'd lsb-compat go? Kent West <westk@acu.edu> - 2019-07-12 16:50 +0200
  Re: Where'd lsb-compat go? Tixy <tixy@yxit.co.uk> - 2019-07-12 10:10 +0200
  Re: Where'd lsb-compat go? Kent West <westk@acu.edu> - 2019-07-15 16:20 +0200
    Re: Where'd lsb-compat go? Michael Stone <mstone@debian.org> - 2019-07-15 16:30 +0200
      Re: Where'd lsb-compat go? Kent West <westk@acu.edu> - 2019-07-15 21:40 +0200
        Re: Where'd lsb-compat go? Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-15 21:40 +0200
        Re: Where'd lsb-compat go? Stefan Monnier <monnier@iro.umontreal.ca> - 2019-07-15 21:50 +0200
          Re: Where'd lsb-compat go? Kent West <westk@acu.edu> - 2019-07-15 22:10 +0200
            Re: Where'd lsb-compat go? Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-15 22:20 +0200
              Re: Where'd lsb-compat go? Nicolas George <george@nsup.org> - 2019-07-15 23:00 +0200
                Re: Where'd lsb-compat go? Kent West <westk@acu.edu> - 2019-07-15 23:20 +0200
              Re: Where'd lsb-compat go? Kent West <westk@acu.edu> - 2019-07-15 23:00 +0200
              Re: Where'd lsb-compat go? Gene Heskett <gheskett@shentel.net> - 2019-07-15 23:20 +0200
            Re: Where'd lsb-compat go? Gene Heskett <gheskett@shentel.net> - 2019-07-15 23:00 +0200
          Re: Where'd lsb-compat go? Andy Smith <andy@strugglers.net> - 2019-07-16 14:30 +0200
    Re: Where'd lsb-compat go? Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-16 08:50 +0200
      Re: Where'd lsb-compat go? Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-16 14:50 +0200

csiph-web