Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 30 Nov 2011 10:16:06 -0700
From:      Warner Losh <imp@bsdimp.com>
To:        Aryeh Friedman <aryeh.friedman@gmail.com>
Cc:        freebsd-x11@freebsd.org, rc@freebsd.org, Chris Rees <utisoft@gmail.com>
Subject:   Re: xdm does not work junder BETA3
Message-ID:  <00701089-9A0A-4309-8A6B-D6AF34CDEBF0@bsdimp.com>
In-Reply-To: <CAGBxaX=sHEcvhM6_jMCCC3jcHn2RVESpW_ujFGi_pJkYGT_EUg@mail.gmail.com>
References:  <CAGBxaXnPHgYNJ4cxKbKgiaChu3%2BCuHDheGPAX7fkU0_BumtG9g@mail.gmail.com> <CAF6rxgkgipSRakreBjMAn5KZKr4KEsfQVj3fyU_N7VAoU7x3oQ@mail.gmail.com> <CAGBxaXmWS7vDtJa00ES6VL8BBpTmg1P2d3Sv=g-zub6noJ=Piw@mail.gmail.com> <CAF6rxg=DCk-ERpMtmDs2xyG5-noOztjgBMguZ_Xp_x=iRp5SOw@mail.gmail.com> <CAGBxaXmnckNWx=aGUzsbonUbJh0is8N%2BtxRA2NhmoZuFwZub-A@mail.gmail.com> <CADLo839qvbmbwAsai7sGFjnx0TT8ABDMDEftVUzi7mBytJsQNQ@mail.gmail.com> <CAGBxaX=sHEcvhM6_jMCCC3jcHn2RVESpW_ujFGi_pJkYGT_EUg@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

/var/run isn't ever cleared on boot.  Programs are supposed to cope with with stale .pid files, since they might have died w/o deleting it...

Warner

On Nov 30, 2011, at 3:07 AM, Aryeh Friedman wrote:

> On Wed, Nov 30, 2011 at 3:34 AM, Chris Rees <utisoft@gmail.com> wrote:
> 
>> 
>> On 29 Nov 2011 03:43, "Aryeh Friedman" <aryeh.friedman@gmail.com> wrote:
>>> 
>>> I found the problem it never deleted the /var/run/xdm.pid on reboot
>> 
>> Shouldn't /var/run be cleared on boot?
>> 
>> Cc rc, sorry for cross-posting but it seems to be that kind of issue.
>> 
>> Chris
>> 
> 
> Yes in theory the machine should when it does a cold (and this includes the
> power/reset button) boot the machine from the moment the processor does
> it's very first cycle to the time I type the very first key and/or the
> first mouse movement as a fully logged in user (via XDM) using the default
> XFCE4 desktop with my default configs means that the when the machine
> shutdown it left *ZERO* evidence that it had ever existed... in other words
> the default start up (POST --> bootloader --> single user mode --> xdm -->
> xfce4) does not need to worry about getting rid of side effects of this....
> in the windows world this is done with a program by the name of "Freeze
> Dry".... the only problem with Freeze Dry is a) it runs on windows only
> (needs a disk formatted and booted with fat32), b) it requires a mirror
> drive with the default config to over write and then boot on the active
> slice and c) makes it nearly impossible to make "local" changes (actually
> it's primary audience is college computer [and other public computer]
> labs/sites that need to be able to reboot to the same config no matter what
> weird thing the user did).... item c is what makes it hard to use that so
> instead the entier start up process should never see any evidence that it
> is not the very first OS ever booted on this machine being booted for the
> first time
> _______________________________________________
> freebsd-rc@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-rc
> To unsubscribe, send any mail to "freebsd-rc-unsubscribe@freebsd.org"
> 
> 




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00701089-9A0A-4309-8A6B-D6AF34CDEBF0>