«

Bling-Bling wrote:
>>Do you think that if any OS has a feature than another OS had earlier,
>>then that feature isn't native? Filesystems themselves then wouldn't be
>>native to Unix according to your logic.

> About as native as a Pakeha New Zealander who was born in New Zealand.
> How "native" is that?

very, Im a new zealander, always have been, so Im native.

other than number 5 below, I fit into each one.

http://dictionary.reference.com/search?q=native

na·tive Audio pronunciation of "native" ( P ) Pronunciation Key (ntv)
adj.

1. Existing in or belonging to one by nature; innate: native ability.
2. Being such by birth or origin: a native Scot.
3. Being one's own because of the place or circumstances of one's
birth: our native land.
4. Originating, growing, or produced in a certain place or region;
indigenous: a plant native to Asia.
5.
1. Being a member of the original inhabitants of a particular
place.
2. Of, belonging to, or characteristic of such inhabitants:
native dress; the native diet of Polynesia.
6. Occurring in nature pure or uncombined with other substances:
native copper.
7. Natural; unaffected: native beauty.
8. Archaic. Closely related, as by birth or race.
9. Biochemistry. Of or relating to the naturally occurring
conformation of a macromolecule, such as a protein.

Bling-Bling wrote:
>>But what proportion of Dimdows software will accept those UNC names with
>>no drive letters?

> If they use file systems not recognised by Windoze then a big fat zero
> percent of those file systems will be given drive letters.
> Windows understands FAT and NTFS. That is all.

there are plenty of third party add-ons... just like the linux kernl
doesn't support some file systems nativly, it can be made to understand
it with additional software.

****, another week another lesson for lennier.

On Tue, 14 Jun 2005 07:17:37 +1200, Dave - Dave.net.nz wrote:

> Bling-Bling wrote:
>>>Do you think that if any OS has a feature than another OS had earlier,
>>>then that feature isn't native? Filesystems themselves then wouldn't be
>>>native to Unix according to your logic.
>
>> About as native as a Pakeha New Zealander who was born in New Zealand.
>> How "native" is that?

<snip>

> http://dictionary.reference.com/search?q=native
>
> na·tive Audio pronunciation of "native" ( P ) Pronunciation Key (ntv)
> adj.
>
> 1. Existing in or belonging to one by nature; innate: native ability.

And I suspect definition 1 is the one that applies in a computer context.

--
Cheers
Anton

On Mon, 13 Jun 2005 22:04:58 +1200, Lawrence D¹Oliveiro wrote:

> In article <>,
> "AD." <> wrote:
>
>>On Mon, 13 Jun 2005 17:45:34 +1200, Lawrence D¹Oliveiro wrote:
>>
>>> In article <>,
>>> "AD." <> wrote:
>>>
>>>>On Sun, 12 Jun 2005 10:18:41 +1200, Lawrence D¹Oliveiro wrote:
>>>>
>>>>> Have you not heard of application partitioning? That's a common
>>>>> concept in the mainframe world where each application is made to
>>>>> believe it's running on its own machine, with careful limits on the
>>>>> resources (CPU, VM etc) it's allowed to use so it doesn't impact
>>>>> other applications. Resources of course would include mounted
>>>>> filesystems. Thus, running a lot of applications could lead to having
>>>>> a lot of filesystems mounted.
>>>>
>>>>Wouldn't those filesystems be virtual? That's how VMWare, Virtual PC,
>>>>SANs etc etc work.
>>>
>>> I don't see why you'd want them to be. You'd want to dedicate real
>>> disks to them.
>>
>>What's the point of having virtual machines then?
>
> ... they had nothing to do with my point anyway.

So what was your point?

--
Cheers
Anton

Bling-Bling wrote:
> On Mon, 13 Jun 2005 22:22:02 +1200, FreedomChooser wrote:
>
>
>>>Right. The Third Party software understands ext2 & 3, not Windoze.
>>
>>Windows understands it with additional software.
>
>
> Windoze needs a translator.
>
>
> Bling Bling
>



It uses an IFS driver,

http://uranus.it.swin.edu.au/~jn/linux/ext2ifs.htm

In article <>,
"AD." <> wrote:

>.. UNC names are paths to network shares...

So you can't use them for locally-connected disks, hotplug devices and
like that?

In article <>,
"Dave - Dave.net.nz" <> wrote:

>Matthew Poole wrote:
>>>>>I believe that most Unix systems won't allow more than 256 mountpoints...
>
>>>>Which is nevertheless an order of magnitude beyond that manageable with
>>>>Dimdows drive letters.
>
>>>and mounting as folders?
>>>has anyone hit the limit? or knows what the limit is?
>
>> If I can find a spare HDD to play with, I'll try it out. Is there a limit
>> to how many partitions an HDD's MBR can reference?
>
>I got bored one days and partitioned my USB flash drive into 2MB
>partitions, I got to ~40 before I got bored.

Shame you don't have command-line tools you can use to write a script to
automate a task like that.

There is. If you had ever found the answer to your original question you
would know the answer already.

"Lawrence D¹Oliveiro" <_zealand> wrote in message
news:ldo-...
> In article <>,
> "Dave - Dave.net.nz" <> wrote:
>
>>Matthew Poole wrote:
>>>>>>I believe that most Unix systems won't allow more than 256
>>>>>>mountpoints...
>>
>>>>>Which is nevertheless an order of magnitude beyond that manageable with
>>>>>Dimdows drive letters.
>>
>>>>and mounting as folders?
>>>>has anyone hit the limit? or knows what the limit is?
>>
>>> If I can find a spare HDD to play with, I'll try it out. Is there a
>>> limit
>>> to how many partitions an HDD's MBR can reference?
>>
>>I got bored one days and partitioned my USB flash drive into 2MB
>>partitions, I got to ~40 before I got bored.
>
> Shame you don't have command-line tools you can use to write a script to
> automate a task like that.

You can use them for for almost anything.
I suggest you read up about IOManager and RDR along with IFS.

"Lawrence D¹Oliveiro" <_zealand> wrote in message
news:ldo-...
> In article <>,
> "AD." <> wrote:
>
>>.. UNC names are paths to network shares...
>
> So you can't use them for locally-connected disks, hotplug devices and
> like that?

In article <>,
FreedomChooser <> wrote:

>On Sat, 11 Jun 2005 18:56:56 +1200, Lawrence D¹Oliveiro
><_zealand> wrote:
>
>>In article <>,
>> Matthew Poole <> wrote:
>>
>>>On Sat, 11 Jun 2005 17:50:29 +1200, someone purporting to be Lawrence
>>>D¹Oliveiro didst scrawl:
>>>
>>>> In article <>,
>>>> Matthew Poole <> wrote:
>>>>
>>>>>I believe that most Unix systems won't allow more than 256 mountpoints...
>>>>
>>>> Which is nevertheless an order of magnitude beyond that manageable with
>>>> Dimdows drive letters.
>>
>>>But not necessarily more than is possible using the directory mounting
>>>concept.
>>
>>You mean the Dimdows directory-mounting/splicing using SUBST/JOIN etc?
>>Last I heard there were severe limitations on that, like being unable to
>>do a SUBST on a SUBST etc.
>
>How many hands removed from an authoritative source was that

Windows API error codes for things that don't work
<http://www.bordergatewayprotocol.net...dows/errorcode
s.html>:

ERROR_IS_JOIN_TARGET
A JOIN or SUBST command cannot be used for a drive that contains
previously joined drives.
ERROR_IS_JOINED
An attempt was made to use a JOIN or SUBST command on a drive that has
already been joined.
ERROR_IS_SUBSTED
An attempt was made to use a JOIN or SUBST command on a drive that has
already been substituted.
ERROR_JOIN_TO_JOIN
The system tried to JOIN a drive to a directory on a joined drive.
ERROR_SUBST_TO_SUBST
The system tried to SUBST a drive to a directory on a substituted drive.
ERROR_JOIN_TO_SUBST
The system tried to JOIN a drive to a directory on a substituted drive.
ERROR_SUBST_TO_JOIN
The system tried to SUBST a drive to a directory on a joined drive.

In other words, you can't stack multiple JOINs/SUBSTs.