On 4/21/2016 3:05 PM, Daniel Barrett wrote:
> If only it were that simple. The Administrators ACL already has Full
> Control of parent "foo" and all its contents, recursively. We have
> also run a recursive "Change Permissions" operation several times for
> "foo", just to be sure, without fixing
On April 21, 2016, Rich Pieri wrote:
>You're just looking in the wrong place for the answer. The lock
>isn't on bar and bar2. It's on foo. bar and bar2 inherit from parent foo
>and it sounds like someone removed the Administrators group ACL from it
>(or perhaps it was never there). You could use
On 4/21/2016 1:41 PM, Daniel Barrett wrote:
> Moreover, when I created a second folder as a sibling, c:\foo\bar2, I
> could not open the bar2 folder either. Note that I had just CREATED
> the folder MYSELF... and did I mention that I'm an administrator?
>
> The mind reels.
Nah. You're just
There are special moments when you just have to thank your favorite
deity that Linux exists.
Today I was working on a Windows Server 2008 system, and I came across
a folder, C:\foo\bar, that I could not open.
The folder is on a local disk, and I'm a local administrator on the
server. And yet, I
On 04/21/2016 12:38 PM, Mike Small wrote:
David Rosenstrauch writes:
On 04/21/2016 12:50 AM, Mike Small wrote:
"Sadly it seems that we now need to either wait for Linux or Windows to
catch up with the 1980s state of the art in distributed systems (think
Locus or AFS). What
On 4/21/2016 12:01 PM, Mike Small wrote:
> I'm thinking from the perspective of a person writing a program more
> than an end user. It's easy to abstract details from a user (though
> whether the result is completely palatable without them buying new
> computers often may be in question). What
David Rosenstrauch writes:
> On 04/21/2016 12:50 AM, Mike Small wrote:
>> "Sadly it seems that we now need to either wait for Linux or Windows to
>> catch up with the 1980s state of the art in distributed systems (think
>> Locus or AFS). What went wrong? Products like
On 04/21/2016 12:50 AM, Mike Small wrote:
After the meeting I was discussing this issue with a friend. It's not an
original criticism I didn't suppose, so I found someone with better
words to sum up my reaction:
"Sadly it seems that we now need to either wait for Linux or Windows to
catch up
Hmmm. I guess I meant single system image more in the sense of an
extension of the research work done in the 80s (and nineties a little?)
in the sense of there being a real network operating
system. i.e. something picking up from where Chorus or Amoeba left
off. (I haven't used these systems only
On 4/21/2016 12:50 AM, Mike Small wrote:
> "Sadly it seems that we now need to either wait for Linux or Windows to
> catch up with the 1980s state of the art in distributed systems (think
> Locus or AFS). What went wrong? Products like DataSynapse’s FabricServer
> look like an interesting attempt
On Thu, Apr 21, 2016 at 04:50:35AM +, Mike Small wrote:
>
> After the meeting I was discussing this issue with a friend. It's not an
> original criticism I didn't suppose, so I found someone with better
> words to sum up my reaction:
>
> "Sadly it seems that we now need to either wait for
11 matches
Mail list logo