From owner-freebsd-x11@FreeBSD.ORG Wed Nov 30 17:22:33 2011 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 27F6F1065673; Wed, 30 Nov 2011 17:22:33 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id AA5628FC0C; Wed, 30 Nov 2011 17:22:32 +0000 (UTC) Received: from [10.30.101.60] ([209.117.142.2]) (authenticated bits=0) by harmony.bsdimp.com (8.14.4/8.14.3) with ESMTP id pAUHGBUZ074738 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Wed, 30 Nov 2011 10:16:12 -0700 (MST) (envelope-from imp@bsdimp.com) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: Date: Wed, 30 Nov 2011 10:16:06 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <00701089-9A0A-4309-8A6B-D6AF34CDEBF0@bsdimp.com> References: To: Aryeh Friedman X-Mailer: Apple Mail (2.1084) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (harmony.bsdimp.com [10.0.0.6]); Wed, 30 Nov 2011 10:16:13 -0700 (MST) Cc: freebsd-x11@freebsd.org, rc@freebsd.org, Chris Rees Subject: Re: xdm does not work junder BETA3 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Nov 2011 17:22:33 -0000 /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 wrote: >=20 >>=20 >> On 29 Nov 2011 03:43, "Aryeh Friedman" = wrote: >>>=20 >>> I found the problem it never deleted the /var/run/xdm.pid on reboot >>=20 >> Shouldn't /var/run be cleared on boot? >>=20 >> Cc rc, sorry for cross-posting but it seems to be that kind of issue. >>=20 >> Chris >>=20 >=20 > 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" >=20 >=20