Re: firefox misbehaviour
On Fri, May 20, 2022 at 10:18:59PM -0700, David Christensen wrote: I am unfamiliar with "TAB AUTO REFRESH icon (and function)". TAB AUTO REFRESH is an extension which automatically reloads the current page every [specified number of] seconds. I use it to refresh the weather bureau forecast web page about once an hour and the web page for my personal weather station about every five minutes. When installed, TAB AUTO REFRESH displays an icon with a countdown of the number of seconds until the next refresh. Clicking on the icon brings up a window for resetting the refresh interval. RLH
Re: firefox misbehaviour
Am Samstag, 21. Mai 2022, 05:09:38 CEST schrieb Russell L. Harris: Hi Russell, I do not have those issues you describe, but on my system firefox sometimes completely freezes the system when calling some special websites. Then nothing can be done, only the mouse is moving but no mouse clicking, nor keyboard input is possible then. The only way is the hard way: long press power button, so it switches off. I admit, there are some plugins installed, like noscript and ublock origin, which also might interfere. However, for testing purposes on those sites I temporarly deactivate the plugins. And of course, it can not be excluded, that these sites also interfere with the graphics driver, which is Nvidia. Does this help? Best regards Hans > Is anyone else having trouble with firefox over the past week? > > At first I noticed that NEW WINDOW sometimes was absent from the menu > (FILE > NEW WINDOW). Then, some bookmarks went missing. Now the TAB > AUTO REFRESH icon (and function) has vanished and does not reinstall. > > Debian 11, firefox 91.9.0esr (64-bit) > > RLH
Re: firefox misbehaviour
On 5/20/22 20:09, Russell L. Harris wrote: Is anyone else having trouble with firefox over the past week? At first I noticed that NEW WINDOW sometimes was absent from the menu (FILE > NEW WINDOW). Then, some bookmarks went missing. Now the TAB AUTO REFRESH icon (and function) has vanished and does not reinstall. Debian 11, firefox 91.9.0esr (64-bit) RLH I upgraded to 91.9.0esr-1~deb11u1 two weeks ago: 2022-05-06 15:42:02 root@laalaa ~ # apt-get upgrade The following packages will be upgraded: firefox-esr ... Get:5 http://security.debian.org/debian-security bullseye-security/main amd64 firefox-esr amd64 91.9.0esr-1~deb11u1 [58.7 MB] Preparing to unpack .../01-firefox-esr_91.9.0esr-1~deb11u1_amd64.deb ... Leaving 'diversion of /usr/bin/firefox to /usr/bin/firefox.real by firefox-esr' Unpacking firefox-esr (91.9.0esr-1~deb11u1) over (91.7.0esr-1~deb11u1) ... Setting up firefox-esr (91.9.0esr-1~deb11u1) ... File -> New Window exists and works. I have not noticed any missing bookmarks. I am unfamiliar with "TAB AUTO REFRESH icon (and function)". David
Re: Resetting a USB port in Debian 10
On Fri, May 20, 2022 at 05:25:54PM -0500, Jason wrote: > On Thu, May 19, 2022 at 09:25:23AM +0200, to...@tuxteam.de wrote: > > On Thu, May 19, 2022 at 09:55:54AM +0300, Anssi Saari wrote: > > > Jason writes: > > > > > > > What is the best way to power cycle or reset a USB port? > > Turns out the easiest answer was within reach all the time: In Debian 10, > 'usbreset' is included in the standard usbutils package [...] Gee. I had it all the time waiting there in /usr/bin. Thanks for discovering it for me :-) For the curious, here [1] is the source (for buster). The core seems to be sending an ioctl to the relevant /dev/bus/usb/... file. Cheers -- t signature.asc Description: PGP signature
firefox misbehaviour
Is anyone else having trouble with firefox over the past week? At first I noticed that NEW WINDOW sometimes was absent from the menu (FILE > NEW WINDOW). Then, some bookmarks went missing. Now the TAB AUTO REFRESH icon (and function) has vanished and does not reinstall. Debian 11, firefox 91.9.0esr (64-bit) RLH -- Woe unto them that call evil good, and good evil; that put darkness for light, and light for darkness; that put bitter for sweet, and sweet for bitter! - Isaiah 5:20
Re: Avoiding command hijacking in shells (was Re: setting path for root after "sudo su" and "sudo" for Debian Bullseye (11))
On Fri, May 20, 2022 at 09:36:40PM -0400, The Wanderer wrote: > I wasn't even thinking of it in those terms, although now that you point > it out that's a good thing to be aware of. I was thinking of it in terms > of A: trying to write scripts that are safe against such problematic > elements being in the environment, You can't. It's really that simple -- if someone can compromise the execution environment of your script, they can make your script do anything they like. Don't think that compiled programs are safe, either -- unless they're statically linked, someone with control over the execution environment can use LD_PRELOAD or similar environment variables to override any library function the program calls. With that in mind, what you do as a programmer is simply ignore the possibility. Your program should assume it's being run in a sane, or at least non-malicious, environment. At the programming level, your security responsibilities are things like: * Use correct and safe programming practices for whatever language(s) you're writing in. * Sanity-check all user inputs, whether from files, from the environment, or from a terminal, before you use them. * Avoid writing programs that write programs whenever possible. If you can't avoid them (e.g. if you *must* call awk from your bash script), be on the lookout for code injections. > and B: being able to detect and > recover from some piece of malware having inserted such elements into > the environment on your *own* computer. Many people will tell you that if your computer has been compromised, there's no recovering from it. It's best to wipe the file systems and reinstall, then restore data from the last non-compromised backup. A post-mortem analysis is possible, if you remove the hard drive(s) and use them as non-booting data disks in another system. From a trusted environment like that, you can mount the file systems and inspect them to see what has been compromised. But it'll be tedious and time-consuming.
Re: Apache2 404
How exactly do you go to the second page? Is it a hyperlink in HTML or
what? If so, what is url?
file:// protocol will not bring you to the server.
On Fri, May 20, 2022 at 7:44 PM ldmko...@yahoo.com
wrote:
> I am having a problem with Apache2. I have set a new configuration and
> have three html pages defined. The inital html (index.html) displays fine
> on my laptop on my home network; however, when I attemp to go to the second
> page I get 404 not found on this server. If I use localhost on my linux
> machine the second page diplays in firefox as "file:///. . .
> I have done the appropriate a2ensite and a2dissite commands. I am new at
> Linux so any advice is appreciated. If there are other files that you need
> to look at, let me know.
>
> Thanks, Larry
>
> This is /etc/apache2/apache2.conf
>
> # This is the main Apache server configuration file. It contains
> theConfiguration
> file /etc/apache2Configuration file
> /etc/apache2/sites/available/ldmdomain.info.confConfiguration file
> /etc/apache2/sites/available/ldmdomain.info.confConfiguration file
> /etc/apache2/sites/available/ldmdomain.info.conf
> /sites/available/ldmdomain.info.conf
> # configuration directives that give the server its instructions.Configuration
> file /etc/apache2/sites/Configuration file
> /etc/apache2/sites/available/ldmdomain.info.conf
> available/ldmdomain.info.conf
> # See http://httpd.apache.org/docs/2.4/ for detailed information about
> # the directives and /usr/share/doc/apache2/README.Debian about Debian
> specificConfigurConfiguration file
> /etc/apache2/sites/available/ldmdomain.info.confConfiguration file
> /etc/apache2/sites/available/ldmdomain.info.confConfiguration file
> /etc/apache2/sites/available/ldmdomain.info.confation file /Configuration
> file /etc/apache2/sites/available/ldmdomain.info.conf
> etc/apache2/sites/available/ldmdomain.info.conf
> # hints.
> #
> #
> # Summary of how the Apache 2 configuration works in Debian:
> # The Apache 2 web server configuration in Debian is quite different to
> # upstream's suggested way to configure the web server. This is because
> Debian's
> # default Apache2 installation attempts to make adding and removing
> modules,
> # virtual hosts, and extra configuration directives as flexible as
> possible, in
> # order to make automating the changes and administering the server as
> easy as
> # possible.
>
> # It is split into several files forming the configuration hierarchy
> outlined
> # below, all located in the /etc/apache2/ directory:
> #
> #/etc/apache2/Configuration file
> /etc/apache2/sites/available/ldmdomain.info.conf
> #|-- apache2.conf
> #|`-- ports.conf
> #|-- mods-enabled
> #||-- *.load
> #|`-- *.conf
> #|-- conf-enabled
> #|`-- *.conf
> # `-- sites-enabled
> # `-- *.conf
> #
> #
> # * apache2.conf is the main configuration file (this file). It puts the
> pieces
> # together by including all remaining configuration files when starting
> up the
> # web server.
> #
> # * ports.conf is always included from the main configuration file. It
> isConfiguration
> file /etc/apache2/sites/available/ldmdomain.info.conf
> # supposed to determine listening ports for incoming connections which
> can be
> # customized anytime.
> #
> # * Configuration files in the mods-enabled/, conf-enabled/ and
> sites-enabled/
> # directories contain particular configuration snippets which manage
> modules,
> # global configuration fragments, or virtual host configurations,
> # respectively.
> #
> # They are activated by symlinking available configuration files from
> their
> # respective *-available/ counterparts. These should be managed by using
> our
> # helpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf.
> See
> # their respective man pages for detailed information.
> #
> # * The binary is called apache2. Due to the use of environment variables,
> inConfiguration file
> /etc/apache2/sites/available/ldmdomain.info.confConfiguration
> file /etc/apache2/sites/available/ldmdomain.info.conf
> # the default configuration, apache2 needs to be started/stopped with
> # /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly
> will not
> # work with the default configuration.
>
>
> # Global configuration
> #
>
> #
> # ServerRoot: The top of the directory tree under which the server's
> # configuration, error, and log files are kept.
> #
> # NOTE! If you intend to place this on an NFS (or otherwise network)
> # mounted filesystem then please read the Mutex documentation (available
> # at http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);
> # you will save yourself a lot of trouble.
> #
> # Do NOT add a slash at the end of the directory path.
> #
> #ServerRoot "/etc/apache2"
>
> #
> # The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
> #
> #Mutex file:${APACHE_LOCK_DIR} default
> Configuration file /etc/apache2/sites/available/ldmdomain.info.conf
Re: Avoiding command hijacking in shells (was Re: setting path for root after "sudo su" and "sudo" for Debian Bullseye (11))
On 2022-05-20 at 21:20, Greg Wooledge wrote:
> On Fri, May 20, 2022 at 08:41:43PM -0400, The Wanderer wrote:
>
>> On 2022-05-20 at 20:28, David Wright wrote:
>>
>> > $ function /usr/bin/sudo { echo teehee; }
>> > $ /usr/bin/sudo whatever
>> > teehee
>> > $
>>
>> A quick test demonstrates that this can be worked around via the 'unset'
>> command:
>
> Until you define a function named unset.
Well, yes - that was the point of the paragraphs after the demonstration.
> But the real point here is that you should only use sudo or su (or
> doas or any other program that reads your password) from a trusted
> environment. What you definitely should NOT do is get called by a
> coworker, go over to their workstation, hear the description of a
> problem, and try to fix it from their computer, where they may have
> overridden su/sudo/etc.
>
> Go back to your own desk first, and fix it from there.
I wasn't even thinking of it in those terms, although now that you point
it out that's a good thing to be aware of. I was thinking of it in terms
of A: trying to write scripts that are safe against such problematic
elements being in the environment, and B: being able to detect and
recover from some piece of malware having inserted such elements into
the environment on your *own* computer.
Which is also about only doing it from a trusted environment, I suppose
- just with even more stringent and depressing considerations about what
the limitations of trustability are.
--
The Wanderer
The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw
signature.asc
Description: OpenPGP digital signature
Re: Avoiding command hijacking in shells (was Re: setting path for root after "sudo su" and "sudo" for Debian Bullseye (11))
On Fri, May 20, 2022 at 08:41:43PM -0400, The Wanderer wrote:
> On 2022-05-20 at 20:28, David Wright wrote:
> > $ function /usr/bin/sudo { echo teehee; }
> > $ /usr/bin/sudo whatever
> > teehee
> > $
>
> A quick test demonstrates that this can be worked around via the 'unset'
> command:
Until you define a function named unset.
But the real point here is that you should only use sudo or su (or doas
or any other program that reads your password) from a trusted environment.
What you definitely should NOT do is get called by a coworker, go over to
their workstation, hear the description of a problem, and try to fix it
from their computer, where they may have overridden su/sudo/etc.
Go back to your own desk first, and fix it from there.
Avoiding command hijacking in shells (was Re: setting path for root after "sudo su" and "sudo" for Debian Bullseye (11))
On 2022-05-20 at 20:28, David Wright wrote:
> On Thu 19 May 2022 at 15:42:33 (-0500), Nicholas Geovanis wrote:
>
>> On Thu, May 19, 2022, 3:14 AM 황병희 wrote:
>> > Tom Browder writes:
>> >
>> > > I need a special path setting for root after both "sudo" and "sudo
>> > > su." (...)
>> >
>> > Just you try like as "sudo su -". Sometimes i use it that way.
>> >
>>
>> When I need to use sudo or su to invoke executables, I fully qualify the
>> path to sudo and the path to that specific executable by using their full
>> path from /. And I often assign values to the important environment
>> variables at the beginning of that same command line. Like...
>>
>> joe="schmoe" slap="moe" /usr/bin/sudo
>>
>> The idea is to draw a line around that invocation by limiting what it
>> "knows".
>
> If you're running bash, then giving the full path for sudo will
> circumvent any aliases you've defined, and any other versions
> of sudo available from earlier in your $PATH, but there's not
> necessarily any security bonus. After Greg (2018):
>
> $ function /usr/bin/sudo { echo teehee; }
> $ /usr/bin/sudo whatever
> teehee
> $
A quick test demonstrates that this can be worked around via the 'unset'
command:
$ type malicious
bash: type: malicious: not found
$ function malicious { echo "Not really, but..."; }
$ type malicious
malicious is a function
malicious ()
{
echo "Not really, but..."
}
$ unset malicious
$ type malicious
bash: type: malicious: not found
It might look as if this could mean you could work around many possible
cases of malice by just issuing 'unset [command-name]' before any
command you're concerned about, but unfortunately, this same process can
be used to override 'unset' itself; I'm not going to reproduce the exact
commands and output here (mostly because I already closed that window
and I don't want to run through it all again), but a malicious actor
could just override 'unset' to something malicious and then you might
have no way of getting out of it within the running session.
(Such an actor could also override 'type' and 'set' and so forth to
something that would report the expected values, so even detecting that
this had been done could be difficult. Writing a shell function that
would behave "correctly" in that role could be difficult, and I
certainly don't intend to try to do it, but I don't think it would be at
all impossible.)
--
The Wanderer
The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw
signature.asc
Description: OpenPGP digital signature
Re: setting path for root after "sudo su" and "sudo" for Debian Bullseye (11)
On Fri, May 20, 2022, 7:28 PM David Wright wrote:
> On Thu 19 May 2022 at 15:42:33 (-0500), Nicholas Geovanis wrote:
> > On Thu, May 19, 2022, 3:14 AM 황병희 wrote:
> > > Tom Browder writes:
> > >
> > > > I need a special path setting for root after both "sudo" and "sudo
> > > > su." (...)
> > >
> > > Just you try like as "sudo su -". Sometimes i use it that way.
> > >
> >
> > When I need to use sudo or su to invoke executables, I fully qualify the
> > path to sudo and the path to that specific executable by using their full
> > path from /. And I often assign values to the important environment
> > variables at the beginning of that same command line. Like...
> >
> > joe="schmoe" slap="moe" /usr/bin/sudo
> >
> > The idea is to draw a line around that invocation by limiting what it
> > "knows".
>
> If you're running bash, then giving the full path for sudo will
> circumvent any aliases you've defined, and any other versions
> of sudo available from earlier in your $PATH, but there's not
> necessarily any security bonus. After Greg (2018):
>
Translation: There is no silver bullet that makes your system secure. There
are many steps large and small that make it incrementally more secure. Yes
that's true.
$ function /usr/bin/sudo { echo teehee; }
> $ /usr/bin/sudo whatever
> teehee
> $
>
> Cheers,
> David.
>
>
Re: setting path for root after "sudo su" and "sudo" for Debian Bullseye (11)
On Thu 19 May 2022 at 15:42:33 (-0500), Nicholas Geovanis wrote:
> On Thu, May 19, 2022, 3:14 AM 황병희 wrote:
> > Tom Browder writes:
> >
> > > I need a special path setting for root after both "sudo" and "sudo
> > > su." (...)
> >
> > Just you try like as "sudo su -". Sometimes i use it that way.
> >
>
> When I need to use sudo or su to invoke executables, I fully qualify the
> path to sudo and the path to that specific executable by using their full
> path from /. And I often assign values to the important environment
> variables at the beginning of that same command line. Like...
>
> joe="schmoe" slap="moe" /usr/bin/sudo
>
> The idea is to draw a line around that invocation by limiting what it
> "knows".
If you're running bash, then giving the full path for sudo will
circumvent any aliases you've defined, and any other versions
of sudo available from earlier in your $PATH, but there's not
necessarily any security bonus. After Greg (2018):
$ function /usr/bin/sudo { echo teehee; }
$ /usr/bin/sudo whatever
teehee
$
Cheers,
David.
Re: Resetting a USB port in Debian 10
On Thu, May 19, 2022 at 09:25:23AM +0200, to...@tuxteam.de wrote: > On Thu, May 19, 2022 at 09:55:54AM +0300, Anssi Saari wrote: > > Jason writes: > > > > > What is the best way to power cycle or reset a USB port? Turns out the easiest answer was within reach all the time: In Debian 10, 'usbreset' is included in the standard usbutils package. One glitch is that because it does not allow the user to specify the reset time (to my knowledge), my modem gets the next higher device number (ttyACM1 instead of ttyACM0). Calling usbreset a 2nd time brings it back to /dev/ttyACM0. If usbreset turns out not to solve my problem(s), I will pursue the other excellent leads that were provided. Thank you for all the helpful responses. -- Jason
Re: setting path for root after "sudo su" and "sudo" for Debian Bullseye (11)
On Thu 19 May 2022 at 20:24:50 -0400, Kenneth Parker wrote: [...] > Note, Debian (at least in the Expert Installation Mode) lets me set a Root > Password. Ubuntu doesn't, so one of my early actions after the Install is > to enter "sudo su -" and, on the resulting Root Shell, type "passwd root". Depends on whta you mean by "Ubuntu". Its mini.iso offers settong a root password. I wonder whether the regular ISO can be preseeded? -- Brian.
Re: Apache2 404
ldmko...@yahoo.com wrote:
> I am having a problem with Apache2. I have set a new configuration and have
> three html pages defined. The inital html (index.html) displays fine on my
> laptop on my home network; however, when I attemp to go to the second page I
> get 404 not found on this server. If I use localhost on my linux machine the
> second page diplays in firefox as "file:///. . .I have done the appropriate
> a2ensite and a2dissite commands. I am new at Linux so any advice is
> appreciated. If there are other files that you need to look at, let me know.
> Thanks, Larry
>
>
> DocumentRoot /var/www/ldmdomain.info/html
>
> Options Indexes FollowSymLinks
> AllowOverride All
> Order deny,Allow
> Allow from all
> Require all granted
>
>
This should be in /etc/apache2/sites-available/ something, and
then linked to sites-enabled/
> # Include the virtual host configurations:
> IncludeOptional sites-enabled/*.conf
This is what allows that.
>Configuration file /etc/apache2/sites/available/ldmdomain.info.conf
It's sites-available and sites-enabled, not sites/available.
> ServerName ldmdomain.info
I can't ping or whois this, so that's a big problem. Register a
domain and get DNS going for it, or this will not work outside
of your own local network.
Inside your local network, you will need an A or and/or
CNAME record pointing to ldmdomain.info and optionally (but you
should) www.ldmdomain.info
>
> ServerAdmin ad...@ldmdomain.info
> ServerName ldmdomain.info
> ServerAlias www.ldmdomain.info
> DocumentRoot /var/www/ldmdomain.info/html
>
> Options -Indexes +FollowSymLinks
> AllowOverride All
>
> ErrorLog ${APACHE_LOG_DIR}/error.log
> CustomLog ${APACHE_LOG_DIR}/access.log combined
>
That all looks OK.
-dsr-
Apache2 404
I am having a problem with Apache2. I have set a new configuration and have
three html pages defined. The inital html (index.html) displays fine on my
laptop on my home network; however, when I attemp to go to the second page I
get 404 not found on this server. If I use localhost on my linux machine the
second page diplays in firefox as "file:///. . .I have done the appropriate
a2ensite and a2dissite commands. I am new at Linux so any advice is
appreciated. If there are other files that you need to look at, let me know.
Thanks, Larry
This is /etc/apache2/apache2.conf# This is the main Apache server
configuration file. It contains theConfiguration file
/etc/apache2Configuration file
/etc/apache2/sites/available/ldmdomain.info.confConfiguration file
/etc/apache2/sites/available/ldmdomain.info.confConfiguration file
/etc/apache2/sites/available/ldmdomain.info.conf/sites/available/ldmdomain.info.conf#
configuration directives that give the server its instructions.Configuration
file /etc/apache2/sites/Configuration file
/etc/apache2/sites/available/ldmdomain.info.confavailable/ldmdomain.info.conf#
See http://httpd.apache.org/docs/2.4/ for detailed information about
# the directives and /usr/share/doc/apache2/README.Debian about Debian
specificConfigurConfiguration file
/etc/apache2/sites/available/ldmdomain.info.confConfiguration file
/etc/apache2/sites/available/ldmdomain.info.confConfiguration file
/etc/apache2/sites/available/ldmdomain.info.confation file /Configuration file
/etc/apache2/sites/available/ldmdomain.info.confetc/apache2/sites/available/ldmdomain.info.conf#
hints.
#
#
# Summary of how the Apache 2 configuration works in Debian:
# The Apache 2 web server configuration in Debian is quite different to
# upstream's suggested way to configure the web server. This is because Debian's
# default Apache2 installation attempts to make adding and removing modules,
# virtual hosts, and extra configuration directives as flexible as possible, in
# order to make automating the changes and administering the server as easy as
# possible.
# It is split into several files forming the configuration hierarchy outlined
# below, all located in the /etc/apache2/ directory:
#
# /etc/apache2/Configuration file
/etc/apache2/sites/available/ldmdomain.info.conf# |-- apache2.conf
# | `-- ports.conf
# |-- mods-enabled
# | |-- *.load
# | `-- *.conf
# |-- conf-enabled
# | `-- *.conf
# `-- sites-enabled
# `-- *.conf
#
#
# * apache2.conf is the main configuration file (this file). It puts the pieces
# together by including all remaining configuration files when starting up the
# web server.
#
# * ports.conf is always included from the main configuration file. It
isConfiguration file /etc/apache2/sites/available/ldmdomain.info.conf#
supposed to determine listening ports for incoming connections which can be
# customized anytime.
#
# * Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/
# directories contain particular configuration snippets which manage modules,
# global configuration fragments, or virtual host configurations,
# respectively.
#
# They are activated by symlinking available configuration files from their
# respective *-available/ counterparts. These should be managed by using our
# helpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf. See
# their respective man pages for detailed information.
#
# * The binary is called apache2. Due to the use of environment variables,
inConfiguration file
/etc/apache2/sites/available/ldmdomain.info.confConfiguration file
/etc/apache2/sites/available/ldmdomain.info.conf# the default configuration,
apache2 needs to be started/stopped with
# /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will
not
# work with the default configuration.
# Global configuration
#
#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE! If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the Mutex documentation (available
# at http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
#ServerRoot "/etc/apache2"
#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
#Mutex file:${APACHE_LOCK_DIR} default
Configuration file /etc/apache2/sites/available/ldmdomain.info.conf#
# The directory where shm and other runtime files will be stored.
#
DefaultRuntimeDir ${APACHE_RUN_DIR}
#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
PidFile ${APACHE_PID_FILE}
#
# Timeout: The number of secondsConfiguration file
/etc/apache2/sites/available/ldmdomain.info.conf before receives and sends time
out
Re: Firefox context menu and tooltip on wrong display?
On Thu, May 19, 2022 at 10:31:44PM -0400, Roberto C. Sánchez wrote: > For those following along, a little while ago the problem "went away". > That is, context menus, tooltips, and application menus now all show in > the expected places in Firefox. I really hope that this is not a > temporary situation and that whatever the problem was has just magically > resolved itself. :shrug: > And this morning the problem returned. -- Roberto C. Sánchez
Debian: perl6 package is replaced by raku package
Hi Some of you may have wondered by perl6 package vanished from Debian Bookworm (aka testing). Belatedly following the rename of Perl6 language to Raku, I've renamed most Debian packages related to Raku. Among them, perl6 package was renamed raku. You can now install raku package to get rakudo compiler and the raku modules that are available in Debian [1]. All the best Dod PS: this announcement does not apply to Debian 11 (aka stable or bullseye) [1] https://qa.debian.org/developer.php?login=pkg-rakudo-devel%40lists.alioth.debian.org
Installing mysql-workbench on Debian Sid
Hi, I need to install mysql-workbench package on debian sid, but i get problems about missing dependencies. The following packages have unmet dependencies: mysql-workbench : Depends: libgdal29 (>= 3.3.0) but it is not installable Depends: python3 (< 3.10) but 3.10.4-1+b1 is to be installed Recommends: ttf-bitstream-vera but it is not installable Recommends: mysql-utilities but it is not installable Recommends: default-mysql-client is to be installed or virtual-mysql-client libgdal29 exists only for sh4 architecture. Is it possible to install it in another way ?
Re: smartctl puzzlement new disk
On 14/05/2022 03:02, ghe2001 wrote: Supermicro workstation, Debian Buster, smartctl v 6.6 I bought a new 12TB Western Digital Gold SATA disk the other day. After testing it, smartctl says, among other things: 22 Unknown_Attribute 0x0023 001 001 025 Pre-fail Always FAILING_NOW 13 And it looks like the test is aborted when smartctl sees that error. And there's lots of yelling all over my monitor. I found some discussion of ID 22 on the 'Net -- it's often used to mean 'helium level' which makes some sense on a 12TB disk. But testing the Seagate 12TB next to the Western Digital is OK -- sorta; there's no ID 22 in the output. The Wikipedia article on S.M.A.R.T lists ID 22 as having to do with the helium. On the web, it looked like there's a way of changing what ID 22's called so smartctl won't hurl. I'd like the test to just keep going and tell me the other things it finds. My questions: Is this error on ID 22 anything to worry about? (I'm guessing that it isn't, and smartctl and/or something in the Western Digital disk's firmware is mildly wrong) Is there really a way to change 22 so smartctl will report the helium level? How do I do that? Regardless of whether smartctl knows what ID 22 means, the error is actually because the _value_ of ID 22 is too low. SMART entries show four values: * VALUE - This is a "normalised" value, between 0 and 255. The RAW_VALUE (shown as the last column) is scaled according to the manufacturer's algorithm such that 100 is the ideal value. * WORST - This represents the worst level of VALUE that the drive has seen. * THRESH - This is a level which the manufacturer has determined. If VALUE is less than THRESH, there is a problem * RAW_VALUE - This is some internal value which the manufacturer knows the meaning of (sometimes it might be obvious such as the number of hours online, but in the case of the helium level it's not obvious what 13 represents) So, Smartctl might not know that the helium level is low, but it _does_ know that ID 22 is at 1, which is less than 25, so therefore the drive is failing. As far as the firmware is concerned, the drive is failing. Whether that decision is justified, only the manufacturer can really say. Is there a way to to get smartctl to finish the test? If so, how do I do that? TIA... > OpenPGP_signature Description: OpenPGP digital signature
