Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!newsfeed.internetmci.com!dimensional.com!uunet!in2.uu.net!136.142.185.26!newsfeed.pitt.edu!jlfox From: jlfox+@pitt.edu (James L Fox) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: MAKEDEV problems Date: 30 Jan 1997 23:47:31 GMT Organization: University of Pittsburgh Lines: 24 Message-ID: <5crbuj$pil@usenet.srv.cis.pitt.edu> References: <5cqlt6$m0t@usenet.srv.cis.pitt.edu> <5cr6qs$ojg@usenet.srv.cis.pitt.edu> NNTP-Posting-Host: unixs-eval.cis.pitt.edu Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:34456 In article <5cr6qs$ojg@usenet.srv.cis.pitt.edu>, James L Fox <jlfox+@pitt.edu> wrote: >In article <5cqlt6$m0t@usenet.srv.cis.pitt.edu>, >James L Fox <jlfox+@pitt.edu> wrote: > >Yes, I'm responding to my own post! Here's more info: > ... >Unfortunately, this failure puts me into a read-only state, >from which I can do nothing. I'm a novice at this level >but it looks like I need mknod action, as in /dev/MAKEDEV. > >How do I get write access to /dev ?? > I scanned earlier posts in this group and found directions for recovering from a disk failure and read-only states. # fsck -y # mount -a solved my problem. Thanks, >--Jim Fox