On 12/10/18 2:10 PM, Rick Stevens wrote:
> On 12/10/18 1:01 PM, Stephen Morris wrote:
>> On 7/12/18 9:10 am, Ed Greshko wrote:
>>> On 12/7/18 4:33 AM, Stephen Morris wrote:
Thanks Ed, I'll try that again.
I am using a vpn called Slickvpn. I did download *.ovpn files for
each
On 12/10/18 1:01 PM, Stephen Morris wrote:
> On 7/12/18 9:10 am, Ed Greshko wrote:
>> On 12/7/18 4:33 AM, Stephen Morris wrote:
>>> Thanks Ed, I'll try that again.
>>>
>>> I am using a vpn called Slickvpn. I did download *.ovpn files for
>>> each location but I
>>> didn't issue the command you
On 12/11/18 5:01 AM, Stephen Morris wrote:
> How do I find out why the Networkmanager dialog won't show them?
I don't know.
Why don't you just go to the slickVPN site and download them from there?
--
Right: I dislike the default color scheme Wrong: What idiot picked the default
color scheme
On 7/12/18 9:10 am, Ed Greshko wrote:
On 12/7/18 4:33 AM, Stephen Morris wrote:
Thanks Ed, I'll try that again.
I am using a vpn called Slickvpn. I did download *.ovpn files for each location
but I
didn't issue the command you mentioned. I manually created the vpn definitions
in
network
On 12/7/18 4:33 AM, Stephen Morris wrote:
> Thanks Ed, I'll try that again.
>
> I am using a vpn called Slickvpn. I did download *.ovpn files for each
> location but I
> didn't issue the command you mentioned. I manually created the vpn
> definitions in
> network manager and manually populated
On 5/12/18 11:18 pm, Ed Greshko wrote:
On 12/5/18 5:20 AM, Ed Greshko wrote:
On 12/5/18 4:41 AM, Stephen Morris wrote:
The vpn I'm using, which operates through Openvpn, has servers all over the
world
Kindly tell us which VPN service you are using.
Oh, and I should have also added this
On 12/5/18 5:20 AM, Ed Greshko wrote:
> On 12/5/18 4:41 AM, Stephen Morris wrote:
>> The vpn I'm using, which operates through Openvpn, has servers all over the
>> world
> Kindly tell us which VPN service you are using.
>
Oh, and I should have also added this
The service you're using most
On 12/5/18 4:41 AM, Stephen Morris wrote:
> The vpn I'm using, which operates through Openvpn, has servers all over the
> world
Kindly tell us which VPN service you are using.
--
Right: I dislike the default color scheme Wrong: What idiot picked the default
color scheme
On 28/11/18 8:51 am, Rick Stevens wrote:
On 11/27/18 12:48 PM, Stephen Morris wrote:
On 27/11/18 10:53 am, Rick Stevens wrote:
On 11/26/18 1:46 PM, Stephen Morris wrote:
On 21/11/18 10:02 am, Rick Stevens wrote:
On 11/20/18 2:09 PM, Ed Greshko wrote:
On 11/21/18 5:07 AM, Stephen Morris
On 11/27/18 12:48 PM, Stephen Morris wrote:
> On 27/11/18 10:53 am, Rick Stevens wrote:
>> On 11/26/18 1:46 PM, Stephen Morris wrote:
>>> On 21/11/18 10:02 am, Rick Stevens wrote:
On 11/20/18 2:09 PM, Ed Greshko wrote:
> On 11/21/18 5:07 AM, Stephen Morris wrote:
>> A second, smaller
On 27/11/18 10:53 am, Rick Stevens wrote:
On 11/26/18 1:46 PM, Stephen Morris wrote:
On 21/11/18 10:02 am, Rick Stevens wrote:
On 11/20/18 2:09 PM, Ed Greshko wrote:
On 11/21/18 5:07 AM, Stephen Morris wrote:
Given that the front screen of the bios is displaying the time as
local time,
On Tue, 2018-11-27 at 08:46 +1100, Stephen Morris wrote:
> At the moment my main OS is Windows as I spend a fair amount of time
> playing online games that can't be played under Linux, so I mainly only
> boot to Linux for email processing, until such time as I decide to forgo
> the gaming
On 11/26/18 1:46 PM, Stephen Morris wrote:
> On 21/11/18 10:02 am, Rick Stevens wrote:
>> On 11/20/18 2:09 PM, Ed Greshko wrote:
>>> On 11/21/18 5:07 AM, Stephen Morris wrote:
Given that the front screen of the bios is displaying the time as
local time, presumably
that means
On 11/27/18 5:46 AM, Stephen Morris wrote:
> I haven't investigated recently the ability of VM's to provide the necessary
> hardware
> graphics quality for gaming, but the last time I
> looked at this possibility the graphics capabilities weren't up to scratch.
That is correct.
If Windows is
On 27/11/18 8:45 am, Lester M Petrie wrote:
On 11/26/2018 4:25 PM, Stephen Morris wrote:
On 21/11/18 9:09 am, Ed Greshko wrote:
question is obvious.
Having installed the motherboard over 12 months ago and not touched
the time settings since, it wasn't until two days ago that I
realised,
On 21/11/18 10:02 am, Rick Stevens wrote:
On 11/20/18 2:09 PM, Ed Greshko wrote:
On 11/21/18 5:07 AM, Stephen Morris wrote:
Given that the front screen of the bios is displaying the time as local time,
presumably
that means that the time settings in the bios are local time and the
On 11/26/2018 4:25 PM, Stephen Morris wrote:
On 21/11/18 9:09 am, Ed Greshko wrote:
question is obvious.
Having installed the motherboard over 12 months ago and not touched the
time settings since, it wasn't until two days ago that I realised,
through trial and error, that the bios
On 21/11/18 9:09 am, Ed Greshko wrote:
On 11/21/18 5:07 AM, Stephen Morris wrote:
Given that the front screen of the bios is displaying the time as local time,
presumably
that means that the time settings in the bios are local time and the
motherboard bios
doesn't provide any means to input
On 11/21/18 7:02 AM, Rick Stevens wrote:
> That's just the way it is (unfortunately).
And one of the myriad of reasons I don't dual boot with Windows. VM's are good
enough for
the few times I've got no choice in the matter.
--
Right: I dislike the default color scheme Wrong: What idiot
On 11/20/18 2:09 PM, Ed Greshko wrote:
> On 11/21/18 5:07 AM, Stephen Morris wrote:
>>
>>
>> Given that the front screen of the bios is displaying the time as local
>> time, presumably
>> that means that the time settings in the bios are local time and the
>> motherboard bios
>> doesn't provide
On 11/21/18 5:07 AM, Stephen Morris wrote:
>
>
> Given that the front screen of the bios is displaying the time as local time,
> presumably
> that means that the time settings in the bios are local time and the
> motherboard bios
> doesn't provide any means to input the time as GMT, hence the
On 11/20/18 1:07 PM, Stephen Morris wrote:
> On 19/11/18 10:13 am, Ed Greshko wrote:
>> On 11/19/18 5:08 AM, Stephen Morris wrote:
>>> From recollection, which may not be completely accurate, the Asrock
>>> motherboard that I
>>> have now is the first motherboard I've had where the bios has not
On 11/20/2018 02:07 PM, Stephen Morris wrote:
Given that the front screen of the bios is displaying the time as local
time, presumably that means that the time settings in the bios are local
time and the motherboard bios doesn't provide any means to input the
time as GMT, hence the bios is not
On 19/11/18 10:13 am, Ed Greshko wrote:
On 11/19/18 5:08 AM, Stephen Morris wrote:
From recollection, which may not be completely accurate, the Asrock
motherboard that I
have now is the first motherboard I've had where the bios has not offered a
setting to
set the system clock to GMT/Local,
On 11/18/18 1:22 PM, Stephen Morris wrote:
> On 16/11/18 12:17 pm, Rick Stevens wrote:
>> On 11/15/18 4:54 PM, Ed Greshko wrote:
>>> On 11/16/18 7:37 AM, Rick Stevens wrote:
On 11/15/18 3:00 PM, Joe Zeff wrote:
> On 11/15/2018 03:17 PM, Rick Stevens wrote:
>> In Linux
>> case, it
On 11/19/18 9:05 PM, Louis Lagendijk wrote:
> On Mon, 2018-11-19 at 06:24 +0800, Ed Greshko wrote:
>> On 11/19/18 5:51 AM, Stephen Morris wrote:
>>> Sure, but if the user is in the United Kingdom where they use GMT,
>>> then presumably they
>>> would run their entire system in GMT, whereas other
On Mon, 2018-11-19 at 06:24 +0800, Ed Greshko wrote:
> On 11/19/18 5:51 AM, Stephen Morris wrote:
> > Sure, but if the user is in the United Kingdom where they use GMT,
> > then presumably they
> > would run their entire system in GMT, whereas other locations may
> > or may not want to, so
> > the
On 11/18/18 2:24 PM, Ed Greshko wrote:
Right: I dislike the default color scheme
Wron: What idiot picked the default color scheme
Thank you! It's sad that it's necessary to point that out though.
___
users mailing list --
On 11/19/18 5:08 AM, Stephen Morris wrote:
>>
> From recollection, which may not be completely accurate, the Asrock
> motherboard that I
> have now is the first motherboard I've had where the bios has not offered a
> setting to
> set the system clock to GMT/Local, and I have always set the
On 11/19/18 5:51 AM, Stephen Morris wrote:
> Sure, but if the user is in the United Kingdom where they use GMT, then
> presumably they
> would run their entire system in GMT, whereas other locations may or may not
> want to, so
> the motherboard should provide that option, and I have had
On 19/11/18 8:21 am, Joe Zeff wrote:
On 11/18/2018 02:08 PM, Stephen Morris wrote:
From recollection, which may not be completely accurate, the Asrock
motherboard that I have now is the first motherboard I've had where
the bios has not offered a setting to set the system clock to
GMT/Local,
On 16/11/18 12:17 pm, Rick Stevens wrote:
On 11/15/18 4:54 PM, Ed Greshko wrote:
On 11/16/18 7:37 AM, Rick Stevens wrote:
On 11/15/18 3:00 PM, Joe Zeff wrote:
On 11/15/2018 03:17 PM, Rick Stevens wrote:
In Linux
case, it expects UTC. In Windows, it expects local time.
I haven't had to deal
On 11/18/2018 02:08 PM, Stephen Morris wrote:
From recollection, which may not be completely accurate, the Asrock
motherboard that I have now is the first motherboard I've had where the
bios has not offered a setting to set the system clock to GMT/Local, and
I have always set the system clock
On 16/11/18 1:12 pm, Tony Nelson wrote:
On 18-11-15 18:00:14, Joe Zeff wrote:
On 11/15/2018 03:17 PM, Rick Stevens wrote:
In Linux
case, it expects UTC. In Windows, it expects local time.
I haven't had to deal with this for years, but if memory serves,
there's a
place where you can tell
On 18-11-15 18:00:14, Joe Zeff wrote:
On 11/15/2018 03:17 PM, Rick Stevens wrote:
In Linux
case, it expects UTC. In Windows, it expects local time.
I haven't had to deal with this for years, but if memory serves,
there's a
place where you can tell Linux that the hardware clock is in local
On 11/15/2018 06:32 PM, Ed Greshko wrote:
Why don't you give it a try and show me it exits?
https://koji.fedoraproject.org/koji/packageinfo?packageID=11
Shows the last time this package was supplied was in F25.
Kindly check your work before making suggestions?
I did, but I'm working on my
On 11/16/18 9:17 AM, Rick Stevens wrote:
> On 11/15/18 4:54 PM, Ed Greshko wrote:
>>
>> Well, I'm just installing an F29 MATE VM and on the TIME screen there
>> is no tick-box
>> to indicate that the HW clock is or isn't "local".
>>
>> Additionally, I could find no trace of "system-config-date"
On 11/16/18 9:26 AM, Joe Zeff wrote:
> On 11/15/2018 05:54 PM, Ed Greshko wrote:
>> Additionally, I could find no trace of "system-config-date" in F29.
>>
>> [root@meimei ~]# dnf whatprovides *bin/system-config-date
>> Fedora 29 - x86_64 - VirtualBox 2.8 kB/s | 6.9 kB
>>
On 11/15/2018 05:54 PM, Ed Greshko wrote:
Additionally, I could find no trace of "system-config-date" in F29.
[root@meimei ~]# dnf whatprovides *bin/system-config-date
Fedora 29 - x86_64 - VirtualBox 2.8 kB/s | 6.9 kB 00:02
Failed to synchronize cache for repo
On 11/15/18 4:54 PM, Ed Greshko wrote:
> On 11/16/18 7:37 AM, Rick Stevens wrote:
>> On 11/15/18 3:00 PM, Joe Zeff wrote:
>>> On 11/15/2018 03:17 PM, Rick Stevens wrote:
In Linux
case, it expects UTC. In Windows, it expects local time.
>>> I haven't had to deal with this for years, but
On 11/16/18 7:37 AM, Rick Stevens wrote:
> On 11/15/18 3:00 PM, Joe Zeff wrote:
>> On 11/15/2018 03:17 PM, Rick Stevens wrote:
>>> In Linux
>>> case, it expects UTC. In Windows, it expects local time.
>> I haven't had to deal with this for years, but if memory serves, there's
>> a place where you
On 11/15/18 3:00 PM, Joe Zeff wrote:
> On 11/15/2018 03:17 PM, Rick Stevens wrote:
>> In Linux
>> case, it expects UTC. In Windows, it expects local time.
>
> I haven't had to deal with this for years, but if memory serves, there's
> a place where you can tell Linux that the hardware clock is in
On 11/15/2018 03:17 PM, Rick Stevens wrote:
In Linux
case, it expects UTC. In Windows, it expects local time.
I haven't had to deal with this for years, but if memory serves, there's
a place where you can tell Linux that the hardware clock is in local
time, not UTC.
On 11/15/18 2:40 PM, Ed Greshko wrote:
> On 11/16/18 6:17 AM, Rick Stevens wrote:
>> On 11/15/18 2:00 PM, Ed Greshko wrote:
>>> On 11/16/18 4:50 AM, Stephen Morris wrote:
On 14/11/18 8:46 am, Ed Greshko wrote:
> On 11/14/18 5:32 AM, Stephen Morris wrote:
>> My hardware clock is
On 11/16/18 6:17 AM, Rick Stevens wrote:
> On 11/15/18 2:00 PM, Ed Greshko wrote:
>> On 11/16/18 4:50 AM, Stephen Morris wrote:
>>> On 14/11/18 8:46 am, Ed Greshko wrote:
On 11/14/18 5:32 AM, Stephen Morris wrote:
> My hardware clock is running a couple of seconds slow as well.
>
On 11/15/18 2:00 PM, Ed Greshko wrote:
> On 11/16/18 4:50 AM, Stephen Morris wrote:
>> On 14/11/18 8:46 am, Ed Greshko wrote:
>>> On 11/14/18 5:32 AM, Stephen Morris wrote:
My hardware clock is running a couple of seconds slow as well.
Just as a matter of curiosity, when you say if
On 11/16/18 4:50 AM, Stephen Morris wrote:
> On 14/11/18 8:46 am, Ed Greshko wrote:
>> On 11/14/18 5:32 AM, Stephen Morris wrote:
>>> My hardware clock is running a couple of seconds slow as well.
>>>
>>> Just as a matter of curiosity, when you say if you issue hwclock from the
>>> bios (how have
On 14/11/18 10:03 am, Samuel Sieb wrote:
On 11/13/18 1:43 PM, Stephen Morris wrote:
Thankyou. I issued the command and got the following output but I'm
not sure what it means.
Nov 14 08:33:43 localhost.localdomain nm-openvpn[3877]: WARNING:
'link-mtu' is used inconsistently, local='link-mtu
On 14/11/18 8:56 am, Ed Greshko wrote:
On 11/14/18 5:43 AM, Stephen Morris wrote:
On 14/11/18 4:36 am, Samuel Sieb wrote:
On 11/13/18 3:07 AM, Ed Greshko wrote:
On 11/13/18 12:39 PM, Samuel Sieb wrote:
Run "sudo journalctl -b -t openvpn" to find all the journal entries.
That would actually
On 14/11/18 8:46 am, Ed Greshko wrote:
On 11/14/18 5:32 AM, Stephen Morris wrote:
My hardware clock is running a couple of seconds slow as well.
Just as a matter of curiosity, when you say if you issue hwclock from the bios
(how have
you done that) what does journalctl show for the same time?
On 14/11/18 8:46 am, Ed Greshko wrote:
On 11/14/18 5:32 AM, Stephen Morris wrote:
My hardware clock is running a couple of seconds slow as well.
Just as a matter of curiosity, when you say if you issue hwclock from the bios
(how have
you done that) what does journalctl show for the same time?
On 11/13/18 1:43 PM, Stephen Morris wrote:
Thankyou. I issued the command and got the following output but I'm not
sure what it means.
Nov 14 08:33:43 localhost.localdomain nm-openvpn[3877]: WARNING:
'link-mtu' is used inconsistently, local='link-mtu 1558',
remote='link-mtu 1557'
Nov 14
On 11/14/18 5:43 AM, Stephen Morris wrote:
> On 14/11/18 4:36 am, Samuel Sieb wrote:
>> On 11/13/18 3:07 AM, Ed Greshko wrote:
>>> On 11/13/18 12:39 PM, Samuel Sieb wrote:
Run "sudo journalctl -b -t openvpn" to find all the journal entries.
>>>
>>> That would actually be
>>>
>>>
On 11/14/18 5:32 AM, Stephen Morris wrote:
> My hardware clock is running a couple of seconds slow as well.
>
> Just as a matter of curiosity, when you say if you issue hwclock from the
> bios (how have
> you done that) what does journalctl show for the same time? Does it show,
> using your
>
On 14/11/18 4:36 am, Samuel Sieb wrote:
On 11/13/18 3:07 AM, Ed Greshko wrote:
On 11/13/18 12:39 PM, Samuel Sieb wrote:
Run "sudo journalctl -b -t openvpn" to find all the journal entries.
That would actually be
journalctl -b -t nm-openvpn
Thank you. I've been running the openvpn
On 13/11/18 8:52 am, Ed Greshko wrote:
On 11/13/18 4:49 AM, Stephen Morris wrote:
So given all this, when searching journalctl for boot messages across particular
datetime ranges, how do you find them when the timestamps in
the journals are blatantly wrong, potentially up until the desktop
On 11/13/18 3:07 AM, Ed Greshko wrote:
On 11/13/18 12:39 PM, Samuel Sieb wrote:
Run "sudo journalctl -b -t openvpn" to find all the journal entries.
That would actually be
journalctl -b -t nm-openvpn
Thank you. I've been running the openvpn client directly from the
command line, so
On 11/13/18 12:39 PM, Samuel Sieb wrote:
> On 11/6/18 1:43 PM, Stephen Morris wrote:
>> When I start one of the two vpn definitions, that have been in
>> networkmanager for
>> years and used to work fine (I haven't used them in quite a while), it
>> starts and I get
>> a pop-up message
On Mon, 2018-11-12 at 20:39 -0800, Samuel Sieb wrote:
> On 11/6/18 1:43 PM, Stephen Morris wrote:
> > When I start one of the two vpn definitions, that have been in
> > networkmanager for years and used to work fine (I haven't used them in
> > quite a while), it starts and I get a pop-up
On 11/6/18 1:43 PM, Stephen Morris wrote:
When I start one of the two vpn definitions, that have been in
networkmanager for years and used to work fine (I haven't used them in
quite a while), it starts and I get a pop-up message saying that
interface tun0 has been activated in the
On 11/13/18 4:49 AM, Stephen Morris wrote:
> So given all this, when searching journalctl for boot messages across
> particular
> datetime ranges, how do you find them when the timestamps in
> the journals are blatantly wrong, potentially up until the desktop loads?
I don't know. I've not had
On 11/12/18 12:49 PM, Stephen Morris wrote:
> On 9/11/18 8:28 pm, Patrick O'Callaghan wrote:
>> On Fri, 2018-11-09 at 00:08 +, Rick Stevens wrote:
>>> On 11/8/18 2:41 PM, Patrick O'Callaghan wrote:
On Fri, 2018-11-09 at 08:02 +1100, Stephen Morris wrote:
> how is linux using GMT when
On 9/11/18 8:28 pm, Patrick O'Callaghan wrote:
On Fri, 2018-11-09 at 00:08 +, Rick Stevens wrote:
On 11/8/18 2:41 PM, Patrick O'Callaghan wrote:
On Fri, 2018-11-09 at 08:02 +1100, Stephen Morris wrote:
how is linux using GMT when everything is running local.
All Unix-based or
On Fri, 2018-11-09 at 00:08 +, Rick Stevens wrote:
> On 11/8/18 2:41 PM, Patrick O'Callaghan wrote:
> > On Fri, 2018-11-09 at 08:02 +1100, Stephen Morris wrote:
> > > how is linux using GMT when everything is running local.
> >
> > All Unix-based or Unix-derived systems, including Linux, use
On 11/8/18 2:41 PM, Patrick O'Callaghan wrote:
> On Fri, 2018-11-09 at 08:02 +1100, Stephen Morris wrote:
>> how is linux using GMT when everything is running local.
>
> All Unix-based or Unix-derived systems, including Linux, use GMT
> internally, and have done since the very first versions back
On Fri, 2018-11-09 at 08:02 +1100, Stephen Morris wrote:
> how is linux using GMT when everything is running local.
All Unix-based or Unix-derived systems, including Linux, use GMT
internally, and have done since the very first versions back in the
70s. Even if you set your hardware clock to
On 8/11/18 11:00 pm, Ed Greshko wrote:
On 11/8/18 8:29 AM, Rick Stevens wrote:
A lot of the timezones are symlinked to Etc/UTC and it's listed as
"canonical", so perhaps we're both right. Nyaah! Tht! :-P
I can live with that. :-)
I'm confused. If I have my linux desktops configured to
On 11/8/18 8:29 AM, Rick Stevens wrote:
> A lot of the timezones are symlinked to Etc/UTC and it's listed as
> "canonical", so perhaps we're both right. Nyaah! Tht! :-P
I can live with that. :-)
--
Fedora Users - The place to go to beat OT dead horses :-) :-)
On 11/7/18 4:14 PM, Ed Greshko wrote:
> On 11/8/18 7:55 AM, Rick Stevens wrote:
>> Yes, HW clock set to GMT (well, technically UTC) for Linux is standard.
>> The local time is computed based on your timezone. I have the HW clock
>> set to UTC on all my machines and I see the correct local time in
On 11/8/18 7:55 AM, Rick Stevens wrote:
> Yes, HW clock set to GMT (well, technically UTC) for Linux is standard.
> The local time is computed based on your timezone. I have the HW clock
> set to UTC on all my machines and I see the correct local time in my
> logs.
Well, we were talking about
On 11/7/18 2:36 PM, Ed Greshko wrote:
> On 11/8/18 5:31 AM, Stephen Morris wrote:
>> Thanks Ed, I issued that command and fed the output into grep to search for
>> tun0, and
>> found messages saying that the device was successfully activated, and then
>> about 30
>> seconds later a message
On 11/8/18 5:31 AM, Stephen Morris wrote:
> Thanks Ed, I issued that command and fed the output into grep to search for
> tun0, and
> found messages saying that the device was successfully activated, and then
> about 30
> seconds later a message saying the connection timed out, and then almost a
On 7/11/18 10:17 am, Ed Greshko wrote:
On 11/7/18 5:43 AM, Stephen Morris wrote:
When I start one of the two vpn definitions, that have been in
networkmanager for
years and used to work fine (I haven't used them in quite a while), it starts
and I get
a pop-up message saying that
On 11/7/18 5:43 AM, Stephen Morris wrote:
> When I start one of the two vpn definitions, that have been in
> networkmanager for
> years and used to work fine (I haven't used them in quite a while), it starts
> and I get
> a pop-up message saying that interface tun0 has been activated in the
74 matches
Mail list logo
