Re: symbolic links

Article View: net.bugs.2bsd

Article #144

#144

From: Dan Lanciani
Date: Thu, 23 Aug 1984 04:53

17 lines
1370 bytes

[]
	The problem with the symlink(2) call is that its entry in sysent.c
is within an '#ifdef UCB_NET'.  The local syscall returns [EINVAL] when
it gets a request for an index greater than the maximum valid local syscall.
	As far as I can tell, the #ifdef in question is totally unnecessary
as the unused entries have already been defined as nosys.  (It may be that
someone wanted to save a little table space?)  At any rate, I have removed
it and symlinks work fine for both normal and networking kernels.
	There is a bug in fsck which causes the blocks allocated to
symlinks to be returned to the free-list when a disk is checked.  This
can be fixed by REMOVING the #ifdef's associated with SPECIAL file types
and symlinks, i.e., symlinks are not special.

					Dan Lanciani
					ddl@tardis
					...!{wjh12,harvard}!tardis!ddl
					ddl%tardis@harvard.ARPA

Technical Details

Message-ID: <110@tardis.UUCP>

Path: arc1-ca.pugleaf.net!utzoo!linus!decvax!genrad!wjh12!tardis!ddl

Show Full Headers

Complete Article Headers

Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site tardis.UUCP
Path: arc1-ca.pugleaf.net!utzoo!linus!decvax!genrad!wjh12!tardis!ddl
From: ddl@tardis.UUCP (Dan Lanciani)
Newsgroups: net.bugs.2bsd
Subject: Re: symbolic links
Message-ID: <110@tardis.UUCP>
Date: Thu, 23-Aug-84 00:53:18 EDT
Article-I.D.: tardis.110
Posted: Thu Aug 23 00:53:18 1984
Date-Received: Fri, 24-Aug-84 06:12:39 EDT
Organization: Harvard University, Cruft Lab (TARDIS)
Lines: 17