Date: Tue, 1 Sep 1998 23:27:16 +0000 (GMT) From: "Jason C. Wells" <jason@washington.edu> Cc: freebsd-stable@FreeBSD.ORG Subject: Compatibility Naming Was: Requisite steps Message-ID: <Pine.BSF.4.02A.9809012314240.1713-100000@s8-37-26.student.washington.edu> In-Reply-To: <Pine.BSF.3.96.980902134829.22379B-100000@angmar.mel.cybec.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2 Sep 1998, Lachlan O'Dea wrote: >Just my 2c on tracking -stable: I think a good example of how it should >work was the removal of compatibility slice names. In that instance, Please don't chuckle. I do not recall the term "compatibilty slice name". I just supped my first sources last week. What does "compatibility slice name" mean? I did notice that the scsi drive was named differently than the ide back when I upgraded to 2.2.6 a while ago. Nothing was broke so I didn't worry about it. I am curious to know if there is something egregiously wrong with my system that I never picked up on. $ mount /dev/wd0s2a on / (local) /dev/sd0f on /usr (local) /dev/sd0e on /var (local) procfs on /proc (local) (In case you were wondering, my bios won't boot scsi. This was a pain in the butt to get working right.) Catchya Later, | UW Mechanical Engineering Jason Wells | http://weber.u.washington.edu/~jcwells/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.02A.9809012314240.1713-100000>