RE: hosed fstab

From owner-freebsd-questions Tue Oct 3 11:41:45 2000 Delivered-To: freebsd-questions@freebsd.org Received: from lcmail2.lc.ca.gov (lcmail2.lc.ca.gov [165.107.12.11]) by hub.freebsd.org (Postfix) with ESMTP id 887D737B503 for ; Tue, 3 Oct 2000 11:41:40 -0700 (PDT) Received: from CONVERSION-DAEMON by lcmail2.lc.ca.gov (PMDF V5.2-27 #40821) id <0G1V00401AKLJ5@lcmail2.lc.ca.gov> for questions@freebsd.org; Tue, 3 Oct 2000 11:41:11 -0700 (PDT) Received: from ldcmsx01.lc.ca.gov ([165.107.11.191]) by lcmail2.lc.ca.gov (PMDF V5.2-27 #40821) with ESMTP id <0G1V0045FAKLEJ@lcmail2.lc.ca.gov> for questions@freebsd.org; Tue, 03 Oct 2000 11:41:09 -0700 (PDT) Received: by ldcmsx01.lc.ca.gov with Internet Mail Service (5.5.2650.21) id ; Tue, 03 Oct 2000 11:41:35 -0700 Content-return: allowed Date: Tue, 03 Oct 2000 11:41:34 -0700 From: "Tomlinson, Drew" Subject: RE: hosed fstab To: "'mattb@finsyn.com'" , "'questions@freebsd.org'" Message-id: <8C224DC088D8D111B67D0000F67AC17E029C5153@ldcmsx01.lc.ca.gov> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: MULTIPART/ALTERNATIVE; BOUNDARY="Boundary_(ID_kGIUbBPoERgGVr1G9Zm0jw)" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --Boundary_(ID_kGIUbBPoERgGVr1G9Zm0jw) Content-type: text/plain; charset="iso-8859-1" I apologize if this message makes it to the list in HTML. My work uses M$ Exchange and being the "friendly" software it is, it converts my messages to HTML for me. But I keep trying to find another way. Sooner or later I'll get it right. > -----Original Message----- > From: Matt Bettinger [mailto:mattb@finsyn.com] > Sent: Tuesday, October 03, 2000 8:11 AM > To: freebsd-questions@freebsd.org > Subject: hosed fstab > > > Hello, > > While messing around with a handspring and coldsync and > editing my fstab (on > a test type machine) i put something in fstab that FreeBSD > did not like upon > a reboot. I don't have the dmesg or bootup screen to show > you but it says > something about 16 bad blocks on usb0 and then immediately > starts fsck which > gives me the error about some bad blocks and the option to > continue or no. > When i continue i immediately get the # prompt but cannot > fix the fstab > file. First of all i can't start an editor but i can use > cat. My thinking > was to delete the ftab file and just cat >> a new one. This was not > possible because i get a message saying it is a read only > system. I am glad > this is just a messing around sort of computer but i started > thinking what > if this happened on one i REALLY use? I had a similar "read-only" problem after upgrading my kernel. Jason was kind enough to resopnd. His message is in the archives at http://www.freebsd.org/cgi/getmsg.cgi?fetch=1960243+1964156+/usr/local/www/d b/text/2000/freebsd-questions/20000910.freebsd-questions. HTH Drew > > How would one fix this problem-- i have the live filesystem > cd and tried > that but i still couldn't write to anything. Are theer any > crash courses > (no pun intended--seriously ;-> ) on how to get in there and > edit a file in > /etc after a messup? I tried to boot the old kernel for > kicks and it still > went into fsck.. Thanks for any info here. > > > Matthew Bettinger > Financial Synergies,Inc. > 1177 West Loop South, Suite 1400 > Houston,Texas 77027-9086 > 713-623-6600 > 713-623-6771 FAX > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > --Boundary_(ID_kGIUbBPoERgGVr1G9Zm0jw) Content-type: text/html; charset="iso-8859-1" Content-transfer-encoding: quoted-printable RE: hosed fstab

I apologize if this message makes it to the list in = HTML. My work uses M$ Exchange and being the "friendly" = software it is, it converts my messages to HTML for me. But I = keep trying to find another way. Sooner or later I'll get it = right.

> -----Original Message-----
> From: Matt Bettinger [mailto:mattb@finsyn.com]
> Sent: Tuesday, October 03, 2000 8:11 AM
> To: freebsd-questions@freebsd.org
> Subject: hosed fstab
>
>
> Hello,
>
> While messing around with a handspring and = coldsync and
> editing my fstab (on
> a test type machine) i put something in fstab = that FreeBSD
> did not like upon
> a reboot. I don't have the dmesg or = bootup screen to show
> you but it says
> something about 16 bad blocks on usb0 and then = immediately
> starts fsck which
> gives me the error about some bad blocks and = the option to
> continue or no.
> When i continue i immediately get the # = prompt but cannot
> fix the fstab
> file. First of all i can't start an = editor but i can use
> cat. My thinking
> was to delete the ftab file and just cat = >> a new one. This was not
> possible because i get a message saying it is a = read only
> system. I am glad
> this is just a messing around sort of computer = but i started
> thinking what
> if this happened on one i REALLY use?

I had a similar "read-only" problem after = upgrading my kernel. Jason was kind enough to resopnd. His = message is in the archives at http://www.freebsd.org/cgi/getmsg.cgi?fetch=3D1960243+= 1964156+/usr/local/www/db/text/2000/freebsd-questions/20000910.freebsd-q= uestions.

HTH

Drew

>
> How would one fix this problem-- i have the = live filesystem
> cd and tried
> that but i still couldn't write to = anything. Are theer any
> crash courses
> (no pun intended--seriously ;-> ) on how to = get in there and
> edit a file in
> /etc after a messup? I tried to boot the = old kernel for
> kicks and it still
> went into fsck.. Thanks for any = info here.
>
>
> Matthew Bettinger
> Financial Synergies,Inc.
> 1177 West Loop South, Suite 1400
> Houston,Texas 77027-9086
> 713-623-6600
> 713-623-6771 FAX
>
>
>
>
>
> To Unsubscribe: send mail to = majordomo@FreeBSD.org
> with "unsubscribe freebsd-questions" = in the body of the message
>

--Boundary_(ID_kGIUbBPoERgGVr1G9Zm0jw)-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message