On Sun, Feb 10, 2019 at 04:22:44PM -0600, Richard Owlett wrote:
> On 02/10/2019 03:42 PM, to...@tuxteam.de wrote:
> >On Sun, Feb 10, 2019 at 02:57:22PM -0600, Richard Owlett wrote:
> >
> >[...]
> >
> >>Unless someone can point to a single location to modify that:
> >> 1. modify existing user(s)
>
On Sun, Feb 10, 2019 at 09:07:13PM -0600, David Wright wrote:
> On Fri 08 Feb 2019 at 10:08:49 (-0500), Dan Ritter wrote:
> > Richard Owlett wrote:
> > > By my problem definition, any thing in /home/user is not relevant as I
> > > explicitly want something that affects all current and future users
On 2019-02-11 05:46, Jude DaShiell wrote:
/etc/shutdown.allow needs to have your user's name in it for that user
to be able to shut the system down without using su or sudo.
/etc/shutdown.deny can have user names in it too, and those will not be
allowed to shut the system down.
I tried that on
Hi there,
Ups is connected via usb:
Bus 003 Device 002: ID 051d:0002 American Power Conversion
Uninterruptible Power Supply
Recently I noticed that nut stopped to recognize it (probably after some
update):
# /lib/nut/usbhid-ups -a APC
Network UPS Tools - Generic HID driver 0.41 (2.7.4)
USB
On Monday, February 11, 2019 03:57:14 AM to...@tuxteam.de wrote:
> On Sun, Feb 10, 2019 at 09:07:13PM -0600, David Wright wrote:
> > On Fri 08 Feb 2019 at 10:08:49 (-0500), Dan Ritter wrote:
> > > Richard Owlett wrote:
> > > > By my problem definition, any thing in /home/user is not relevant as
> >
On 11.02.2019 16:20, Grzesiek Sójka wrote:
> Hi there,
>
> Ups is connected via usb:
>
> Bus 003 Device 002: ID 051d:0002 American Power Conversion
> Uninterruptible Power Supply
>
> Recently I noticed that nut stopped to recognize it (probably after
> some update):
>
> # /lib/nut/usbhid-ups -a APC
On 2019-02-11, rhkra...@gmail.com wrote:
> On Monday, February 11, 2019 03:57:14 AM to...@tuxteam.de wrote:
>> On Sun, Feb 10, 2019 at 09:07:13PM -0600, David Wright wrote:
>> > On Fri 08 Feb 2019 at 10:08:49 (-0500), Dan Ritter wrote:
>> > > Richard Owlett wrote:
>> > > > By my problem definition
On Mon 11 Feb 2019 at 09:53:39 (+0100), to...@tuxteam.de wrote:
> On Sun, Feb 10, 2019 at 04:22:44PM -0600, Richard Owlett wrote:
> > On 02/10/2019 03:42 PM, to...@tuxteam.de wrote:
> > >On Sun, Feb 10, 2019 at 02:57:22PM -0600, Richard Owlett wrote:
> > >
> > >[...]
> > >
> > >>Unless someone can
Hello,
Hope you're having a great day!
I just wanted to know if you're looking to acquire Microsoft Power BI Users
Contact List for your marketing efforts?
Other BI users like: Sisense, Dundas BI, IBM Cognos Analytics, SAP Business
Objects, Tableau, Qlik Sense, QlikView, SAP Crystal Repo
C.T.F. Jansen wrote:
> Buying the said Asus X541U notebook, Microsoft Windows does not show errors
> but other people complain of spotty performance from the Realtek
> Wifi/Bluetooth unit in it.
>
> One could also replace the Realtek Wifi/Bluetooth unit with one that works
> properly.
> Is there
On Sun, Feb 10, 2019 at 07:28:02PM -0500, Lee wrote:
> Which is semi-interesting I guess, but you're the one that wanted a
> single location to add $PATH elements for all current & future users -
> yes? The interesting answer would be if adding
> export PATH=$PATH:/foo
> to /etc/bash.bashrc is wha
On Sat 09 Feb 2019 at 07:03:50 (-0500), Gene Heskett wrote:
> On Saturday 09 February 2019 03:18:43 Paul Sutton wrote:
> > On 09/02/2019 08:11, Brad Rogers wrote:
> > > On Fri, 8 Feb 2019 21:38:30 -0600
> > > David Wright wrote:
> > >
> > > Hello David,
> > >
> > >> I can't understand why modern G
On Monday, February 11, 2019 08:07:24 AM Curt wrote:
> On 2019-02-11, rhkra...@gmail.com wrote:
> > There is a directory /etc/sket (with all hidden files thus you need
> > something like ls /etc/skel/.* to get a listing).
>
> I believe you need something like 'ls -a /etc/skel/', in fact, to see t
On 2019-02-11, rhkra...@gmail.com wrote:
> On Monday, February 11, 2019 08:07:24 AM Curt wrote:
>> On 2019-02-11, rhkra...@gmail.com wrote:
>> > There is a directory /etc/sket (with all hidden files thus you need
>> > something like ls /etc/skel/.* to get a listing).
>>
>> I believe you need som
On Mon, Feb 11, 2019 at 05:26:34PM -, Curt wrote:
> I follow your logic. Give me everything in /etc/skel/ beginning with a dot.
> Which works. But apparently a dot is also something else. Like a directory.
>
> curty@einstein:~$ ls /etc/skel/.*
> /etc/skel/.bash_logout /etc/skel/.bashrc /etc/
On 2019-02-11, Greg Wooledge wrote:
> On Mon, Feb 11, 2019 at 05:26:34PM -, Curt wrote:
>> I follow your logic. Give me everything in /etc/skel/ beginning with a dot.
>> Which works. But apparently a dot is also something else. Like a directory.
>>
>> curty@einstein:~$ ls /etc/skel/.*
>> /etc
Hello folks:
When I hit the networking section on a fresh install of 9.6 (full
install .ISO, not live),
I'm told to insert a USB of these non-free bits.
iwlwifi-8625-26.ucode, iwlwifi-8625-25.ucode, iwlwifi-8625-24.ucode,
iwlwifi-8625-23.ucode, iwlwifi-8625-22.ucode
The Problem is -
M.W.C., on 2019-02-11:
> I use LXDE and now I just found out that I cannot shut down from LXDE,
> "Logout - Shutdown"
>
> It gives the error saying "GDBUS Error System Error ENXIO No such drive
> or address"
>
> I tried with XFCE but still it won't shutdown, it just logs out instead.
Good Day,
I
On Mon 11 Feb 2019 at 13:33:39 -0500, deb wrote:
[...]
> * wouldn't it be useful for the installer to Also say what exact hardware it
> is, that is requiring various bits & pieces?
As far as I can see, you haven't given which hardware you are using either.
--
Brian.
Good Day,
Usually this shouldn't be an issue, but due to the nature of
the recent vulnerability in the package installer APT, any
Debian ISO up to 9.6 should be trashed and replaced by 9.7 or
greater.
See https://www.debian.org/security/2019/dsa-4371
and https://www.debian.org/News/2019/20190123
On 2/11/19 8:42 PM, Étienne Mollier wrote:
> I believe I found those firmware images in the package
> firmware-misc-nonfree. You can install it using:
>
> $ sudo apt install firmware-misc-nonfree
Whoopsie, one should read "firmware-iwlwifi".
Anyway, the iwlwifi-8625-22.ucode alone should d
On Mon 11 Feb 2019 at 17:48:23 (-), Curt wrote:
> On 2019-02-11, Greg Wooledge wrote:
> > On Mon, Feb 11, 2019 at 05:26:34PM -, Curt wrote:
> >> I follow your logic. Give me everything in /etc/skel/ beginning with a dot.
> >> Which works. But apparently a dot is also something else. Like a
On Mon 11 Feb 2019 at 13:33:39 (-0500), deb wrote:
>
> Hello folks:
>
> When I hit the networking section on a fresh install of 9.6 (full
> install .ISO, not live),
>
> I'm told to insert a USB of these non-free bits.
>
> iwlwifi-8625-26.ucode, iwlwifi-8625-25.ucode,
> iwlwifi-8625-24.ucode,
On Mon 11 Feb 2019 at 20:42:10 +0100, Étienne Mollier wrote:
> I believe I found those firmware images in the package
> firmware-misc-nonfree. You can install it using:
I believe you have not.
https://packages.debian.org/sid/all/firmware-misc-nonfree/filelist
--
Brian.
On Mon 11 Feb 2019 at 14:01:06 -0600, David Wright wrote:
> Are you sure about 8625, rather than 8265?
Well-spotted.
https://packages.debian.org/stretch/firmware-iwlwifi
--
Brian.
the last time I had such a problem (Buster net install using wifi) I
bookmarked this
https://wiki.debian.org/Firmware#Firmware_during_the_installation
I believe restarting the installer (from USB) with a second USB inserted
with the firmware solved it... needed packages were found and used.
s
Hi Paul,
> Updated from Stretch to Buster (non-free) the other day all went fine, just
> undertaken
>
> apt update && apt upgrade
>
> today and all seem to go fine, The process seems to be pretty painless for
> the most part.
I do hope you did
apt dist-upgrade
too. ;-)
Bonno Bloksma
Good evening *,
I have a ThinkPad T400 with Docking Station and whenever I have a power
failer, the ThinkPad crash... I have Stretch with sysv-init running.
However, I can hard reset the ThinkPad and thath it is.
Today I got an unexpected result AFTER A HARD REBOOT.
The sound stoped...
If I ru
Thanks ~everyone:
Do I gather correctly that Brian is the resident, sarcastic,
cranky-pants herein?
I stopped reading his replies to folks.
anyways:
> A suggestion, especially when installing on unfamiliar hardware, is
to download the firmware archive for your platform and unpack it i
Hello Michelle.
Just an obvious question -- do you have any way to ensure that the
actual speaker hardware was not fried in the hardware crash?
Are you getting ANY sound from the speakers?
On 2/11/2019 4:37 PM, Michelle Konzack wrote:
Good evening *,
I have a ThinkPad T400 with Docking Sta
deb, on 2019-02-11 :
> Do I gather correctly that Brian is the resident, sarcastic,
> cranky-pants herein?
>
> I stopped reading his replies to folks.
Well, I prefer to make no assumptions about people just by
looking on the content of two emails. After all the first
intervention from Brian has m
On Mon 11 Feb 2019 at 17:46:19 -0500, deb wrote:
> Do I gather correctly that Brian is the resident, sarcastic, cranky-pants
> herein?
Flatterer.
--
Brian.
On Mon 11 Feb 2019 at 17:46:19 (-0500), deb wrote:
> [ Peter wrote: ]
> > A suggestion, especially when installing on unfamiliar hardware, is
> to download the firmware archive for your platform and unpack it into
> a directory named firmware
>
> I hear you on this @Peter^
>
> I guess I'm kinda w
Tom Bachreier, on 2019-02-11:
> With the migration of man-db 2.8.5-1 into testing about a month ago I
> get bothered once a day with a lot of useless lines in syslog:
> > Feb 10 00:00:51 osprey mandb[3543]: Purging old database entries in
> > /usr/share/man...
> > Feb 10 00:00:51 osprey mandb[3543
34 matches
Mail list logo
