So it seems that now when I use --daemon it backgrounds BEFORE
prompting for my password instead of after
So I am good as long as I don't do that.
Why this all of a sudden?
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listin
On 07/25/2015 05:00 PM, Gordon Messmer wrote:
> On 07/25/2015 11:45 AM, Jake Shipton wrote:
>> I think a better solution to suite both worlds would be to simply have a
>> boot flag on the installation media such as maybe
>> "passwordcheck=true/false"
>
> https://xkcd.com/1172/
>
> It's practicall
On 07/26/2015 08:13 AM, Johnny Hughes wrote:
> On 07/25/2015 05:00 PM, Gordon Messmer wrote:
>> On 07/25/2015 11:45 AM, Jake Shipton wrote:
>>> I think a better solution to suite both worlds would be to simply have a
>>> boot flag on the installation media such as maybe
>>> "passwordcheck=true/fals
Hi all!
I usually keep the panels on my Centos 6.6 (Gnome) so they auto-hide,
but t'other day I wanted to keep the top panel visible for a while to
make the clock visible for doing some rough timings.
so I open the top panel, click properties, and UNcheck the "autohide"
checkbox, close the proper
On 07/27/2015 05:34 AM, Fred Smith wrote:
Hi all!
I usually keep the panels on my Centos 6.6 (Gnome) so they auto-hide,
but t'other day I wanted to keep the top panel visible for a while to
make the clock visible for doing some rough timings.
so I open the top panel, click properties, and UNche
greetings,
system:
CentOS = 6.6 - current updates
KDE = 4.3.4
Network Manager = 0.8.1
wicd = 1.7.0 (bzr-r552)
from what i have read in threads, it appears that 'wicd' is recommended
network controller over 'network manager'.
because of this, i installed wicd and
greetings,
during past week or so, i have been having problems with mozilla firefox
locking up kde desktop and i have to open a terminal to reboot system.
to insure that i get kde back to a desired state, i make backups of
~/.kde path when ever i change any settings of kde.
after system reboots
greetings,
i find this strange because i see problems when using 'wicd'.
1st problem is that wicd allows network to be connected on reboot, even
when network is disconnected at time of reboot.
such does not seem to be good because i leave system up 24/7/365 and if
there is a mains failure and u
greetings,
wicd is preventing firefox and yumex to connect to internet.
when i first try to connect to a web site with firefox, i get err message;
Unable to connect
when i click [Try Again], connection is made. all further connection
attempts are ok.
when i try to run yumex, i get error mes
greetings,
following are command line problems as user using virtual terminals.
]$ ifconfig;date
eth0 Link encap:Ethernet HWaddr 00:0F:FE:8F:8F:23
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::20f:feff:fe8f:8f23/64 Scope:Link
greetings,
to further check wicd problem, i decided to run test as root user and
as user.
i verified wicd problems 1, 2, 3 happen when logged in as root user.
to further test wicd problems, i tried a few command line problems
using virtual terminals.
in following, note changing of status for
On 7/26/2015 9:18 PM, g wrote:
from what i have read in threads, it appears that 'wicd' is recommended
network controller over 'network manager'.
recommended by whom ?rhel and therefore centos use network
manager. wicd is used by arch and some other distributions... wicd
is not availa
12 matches
Mail list logo
