Windows drive mapping conventions

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: Bryce C
Date:  
Subject: Windows drive mapping conventions
--=-k60SYIVombT44C48oB5r
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Way back when, before my life was completely rid of windows file
sharing, it was P that was the shared drive and H was the home
directory. There was also a U drive that had all the users but only
"you" could access "your" directory but that was with w2k and AD.

On Sat, 2003-10-11 at 15:07, Chris Gehlker wrote:
> I'm installing a nice Linux database server for some folks on hardware=20
> that is currently running an NT 4 file/print server. Naturally they=20
> want to keep their file and print services so I need Samba on the Linux=20
> machine. I've been messing with Samba at home and I think I've mastered=20
> it. It really seems to be very easy to set up.
>=20
> There is one thing that I simply can't remember from my brief sentence=20
> in the windows world and that is the convention for 'p' and 'm' drives.=20
> I remember that one is supposed to be mapped to the users home=20
> directory and the other is supposed to be mapped to a shared directory=20
> but I can't for the life of me remember which is which. I did Google=20
> for it but I found one reference that said 'p' is for public drive and=20
> 'm' is the other one while a different reference said 'p' is for=20
> private drive and m is the other one. I couldn't find anything from a=20
> source that could be considered authoritative. I guess this is just=20
> something that Windows users know.
>=20
> What is the real convention, if there is one? Can anyone satisfy my=20
> curiosity as to why it's 'p' and 'm'?
>=20
> ---------------------------------------------------
> PLUG-discuss mailing list -
> To subscribe, unsubscribe, or to change you mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss

--=20
Bryce C <>
CoBryce Communications

--=-k60SYIVombT44C48oB5r
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQA/iIX8/wbq/C6yyPcRArjSAJ9EHy2BYZ1uZA6tpoLw7wNwWK/hpQCfZRQH
yUB22z26xnd7ZTHM9FBn4sY=
=cq6W
-----END PGP SIGNATURE-----

--=-k60SYIVombT44C48oB5r--