On Sat, 04 Sep 2021 18:08:18 -0500
"David Palacio" wrote:
> I have compared my previous install nft ruleset and installed
> packages list with the current install and found that firewalld
> wasn't installed in the working system but ufw was. The nft ruleset
> was nearly identical save for the mis
> In /root/.bashrc I use this to give a red prompt including host and
> full path followed by a new line.
I take this idea a bit further, setting a longer prompt and setting
workstation hosts for specific colors for user logins, and then doing a red
prompt for servers.
Part of my ~/.bashr
On Sat 04 Sep 2021 at 23:04:49 (-0300), Dedeco Balaco wrote:
>
> today, i started to upgrade my computer from Debian 9 (Stretch) to
> Debian 11 (Bullseye). I had some trouble finding what i wanted to do, a
> completely internet based upgrade, if possible. In the Debian
> documention, i did not fin
On Fri 03 Sep 2021 at 02:45:03 (+0100), piorunz wrote:
> On 03/09/2021 01:34, David Wright wrote:
> > (I use my own customisations for distinct colours on each host,
> > and inverse colours for root's prompt.)
>
> Can you please share your root prompt invocation? Thanks!
Sure. The colours come fr
Hi,
I have this `phwmon.py`[1] which I use with fluxbox to have a couple
of system monitors at hand. It depends on some python2 packages, so
stopped working some time ago.
I've just made it work, installing manually (# apt-get install packages.deb)
this packages that I've downloaded from Debian Ol
On Sat, Sep 04, 2021 at 11:04:49PM -0300, Dedeco Balaco wrote:
> So, i should to 2 upgrades: one to Debian 10, and one more to Debian 11.
> Fine. And for each one, the steps are:
> But after my first edition to sources.list, apt update fails. I have
> tried apt-get update to, but it also fails for
On Sat, 4 Sep 2021 13:50:19 +0200
"Daniel M." wrote:
> To my understanding, unstable has 91.0.1-1 and experimental has
> 91.0.1-2 as seen in https://tracker.debian.org/pkg/firefox.
>
Or you can download v92.0.b9 from
https://www.mozilla.org/en-US/firefox/developer/
The button links to:
http
I have compared my previous install nft ruleset and installed packages list
with the current install and found that firewalld wasn't installed in the
working system but ufw was. The nft ruleset was nearly identical save for the
missing firewalld rules.
And so after purging firewalld, plasma-fir
Greg Wooledge [2021-09-04 11:35:25] wrote:
> On Sat, Sep 04, 2021 at 04:49:24PM +0200, sp...@caiway.net wrote:
>> # file /sbin/reboot
>> /sbin/reboot: POSIX shell script, ASCII text executable
>
> That's not normal for a bullseye system using systemd for init.
Indeed.
> I'm not sure what you did
On 9/3/21 7:42 PM, Emanuel Berg wrote:
David Christensen wrote:
OK, changed.
Your data format still has issues.
You seem to have got the old file again, check it out again,
because some of those issues have already been
mentioned/fixed:
https://dataswamp.org/~incal/ebchw/cpu.txt
Much
On Sat, 04 Sep 2021 14:46:21 -0400
The Wanderer wrote:
> On 2021-09-04 at 13:20, Greg Wooledge wrote:
>
> > On Sat, Sep 04, 2021 at 12:54:35PM -0400, Stefan Monnier wrote:
> >
> >> Greg Wooledge [2021-09-04 11:35:25] wrote:
> >> > On Sat, Sep 04, 2021 at 04:49:24PM +0200, sp...@caiway.net wrote:
On 2021-09-04 at 13:20, Greg Wooledge wrote:
> On Sat, Sep 04, 2021 at 12:54:35PM -0400, Stefan Monnier wrote:
>
>> Greg Wooledge [2021-09-04 11:35:25] wrote:
>> > On Sat, Sep 04, 2021 at 04:49:24PM +0200, sp...@caiway.net wrote:
>> >> # file /sbin/reboot
>> >> /sbin/reboot: POSIX shell script, AS
On Sat, Sep 04, 2021 at 12:54:35PM -0400, Stefan Monnier wrote:
> Greg Wooledge [2021-09-04 11:35:25] wrote:
> > On Sat, Sep 04, 2021 at 04:49:24PM +0200, sp...@caiway.net wrote:
> >> # file /sbin/reboot
> >> /sbin/reboot: POSIX shell script, ASCII text executable
> >
> > That's not normal for a bu
rhkra...@gmail.com writes:
> Top posting and not quoting anything as I'm coming from a different POV.
>
> If the OP needs firefox 91 (or whatever), there is another option, installing
> the package available from Mozilla as a separate executable.
Sure. I've had an issue with the Debian Buster's
Top posting and not quoting anything as I'm coming from a different POV.
If the OP needs firefox 91 (or whatever), there is another option, installing
the package available from Mozilla as a separate executable.
(Aside: I had to do that (for an earlier version of Firefox) because a website
that
SOLVED
/usr/share/open-infrastructure/container/shutdown.txt
is from package progress-linux-container:
Progress Linux is a Debian derivative distribution focused on system
integration.
This package is a metapackage to be installed in a container
(systemd-nspawn).
# apt remove progress-linux-con
On Sat, Sep 04, 2021 at 04:49:24PM +0200, sp...@caiway.net wrote:
> On Sat, 4 Sep 2021 16:42:45 +0300
> Reco wrote:
>
> > Hi.
> >
> > On Sat, Sep 04, 2021 at 02:40:13PM +0200, sp...@caiway.net wrote:
> > > Suddenly I can no longer reboot or poweroff my up-to-date
> > > bullseye system:
> > >
On Sat, Sep 04, 2021 at 04:49:24PM +0200, sp...@caiway.net wrote:
> On Sat, 4 Sep 2021 16:42:45 +0300
> Reco wrote:
>
> > Hi.
> >
> > On Sat, Sep 04, 2021 at 02:40:13PM +0200, sp...@caiway.net wrote:
> > > Suddenly I can no longer reboot or poweroff my up-to-date
> > > bullseye system:
> > >
On Sat, 4 Sep 2021 16:42:45 +0300
Reco wrote:
> Hi.
> /bin/systemd reboot
>
> And, what about these:
>
> ls -al /sbin/reboot
> file /sbin/reboot
>
> Reco
>
the commands poweroff and reboot are textfiles.
I have no idea
# mcedit /sbin/reboot:
#!/bin/sh
echo "${0}: disabled in systemd
On Sat, 4 Sep 2021 16:42:45 +0300
Reco wrote:
> Hi.
>
> On Sat, Sep 04, 2021 at 02:40:13PM +0200, sp...@caiway.net wrote:
> > Suddenly I can no longer reboot or poweroff my up-to-date
> > bullseye system:
> >
> > # reboot
> > /usr/sbin/reboot: disabled in systemd-nspawn container
>
> Unl
Hi.
On Sat, Sep 04, 2021 at 02:40:13PM +0200, sp...@caiway.net wrote:
> Suddenly I can no longer reboot or poweroff my up-to-date
> bullseye system:
>
> # reboot
> /usr/sbin/reboot: disabled in systemd-nspawn container
Unless I'm mistaken, these messages are not generated by systemd.
In
Marko Randjelovic writes:
> Your control 'Capture',0 is turned on and volume is at maximum, so
> that's fine, but you don't have 'input source' control. On my machine
> output of 'amixer -c0' gives among other controls the following:
>
> Simple mixer control 'Input Source',0
> Capabilities: cen
"Andrew M.A. Cater" writes:
> Very new laptop? Does it need Intel firmware for the soundcard?
> firmware-intel-sound from non-free?
>
> https://packages.debian.org/bullseye/firmware-intel-sound
Thanks for the advice, Andy. I just tried it. But this did not work. I
even rebooted the system afte
> If you mean the line from that page "[2021-08-18] Accepted firefox
> 91.0.1-1 (source) into unstable (Mike Hommey)", that doesn't mean binary
> packages are available as you've noticed.
Okay, that explains it. In fact, i was referring to the versions table
in the left column.
> I don't actually
"Daniel M." writes:
> The debian package tracker (https://tracker.debian.org/pkg/firefox)
> states that version 91.0.1-1 of firefox should be available, but I can
> in no way install it.
If you mean the line from that page "[2021-08-18] Accepted firefox
91.0.1-1 (source) into unstable (Mike Homm
Hi,
Suddenly I can no longer reboot or poweroff my up-to-date
bullseye system:
# reboot
/usr/sbin/reboot: disabled in systemd-nspawn container
Linux container share the kernel of the host system they are running on,
there is no need to reboot just the container.
However, please contact your sys
On Sat, Sep 04, 2021 at 01:50:19PM +0200, Daniel M. wrote:
> To my understanding, unstable has 91.0.1-1 and experimental has
> 91.0.1-2 as seen in https://tracker.debian.org/pkg/firefox.
>
The buildd status page for the firefox package [0] shows that the
builders have the package in state BD-Unins
On Samstag, 4. September 2021 07:50:19 -04 Daniel M. wrote:
> To my understanding, unstable has 91.0.1-1 and experimental has
> 91.0.1-2 as seen in https://tracker.debian.org/pkg/firefox.
Unstable here still with 88.0.1-1 not 91...
same as OP
Have no time neither today nor tomorrow to look into pr
To my understanding, unstable has 91.0.1-1 and experimental has
91.0.1-2 as seen in https://tracker.debian.org/pkg/firefox.
On Sat, 04 Sep 2021 07:47:02 +0530
Pankaj Jangid wrote:
> Marko Randjelovic writes:
>
> > Did you make sure:
> >
> > 1. correct device is set to record from
> > 2. recording is enabled
> > 3. input volume is large enough
>
> I guess I have only one device so there is nothing to set.
I mean
On Fri, Sep 03, 2021 at 10:52:45PM +0530, Pankaj Jangid wrote:
> I have a fresh Bullseye installation on a laptop. Sound output is
> working. But the input is not working. The device is detected.
>
> --8<---cut here---start->8---
> $ arecord -l
> List of CA
On Fri, Sep 03, 2021 at 10:17:21AM -0400, Roberto C. Sánchez wrote:
> On Fri, Sep 03, 2021 at 04:11:49PM +0200, Richard Forst wrote:
> > I just installed Debian using netinstall image. I thought I install testing
> > version, but apparently it's Debian 11. So now my source.list looks like
> > bel
On 4/09/21 9:26 pm, Brian wrote:
On Sat 04 Sep 2021 at 21:21:38 +1200, Richard Hector wrote:
Greg Wooledge pointed out in another thread that 'type' is often better than
'which' for finding out what kind of command you're about to run, and where
it comes from.
A quick test, however, threw up a
On Sat 04 Sep 2021 at 21:21:38 +1200, Richard Hector wrote:
> Greg Wooledge pointed out in another thread that 'type' is often better than
> 'which' for finding out what kind of command you're about to run, and where
> it comes from.
>
> A quick test, however, threw up another issue:
>
> richard
On 9/4/2021 11:21 AM, Richard Hector wrote:
Greg Wooledge pointed out in another thread that 'type' is often better
than 'which' for finding out what kind of command you're about to run,
and where it comes from.
A quick test, however, threw up another issue:
richard@zircon:~$ type ls
ls is alia
On Sat, Sep 04, 2021 at 01:58:41AM -0400, Bob Bernstein wrote:
> On Fri, 3 Sep 2021, Michael Lange wrote:
>
> > according to https://ice-wm.org/man/icewm-preferences the syntax for
> > using a bold font should rather be:
>
> > ActiveTaskBarFontNameXft=”sans-serif:size=12:bold” .
>
> Ah. RTFM sti
On 1/09/21 3:32 am, Greg Wooledge wrote:
In bash, which is *not* a shell builtin -- it's a separate program,
/usr/bin/which.
Well _that_ took a while to parse correctly :-) I know bash is not a
shell builtin, that would be weird ...
Cheers,
Richard
Greg Wooledge pointed out in another thread that 'type' is often better
than 'which' for finding out what kind of command you're about to run,
and where it comes from.
A quick test, however, threw up another issue:
richard@zircon:~$ type ls
ls is aliased to `ls --color=auto'
Great, so it's an
38 matches
Mail list logo
