On Sun, 2013-05-26 at 17:36 -0700, jackson byers wrote:
>
> I am concerned re
> notes section from 'man hwclock'
>
>
>
> "It is important that the System Time not have any dis‐
>continuities such as would happen if you used the
>date(1L) program to set it while the sys
On 05/26/2013 at 07:38 PM, Ed Greshko wrote:
>On 05/27/13 08:19, Jim wrote:
>> Fedora 18, Trying to install a package, nitroshare-0.2-2.i386.rpm and I get
the following error message, What Gives ??
>
>You have downloaded a poorly packaged application. It is potentially making
changes to permissio
On 05/27/13 08:19, Jim wrote:
> Fedora 18, Trying to install a package, nitroshare-0.2-2.i386.rpm and I get
> the following error message, What Gives ??
You have downloaded a poorly packaged application. It is potentially making
changes to permissions and/or selinux contexts on /, /usr, /opt an
>If it keeps resetting to the same wrong date, chances are the power
>failure caused your machine's hardware clock to be set to the wrong
>time. Try first getting your OS system clock set properly (as you have
>done already), and then use "hwclock" to sync the hardware clock to the
>system clock. I
Fedora 18, Trying to install a package, nitroshare-0.2-2.i386.rpm and I
get the following error message, What Gives ??
# yum -y localinstall nitroshare-0.2-2.i386.rpm
Loaded plugins: keys, langpacks, presto, refresh-packagekit, versionlock
Examining nitroshare-0.2-2.i386.rpm: nitroshare-0.2-2.
On 05/26/2013 04:20 PM, Robin Laing wrote:
During today's searches, I realized that I have not done a full look
through the boot sequence to see when the screen changes from single to
mirrored(cloned) from single screen.
I will check dmesg closer tomorrow at work.
Grep is your friend, here, al
On 2013-05-26 17:08, David wrote:
> On 5/26/2013 7:06 PM, David wrote:
>> On 5/26/2013 5:54 PM, Robin Laing wrote:
>>> On 2013-05-25 10:25, ergodic wrote:
I have a similar problem. In previous Fedoras it was possible to select
the monitor to be used during booting or display the booting
On 5/26/2013 5:54 PM, Robin Laing wrote:
> On 2013-05-25 10:25, ergodic wrote:
>> I have a similar problem. In previous Fedoras it was possible to select
>> the monitor to be used during booting or display the booting screen in
>> both monitors.
>>
>> It looks that the distro is becoming less fle
On 5/26/2013 7:06 PM, David wrote:
> On 5/26/2013 5:54 PM, Robin Laing wrote:
>> On 2013-05-25 10:25, ergodic wrote:
>>> I have a similar problem. In previous Fedoras it was possible to select
>>> the monitor to be used during booting or display the booting screen in
>>> both monitors.
>>>
>>> It
On 2013-05-25 10:25, ergodic wrote:
> I have a similar problem. In previous Fedoras it was possible to select
> the monitor to be used during booting or display the booting screen in
> both monitors.
>
> It looks that the distro is becoming less flexible or much harder to
> configure.
>
It is
If it keeps resetting to the same wrong date, chances are the power
failure caused your machine's hardware clock to be set to the wrong
time. Try first getting your OS system clock set properly (as you have
done already), and then use "hwclock" to sync the hardware clock to the
system clock. I have
>Most likely. Either the power failed in a bad way, upsetting the
>hardware in your computer along the way, or your CMOS battery may be
>running low, and this failure happened coincidentally.
>If you often leave your computer switched off for many hours and your
>clock is fine, then the battery i
On 05/26/2013 05:11 AM, Phil Dobbin wrote:
The same address assigned is in the 192.168.1.xxx range & is, obviously,
internal. The dynamic IP is external & this is the one that changes & I
have no control over it (& I can't get a static IP unfortunately).
Sorry, I'd been under the impression tha
On Sun, 2013-05-26 at 02:00 +0100, Phil Dobbin wrote:
> I've got several machines on a LAN behind a NAT with DHCP assigning
> always the same addresses from a dynamic IP.
>
> A couple of days ago the IP changed & since then, one of the machines
> running Fedora 17 always fails first time to conne
On 05/26/2013 02:54 PM, Mikkel L. Ellertson wrote:
[...]
> Dumb question - have you checked the network connection? See if
> changing the cable or the port on the switch helps. It seams strange
> that the external IP address changing would cause this, but for some
> strange reason hardware probl
On 05/26/2013 02:54 PM, Mikkel L. Ellertson wrote:
> On 05/26/2013 07:18 AM, Phil Dobbin wrote:
>> On 05/26/2013 11:54 AM, Mikkel L. Ellertson wrote:
>>> On 05/25/2013 08:00 PM, Phil Dobbin wrote:
Hi, all.
I've got several machines on a LAN behind a NAT with DHCP assigning
alwa
On 05/26/2013 07:18 AM, Phil Dobbin wrote:
> On 05/26/2013 11:54 AM, Mikkel L. Ellertson wrote:
>> On 05/25/2013 08:00 PM, Phil Dobbin wrote:
>>> Hi, all.
>>>
>>> I've got several machines on a LAN behind a NAT with DHCP assigning
>>> always the same addresses from a dynamic IP.
>>>
>>> A couple of
On 05/26/2013 11:54 AM, Mikkel L. Ellertson wrote:
> On 05/25/2013 08:00 PM, Phil Dobbin wrote:
>> Hi, all.
>>
>> I've got several machines on a LAN behind a NAT with DHCP assigning
>> always the same addresses from a dynamic IP.
>>
>> A couple of days ago the IP changed & since then, one of the ma
On 05/26/2013 02:21 AM, Joe Zeff wrote:
> On 05/25/2013 06:00 PM, Phil Dobbin wrote:
>> I've got several machines on a LAN behind a NAT with DHCP assigning
>> always the same addresses from a dynamic IP.
>>
>> A couple of days ago the IP changed & since then, one of the machines
>> running Fedora
On 05/25/2013 08:00 PM, Phil Dobbin wrote:
> Hi, all.
>
> I've got several machines on a LAN behind a NAT with DHCP assigning
> always the same addresses from a dynamic IP.
>
> A couple of days ago the IP changed & since then, one of the machines
> running Fedora 17 always fails first time to conne
20 matches
Mail list logo
