From owner-freebsd-current Sun Aug 13 08:40:38 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id IAA28029 for current-outgoing; Sun, 13 Aug 1995 08:40:38 -0700 Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id IAA27957 for ; Sun, 13 Aug 1995 08:40:01 -0700 Received: from localhost (localhost [127.0.0.1]) by palmer.demon.co.uk (8.6.11/8.6.11) with SMTP id QAA01938 ; Sun, 13 Aug 1995 16:35:51 +0100 X-Message: This is a dial-up site. Quick responses to e-mails should not be relied upon. Thanks! To: Kim Culhan cc: "Jordan K. Hubbard" , freebsd-current@freebsd.org Subject: Re: -current changed fstab or fstab changed.. In-reply-to: Your message of "Sun, 13 Aug 1995 11:10:29 EDT." Date: Sun, 13 Aug 1995 16:35:50 +0100 Message-ID: <1936.808328150@palmer.demon.co.uk> From: Gary Palmer Sender: current-owner@freebsd.org Precedence: bulk In message , Kim Culh an writes: >Let me know if there is anything I can do to help track this down. >I did a "MAKEDEV all" in the process. Are there negative effects to >running this way? Probably - I think MAKEDEV all will delete the old slice device files before going on to make new device files (missing the slice entries). Try running MAKEDEV sd0s1a (I think, assuming sd0s1 is your FreeBSD partition) and then try mounting something from the old /etc/fstab. I think it should work. It'd probably be safer to unmount it from the current non-slice device before trying the slice device, as I'm not sure what the effects would be of trying to mount the same slice, one through the old pre-slice device, and one through the new slice device :-) Gary