start_udev and X crashing after latest FC3T2 update

[Clyde Kunkel]

On Wed, 2004-09-29 at 13:54, Brian Millett wrote:
> > On Wed, 2004-09-29 at 11:56, Matias Feliciano wrote:
> >> Le mer 29/09/2004 à 17:29, Clyde Kunkel a écrit :
> >> > Finished updated FC3T2 this AM and get error msg unexpected } in
> >> line 79 of /sbin/start_udev.
> >>
> >> Don't know if this is related but udev-032-4 seems broken.
> >> http://www.redhat.com/archives/fedora-devel-list/2004-September/msg01189.html
> >>
> >>
> >> ______________________________________________________________________
> >> --
> >> fedora-test-list mailing list
> >> fedora-test-list at redhat.com
> >> To unsubscribe:
> >> http://www.redhat.com/mailman/listinfo/fedora-test-list
> >
> > Yeah...saw this...too late...now trying to recover.  Hope someone can
> > tell me how.
> 
> Well, I booted into single user.  Vied /sbin/start_udev and added a 'fi'
> to the code to fix the sintax error (see arrow):
> 
> mount_udev() {
>         if [ -z "$SELINUX" ]; then
>                 if [ -n "$selinuxfs" ] && [ "`cat
> /proc/self/attr/current`" != "kernel" ]; then
>                 if [ -r $selinuxfs/enforce ] ; then
>                         SELINUX=`cat $selinuxfs/enforce`
>                 else
>                         # assume enforcing if you can't read it
>                         SELINUX=1
> ---->           fi
>                 fi
>         fi
>         if [ -n "$SELINUX" -a "$SELINUX" = "1" -o "$SELINUX" = "enforcing"
> ]; then
>                 mount -n -o fscontext=system_u:object_r:device_t,mode=0755 \
>                         -t tmpfs none "$udev_root" >/dev/null 2>&1 &&
> return 0
>         fi
>         mount -n -o mode=0755 -t tmpfs none "$udev_root"
>         return $?
> }
> 
> Then I rebooted and other than kudzu wanting to add a new graphic card
> (which I ignored),  it came up ok.

I made the same change, but still don't get an X system.