lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110220231015.GA4001@thunk.org>
Date:	Sun, 20 Feb 2011 18:10:15 -0500
From:	Ted Ts'o <tytso@....edu>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	ext4 development <linux-ext4@...r.kernel.org>, mitchb@....edu
Subject: Re: [PATCH] e2fsprogs: create com_err.h symlink in includedir

On Wed, Feb 16, 2011 at 12:01:39PM -0600, Eric Sandeen wrote:
> After debian bug #192277, debian/rules started making a symlink
> to com_err.h in /usr/include.  Now I have Fedora bug #550889
> for the same issue, and perhaps it's time to make this symlink
> by default, rather than fixing it up in packaging steps?
> 
> Signed-off-by: Eric Sandeen <sandeen@...hat.com>

Pulled into the e2fsprogs tree, with the following change:

    [ Changed by tytso to remove the explicit -s option; this will
      default to creating a hard link by default, which slightly faster.
      If people want to use symlinks for all links during the install
      process, they can use configure option --enable-symlink-install.
      The reason for this change is that some file systems, like AFS,
      don't support symlinks, and AFS users complain when they can't build
      or install into AFS.  So I don't want to use symlinks
      unconditionally without a way of switching things back and forth,
      and it's easier if we just make all links made during the install
      process to be hard links or sym links. ]


      	      	    	       	      	     - Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ