Processed: Re: Bug#241062: base-config should start xfs before *dm
Processing commands for [EMAIL PROTECTED]: > clone 241062 -1 Bug#241062: base-config should start xfs before *dm Bug 241062 cloned as bug 241539. > retitle -1 xfs: hack preinst and postinst to start daemon on install Bug#241539: base-config should start xfs before *dm Changed Bug title. > reassign -1 xfs Bug#241539: xfs: hack preinst and postinst to start daemon on install Bug reassigned from package `base-config' to `xfs'. > tag -1 - patch Bug#241539: xfs: hack preinst and postinst to start daemon on install Tags were: patch Tags removed: patch > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Re: Bug#241062: base-config should start xfs before *dm
> On Wed, Mar 31, 2004 at 05:57:55PM -0500, Joey Hess wrote: > > I don't think it's base-config's job to work around what looks like a > > bug in xdm for not starting the daemon on initial install. Forwarding > > to the XSF. > > This done for two reasons: > > 1) historical > 2) display managers are not like other daemons; they start an X server > on a local VT by default which yanks the console away > > I'm willing to listen to a case against both of these. There was a typo. It's actually not about xdm, it's about xfs.
Re: Bug#241062: base-config should start xfs before *dm
On Wed, Mar 31, 2004 at 05:57:55PM -0500, Joey Hess wrote: > I don't think it's base-config's job to work around what looks like a > bug in xdm for not starting the daemon on initial install. Forwarding > to the XSF. This done for two reasons: 1) historical 2) display managers are not like other daemons; they start an X server on a local VT by default which yanks the console away I'm willing to listen to a case against both of these. -- G. Branden Robinson| My first priority in any attack is Debian GNU/Linux | to solve the problem - not issue a [EMAIL PROTECTED] | press release. http://people.debian.org/~branden/ | -- Steve McInerney signature.asc Description: Digital signature
Re: Bug#241062: base-config should start xfs before *dm
Nikita V. Youshchenko wrote: > > > Nikita V. Youshchenko wrote: > > > Since debian defaults to use xfs to provide X server with fonts, > > > base-config should start it before starting *dm. Currently it seems > > > not to be started automatically during initial installation. > > > > It's news to me that we use xfs by default; it is not part of > > x-window-system-core, and X includes a built-in font server. > > > > Also, like most other daemons in Debian, xfs is started automatically > > when it is installed. > > > > Could you describe the actual problem you ran into, please? > > Well, probably I was wrong with "default" - actually, it is difficult to > say what is "default" in this case. > > - XF86Config generated by dexconf does reference local xfs, and includes > more font paths only "if the local font server has problems" (quoted from > comment in generated XF86Config-4) Makes sense, if you have a font server, you want to use it. However, most systems do not have a font sever, and X goes with the fallback fontpath entries. > - xfs is NOT start automatically by it's postinst, because in general case > it is not safe. In particular, restarting xfs on package upgrade while it > is in use by local or remote X server may cause that X server and/or it's > clients to misbehave or crash. Probably xfs postinst may be modified to > start xfs on initial install unconditionally, while not touching a running > daemon on upgrade, but at this moment it is not done. At least, on initial > installation of what is in testing now, xfs is not started automatically. > > - if xfs was installed during the initial install process, it will be > started after reboot. So, if it is not started also by base-config, X will > get different configuration before and after reboot. This is bad IMHO. > > So it is better for base-config to start xfs if it was installed. At least > it won't do any harm, and will make system more consistent. I don't think it's base-config's job to work around what looks like a bug in xdm for not starting the daemon on initial install. Forwarding to the XSF. -- see shy jo signature.asc Description: Digital signature
