Re: Amazon used lisp & C exclusively?

Tim X wrote:
What absolute nonsense - for someone who made reference to having
worked with Unix and I thought had some sys admin knowledge

I do. I just never used whatever package is being discussed. So the package seems to check for the existance of a symlink. I assumed it was simply a convenient way to "delete and undelete" the package. Obviously, if the code to start the service is checking whether the directory in which the service is installed is there and not complaining if it isn't, then you won't get errors in the logs.

Note that this technique would work equally well under Windows, since Windows has symlinks to directories.

Well make up your mind. Your claim was that sym links were simply
reuired because of broken unix programs. I point out they are a useful
tool and now you state it could have been done a different way. Well,
almost anything can be done a different way - sym links are just an
easy way that currently exists.

Yes. And if Windows does such things a different way, that doesn't mean Windows is broken because it's missing symlinks. (Which it isn't, btw. It has hard links to files, symlinks to directories, and reparse points.)

with BSD), but I do know AT&T Unix v1 had a sticky command and this
was incorporated into the chmod command around v3. The sticky bit
locked data in memory not swap

Um, OK. Considering V1 ran in 32K of RAM on a machine that didn't have page tables, I find this difficult to believe without further evidence. Considering the implementation of fork() was "swap out the process *and* leave it in memory also", I think leaving something in memory when you weren't using it would be problematic. I'd be happy to see evidence to the contrary, tho.

Also, with your claim the chattr command is recent is pretty doddgy.

Fair enough. It wasn't around when *I* was doing my own UNIX admin, is all, which was mid-90's or so. I don't believe it was widespread for quite some time after.

been around for 8 years recent. I won't bother comparing that
functionality at that time with what Windows had to offer.

Windows NT 3.5 had all the same permissions stuff, which was before 1998 obviously.

--
Darren New / San Diego, CA, USA (PST)
This octopus isn't tasty. Too many
tentacles, not enough chops.
.

Relevant Pages

  • Re: Amazon used lisp & C exclusively?
    ... > no real value and implying Unix only needed them because of broken software. ... Just code up a reparse point, and don't restrict it to symlinks for directories, and you're golden. ... And of course Windows also has the distributed link tracking, so if you have a symlink that someone moves the target of, you can get the symlinks fixed automatically, even if the target is on a network drive and you're offline at the time. ... There's all kinds of stuff that Windows does that Linux et al don't, and symlinks to files are the only thing in the file system I hear about Linux doing that Windows doesn't. ...
    (comp.lang.lisp)
  • Re: Can we use Unix as the server?
    ... The server must be Unix ... If so then problem since .net was developed for windows (mono ... I would like to use C#.Net or VB.Net to develop> the C/S package and ASP.Net to develop B/S package. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Creating standalone executables
    ... It doesn't take a genius to figure out how symlinks work. ... >halfway reasonable Unix sysadmin know how to do this. ... allows one to install and test foobar-$new while keeping ... And if I need the foobar package on more than one or two machines, ...
    (comp.lang.lisp)
  • Re: vms versus solaris
    ... > forced people to buy a database package. ... Had RMS been made available to ... > Windows and various Unixes, Oracle wouldn't be where it is today because ... the competition is Windows and Unix which do not have ISAM. ...
    (comp.os.vms)
  • Re: Embedded TCL and Single File Executables
    ... Windows, .so files under UNIX). ... This requires you to modify your application so that it first copies the dynamic library to the run-time file system prior to using it. ... Typically most people would write a standard pkgIndex.tcl file for their dynamic library, and then [package require] it in their code. ...
    (comp.lang.tcl)