From owner-freebsd-current Tue Mar 6 8:38:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id 12D6F37B718 for ; Tue, 6 Mar 2001 08:38:48 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.11.3/8.11.3) id f26GfJe09146; Tue, 6 Mar 2001 08:41:19 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <200103061641.f26GfJe09146@troutmask.apl.washington.edu> Subject: Re: tape device names and devfs In-Reply-To: <982uie$cer$1@kemoauc.mips.inka.de> "from Christian Weisgerber at Mar 6, 2001 03:09:02 pm" To: Christian Weisgerber Date: Tue, 6 Mar 2001 08:41:19 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christian Weisgerber wrote: > Steve Kargl wrote: > > > dump.8 and dump(8) both refer explicitly to nsa0 and nrsa0 whereas ^^^^ whoops rsa0 > > sa0 and nsa0 are the actual device names in -current. > > Then this should be fixed. But, what is the correct fix? Add symlink magic to rc.devfs? Change dump(8)? > The non-'r' device names have been standard in -CURRENT for quite > some time. MAKEDEV only creates 'r'-names for backwards compatibility. MAKEDEV's behavior satisfies POLA by creating the symlinks. If symlinks aren't created in rc.devfs, then how many (custom) scripts will this break? -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message