on 09/06/2012 19:17 Doug Barton said the following:
If this were a problem we didn't already have a solution for, I'd be
much more interested in what you're proposing.
I wonder if you were in the same mindset when you worked on service(8).
This is not to doubt service(8) usefulness, of course.
On 06/13/2012 06:50 AM, Andriy Gapon wrote:
on 09/06/2012 19:17 Doug Barton said the following:
If this were a problem we didn't already have a solution for, I'd be
much more interested in what you're proposing.
I wonder if you were in the same mindset when you worked on service(8).
This is
on 09/06/2012 17:45 Marcin Wisnicki said the following:
On Thu, 07 Jun 2012 12:57:41 +0300, Gleb Kurtsou wrote:
On (07/06/2012 11:56), Andriy Gapon wrote:
A user doesn't have to select the option unless he needs to. A simple
user can just reboot without selecting the option to get back his
On Sat, Jun 09, 2012 at 07:28:50AM +0300, Andriy Gapon wrote:
on 09/06/2012 04:16 Jason Hellenthal said the following:
runlevel support might be a better solution so it does not differ that
much from what other systems do and would be easy for people to grasp.
Patches are welcome, as
On Thu, 07 Jun 2012 12:57:41 +0300, Gleb Kurtsou wrote:
On (07/06/2012 11:56), Andriy Gapon wrote:
A user doesn't have to select the option unless he needs to. A simple
user can just reboot without selecting the option to get back his X. A
user doesn't have to learn anything about the code,
On 06/07/2012 11:10, Andriy Gapon wrote:
on 07/06/2012 17:29 Doug Barton said the following:
On 06/07/2012 02:57 AM, Gleb Kurtsou wrote:
What do you think about adding generic support for overriding *_enable
options in rc.conf?
I'd like to be able to disable services at boot prompt, e.g.
#
On 06/09/12 10:37, Jason Hellenthal wrote:
On Sat, Jun 09, 2012 at 07:28:50AM +0300, Andriy Gapon wrote:
on 09/06/2012 04:16 Jason Hellenthal said the following:
runlevel support might be a better solution so it does not differ that
much from what other systems do and would be easy for people
On 7 June 2012 16:12, Garrett Cooper yaneg...@gmail.com wrote:
I've run into _multiple_ scenarios where this isn't possible because
the terminal settings are screwed up in single user mode, and had to
resort to `sed -i '' `.
ed is the standard text editor
Aled
On Thu, Jun 07, 2012 at 01:06:09PM +0300, Andriy Gapon wrote:
on 07/06/2012 12:57 Gleb Kurtsou said the following:
What do you think about adding generic support for overriding *_enable
options in rc.conf?
I'd like to be able to disable services at boot prompt, e.g.
# set
on 09/06/2012 04:16 Jason Hellenthal said the following:
runlevel support might be a better solution so it does not differ that
much from what other systems do and would be easy for people to grasp.
Patches are welcome, as always.
--
Andriy Gapon
It's long been a wish of mine to have an ability to decide at boot time that a
system should boot in console-only mode. That is, that no graphics/X
applications like e.g. xdm/kdm/gdm are automatically started even when they are
configured to do so.
Here is my attempt at implementing that:
On Thu, Jun 07, 2012 at 10:45:26AM +0300, Andriy Gapon wrote:
It's long been a wish of mine to have an ability to decide at boot time that a
system should boot in console-only mode. That is, that no graphics/X
applications like e.g. xdm/kdm/gdm are automatically started even when they
are
on 07/06/2012 11:47 Konstantin Belousov said the following:
On Thu, Jun 07, 2012 at 10:45:26AM +0300, Andriy Gapon wrote:
It's long been a wish of mine to have an ability to decide at boot time that
a
system should boot in console-only mode. That is, that no graphics/X
applications like
On (07/06/2012 11:56), Andriy Gapon wrote:
on 07/06/2012 11:47 Konstantin Belousov said the following:
On Thu, Jun 07, 2012 at 10:45:26AM +0300, Andriy Gapon wrote:
It's long been a wish of mine to have an ability to decide at boot time
that a
system should boot in console-only mode.
on 07/06/2012 12:57 Gleb Kurtsou said the following:
What do you think about adding generic support for overriding *_enable
options in rc.conf?
I'd like to be able to disable services at boot prompt, e.g.
# set rc.slim_enable=no -- overrides slim_enable=yes in rc.conf
Similarly
On 06/07/2012 02:57 AM, Gleb Kurtsou wrote:
What do you think about adding generic support for overriding *_enable
options in rc.conf?
I'd like to be able to disable services at boot prompt, e.g.
# set rc.slim_enable=no -- overrides slim_enable=yes in rc.conf
Similarly rc.pf_enable=no
On Thu, Jun 7, 2012 at 7:29 AM, Doug Barton do...@freebsd.org wrote:
On 06/07/2012 02:57 AM, Gleb Kurtsou wrote:
What do you think about adding generic support for overriding *_enable
options in rc.conf?
I'd like to be able to disable services at boot prompt, e.g.
# set rc.slim_enable=no --
On Thu, Jun 7, 2012 at 2:57 AM, Gleb Kurtsou gleb.kurt...@gmail.com wrote:
On (07/06/2012 11:56), Andriy Gapon wrote:
on 07/06/2012 11:47 Konstantin Belousov said the following:
On Thu, Jun 07, 2012 at 10:45:26AM +0300, Andriy Gapon wrote:
It's long been a wish of mine to have an ability
On 06/07/2012 08:12 AM, Garrett Cooper wrote:
I've run into _multiple_ scenarios where this isn't possible because
the terminal settings are screwed up in single user mode, and had to
resort to `sed -i '' `.
If that happens, a) report it! SUM is a very important part of FreeBSD,
and it needs
on 07/06/2012 17:29 Doug Barton said the following:
On 06/07/2012 02:57 AM, Gleb Kurtsou wrote:
What do you think about adding generic support for overriding *_enable
options in rc.conf?
I'd like to be able to disable services at boot prompt, e.g.
# set rc.slim_enable=no -- overrides
On Thu, Jun 07, 2012 at 10:45:26AM +0300, Andriy Gapon wrote:
It's long been a wish of mine to have an ability to decide at boot time that a
system should boot in console-only mode. That is, that no graphics/X
applications like e.g. xdm/kdm/gdm are automatically started even when they
are
21 matches
Mail list logo
