Re: strange time problem with bullseye

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: > > > >

Re: strange time problem with bullseye/buster

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.

Re: strange time problem with bullseye/buster

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 pac

Re: strange time problem with bullseye/buster

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 > > > > remo

Re: strange time problem with bullseye

On 3/7/24 14:16, Roy J. Tellason, Sr. wrote: On Wednesday 06 March 2024 12:42:12 pm Greg Wooledge wrote: How do I get the RTC to agree with the right time? "hwclock -w" to copy the system clock to the hardware clock (RTC).  This should also be done during shutdown, but it doesn't hurt to do it

Re: strange time problem with bullseye/buster

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 pa

Re: strange time problem with bullseye

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: l

Re: strange time problem with bullseye

Roy J. Tellason, Sr. wrote: > I don't ordinarily shut this machine down for the most part. Every once in a > while all of my swap partition gets filled up, and then there's this > continuous hard drive activity that I'm assuming is what they mean by > "thrashing". The only option at that poin

Re: strange time problem with bullseye

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: enabl

Re: strange time problem with bullseye

On Wednesday 06 March 2024 12:42:12 pm Greg Wooledge wrote: > > How do I get the RTC to agree with the right time? > > "hwclock -w" to copy the system clock to the hardware clock (RTC).  This > should also be done during shutdown, but it doesn't hurt to do it now. That seemed to do what I needed

Re: strange time problem with bullseye/buster

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 alway

Re: strange time problem with bullseye

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 systemd-

Re: strange time problem with bullseye

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 reboo

Re: strange time problem with bullseye

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 th

Re: strange time problem with bullseye

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 th

Re: strange time problem with bullseye

* 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 abou

Re: strange time problem with bullseye

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 h

Re: strange time problem with bullseye

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

Re: strange time problem with bullseye

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 acce

Re: strange time problem with bullseye

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 unlim

Re: strange time problem with bullseye

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 wa

Re: strange time problem with bullseye

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

Re: strange time problem with bullseye

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 N

Re: strange time problem with bullseye

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 > >

Re: strange time problem with bullseye

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 (E

Re: strange time problem with bullseye

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: $ timedatectl Local

Re: strange time problem with bullseye

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 time > > settings. Without com

Re: strange time problem with bullseye

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 > > settings. Without command-l

Re: strange time problem with bullseye

On Wed, Mar 6, 2024 at 12:13 PM Roy J. Tellason, Sr. wrote: > > On Wednesday 06 March 2024 12:37:09 am Teemu Likonen wrote: > > * 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 bet

Re: strange time problem with bullseye

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: ye

Re: strange time problem with bullseye

* 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 > RT

Re: strange time problem with bullseye

On Wednesday 06 March 2024 12:37:09 am Teemu Likonen wrote: > * 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 t

Re: strange time problem with bullseye

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 lot of useful info: > > $ timeda

Re: strange time problem with bullseye

* 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" is a good high-level to

Re: strange time problem with bullseye

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

Re: strange time problem with bullseye

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

Re: strange time problem with bullseye

On Tue, Mar 05, 2024 at 08:28:49PM +0800, hlyg wrote: > Thank Greg Wooledge! > > zhou@debian:~$ date > Wed 06 Mar 2024 04:07:02 AM CST > zhou@debian:~$ date -u > Tue 05 Mar 2024 08:07:07 PM UTC > > above is from deb11 for i386, it's correct OK, and your time zone is 20 hours ahead of UTC, it app

Re: strange time problem with bullseye

On 3/5/24 20:28, hlyg wrote: Thank Greg Wooledge! zhou@debian:~$ date Wed 06 Mar 2024 04:07:02 AM CST zhou@debian:~$ date -u Tue 05 Mar 2024 08:07:07 PM UTC above is from deb11 for i386, it's correct zhou@debian:~$ date Tue 05 Mar 2024 08:13:23 PM CST zhou@debian:~$ date -u Tue 05 Mar 2024 1

Re: strange time problem with bullseye

Thank Greg Wooledge! zhou@debian:~$ date Wed 06 Mar 2024 04:07:02 AM CST zhou@debian:~$ date -u Tue 05 Mar 2024 08:07:07 PM UTC above is from deb11 for i386, it's correct zhou@debian:~$ date Tue 05 Mar 2024 08:13:23 PM CST zhou@debian:~$ date -u Tue 05 Mar 2024 12:13:27 PM UTC above is from de

Re: strange time problem with bullseye

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? https://charlescur

Re: strange time problem with bullseye

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 the

strange time problem with bullseye

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 go

Re: Date time problem bookworm, fvwm....

On Sun, Oct 22, 2023 at 01:51:41PM +0200, Thomas Schmitt wrote: [...] > Originally it did only put out text in an xterm, but then i shamelessly > exploited code from the exploitation chain xpppload <- xisdnload <- xload > to give it a histogram in ain additional separate window. Now this one bea

Re: Date time problem bookworm, fvwm....

On Sun, Oct 22, 2023 at 07:50:54AM -0400, The Wanderer wrote: > On 2023-10-22 at 07:24, to...@tuxteam.de wrote: > > > I better not tell. My clock is a... shell script in a tiny Xterm > > which also shows my battery status. > > Ooo, that sounds interesting. I don't currently have a laptop, so the

Re: Date time problem bookworm, fvwm....

On 2023-10-22 at 07:24, to...@tuxteam.de wrote: > I better not tell. My clock is a... shell script in a tiny Xterm > which also shows my battery status. Ooo, that sounds interesting. I don't currently have a laptop, so the battery-status part wouldn't currently apply, but this sounds like somethi

Re: Date time problem bookworm, fvwm....

Hi, to...@tuxteam.de wrote: > My clock is a... shell script in a tiny Xterm which > also shows my battery status. My digital clock with date display is a C program which mainly watches the network traffic. It even has an own date format ("A0" = 2000, now is "C3") which has an odd history beginnin

Re: Date time problem bookworm, fvwm....

On Sun, Oct 22, 2023 at 11:16:25AM +0200, Thomas Schmitt wrote: > Hi, > > Charlie wrote: > > I removed the clock from the > > FVWM task bar and Gkrellm now dis[pays the right time. So a fix > > of sorts with which I can live. > > Congrats. :)) > > > > being a bit long in > > the tooth to start

Re: Date time problem bookworm, fvwm....

Hi, Charlie wrote: > I removed the clock from the > FVWM task bar and Gkrellm now dis[pays the right time. So a fix > of sorts with which I can live. Congrats. :)) > being a bit long in > the tooth to start relearning another window manager. I'm using fvwm since the last century. It's configur

Re: Date time problem bookworm, fvwm....

On Sun, 22 Oct 2023 10:13:59 +0200 "Thomas Schmitt" wrote: > Hi, > > Charlie wrote: > > The date on that system is one day in advance and one hour late. Not > > terrible, > > However after a short period 100% of one of the CPU cores is used, > > noisy running, and top -c shows this as the user:

Re: Date time problem bookworm, fvwm....

Hi, Charlie wrote: > The date on that system is one day in advance and one hour late. Not > terrible, > However after a short period 100% of one of the CPU cores is used, > noisy running, and top -c shows this as the user: > /usr/libexe/fvwm2/2.7.0/FvwmScript 17 4 none 0 8 FvwmScript DateTime Loo

Date time problem bookworm, fvwm....

Hello All, Have a a Dell Vostro laptop: Bookworm up to date and upgraded operating system to that state. Using FVWM window manager. The date on that system is one day in advance and one hour late. Not terrible, However after a short period 100% of one of the CPU

Re: jessie and stretch time problem

On Sun 14 Oct 2018 at 21:29:57 +0300, Reco wrote: > On Sun, Oct 14, 2018 at 07:18:12PM +0100, Brian wrote: > > > At present there is an effort to update documentation for buster. Get > > your bug report in. Don't delay! > > I'll consider your suggestion. Striking. Iron. Hot. #911020. -- Bria

Re: jessie and stretch time problem

Hi. On Sun, Oct 14, 2018 at 07:18:12PM +0100, Brian wrote: > On Sun 14 Oct 2018 at 17:21:43 +0300, Reco wrote: > > > Hi. > > > > On Sun, Oct 14, 2018 at 09:22:53AM -0400, Cindy-Sue Causey wrote: > > > On 10/14/18, to...@tuxteam.de wrote: > > > > On Sat, Oct 13, 2018 at 07:11:07AM +0

Re: jessie and stretch time problem

On Sun 14 Oct 2018 at 17:21:43 +0300, Reco wrote: > Hi. > > On Sun, Oct 14, 2018 at 09:22:53AM -0400, Cindy-Sue Causey wrote: > > On 10/14/18, to...@tuxteam.de wrote: > > > On Sat, Oct 13, 2018 at 07:11:07AM +, Long Wind wrote: > > >> Thank tomas! > > >> > > >> i run "cat /etc/adjtime"

Re: jessie and stretch time problem

Hi. On Sun, Oct 14, 2018 at 09:22:53AM -0400, Cindy-Sue Causey wrote: > On 10/14/18, to...@tuxteam.de wrote: > > On Sat, Oct 13, 2018 at 07:11:07AM +, Long Wind wrote: > >> Thank tomas! > >> > >> i run "cat /etc/adjtime" in jessie and it says LOCALbut in stretch > >> /etc/adjtime does

Re: jessie and stretch time problem

On 10/14/18, to...@tuxteam.de wrote: > On Sat, Oct 13, 2018 at 07:11:07AM +, Long Wind wrote: >> Thank tomas! >> >> i run "cat /etc/adjtime" in jessie and it says LOCALbut in stretch >> /etc/adjtime doesn't seem to exist > > I see. Perhaps this is the root of the problem. On the other > hand,

Re: jessie and stretch time problem

On Sat, Oct 13, 2018 at 07:11:07AM +, Long Wind wrote: > Thank tomas! > > i run "cat /etc/adjtime" in jessie and it says LOCALbut in stretch > /etc/adjtime doesn't seem to exist I see. Perhaps this is the root of the problem. On the other hand, perhaps, systemd is taking care of time in str

Re: (solved) Re: jessie and stretch time problem

On Sat 13 Oct 2018 at 19:51:07 (+), Curt wrote: > On 2018-10-13, Brian wrote: > > On Sat 13 Oct 2018 at 09:03:44 -0500, David Wright wrote: > >> On Sat 13 Oct 2018 at 07:27:57 (+), Long Wind wrote: > >> > Thank Teemu Likonen! > >> > You are right. My stretch and jessie think differently ab

Re: (solved) Re: jessie and stretch time problem

On 2018-10-13, Brian wrote: > On Sat 13 Oct 2018 at 09:03:44 -0500, David Wright wrote: > >> On Sat 13 Oct 2018 at 07:27:57 (+), Long Wind wrote: >> > Thank Teemu Likonen! >> > You are right. My stretch and jessie think differently about hardware >> > clock. >> > i run "timedatectl set-local-

Re: (solved) Re: jessie and stretch time problem

On Sat 13 Oct 2018 at 09:03:44 -0500, David Wright wrote: > On Sat 13 Oct 2018 at 07:27:57 (+), Long Wind wrote: > > Thank Teemu Likonen! > > You are right. My stretch and jessie think differently about hardware clock. > > i run "timedatectl set-local-rtc 1", it should be ok for both now. > >

Re: (solved) Re: jessie and stretch time problem

On Sat 13 Oct 2018 at 07:27:57 (+), Long Wind wrote: > Thank Teemu Likonen! > You are right. My stretch and jessie think differently about hardware clock. > i run "timedatectl set-local-rtc 1", it should be ok for both now. > though there's warning, i think it's ok Because China doesn't use Da

Re: jessie and stretch time problem

Long Wind [2018-10-12 21:59:40Z] wrote: > jessie and stretch are installed on same PCtime of jessie is wrong: > Fri Oct 12 21:51:05 CST 2018then i reboot and enter stretch time of > stretch is right: Sat Oct 13 05:55:30 CST 2018 tzdata of both are > reconfig to same place As others have pointed o

Re: jessie and stretch time problem

On Fri, Oct 12, 2018 at 10:32:16PM +, Long Wind wrote: > Thanks! How could I find out  if debian thinks bios clock is set to local > time or universal time? This is one way to do it: tomas@trotzki:~$ cat /etc/adjtime 0.00 1539378883 0.00 1539378883 UTC The last line will te

Re: jessie and stretch time problem

On Fri, Oct 12, 2018 at 6:32 PM Long Wind wrote: > Thanks! How could I find out if debian thinks bios clock is set to local > time or universal time? > I looked it up. Even though Arch Linux isn't Debian, I respect them, for giving good, technical details about Linux Concepts. Here's a Link:

Re: jessie and stretch time problem

On Fri, Oct 12, 2018 at 6:01 PM Long Wind wrote: > jessie and stretch are installed on same PC > time of jessie is wrong: Fri Oct 12 21:51:05 CST 2018 > then i reboot and enter stretch > time of stretch is right: Sat Oct 13 05:55:30 CST 2018 > > tzdata of both are reconfig to same place > Is it

Re: How to get Jessie to run at boot time -- Problem solved

On Thu 15 Sep 2016 at 19:07:46 +0100, Lisi Reisz wrote: > On Thursday 15 September 2016 13:38:49 Brian wrote: > > On Thu 15 Sep 2016 at 11:01:12 +0100, Lisi Reisz wrote: > > > Are you deliberately remaining uncontactable off list? You must be > > > sending > > > > I am not uncontactable. > > > >

Re: How to get Jessie to run at boot time -- Problem solved

On Thursday 15 September 2016 13:38:49 Brian wrote: > On Thu 15 Sep 2016 at 11:01:12 +0100, Lisi Reisz wrote: > > Are you deliberately remaining uncontactable off list? You must be > > sending > > I am not uncontactable. > > > from one email address and receiving to another, since the email addres

Re: How to get Jessie to run at boot time -- Problem solved

On Thu 15 Sep 2016 at 11:01:12 +0100, Lisi Reisz wrote: > Are you deliberately remaining uncontactable off list? You must be sending I am not uncontactable. > from one email address and receiving to another, since the email address > still doesn't work, and you are getting list emails. The

Re: How to get Jessie to run at boot time -- Problem solved

On Thursday 15 September 2016 00:50:25 Brian wrote: > On Thu 15 Sep 2016 at 00:33:09 +0100, Lisi Reisz wrote: > > On Wednesday 14 September 2016 23:09:12 Brian wrote: > > > >        Ah. That's good.  Your E-mail reader seems to respect my > > > > indentations.  Others don't, alas.  Do you perchance

Re: How to get Jessie to run at boot time -- Problem solved

- Original Message - From: "Brian" To: debian-user@lists.debian.org Sent: Wednesday, September 14, 2016 5:09:12 PM Subject: Re: How to get Jessie to run at boot time -- Problem solved > What is "unenlightening" to you may not be unenlightening to others; >

Re: How to get Jessie to run at boot time -- Problem solved

On Thu 15 Sep 2016 at 00:33:09 +0100, Lisi Reisz wrote: > On Wednesday 14 September 2016 23:09:12 Brian wrote: > > >        Ah. That's good.  Your E-mail reader seems to respect my > > > indentations.  Others don't, alas.  Do you perchance use mutt? > > Indentations count as formatting. Plain te

Re: How to get Jessie to run at boot time -- Problem solved

On Wednesday 14 September 2016 23:09:12 Brian wrote: > >        Ah. That's good.  Your E-mail reader seems to respect my > > indentations.  Others don't, alas.  Do you perchance use mutt? Indentations count as formatting. Plain text is supposed not to preserve formatting. Lisi

Re: How to get Jessie to run at boot time -- Problem solved

On Wed 14 Sep 2016 at 17:11:26 -0400, Alan McConnell wrote: Alan McConnell's responses are indented and begin with >. > From: "Brian" Brian's resonses are not indented. > > > Yep. I have been back to my Jessie in the meantime, and run > > os-prober. > > I didn't attempt to

Re: How to get Jessie to run at boot time -- Problem solved

- Original Message - From: "Brian" To: debian-user@lists.debian.org Sent: Wednesday, September 14, 2016 1:51:50 PM Subject: Re: How to get Jessie to run at boot time -- Problem solved On Wed 14 Sep 2016 at 11:34:31 -0400, Alan McConnell wrote: > From: "Felix Miata&q

Re: How to get Jessie to run at boot time -- Problem solved

- Original Message - From: "Lisi Reisz" To: debian-user@lists.debian.org Sent: Wednesday, September 14, 2016 2:05:47 PM Subject: Re: How to get Jessie to run at boot time -- Problem solved On Wednesday 14 September 2016 19:51:50 Brian wrote: > You are probably asking the w

Re: How to get Jessie to run at boot time -- Problem solved

On Wednesday 14 September 2016 19:51:50 Brian wrote: > You are probably asking the wrong question. Oh, no, Brian. He is asking the right question by definition. Alan is asking it, it is therefore right. We are providing the wrong answers. And to make matters worse we are doing so in Old Engl

Re: How to get Jessie to run at boot time -- Problem solved

On Wed 14 Sep 2016 at 11:34:31 -0400, Alan McConnell wrote: > From: "Felix Miata" > > It does seem curious that the Debian installer would need knowledge of a > particular Windows version in order to provide a boot menu selection for it, > rather than simply having one that says "Windows", boo

Re: How to get Jessie to run at boot time -- Problem solved

On Wednesday 14 September 2016 16:34:31 Alan McConnell wrote: > - Original Message - > From: "Felix Miata" > To: debian-user@lists.debian.org > Sent: Wednesday, September 14, 2016 1:44:14 AM > Subject: Re: How to get Jessie to run at boot time -- Problem solved &g

Re: How to get Jessie to run at boot time -- Problem solved

- Original Message - From: "Felix Miata" To: debian-user@lists.debian.org Sent: Wednesday, September 14, 2016 1:44:14 AM Subject: Re: How to get Jessie to run at boot time -- Problem solved Alan McConnell composed on 2016-09-13 20:50 (UTC-0400): > when my home Debian in

Re: How to get Jessie to run at boot time -- Problem solved

On Wed 14 Sep 2016 at 02:44:14 -0400, Felix Miata wrote: > Alan McConnell composed on 2016-09-13 20:50 (UTC-0400): > ... > >But maybe someone > >can tell me why the installer can't look at the partitions and determine > >that there > >is some kind of OS already installed? Why does it have to kno

Re: How to get Jessie to run at boot time -- Problem solved

On Wednesday 14 September 2016 01:50:44 Alan McConnell wrote: >Re Royal Holloway: boys were added in 1966, a year before my time > there. But there were always male faculty there, especially in math, which > subject has, most unfortunately, suffered from a dearth of qualified women. > Th

Re: How to get Jessie to run at boot time -- Problem solved

On Wednesday 14 September 2016 01:50:44 Alan McConnell wrote: > More perhaps tomorrow.  I have tasks to perform before bed.  But maybe > someone can tell me why the installer can't look at the partitions and > determine that there is some kind of OS already installed?  Why does it > have to know ab

Re: How to get Jessie to run at boot time -- Problem solved

Alan McConnell composed on 2016-09-13 20:50 (UTC-0400): Lisi Reisz composed: Gene Heskett wrote: Now I am going to push back Alan. If you are going to come in here and berate folks about this and that, the first thing you need to do is to train your email agent (wth is "X-Mailer: Zim

Re: How to get Jessie to run at boot time -- Problem solved

- Original Message - From: "Lisi Reisz" To: debian-user@lists.debian.org Sent: Tuesday, September 13, 2016 3:58:01 PM Subject: Re: How to get Jessie to run at boot time -- Problem solved On Tuesday 13 September 2016 18:24:07 Gene Heskett wrote: > On Tuesday 13 September

Re: How to get Jessie to run at boot time -- Problem solved

On Tue 13 Sep 2016 at 21:02:01 (+0100), Lisi Reisz wrote: > On Tuesday 13 September 2016 20:30:20 Brian wrote: > > > A final question:  I've used Wiktionary to learn that 'whinging' is the > > > English for what we Murricans call 'whining'.  Is it used a lot nowadays? > > >  I don't recall ever hav

Re: How to get Jessie to run at boot time -- Problem solved

On Tuesday 13 September 2016 18:24:07 Gene Heskett wrote: > On Tuesday 13 September 2016 08:57:19 Alan McConnell wrote: > > Warning: This E-mail is for the most part in the nature of a pushback > > against various insinuations that have been made. > > Now I am going to push back Alan. > > If you a

Re: How to get Jessie to run at boot time -- Problem solved

On Tuesday 13 September 2016 20:30:20 Brian wrote: > > A final question:  I've used Wiktionary to learn that 'whinging' is the > > English for what we Murricans call 'whining'.  Is it used a lot nowadays? > >  I don't recall ever having heard it when I taught at Royal Holloway > > College back in 1

Re: How to get Jessie to run at boot time -- Problem solved

On Mon 12 Sep 2016 at 14:14:53 (-0400), Alan McConnell wrote: > - Original Message - > From: "Felix Miata" > Sent: Sunday, September 11, 2016 10:14:26 PM > Subject: Re: How to get Jessie to run at boot time -- Problem solved > > David Wright composed o

Re: How to get Jessie to run at boot time -- Problem solved

On Tue 13 Sep 2016 at 13:01:58 -0400, Alan McConnell wrote: > You were asked for some information. You declined to provide it. As a > route to solving a technical problem your response leaves a lot to be > desired. > Did you read why I declined? I repeat my reason for your benefit: I im

Re: How to get Jessie to run at boot time -- Problem solved

On Sun 11 Sep 2016 at 23:14:26 (-0400), Felix Miata wrote: > David Wright composed on 2016-09-11 21:44 (UTC-0500): > ... > >>Subject: Re: How to get Jessie to run at boot time -- Problem solved > ... > How is it beneficial to list anyone here or searching list archives >

Re: How to get Jessie to run at boot time -- Problem solved

On Tuesday 13 September 2016 08:57:19 Alan McConnell wrote: > Warning: This E-mail is for the most part in the nature of a pushback > against various insinuations that have been made. > Now I am going to push back Alan. If you are going to come in here and berate folks about this and that, the

Re: How to get Jessie to run at boot time -- Problem solved

On Tuesday 13 September 2016 18:01:58 Alan McConnell wrote: > > Finally:  I have taken a resolution not to respond to further > > chastisement or smarm. Please help me to keep it! What a pity you didn't! What happened to your self control?? Lisi

Re: How to get Jessie to run at boot time -- Problem solved

- Original Message - From: "Brian" To: debian-user@lists.debian.org Sent: Tuesday, September 13, 2016 9:40:11 AM Subject: Re: How to get Jessie to run at boot time -- Problem solved On Tue 13 Sep 2016 at 08:57:19 -0400, Alan McConnell wrote: > Warning: This E-mail is

Re: How to get Jessie to run at boot time -- Problem solved

On Tue 13 Sep 2016 at 08:57:19 -0400, Alan McConnell wrote: > Warning: This E-mail is for the most part in the nature of a pushback against > various insinuations that have been made. Warning duly noted; most of this mail is snipped so we can concentrate on the technical aspects of your issue.

Re: How to get Jessie to run at boot time -- Problem solved

un at boot time -- Problem solved On Monday 12 September 2016 19:14:53 Alan McConnell wrote: > Maybe I should apologize for "hijacking a thread"? Yes, you should. It has left the person whose thread you have hijacked high and dry. It is most definitely "not done" to hijack t

Re: How to get Jessie to run at boot time -- Problem solved

On Monday 12 September 2016 19:14:53 Alan McConnell wrote: > Maybe I should apologize for "hijacking a thread"? Yes, you should. It has left the person whose thread you have hijacked high and dry. It is most definitely "not done" to hijack threads. By those who care about etiquette and other

Re: How to get Jessie to run at boot time -- Problem solved

On Mon 12 Sep 2016 at 14:14:53 -0400, Alan McConnell wrote: > From: "Felix Miata" > ... > How is it beneficial to list anyone here or searching list archives to > continue a thread by chastising an OP for being imperfect more than 12 hours > after OP added string "solved" to the subject and tha

Re: How to get Jessie to run at boot time -- Problem solved

- Original Message - From: "Felix Miata" To: debian-user@lists.debian.org Sent: Sunday, September 11, 2016 10:14:26 PM Subject: Re: How to get Jessie to run at boot time -- Problem solved David Wright composed on 2016-09-11 21:44 (UTC-0500): ... >> Subject: Re: How to g

Re: How to get Jessie to run at boot time -- Problem solved

On Sunday 11 September 2016 20:51:50 Brian wrote: > On Sun 11 Sep 2016 at 15:17:00 -0400, Alan McConnell wrote: > > On Sun 11 Sep 2016 at 11:13:45 -0400, Alan McConnell wrote: > > > Addendum: during my Jessie install, the install program commented at > > > one point: "There doesn't seem to be any

Re: How to get Jessie to run at boot time -- Problem solved

On Sun 11 Sep 2016 at 23:14:26 -0400, Felix Miata wrote: > David Wright composed on 2016-09-11 21:44 (UTC-0500): > ... > >>Subject: Re: How to get Jessie to run at boot time -- Problem solved > ... > How is it beneficial to list anyone here or searching list archives to &

  1   2   >