From owner-freebsd-current Sun Jun 20 23:17:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from hun.org (hun.org [216.190.28.252]) by hub.freebsd.org (Postfix) with ESMTP id C39BE14C13 for ; Sun, 20 Jun 1999 23:17:09 -0700 (PDT) (envelope-from attila@hun.org) Received: (from attila@localhost) by hun.org (8.9.3/8.9.2) id GAA10996; Mon, 21 Jun 1999 06:16:47 GMT (envelope-from attila) Date: Mon, 21 Jun 1999 06:16:47 GMT Message-Id: <199906210616.GAA10996@hun.org> From: attila! Reply-To: attila@hun.org To: Mike Smith Cc: freebsd-current@FreeBSD.ORG Subject: Re: ROOTDEVNAME error in conf/LINT Owner: attila@hun.org Organization: hun.org, over 40 years beyond the fringe home for unpenitent hackers and anarcho-cryptophreaks Mailer: XEmacs V20.4 (see alt.religion.emacs) Encrypted: NO Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From mike@smith.net.au Mon Jun 21 05:41:50 1999 * Subject: Re: ROOTDEVNAME error in conf/LINT * * attila said: * > * > am one of those who suffers from lack of politically correct * > attitude -- I dont do M$lop (refuse to), so why should I * > worry about slices? never need slices before M$lop.... however, * > that may change as SCSI disk sizes keep climbing and too large * > partitions take performance hits. * * Has nothing to do with Microsoft. Has everything to do with correct * disk layout. Must use slice entries for system disks likely to be * shared with other operating systems. Should use "truly dedicated" disk * layout for non-shared disks. Defect in libdisk prevents this. Fix * libdisk. Become hero. * well, maybe it is not exclusively M$lop, but I do not run other operating systems... I'm a real BSD bigot. so I run "dangerously dedicated". start with your definition of virgin -out of the box drives and install the old way. never had to live with the boot sector virus from Redmond... manually create fstab and partitions for a pair of IBM 4.5G UW2 SCSIs: # Device Mountpoint FStype Options Dump Pass# /dev/da0b none swap sw 0 0 /dev/da1b none swap sw 0 0 /dev/da0a / ufs rw 1 1 /dev/da0e /user ufs rw 2 2 /dev/da0f /var ufs rw 2 2 /dev/da0g /usr ufs rw 2 2 /dev/da1e /tmp ufs rw 2 2 /dev/da1f /x1 ufs rw 2 2 /dev/da1g /x2 ufs rw 2 2 /dev/da1h /x3 ufs rw 2 2 /dev/cd0c /cdrom cd9660 ro,noauto 0 0 proc /proc procfs rw 0 0 manually (with a script) create the device entries and wipe out any of the slice entries, wd entries and other non-functionals. the boot/loader in 4.0 wants to start you off with disk1s1; first I modified it manually at load, then added /boot/loader.rc load /kernel set rootdev=disk1a set currdev=$rootdev autoboot and off we go --no problems. so, what is the problem in "libdisk" and how do I "become a hero"? --I'm no hero to my 5 kids anymore... might be nice to be known other than as 'pops', 'gramps', or 'the old fart' for a change. ___ ___ ___ _ __ ___ | _ ) __| \ freeBSD: The Power to Serve! _ __ ___ ____ | _ \__ \ |) | Release 4.0 - The Fast Lane! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message