Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 07 Sep 2003 15:25:52 -0700
From:      "Bruce A. Mah" <bmah@freebsd.org>
To:        Randy Bush <randy@psg.com>
Cc:        freebsd-security@freebsd.org
Subject:   Re: @LongLink 
Message-ID:  <200309072225.h87MPqYe008845@intruder.kitchenlab.org>
In-Reply-To: <E19w6hP-000LPn-0I@ran.psg.com> 
References:  <E19w5ZA-000JeV-H4@ran.psg.com> <20030907203633.GA35241@x-anthony.com> <5.2.0.9.0.20030907170253.0993d6a0@209.112.4.2> <E19w6hP-000LPn-0I@ran.psg.com>

next in thread | previous in thread | raw e-mail | index | archive | help
--==_Exmh_-2143965968P
Content-Type: text/plain; charset=us-ascii

If memory serves me right, Randy Bush wrote:
> >>> what does 'file' tell you?
> >>>> what the heck is
> >>>> # ls -li /usr/\@LongLink
> >>>> 3 ----------  1 root  wheel  111 Jan  1  1970 /usr/@LongLink
> >> @LongLink: ASCII text, with no line terminators
> >> what disturbs me is the inode number
> > What does
> > find / -inum 3 -ls
> > show it linked to ?
> 
> <doh>  but it does not make me more clueful

[snip]

> it's the only inode 3 on /usr

We used to have this problem with extremely long (>100 characters or so)
pathnames in the ports tree, almost always patch files.  Part of the
problem was that we used GNU tar to create an archive that was then
unpacked using cpio (in sysinstall).  I remember dealing with this twice
since joining the RE team.  Not sure if that's related to your
situation, tho'.

Bruce.



--==_Exmh_-2143965968P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (FreeBSD)
Comment: Exmh version 2.5+ 20020506

iD8DBQE/W7Bv2MoxcVugUsMRAubPAJ9sEI8AgWcbquZ6giNU/71NOZ+fmQCg8eIK
+gHA5S3LnDioQRktlkHDGp4=
=BTB4
-----END PGP SIGNATURE-----

--==_Exmh_-2143965968P--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200309072225.h87MPqYe008845>