Hi,
I have no idea - this is just how Suse does it so I wouldn't be surprised.
Andrew.
-----Original Message-----
From: gnome-accessibility-list-bounces gnome org on behalf of Al Puzzuoli
Sent: Wed 22/03/2006 15:54
To: Gnome accessibility
Subject: Re: FC5 fresh install defaults to runlevel 3?
RE: FC5 fresh install defaults to runlevel 3?interesting.
This is definitely a nice value add in terms of accessibility, but am I
missing something, or is this a new feature in the release of FC5? I've
been doing
telnet based text installs of fedora for years and have always
come up in runlevel 5 and needed to run firstboot until now.
--Al
Block quote start
----- Original Message -----
From:
Andrew Hodgson
To:
Al Puzzuoli
Sent: Wednesday, March 22, 2006 5:53 AM
Subject: RE: FC5 fresh install defaults to runlevel 3?
Hi,
if you do the install using text mode it will default to runlevel 3 and also
will not do the first boot sequence unless you start the command. In Suse
there is a command to start this first boot procedure in Yast over SSH,
which is how I get servers up and running at work - over the SSH interface
for
initial installation, then connect over SSH and do the initial config from
running the yast script.
Andrew.
-----Original Message-----
From: gnome-accessibility-list-bounces gnome org on behalf of Al Puzzuoli
Sent: Wed 22/03/2006 05:05
To: Gnome accessibility
Subject: FC5 fresh install defaults to runlevel 3?
Hi all,
I just did a fresh install over telnet of the release version of FC5.
After the install completed, I immediately found myself at a text login
prompt. My initial reaction was that something had gone amiss; However,
upon poking around, I discovered that the system was set to start at
runlevel 3. Also, my sound card had already been detected, and when I used
startx to launch Gnome, I was never prompted to go through the firstboot
process.
I was quite surprised indeed by this behavior because I installed test 3
just a few weeks ago and after installation, it started in runlevel 5 and
did in fact require the firstboot process.
What's the deal? If this change was made to enhance accessibility, then I
welcome it whole-heartedly as firstboot did used to be rather a pain;
however, if something this drastic were in the works, I would have expected
to see it implemented in one of the test versions as opposed to suddenly
showing up in the release.
Does anyone know what's going on?
Thanks,
--Al
_______________________________________________
gnome-accessibility-list mailing list
gnome-accessibility-list gnome org
http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Block quote end
----- Original Message -----
From: Al Puzzuoli
To: Andrew Hodgson
Sent: Wednesday, March 22, 2006 10:53 AM
Subject: Re: FC5 fresh install defaults to runlevel 3?
interesting.
This is definitely a nice value add in terms of accessibility, but am I
missing something, or is this a new feature in the release of FC5? I've
been doing telnet based text installs of fedora for years and have always
come up in runlevel 5 and needed to run firstboot until now.
--Al
----- Original Message -----
From: Andrew Hodgson
To: Al Puzzuoli
Sent: Wednesday, March 22, 2006 5:53 AM
Subject: RE: FC5 fresh install defaults to runlevel 3?
Hi,
if you do the install using text mode it will default to runlevel 3 and
also will not do the first boot sequence unless you start the command. In
Suse there is a command to start this first boot procedure in Yast over SSH,
which is how I get servers up and running at work - over the SSH interface
for initial installation, then connect over SSH and do the initial config
from running the yast script.
Andrew.
-----Original Message-----
From: gnome-accessibility-list-bounces gnome org on behalf of Al
Puzzuoli
Sent: Wed 22/03/2006 05:05
To: Gnome accessibility
Subject: FC5 fresh install defaults to runlevel 3?
Hi all,
I just did a fresh install over telnet of the release version of FC5.
After the install completed, I immediately found myself at a text login
prompt. My initial reaction was that something had gone amiss; However,
upon poking around, I discovered that the system was set to start at
runlevel 3. Also, my sound card had already been detected, and when I
used
startx to launch Gnome, I was never prompted to go through the firstboot
process.
I was quite surprised indeed by this behavior because I installed test 3
just a few weeks ago and after installation, it started in runlevel 5
and
did in fact require the firstboot process.
What's the deal? If this change was made to enhance accessibility, then
I
welcome it whole-heartedly as firstboot did used to be rather a pain;
however, if something this drastic were in the works, I would have
expected
to see it implemented in one of the test versions as opposed to suddenly
showing up in the release.
Does anyone know what's going on?
Thanks,
--Al
_______________________________________________
gnome-accessibility-list mailing list
gnome-accessibility-list gnome org
http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
_______________________________________________
gnome-accessibility-list mailing list
gnome-accessibility-list gnome org
http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list