From: Brian Dessent [mailto:[EMAIL PROTECTED]
Yes, those symlinks in /etc are explicitly created with Win32
paths by the base-files postinstall script. I think the
reasoning here is that if a POSIX path were used for the
target of the symlink then it would have to be updated if the
Matt Seitz (matseitz) wrote:
I appreciate your taking the time to read my suggestion and respond so
quickly with such a complete clear and complete explanation.
As an alternative suggestion, how about using forward slashes instead of
backwards slashes (C:/windows/system32/drivers/etc/hosts)
From: Brian Dessent [mailto:[EMAIL PROTECTED]
That would be up to the base-files package maintainer,
however I don't think it's necessary. As I said the current
DLL code already normalizes symlink targets so if you use a
snapshot you will see those links in POSIX form with ls -l
even
What do you think of changing ls -l to display symbolic links using
POSIX style paths instead of Windows style?
When I run ls -l /etc, the symbolic links are displayed using Windows
format (C:\WINDOWS\system32\drivers\etc\hosts). It would be easier to
copy and paste the output to a cd command if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Matt Seitz (matseitz) on 9/19/2007 5:32 PM:
What do you think of changing ls -l to display symbolic links using
POSIX style paths instead of Windows style?
When I run ls -l /etc, the symbolic links are displayed using Windows
format
Eric Blake wrote:
Symlinks merely contain whatever text they were created with. If the text
it was created with was Windows style, then readlink(2) will not translate
it. I suppose I could try to patch ln(1) to posix-ify any name that looks
like a Windows filename before actually calling
6 matches
Mail list logo
