On 11/04/2024 20:53, Stephen P. Molnar wrote:
I am running Bullseye and attempting to use QEMU/KVM virt-manager, on
the computers on my LAN rather than Oracle VM VirtualBox.
[...]
However, when I pinged yahoo.com. I got the result:
Reply from 169.234.75.136: Destination host unreachable.
On 4/11/24 10:14, Greg Wooledge wrote:
On Thu, Apr 11, 2024 at 01:30:46PM +, sarath wrote:
dear debian
I have created live usb with debian-live-12.5.0-amd64-standard.iso using tool
Ventoy-1.0.95. When tried to booting it is ended with command line options.
please help me to the next
On Thu, Apr 11, 2024 at 01:30:46PM +, sarath wrote:
> dear debian
>
> I have created live usb with debian-live-12.5.0-amd64-standard.iso using tool
> Ventoy-1.0.95. When tried to booting it is ended with command line options.
> please help me to the next step
It's not clear to me what you
Am 11.04.2024 um 09:53:30 Uhr schrieb Stephen P. Molnar:
> I followed the How To (HowTo.txt, attached) without any warning or
> error messages. However, when I pinged yahoo.com. I got the result:
>
> Reply from 169.234.75.136: Destination host unreachable.
You have to specify how your network
I am running Bullseye and attempting to use QEMU/KVM virt-manager, on
the computers on my LAN rather than Oracle VM VirtualBox.
I particularly would like to be able to run Windows 10 as there in one
application that I need for my molecular modeling research that is not
available for Linux.
dear debian
I have created live usb with debian-live-12.5.0-amd64-standard.iso using tool
Ventoy-1.0.95. When tried to booting it is ended with command line options.
please help me to the next step
thanks regards
Sarathdc
Sent with [Proton Mail](https://proton.me/) secure email.
The newly released debian installer (daily build) for testing do not show
the LVM logical volumes and fail when asked for LVM configuration.
The problem is quite new because a installer build im mid February
worked fine.
So who do I have to file the bug to?
Regards
Angelo Pozzi
On Thursday 07 March 2024 02:44:42 pm Greg Wooledge wrote:
> On Thu, Mar 07, 2024 at 02:33:05PM -0500, Roy J. Tellason, Sr. wrote:
> > On Thursday 07 March 2024 09:02:44 am Teemu Likonen wrote:
> > > systemctl status systemd-timesyncd.service
> >
> > This got me some interesting results:
> >
> >
On 08/03/2024 07:17, gene heskett wrote:
I have NDI how to extract chrony's logs from journalctl.
- man journalctl,
- docs listed on the systemd web site.
On 3/7/24 21:30, David Wright wrote:
On Thu 07 Mar 2024 at 19:17:02 (-0500), gene heskett wrote:
On 3/7/24 12:19, David Wright wrote:
On Thu 07 Mar 2024 at 11:29:47 (-0500), gene heskett wrote:
On 3/7/24 10:59, Greg Wooledge wrote:
You should be able to verify that the systemd-timesyncd
On Thu 07 Mar 2024 at 19:17:02 (-0500), gene heskett wrote:
> On 3/7/24 12:19, David Wright wrote:
> > On Thu 07 Mar 2024 at 11:29:47 (-0500), gene heskett wrote:
> > > On 3/7/24 10:59, Greg Wooledge wrote:
> >
> > > > You should be able to verify that the systemd-timesyncd package is
> > > >
o
look at that system monitor every once in a while and when things start getting excessive
shut firefox down and restart it. Then I don't have the problem...
I'm not sure if I have ntp or something else running here. (Looking...) I
don't see it in my process list.
Cheers, Gene Heskett,
On 3/7/24 12:19, David Wright wrote:
On Thu 07 Mar 2024 at 11:29:47 (-0500), gene heskett wrote:
On 3/7/24 10:59, Greg Wooledge wrote:
You should be able to verify that the systemd-timesyncd package is
removed.
In some older versions of Debian, systemd-timesyncd was part of the
systemd
On Thu, Mar 07, 2024 at 02:33:05PM -0500, Roy J. Tellason, Sr. wrote:
> On Thursday 07 March 2024 09:02:44 am Teemu Likonen wrote:
> > systemctl status systemd-timesyncd.service
>
> This got me some interesting results:
>
> ● systemd-timesyncd.service - Network Time Synchronization
>Loaded:
a while and when things start
> getting excessive shut firefox down and restart it. Then I don't have the
> problem...
There's a kernel feature called the OOM-killer (out of memory)
which is supposed to detect when you are running out of memory
and select a process to kill.
Did you
On Thursday 07 March 2024 09:02:44 am Teemu Likonen wrote:
> systemctl status systemd-timesyncd.service
This got me some interesting results:
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled;
vendor preset:
refox down and restart it. Then I don't have the problem...
I'm not sure if I have ntp or something else running here. (Looking...) I
don't see it in my process list.
--
Member of the toughest, meanest, deadliest, most unrelenting -- and
ablest -- form of life in this section of space, a
On Thu 07 Mar 2024 at 11:29:47 (-0500), gene heskett wrote:
> On 3/7/24 10:59, Greg Wooledge wrote:
> > You should be able to verify that the systemd-timesyncd package is
> > removed.
> >
>
> > In some older versions of Debian, systemd-timesyncd was part of the
> > systemd package, and was
On 3/7/24 11:18, Jeffrey Walton wrote:
On Thu, Mar 7, 2024 at 8:44 AM wrote:
On Thu, Mar 07, 2024 at 08:31:16AM -0500, gene heskett wrote:
[...]
Now, how do I assure timedatectl stays stopped on a reboot? [...]
I'll have to leave this to others more fluent in systemd-ish.
Mask the
On 3/7/24 10:59, Greg Wooledge wrote:
On Thu, Mar 07, 2024 at 08:31:16AM -0500, gene heskett wrote:
So I purged ntpsec and re-installed chrony which I had done once before with
no luck but this time timedatectl was stopped and it worked!
Now, how do I assure timedatectl stays stopped on a
On Thu, Mar 7, 2024 at 8:44 AM wrote:
>
> On Thu, Mar 07, 2024 at 08:31:16AM -0500, gene heskett wrote:
>
> [...]
> Now, how do I assure timedatectl stays stopped on a reboot? [...]
>
> I'll have to leave this to others more fluent in systemd-ish.
Mask the systemd-timesyncd service. Masking is
On Thu, Mar 07, 2024 at 08:31:16AM -0500, gene heskett wrote:
> So I purged ntpsec and re-installed chrony which I had done once before with
> no luck but this time timedatectl was stopped and it worked!
>
> Now, how do I assure timedatectl stays stopped on a reboot?
Which version of Debian is
* 2024-03-07 08:31:16-0500, gene heskett wrote:
> So I purged ntpsec and re-installed chrony which I had done once before
> with no luck but this time timedatectl was stopped and it worked!
>
> Now, how do I assure timedatectl stays stopped on a reboot? systemd's
> docs are positively opaque
On Thu, Mar 07, 2024 at 08:31:16AM -0500, gene heskett wrote:
[...]
> So I purged ntpsec and re-installed chrony which I had done once before with
> no luck but this time timedatectl was stopped and it worked!
great :-)
> Now, how do I assure timedatectl stays stopped on a reboot? [...]
I'll
On 3/7/24 00:22, to...@tuxteam.de wrote:
On Wed, Mar 06, 2024 at 08:06:15PM -0600, John Hasler wrote:
Look at the chronyd settime command and the chrony.conf makestep
directive. These are intended for your situation.
This from man(8) ntpd:
-g, --panicgate
Allow the first adjustment to
On Wed, Mar 06, 2024 at 09:36:56PM -0500, Greg Wooledge wrote:
> On Wed, Mar 06, 2024 at 08:33:37PM -0500, gene heskett wrote:
> > no place in the ntpsec docs, nor the chrony docs
> > does it show the ability to slam the current time into the SW clock on these
> > arm systems at bootup's first
On Wed, Mar 06, 2024 at 08:06:15PM -0600, John Hasler wrote:
> Look at the chronyd settime command and the chrony.conf makestep
> directive. These are intended for your situation.
This from man(8) ntpd:
-g, --panicgate
Allow the first adjustment to be Big. This option may appear an
On Wed, Mar 06, 2024 at 08:33:37PM -0500, gene heskett wrote:
> no place in the ntpsec docs, nor the chrony docs
> does it show the ability to slam the current time into the SW clock on these
> arm systems at bootup's first access time.
Traditionally, this was done by the ntpdate command, which
Look at the chronyd settime command and the chrony.conf makestep
directive. These are intended for your situation.
--
John Hasler
j...@sugarbit.com
Elmwood, WI USA
On 3/6/24 18:02, Greg Wooledge wrote:
On Wed, Mar 06, 2024 at 05:56:29PM -0500, gene heskett wrote:
On 3/6/24 12:42, Greg Wooledge wrote:
On Wed, Mar 06, 2024 at 12:31:46PM -0500, Roy J. Tellason, Sr. wrote:
sudo timedatectl set-ntp true
But *don't* do that if you're using some other
On Wed, Mar 06, 2024 at 05:56:29PM -0500, gene heskett wrote:
> On 3/6/24 12:42, Greg Wooledge wrote:
> > On Wed, Mar 06, 2024 at 12:31:46PM -0500, Roy J. Tellason, Sr. wrote:
> > > sudo timedatectl set-ntp true
> >
> > But *don't* do that if you're using some other NTP program instead of
>
On 3/6/24 12:42, Greg Wooledge wrote:
On Wed, Mar 06, 2024 at 12:31:46PM -0500, Roy J. Tellason, Sr. wrote:
Mine shows:
Local time: Wed 2024-03-06 12:09:44 EST
Universal time: Wed 2024-03-06 17:09:44 UTC
RTC time: Wed 2024-03-06 17:20:53
Time zone: America/New_York
On 3/6/24 13:37, Teemu Likonen wrote:
It seems that you have solved the problem but here is another hint.
"timedatectl" is a good high-level tool for querying and adjusting time
settings. Without command-line arguments it prints a lot of useful info:
$ t
On Wed 06 Mar 2024 at 07:07:36 (-0500), Greg Wooledge wrote:
> On Wed, Mar 06, 2024 at 07:37:09AM +0200, Teemu Likonen wrote:
> > It seems that you have solved the problem but here is another hint.
> > "timedatectl" is a good high-level tool for querying and adjusting t
On Wed, Mar 6, 2024 at 7:08 AM Greg Wooledge wrote:
>
> On Wed, Mar 06, 2024 at 07:37:09AM +0200, Teemu Likonen wrote:
> > It seems that you have solved the problem but here is another hint.
> > "timedatectl" is a good high-level tool for querying and adjusting time
&
ct time by 8 hours though difference between universal and local
> > > is ok.
> >
> > It seems that you have solved the problem but here is another hint.
> > "timedatectl" is a good high-level tool for querying and adjusting time
> > settings. Without c
On Wed, Mar 06, 2024 at 12:31:46PM -0500, Roy J. Tellason, Sr. wrote:
> Mine shows:
>
> Local time: Wed 2024-03-06 12:09:44 EST
> Universal time: Wed 2024-03-06 17:09:44 UTC
> RTC time: Wed 2024-03-06 17:20:53
>Time zone: America/New_York (EST, -0500)
> Network time on:
* 2024-03-06 12:31:46-0500, Roy J. Tellason, Sr. wrote:
> Local time: Wed 2024-03-06 12:09:44 EST
> Universal time: Wed 2024-03-06 17:09:44 UTC
> RTC time: Wed 2024-03-06 17:20:53
>Time zone: America/New_York (EST, -0500)
> Network time on: yes
> NTP synchronized: no
>
It seems that you have solved the problem but here is another hint.
> "timedatectl" is a good high-level tool for querying and adjusting time
> settings. Without command-line arguments it prints a lot of useful info:
>
> $ timedatectl
>Local time
not encountered this
particular problem before.
Are you "abnormal.att.net"? Or at least pretending to be that host
in your error messages?
Or is your web browser going to that host, when you expected it to go
to localhost or something?
When I went to abnormal.att.net there was an index.html in /va
On Wed, Mar 06, 2024 at 08:21:11AM -0500, Stephen P. Molnar wrote:
> Not Found
>
> The requested URL was not found on this server.
> Apache/2.4.57 (Debian) Server at abnormal.att.net Port 80
>
> I've installed WebMO a number of times and have not encountered this
> part
Am 06.03.2024 schrieb "Stephen P. Molnar" :
> The requested URL was not found on this server.
> Apache/2.4.57 (Debian) Server at abnormal.att.net Port 80
Check the apache config.
What is the Webroot?
Is the file you are looking for available in the webroot?
I am running a new installation of Bookworm and have encountered a 404
Not Found error problem with WebMO (https://www.webmo.net):
Not Found
The requested URL was not found on this server.
Apache/2.4.57 (Debian) Server at abnormal.att.net Port 80
I've installed WebMO a number of times
On Wed, Mar 06, 2024 at 07:37:09AM +0200, Teemu Likonen wrote:
> It seems that you have solved the problem but here is another hint.
> "timedatectl" is a good high-level tool for querying and adjusting time
> settings. Without command-line arguments it prints a
* 2024-03-06 02:47:06+0800, hlyg wrote:
> my newly-installed deb11 for amd64 shows wrong time, it lags behind
> correct time by 8 hours though difference between universal and local
> is ok.
It seems that you have solved the problem but here is another hint.
"timedatectl" i
On Tue, Mar 5, 2024 at 7:07 PM hlyg wrote:
>
> [...]
>
> Windows shall not cause problem, i rarely use Windows
>
> i don't know if ntp is running, what's default configuration by deb11
> amd64 installer?
If you are dual booting Linux and Windows, then see
<https://
Thank Greg Wooledge! it's solved with your help
i reboot to enter bios, it use UTC
then i change 3rd line of /etc/adjtime to UTC, reboot to take effect,
time is shown correctly now
i am timezone 0800, 8 hours ahead of GMT
both /etc/localtime points to same place
the 8:13:23 PM
from the second.
> Windows shall not cause problem, i rarely use Windows
The question isn't how often you use it, but whether you booted it in
between the two instances above. Probably not, I suppose.
> i don't know if ntp is running, what's default configuration b
i run only deb11 for i386 and amd64 on this machine, other OS
shall not cause problem
deb11 for amd64, it's wrong, utc lag behind by 4 hours
Windows shall not cause problem, i rarely use Windows
i don't know if ntp is running, what's default configuration by deb11
amd64 installer?
On Wed, 6 Mar 2024 02:47:06 +0800
hlyg wrote:
> wifi connection is good, i suppose both correct time with server
> automatically
Not necessarily. You should install an NTP client if you haven't
already. I suggest systemd-timesyncd.
--
Does anybody read signatures any more?
On Wed, Mar 06, 2024 at 02:47:06AM +0800, hlyg wrote:
> my newly-installed deb11 for amd64 shows wrong time, it lags behind correct
> time by 8 hours though difference between universal and local is ok.
Run the commands "date" and "date -u" and show us the output.
Then tell us what you think
my newly-installed deb11 for amd64 shows wrong time, it lags behind
correct time by 8 hours though difference between universal and local is
ok.
i am normal user, i install only from main of deb11 plus wifi adapter
firmware, though i don't install security update. i don't know where i
can
On Tue, Mar 5, 2024 at 11:30 AM Jeffrey Walton wrote:
>
> On Tue, Mar 5, 2024 at 11:22 AM genti pp wrote:
> >
> > I want to install debian 12 but I need to try it first.
> > Having Debian 12 live iso it asks me for username and password. Please tell
> > me the correct username and password so I
Hello.
Default login and password for the Debian live is user / live
2024-03-05, an, 18:22 genti pp rašė:
>
> Hello!
> I want to install debian 12 but I need to try it first.
> Having Debian 12 live iso it asks me for username and password. Please tell
> me the correct username and password so
On Tue, Mar 5, 2024 at 11:22 AM genti pp wrote:
>
> I want to install debian 12 but I need to try it first.
> Having Debian 12 live iso it asks me for username and password. Please tell
> me the correct username and password so I can try it.
I usually use 'sudo su -' from the command line.
On Tue, 5 Mar 2024 15:09:34 +0100
Mansour Nasri wrote:
Hello Mansour,
>Hi I'm using debian 12 in Lenovo yoga legion core i5 12th-gen with
>Nvidia
{cut}
You asked this, or a very similar question, on 29 Feb. You had two
responses that I saw. I suggest you review those replies and respond
On Tue, Mar 05 2024 at 02:28:08 PM, genti pp wrote:
> Hello!
> I want to install debian 12 but I need to try it first.
> Having Debian 12 live iso it asks me for username and password. Please tell
> me the correct username and password so I can try it.
> Thank you in advance!
username: user
are disabled )of course, the PC wake up but the screen is totally
black nothing displayed on the screen, ( installed Nvidia drivers from the
APT repo ) and is same problem.
"on my old PC dell i7 10th ( no additional GPU ) i never had this kind of
issue", please help to resolve this proble
Hello!
I want to install debian 12 but I need to try it first.
Having Debian 12 live iso it asks me for username and password. Please tell
me the correct username and password so I can try it.
Thank you in advance!
On 3/1/24 1:38 PM, Byunghee HWANG wrote:
RTX 3050
this is a nvidia product, hang is usual with this shit.
may be you can try nouveau drivers (to replace nvidia drivers), and hope you
will have a solution.
https://duckduckgo.com/?q=RTX+3050+linux+resume+hang <-- there is some way to
search
time the PC turns on suspend mode, (
> fastboot are disabled )of course, on my old PC dell i7 10th I
> never had this kind of issue, but this it it's the case, please help to
> resolve this problem I really don't want to back to windows anymore. Thank
> you so much
What is your
debian 12 on this PC,
> > …
> >
> > Sent from Yahoo Mail for iPhone
>
> Apparently some people haven't noticed that this is a near duplicate of
> this recent email on the list:
>
> From: Mansour Nasri
> To: debian-user@lists.debian.org
> Subject: Problem of suspend acti
haven't noticed that this is a near duplicate of
this recent email on the list:
From: Mansour Nasri
To: debian-user@lists.debian.org
Subject: Problem of suspend activities ( debian 12 )
Date: Thu, 29 Feb 2024 09:38:05 +0100
The main difference, as far as I can see, it the sender's email
address. Troll?
ing shutting down and this each time the PC turns
> on suspend mode, ( fastboot are disabled )of course, on my old PC
> dell i7 10th I never had this kind of issue, but this it it's the
> case, please help to resolve this problem I really don't want to
> back to windows anymore. Thank you
ntil forcing shutting down and this each time the PC turns on
> suspend mode, ( fastboot are disabled )of course, on my old PC dell
> i7 10th I never had this kind of issue, but this it it's the case,
> please help to resolve this problem I really don't want to back to
> windows an
are disabled )of course, on my old PC dell i7 10th I never had this
kind of issue, but this it it's the case, please help to resolve this problem I
really don't want to back to windows anymore. Thank you so much
Sent from Yahoo Mail for iPhone
s PC,
> > When the PC is on sleep mode ( suspend ) it's doesn't wake up anymore
> > until forcing shutting down and this each time the PC turns on
> > suspend mode, ( fastboot are disabled )of course, on my old PC dell
> > i7 10th I never had this kind of issue, but this it it's the ca
ing shutting down and this each time the PC turns on
> suspend mode, ( fastboot are disabled )of course, on my old PC dell
> i7 10th I never had this kind of issue, but this it it's the case,
> please help to resolve this problem I really don't want to back to
> windows anymore. Thank you
are disabled )of course, on my old PC dell i7 10th I never had
this kind of issue, but this it it's the case, please help to resolve this
problem I really don't want to back to windows anymore. Thank you so much
Henning Follmann wrote on 22/02/2024 08:43:
You didn't answer where you read that. I would be interested in that. I do
not claim to be an expert on this and I would like to understand it better.
-H
Concededly, I didn't noted that down. It was a discussion like in this blog:
On Wed, Feb 21, 2024 at 05:15:55PM +0100, Jörg-Volker Peetz wrote:
> Henning Follmann wrote on 21/02/2024 14:16:
> > On Wed, Feb 21, 2024 at 12:00:17PM +0100, Jörg-Volker Peetz wrote:
>
> > > Somewhere I read, for maintainance of an SSD all it's cells should be read
> > > from time to time like
On Wed, Feb 21, 2024 at 05:15:55PM +0100, Jörg-Volker Peetz wrote:
> Henning Follmann wrote on 21/02/2024 14:16:
> > On Wed, Feb 21, 2024 at 12:00:17PM +0100, Jörg-Volker Peetz wrote:
>
> > > Somewhere I read, for maintainance of an SSD all it's cells should be read
> > > from time to time like
On 2/21/24 08:17, Henning Follmann wrote:
On Wed, Feb 21, 2024 at 12:00:17PM +0100, Jörg-Volker Peetz wrote:
Hi,
did you take a look at the smartctl output?
Somewhere I read, for maintainance of an SSD all it's cells should be read
from time to time like this
sudo dd if=/dev/DEVICE
On 2/21/24 13:14, David Christensen wrote:
On 2/21/24 03:00, Jörg-Volker Peetz wrote:
Hi,
did you take a look at the smartctl output?
Somewhere I read, for maintainance of an SSD all it's cells should be
read from time to time like this
sudo dd if=/dev/DEVICE of=/dev/null bs=8M
On 2/21/24 03:00, Jörg-Volker Peetz wrote:
Hi,
did you take a look at the smartctl output?
Somewhere I read, for maintainance of an SSD all it's cells should be
read from time to time like this
sudo dd if=/dev/DEVICE of=/dev/null bs=8M status=progress
where device is something like sda or
Henning Follmann wrote on 21/02/2024 14:16:
On Wed, Feb 21, 2024 at 12:00:17PM +0100, Jörg-Volker Peetz wrote:
Somewhere I read, for maintainance of an SSD all it's cells should be read
from time to time like this
sudo dd if=/dev/DEVICE of=/dev/null bs=8M status=progress
Where did you read
On Wed, Feb 21, 2024 at 12:00:17PM +0100, Jörg-Volker Peetz wrote:
> Hi,
>
> did you take a look at the smartctl output?
>
> Somewhere I read, for maintainance of an SSD all it's cells should be read
> from time to time like this
>
> sudo dd if=/dev/DEVICE of=/dev/null bs=8M status=progress
Hi,
did you take a look at the smartctl output?
Somewhere I read, for maintainance of an SSD all it's cells should be read from
time to time like this
sudo dd if=/dev/DEVICE of=/dev/null bs=8M status=progress
where device is something like sda or nvme0n1, especially if it was switched off
On Dienstag, 20. Februar 2024 06:58:31 -03 Eike Lantzsch ZP5CGE / KY4PZ
wrote:
> On Montag, 19. Februar 2024 21:48:52 -03 Andy Smith wrote:
> > Hi,
> >
> > On Mon, Feb 19, 2024 at 04:12:44PM -0300, Eike Lantzsch ZP5CGE /
> > KY4PZ
> wrote:
> > > The notorious red SATA cables - I threw them out
On Montag, 19. Februar 2024 21:48:52 -03 Andy Smith wrote:
> Hi,
>
> On Mon, Feb 19, 2024 at 04:12:44PM -0300, Eike Lantzsch ZP5CGE / KY4PZ
wrote:
> > The notorious red SATA cables - I threw them out long ago. The red
> > pigment eats up the fine copper threads, changing the impedance of
> > the
On 20/2/24 08:48, Andy Smith wrote:
Hi,
On Mon, Feb 19, 2024 at 04:12:44PM -0300, Eike Lantzsch ZP5CGE / KY4PZ wrote:
The notorious red SATA cables - I threw them out long ago. The red
pigment eats up the fine copper threads, changing the impedance of the
cable and eventually making false
On 2/19/24 19:49, Andy Smith wrote:
Hi,
On Mon, Feb 19, 2024 at 04:12:44PM -0300, Eike Lantzsch ZP5CGE / KY4PZ wrote:
The notorious red SATA cables - I threw them out long ago. The red
pigment eats up the fine copper threads, changing the impedance of the
cable and eventually making false
Hi,
On Mon, Feb 19, 2024 at 04:12:44PM -0300, Eike Lantzsch ZP5CGE / KY4PZ wrote:
> The notorious red SATA cables - I threw them out long ago. The red
> pigment eats up the fine copper threads, changing the impedance of the
> cable and eventually making false contact before failing completely.
ry 8026MB (5267MB used)
> > Machine TypeDesktop
> > Operating SystemDebian GNU/Linux 12 (bookworm)
> >
> > I have been plagued with orphaned inodes. Last night the problem
> > cane to a head. When I reboot the computer, after an orphaned inode
> >
On Mon, Feb 19, 2024 at 12:30:30PM -0500, Stephen P. Molnar wrote:
[...]
> Thanks for he reply. It's somewhat reassuring.
>
> According to my logs the box had its' last major last upgrade in 2014, so I
> shouldn't be too surprised.
>
> My backup is underweight and should be done sometime
SystemDebian GNU/Linux 12 (bookworm)
I have been plagued with orphaned inodes. Last night the problem cane to a
head. When I reboot the computer, after an orphaned inode incident created
stop, it got as far as the user login. After the return I got the Windows
infamous blue screen. Restarting
Linux 12 (bookworm)
>
> I have been plagued with orphaned inodes. Last night the problem cane to a
> head. When I reboot the computer, after an orphaned inode incident created
> stop, it got as far as the user login. After the return I got the Windows
> infamous blue screen. Res
I am running up to date Bookworm on my Debian platform:
Processor AMD FX(tm)-8320 Eight-Core Processor
Memory 8026MB (5267MB used)
Machine TypeDesktop
Operating SystemDebian GNU/Linux 12 (bookworm)
I have been plagued with orphaned inodes. Last night the problem cane
On Sat, Feb 17 2024 at 01:34:05 PM, Lothar Braun wrote:
> Hi,
>
> I'm debugging a permission problem with the log files created by
> minidlna in /var/log/minidlna. I'm trying to use a different username
> to run minidlna and do not use the default user account minidlna. The
> p
On Sat, Feb 17, 2024 at 01:34:05PM +0100, Lothar Braun wrote:
> I'm debugging a permission problem with the log files created by minidlna in
> /var/log/minidlna. I'm trying to use a different username to run minidlna and
> do not use the default user account minidlna. The problem is
On 2/4/24 09:03, Marco Moock wrote:
Am 04.02.2024 um 07:12:50 Uhr schrieb Gremlin:
I also slay all the mDNS non sense.
mDNS works fine if the host names are properly set and no other way of
setting the addresses (Unicast DNS, /etc/hosts) is being used.
It is not needed if the network is
Am 04.02.2024 um 07:12:50 Uhr schrieb Gremlin:
> I also slay all the mDNS non sense.
mDNS works fine if the host names are properly set and no other way of
setting the addresses (Unicast DNS, /etc/hosts) is being used.
--
kind regards
Marco
Spam und Werbung bitte an
other IP addresses.
His "problem" could have been resolved by properly setting up a DNS
server. I also slay all the mDNS non sense.
# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-doc-reference' and `info' packages inst
On Fri, 2024-02-02 at 16:47 -0700, Charles Curley wrote:
> On Fri, 2 Feb 2024 15:52:41 -0700
> Charles Curley wrote:
>
> > But I don't think that will solve the routing problem.
>
> Well, I was wrong. That did solve the routing problems.
>
> I moved the apt-prox
Am 02.02.2024 um 17:12:06 Uhr schrieb Gremlin:
> On 2/2/24 16:28, Greg Wooledge wrote:
> > On Fri, Feb 02, 2024 at 02:03:46PM -0700, Charles Curley wrote:
> >> root@hawk:~# host samba
> >> samba.localdomain is an alias for hawk.localdomain.
> >> hawk.localdomain has address 192.168.100.6
> >
On Fri, 2 Feb 2024 15:52:41 -0700
Charles Curley wrote:
> But I don't think that will solve the routing problem.
Well, I was wrong. That did solve the routing problems.
I moved the apt-proxy line for the VMs' benefit into a VM's /etc/hosts
and took it out of hawk's /etc/hosts. samba is
you need different name resolution depending on whether you're
> running on the host vs. running on the guest, then I would imagine
> there is some well-known way to define that. Perhaps a different
> hosts file that's only used by guests? I don't know virtualization
> stuff well.
Yup. I
On 2/2/24 16:28, Greg Wooledge wrote:
On Fri, Feb 02, 2024 at 02:03:46PM -0700, Charles Curley wrote:
root@hawk:~# host samba
samba.localdomain is an alias for hawk.localdomain.
hawk.localdomain has address 192.168.100.6
host(1) looks in DNS only. It doesn't do the standard name resolution
> > > # For the benefit of virtual machines.
> > > 192.168.100.12 apt-proxy
> > > 192.168.122.1 samba samba.localdomain
> >
> > And that's where it came from (/etc/hosts). If this IP address is
> > wrong, then it shouldn't be in here.
>
> Gnrrr. It's right for the virtual network
1 - 100 of 43182 matches
Mail list logo
