I'm currently trying to use the Fixit cd on AMD64 ( 6.2 )
and it appears it has issues. When trying to fsck a
disk it reports:
fsck: exec fsck_4.2bsd for XXXX in /sbin:/usr/sbin: No such file or directory
When looking on the mounted volumes for fsck_4.2bsd its
located under:
/dist/rescue/fsck_4.2bsd
/dist/sbin/fsck_4.2bsd
Surely /dist/sbin and /dist/usr/sbin should be in the PATH
by default?
Also it seems that fsck uses a hardcoded search path so
setting PATH is not good enough, I had to create a symlink
it into /sbin. With fsck being one of the common things
people do with fixit would be nice if it just worked.
P.S. Not sure if this is limited to AMD64, I suspect not
but thats what I was working on.
Steve
===============================================This e.mail is private and
confidential between Multiplay (UK) Ltd. and the person or entity to whom it is
addressed. In the event of misdirection, the recipient is prohibited from using,
copying, printing or otherwise disseminating it or any information contained in
it.
In the event of misdirection, illegible or incomplete transmission please
telephone +44 845 868 1337
or return the E.mail to postmaster@multiplay.co.uk.
Steven Hartland wrote:> I'm currently trying to use the Fixit cd on AMD64 ( 6.2 ) > and it appears it has issues. When trying to fsck a > disk it reports: > fsck: exec fsck_4.2bsd for XXXX in /sbin:/usr/sbin: No such file or > directory > > When looking on the mounted volumes for fsck_4.2bsd its > located under: > /dist/rescue/fsck_4.2bsd > /dist/sbin/fsck_4.2bsd > > Surely /dist/sbin and /dist/usr/sbin should be in the PATH > by default? > > Also it seems that fsck uses a hardcoded search path so > setting PATH is not good enough, I had to create a symlink > it into /sbin. With fsck being one of the common things > people do with fixit would be nice if it just worked. > > P.S. Not sure if this is limited to AMD64, I suspect not > but thats what I was working on.Sometime back I needed the fixit CD and hit various problems like this (generated a 1/2 dozen items on my TODO list not all of which have been crossed off yet). This stuff gets precious little testing and could use a champion to help improve it. Seems like a chore most anyone could help with... Sam
"Steven Hartland" <killing@multiplay.co.uk> writes:> I'm currently trying to use the Fixit cd on AMD64 ( 6.2 ) > and it appears it has issues. When trying to fsck a > disk it reports: > fsck: exec fsck_4.2bsd for XXXX in /sbin:/usr/sbin: No such file or directory > > When looking on the mounted volumes for fsck_4.2bsd its > located under: > /dist/rescue/fsck_4.2bsd > /dist/sbin/fsck_4.2bsd > > Surely /dist/sbin and /dist/usr/sbin should be in the PATH > by default? > > Also it seems that fsck uses a hardcoded search path so > setting PATH is not good enough, I had to create a symlink > it into /sbin. With fsck being one of the common things > people do with fixit would be nice if it just worked.Sounds similar to this problem I encountered with mount: http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/100436 Bengt