Date: Fri, 5 Feb 2010 16:16:34 -0800 (PST) From: Dan <meslists@yahoo.fr> To: Marc Fonvieille <blackend@freebsd.org> Cc: freebsd-doc@freebsd.org Subject: Re : handbook - [5.4.2 Configuring X11] - suggesting an improvement Message-ID: <377659.99448.qm@web28104.mail.ukl.yahoo.com> In-Reply-To: <20100205183925.GA1275@gothic.blackend.org> References: <4B6BF9C0.8070706@yahoo.fr> <20100205183925.GA1275@gothic.blackend.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi :-)=0A=0AThank you for the fast feedback. So in your tests hal did not a= ctually =0Aparse the new/modified fdi file(s) ? Or some hardware, that was = =0Apreviously working, stopped ?=0A=0AHere, hal needed a restart together w= ith the X-Window System (maybe one =0Ashould also state this in the doc). I= was pretty sure that starting a =0Ascript at boot time or restarting it la= ter when the system was already =0Arunning would not lead to differences in= behaviour (reading config files I mean). =0A=0ABTW, I am not aware of the = FreeBSD policies in this respect but, you =0Aalready know, one of the criti= cs made to some well-known software is =0Athat it leads to too many (unnece= ssary) reboots. I think it would not be bad here to underline that a reboot= is needed just in the worst case. =0AAnd what if a new FreeBSD user, who i= s reading the guide, has to test =0Aseveral fdi files because she/he is not= able to write a working one at =0Afirst (how many reboots...) ? (But It's= also true that she/he also =0Awould be unnecessarily worried if hal would = not read the config files =0Awhen the script restarts -...isnt there any lo= g??)=0A=0ABut, definitely, all this is just my own opinion. =0A=0Aciao,=0Ad= aniele=0A=0A=0A=0A________________________________=0ADe : Marc Fonvieille <= blackend@freebsd.org>=0A=C0 : daniele <meslists@yahoo.fr>=0ACc : freebsd-do= c@freebsd.org=0AEnvoy=E9 le : Ven 5 F=E9vrier 2010, 19 h 39 min 25 s=0AObje= t : Re: handbook - [5.4.2 Configuring X11] - suggesting an improvement=0A= =0AOn Fri, Feb 05, 2010 at 11:58:08AM +0100, daniele wrote:=0A> >=0A> > >/= =0A> > />/ I was reading the section 5.4.2 of the handbook. In the 2nd and= 3rd Notes,=0A> > />/ after the fdi file code, one reads=0A> > />/=0A> > /= >/ "You will have to reboot your machine to force *hald* to read this file= ."=0A> > />/=0A> > />/ I think this is not the most efficient solution to = let hald read again the=0A> > />/ file.=0A> > />/=0A> > />/ Restarting ju= st the hal start script wouldn't be enough ?=0A> > /=0A> > Not always:=0A>= >=0A> > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=3D595146+0+archive/20= 09/freebsd-doc/20091101.freebsd-doc=0A> > =0A> Hi,=0A> =0A> Thanks for a= nswering. That seems a bit "strange". The specifically =0A> reported "probl= ems" in the end are a mouse not working after the restart =0A> but the auth= or did not specify the number of machines he made the test =0A> on and if o= ther problems occur. It would be interesting to know a bit =0A> more about = this (I mean if it happens frequently and if other problems =0A> occur). I = changed the keyboard layout 1-2 times but got no problems here =0A> restart= ing the script.=0A>=0A=0AI think the problem is not the number of machines = tested but the fact it=0Ajust did not work for some users/hardware. This i= s a problem since=0Apeople may think the issue is coming from their fdi scr= ipt when it's=0Ajust the hald daemon unable to reread a file. The proposed= solution=0Aworks for everyone.=0A=0AMaybe we can rewrite the part with a m= ention of rc.d HAL restart and=0Athen with a note telling "if it does not w= ork , you will have to reboot=0Ayour box... blahblah".=0A=0A-- =0AMarc=0A= =0A=0A=0A
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?377659.99448.qm>