Why aren't all files in a Package?
Loren M. Lang
lorenl at alzatex.com
Sun Feb 8 07:00:52 PST 2004
Certain core files that come with freebsd don't seem to belong to any
package, one of them being zlib. I was trying to figure out what
version of zlib FreeBSD is using, but since it wasn't part of any
package, it was a little difficult, I had to edit libz.so and greped for
1.1.4. Since I found that, I'm assuming that that's the correct
version, but I think a simple pkg_info -W should have answered that.
Also, programs like named seem to come default as part of named and
therefore have no package associated with them, but there is also a
version in the ports collection. How do I uninstall the version in
/usr so I can be assured that the version being invoked is in
The last problem is that it makes it more difficult to find the source
code for a particular core program. Is there any way I can access it
any easier like I was doing in debian? "dpkg -S /path/to/file" tells me
the package name, then "apt-get source package" downloads that package.
I sense much NT in you.
NT leads to Bluescreen.
Bluescreen leads to downtime.
Downtime leads to suffering.
NT is the path to the darkside.
Powerful Unix is.
Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc
Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20040208/62b4c536/attachment.bin
More information about the freebsd-questions