What would be the correct security settings for a directory that:
- Allows anyone to add a file
- Anyone can read any file
- Nobody can delete, edit or replace existing files.
Thinking of setting this up on CHIMPY for people to store nifty stuff they find.
sampsa <sampsa at mac.com>
mobile +358 40 7208932
On Mon, 7 Oct 2013, Rok Vidmar wrote:
That doesn't list VAX support
True. My bad. Sorry.
No Alpha in cluster? That's why I love cluster.
--
Regards, Rok
If my Alpha didn't pull 700W i'd happily drop it in to a cluster. ;)
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On Mon, 7 Oct 2013, Rok Vidmar wrote:
Fighting with having no compilers as valid commands
despite having them installed is the only problem now.
Get <http://www.digiater.nl/dfu.html> and use it to search
for newest DCLTABLES.EXE and copy it to
SYS$COMMON:[SYSLIB]
--
Regards, Rok
That doesn't list VAX support
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
Fighting with having no compilers as valid commands
despite having them installed is the only problem now.
Get <http://www.digiater.nl/dfu.html> and use it to search
for newest DCLTABLES.EXE and copy it to
SYS$COMMON:[SYSLIB]
--
Regards, Rok
On 7 Oct 2013, at 23:27, "Brian Schenkenberger, VAXman-" <system at TMESIS.COM> wrote:
Sampsa Laine <sampsa at mac.com> writes:
Brian,
Any news / progress on the EISNER project?
No news. Hopefully, that trasnlates to good news.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
Cool. Pretty excited about the prospect myself.
Sampsa
On Mon, 7 Oct 2013, Brian Schenkenberger, VAXman- wrote:
Weird. Despite the error UUCP seems to be working correctly.
What error are you getting and where?
%SYS-Abort. It seems it might just be when there's no data to send either way as UUCP transfers work.
Fighting with having no compilers as valid commands despite having them installed is the only problem now.
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
Cory Smelosky <b4 at gewt.net> writes:
On Mon, 7 Oct 2013, Cory Smelosky wrote:
On Mon, 7 Oct 2013, Cory Smelosky wrote:
On Mon, 7 Oct 2013, Brian Schenkenberger, VAXman- wrote:
Cory Smelosky <b4 at gewt.net> writes:
On Mon, 7 Oct 2013, Cory Smelosky wrote:
Let's assume you have no need for your prior accounting information...
$ SET ACCOUNTING/NEW_FILE/ENABLE=IMAGE
Execute the UUCP command(s) which fail.
$ ACCOUNTING/SINCE=TODAY
Post that output and let's see if there's anything revealing in there.
Also, you can $ SET ACCOUNTING/DISABLE=IMAGE because /ENABLE=IMAGE can
become a resource hog.
Doing so now.
I disabled TERM/INQ on login in SYLOGIN and the abort went away
(ACCOUNTING didn't have anything useful to say). I know I can disable it
per-line/per-use but this was the quickest test.
Now we're getting somewhere.
Try putting:
$ IF "''F$mode()'".EQS."NETWORK" THEN $ EXIT
at the beginning of your SYLOGIN.COM and LOGIN.COM files.
You can not SET TERM/INQUIRE if there's no terminal. ;)
It's coming in on a serial line, actually. Apparently that's not the
problem though as it's SYSTEM-ABORTing again...
Don't get why it works sometimes and sometimes not. I need Mark P's help for
this.
Weird. Despite the error UUCP seems to be working correctly.
What error are you getting and where?
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
On Mon, 7 Oct 2013, Cory Smelosky wrote:
On Mon, 7 Oct 2013, Cory Smelosky wrote:
On Mon, 7 Oct 2013, Brian Schenkenberger, VAXman- wrote:
Cory Smelosky <b4 at gewt.net> writes:
On Mon, 7 Oct 2013, Cory Smelosky wrote:
Let's assume you have no need for your prior accounting information...
$ SET ACCOUNTING/NEW_FILE/ENABLE=IMAGE
Execute the UUCP command(s) which fail.
$ ACCOUNTING/SINCE=TODAY
Post that output and let's see if there's anything revealing in there.
Also, you can $ SET ACCOUNTING/DISABLE=IMAGE because /ENABLE=IMAGE can
become a resource hog.
Doing so now.
I disabled TERM/INQ on login in SYLOGIN and the abort went away
(ACCOUNTING didn't have anything useful to say). I know I can disable it
per-line/per-use but this was the quickest test.
Now we're getting somewhere.
Try putting:
$ IF "''F$mode()'".EQS."NETWORK" THEN $ EXIT
at the beginning of your SYLOGIN.COM and LOGIN.COM files.
You can not SET TERM/INQUIRE if there's no terminal. ;)
It's coming in on a serial line, actually. Apparently that's not the problem though as it's SYSTEM-ABORTing again...
Don't get why it works sometimes and sometimes not. I need Mark P's help for this.
Weird. Despite the error UUCP seems to be working correctly.
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
