Thanks Josh - good writeup. I was drawing a blank... I've got a scenario
where I use the RK utility linkd.exe to compensate for development
shortcomings where they refer to C:\WINNT and our XP installs used the
default Windows folder. So the word links sometimes blocks out the new term
for them...
Administrators can use the mklink command-line utility from an elevated
(run-as-administrator'd) command prompt to make junctions, hard links, and
symbolic links.
uhoh,
a "symbolic" link?
is that like a "virtual" link?
a "print to screen" link?
a"sandboxed" link?
or the best yet- a "administrator group" link?(will the REAL admin pls STAND
UP?)
LMFAO
lolololololol
Hi Jimmy
Administrators can use the mklink command-line utility from an elevated
(run-as-administrator'd) command prompt to make junctions, hard links, and
symbolic links.
some functionality is simply inevitable and unavoidable, no matter how much
it ends up looking like linux... open source community can respond quicker
to good ideas than Microsoft, though Microsoft can sometimes write more
robust code for it when it does come out. Case in point is the hardware
detection in Windows - linux only wishes it was that good. I've heard it
said that a perfect OS would have the hardware layer of Windows and the rest
would be linux on top of that. There was even speculation on whether or not
Microsoft would license or sell just the hardware layer and open the hooks
so linux could sit on top.
Sorry for my late reply. Thanks for your response and the link in it.
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.