× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On a similar note:
IFS != NetServer


date: Tue, 20 Oct 2020 15:30:52 +0000
from: Rob Berendt <rob@xxxxxxxxx>
subject: Note: WRKLNK is not the same as a 'share'!

You do not use WRKLNK to set up shares. You use it to handle things in
the IFS. Sharing is done through other interfaces such as iACS or the
webby navigator for i. Or even GO NETS if you have that loaded.

The reason I bring this up is I was just on a webinar. Part of it was
discussing the evils of sharing the root on IBM i. Something I
wholeheartedly agree with.
You can use multiple interfaces such as WRKLNK, iACS, etc to define
security on a share. That is totally different than using interfaces other
than WRKLNK to define a share as update or read only.
Ok, now with this in mind, this happened on the chat:

Audience Question
Q: wrklnk '/' should have no write permission? Also qopensys/ibm?
A: Correct, never share the root

Well, if someone does this, and uses WRKLNK to change the authority on '/'
to read only they just made the system unusable to a bulk of people. They
should expect a large crowd of pitchforks and torches.
What they should have done is use one of the interfaces other than WRKLNK
to either remove any shares on '/', or to mark the share as read only.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818
http://www.dekko.com




As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.