From mboxrd@z Thu Jan 1 00:00:00 1970 From: andreww591@gmail.com (Andrew Warkentin) Date: Sat, 25 Mar 2017 06:48:12 -0600 Subject: [TUHS] Were all of you.. Hippies? In-Reply-To: <1490418111.873845.922914640.6B33341A@webmail.messagingengine.com> References: <009301d2a1c9$cb604c70$6220e550$@ronnatalie.com> <20170321202839.GG21805@naleco.com> <20170324001832.GA13511@naleco.com> <20170324002754.GW23802@mcvoy.com> <20170324034915.GA23802@mcvoy.com> <1490418111.873845.922914640.6B33341A@webmail.messagingengine.com> Message-ID: On 3/24/17, Random832 wrote: > > Does readlink need to exist as a system call? Maybe it should be > possible to open and read a symbolic link - using a flag passed to open, > like AT_SYMLINK_NOFOLLOW. > You have a point there. UX/RT will still obviously need to retain the readlink() function (since compatibility with conventional Unix will be a major feature, and it's also convenient to have a single function to get the target of a link), although it could be implemented with a normal read underneath. Same with opendir(), readdir(), and the like, which I was definitely planning on implementing with normal reads (under BSD they seem to already be implemented that way).