Date: Thu, 7 Jun 2012 08:16:00 -0700 From: Garrett Cooper <yanegomi@gmail.com> To: Gleb Kurtsou <gleb.kurtsou@gmail.com> Cc: Konstantin Belousov <kostikbel@gmail.com>, freebsd-hackers@freebsd.org, Andriy Gapon <avg@freebsd.org> Subject: Re: boot menu option to disable graphics mode Message-ID: <CAGH67wTqq7kwfjhvruWsJS%2BAm52ToSOBjn1MegBQvzi=PYeQQw@mail.gmail.com> In-Reply-To: <20120607095741.GA1361@reks> References: <4FD05C16.9040905@FreeBSD.org> <20120607084738.GT85127@deviant.kiev.zoral.com.ua> <4FD06CD3.3080602@FreeBSD.org> <20120607095741.GA1361@reks>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jun 7, 2012 at 2:57 AM, Gleb Kurtsou <gleb.kurtsou@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 to decide at boot ti= me that a >> >> system should boot in "console-only" mode. =A0That is, that no graphi= cs/X >> >> applications like e.g. xdm/kdm/gdm are automatically started even whe= n they are >> >> configured to do so. >> >> >> >> Here is my attempt at implementing that: >> >> https://gitorious.org/~avg/freebsd/avgbsd/commit/96f7051d63d4286ef6f0= 196d241e7855338a6ed7?format=3Dpatch >> >> >> >> All the option does at boot time is setting of 'inhibit_gui' variable= for kernel >> >> environment. =A0I envision that this variable could be properly and g= racefully >> >> handled in various startup scripts and/or application startup logic. >> >> But to ensure that the option is always honored I've also added "ulti= mate >> >> protection" to syscons that prohibits KDSETMODE/KD_GRAPHICS ioctl. >> > This is too much, IMO. I understand why you may want to disable >> > auto-start of login manager, but preventing a user from running X at a= ll >> > until she learns about kenv -u _and_ obscure code somewhere in the ker= nel, >> > is unreasonable. >> >> 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, just about kenv an= d >> "magic" inhibit_gui variable. > > 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=3D"no" -- overrides slim_enable=3D"yes" in rc.conf > > Similarly rc.pf_enable=3D"no" > > Then introduce x_enable knob (=3Dyes by default) to disable login > managers. User will be able to override this setting with > # service xdm forcestart It needs to be profiled, but I would be curious what the slowdown would be for this change. Also, it sort of introduces a fun chicken and egg problem with sourcing rc.conf files, like I discovered recently at $JOB. Thanks, -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGH67wTqq7kwfjhvruWsJS%2BAm52ToSOBjn1MegBQvzi=PYeQQw>