Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 27 Oct 95 23:57 WET DST
From:      uhclem%nemesis@fw.ast.com
To:        FreeBSD-gnats-submit@freebsd.org
Subject:   bin/797: X probeonly during install gets Not Found error FDIV037
Message-ID:  <m0t93Kr-000IvJC@nemesis.lonestar.org>
Resent-Message-ID: <199510280510.WAA13391@freefall.freebsd.org>

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

>Number:         797
>Category:       bin
>Synopsis:       X probeonly during install gets Not Found error FDIV037
>Confidential:   no
>Severity:       non-critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Oct 27 22:10:01 PDT 1995
>Last-Modified:
>Originator:     Frank Durda IV
>Organization:
>Release:        FreeBSD 2.1.0-951026-SNAP
>Environment:

1026 system freshly installed and still running from boot floppy (not
yet rebooted.)

>Description:

After a successful installation, if you have installed X and elect
to configure X, at one point it asks if you would like to set up a
Symlink X to start X.  I answered "yes".  A few dozen questions later
when configuring my video board, I was offered the chance to test the
clock settings by doing a probeonly.  When this was attempted, I get a
"X: Command not found.", so the probeonly is not performed.

It appears the symlink is not yet in place or is not in the right place
for where the X configuration is looking.

>How-To-Repeat:

See above.

>Fix:
	
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m0t93Kr-000IvJC>