Re: determining what's in the base system
Chad Perrin wrote: On Tue, Apr 15, 2008 at 04:35:52PM -0700, Luke Dean wrote: For the second question, I've always assumed that /COPYRIGHT applied to everything in the base system. I'm pretty sure GCC is in the base system (for instance), and it's GPL software. There's no mention of it in /COPYRIGHT at all. Please correct me if I'm mistaken somehow. There's also the ath_hal driver which has its own fairly restrictive license in /sys/contrib/dev/ath/COPYRIGHT . -- Bruce ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: determining what's in the base system
On Tue, Apr 15, 2008 at 05:02:54PM -0700, Chuck Swiger wrote: > On Apr 15, 2008, at 4:14 PM, Chad Perrin wrote: > >I have two questions. First: > > > >Assume you have a FreeBSD system installed that has been running for > >at > >least a year, with a bunch of graphical desktop and productivity > >software > >installed, and have both installed and uninstalled a lot of software > >over > >that time. Now imagine that you want to know whether a given > >utility was > >something that came with the base system or was installed by some > >port or > >package later on. What's the easiest way to do that (preferably > >without > >installing the FreeBSD base system on a computer and checking > >whether the > >utility is present)? > > Run "pkg_which" on the name of the file, and it will tell you which > port that file comes from. Otherwise, the file is part of the base > system, or created by a user. Thanks. That's another good suggestion. > > >Second: > > > >Where can I get a list of all licenses on all software in the base > >system? I know there's at least the BSD License, the GPL, and the > >LGPL, > >but I'm a little hazy on what else is in there. > > There are dozens of variants of the BSD License, and the closely > related Zlib/PNG license; there are also MIT, GPL, LGPL, a bit of > Sun's SISSL or CDDL, and probably other licenses present. A decent > starting point is: > > % locate LICENSE > [ ... ] > /usr/src/contrib/bzip2/LICENSE > /usr/src/contrib/groff/LICENSE > /usr/src/contrib/ipfilter/perl/LICENSE > /usr/src/contrib/less/LICENSE > /usr/src/contrib/libpcap/LICENSE > /usr/src/contrib/nvi/LICENSE > /usr/src/contrib/openbsm/LICENSE > /usr/src/contrib/openpam/LICENSE > /usr/src/contrib/pam_modules/pam_passwdqc/LICENSE > /usr/src/contrib/sendmail/LICENSE > /usr/src/contrib/tcpdump/LICENSE > /usr/src/crypto/openssl/LICENSE > /usr/src/lib/libc/rpc/LICENSE > /usr/src/sys/contrib/dev/npe/LICENSE > /usr/src/sys/dev/em/LICENSE > /usr/src/sys/dev/ixgb/LICENSE > /usr/src/sys/dev/rr232x/LICENSE > /usr/src/usr.sbin/mrouted/LICENSE Duly noted. -- CCD CopyWrite Chad Perrin [ http://ccd.apotheon.org ] Marvin Minsky: "It's just incredible that a trillion-synapse computer could actually spend Saturday afternoon watching a football game." pgp2jE2ErUFWo.pgp Description: PGP signature
Re: determining what's in the base system
On Tue, Apr 15, 2008 at 4:59 PM, Chad Perrin <[EMAIL PROTECTED]> wrote: > > That's more the sort of answer I was expecting, but seems less easily > employed than just using `which` to determine whether something's located > under /usr/local. > Hi, It just occurs to me to mention that "which" searches the user's PATH and reports back the first instance of the executable it finds. So you'd potentially get different results for different users on the same system, and it doesn't tell you that something isn't installed or located in more than one place, it just tells you where the *first* instance of it was found. You might say "which bash" and get a result of '/usr/bin/bash' ...and meanwhile there might also be '/usr/local/bin/bash' but it won't tell you that. The 'locate' command could be useful too, but it depends on how complete the locate database is. Anyway... take care, dharma ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: determining what's in the base system
that time. Now imagine that you want to know whether a given utility was something that came with the base system or was installed by some port or package later on. What's the easiest way to do that (preferably without installing the FreeBSD base system on a computer and checking whether the utility is present)? ports go to /usr/local unlike base system's things. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: determining what's in the base system
On Apr 15, 2008, at 4:14 PM, Chad Perrin wrote: I have two questions. First: Assume you have a FreeBSD system installed that has been running for at least a year, with a bunch of graphical desktop and productivity software installed, and have both installed and uninstalled a lot of software over that time. Now imagine that you want to know whether a given utility was something that came with the base system or was installed by some port or package later on. What's the easiest way to do that (preferably without installing the FreeBSD base system on a computer and checking whether the utility is present)? Run "pkg_which" on the name of the file, and it will tell you which port that file comes from. Otherwise, the file is part of the base system, or created by a user. Second: Where can I get a list of all licenses on all software in the base system? I know there's at least the BSD License, the GPL, and the LGPL, but I'm a little hazy on what else is in there. There are dozens of variants of the BSD License, and the closely related Zlib/PNG license; there are also MIT, GPL, LGPL, a bit of Sun's SISSL or CDDL, and probably other licenses present. A decent starting point is: % locate LICENSE [ ... ] /usr/src/contrib/bzip2/LICENSE /usr/src/contrib/groff/LICENSE /usr/src/contrib/ipfilter/perl/LICENSE /usr/src/contrib/less/LICENSE /usr/src/contrib/libpcap/LICENSE /usr/src/contrib/nvi/LICENSE /usr/src/contrib/openbsm/LICENSE /usr/src/contrib/openpam/LICENSE /usr/src/contrib/pam_modules/pam_passwdqc/LICENSE /usr/src/contrib/sendmail/LICENSE /usr/src/contrib/tcpdump/LICENSE /usr/src/crypto/openssl/LICENSE /usr/src/lib/libc/rpc/LICENSE /usr/src/sys/contrib/dev/npe/LICENSE /usr/src/sys/dev/em/LICENSE /usr/src/sys/dev/ixgb/LICENSE /usr/src/sys/dev/rr232x/LICENSE /usr/src/usr.sbin/mrouted/LICENSE -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: determining what's in the base system
On Wed, Apr 16, 2008 at 01:31:23AM +0200, Mel wrote: > On Wednesday 16 April 2008 01:14:50 Chad Perrin wrote: > > > Assume you have a FreeBSD system installed that has been running for at > > least a year, with a bunch of graphical desktop and productivity software > > installed, and have both installed and uninstalled a lot of software over > > that time. Now imagine that you want to know whether a given utility was > > something that came with the base system or was installed by some port or > > package later on. What's the easiest way to do that (preferably without > > installing the FreeBSD base system on a computer and checking whether the > > utility is present)? > > > If you didn't change LOCALBASE/PREFIX during installation, anything > below /usr/local belongs to ports. Only exception would be kernel modules > that need to be loaded before /usr is mounted (like graphic card drivers). > > See hier(7). I definitely should have thought of that. Thanks for the wake-up call. > > Also, grep -v '^@' /var/db/pkg/*/+CONTENTS lists all files installed by ports. That's more the sort of answer I was expecting, but seems less easily employed than just using `which` to determine whether something's located under /usr/local. -- CCD CopyWrite Chad Perrin [ http://ccd.apotheon.org ] Baltasar Gracian: "A wise man gets more from his enemies than a fool from his friends." pgpTyfut7YIIq.pgp Description: PGP signature
Re: determining what's in the base system
On Tue, Apr 15, 2008 at 04:35:52PM -0700, Luke Dean wrote: > On Tue, 15 Apr 2008, Chad Perrin wrote: > > >I have two questions. First: > > > >Assume you have a FreeBSD system installed that has been running for at > >least a year, with a bunch of graphical desktop and productivity software > >installed, and have both installed and uninstalled a lot of software over > >that time. Now imagine that you want to know whether a given utility was > >something that came with the base system or was installed by some port or > >package later on. What's the easiest way to do that (preferably without > >installing the FreeBSD base system on a computer and checking whether the > >utility is present)? > > > >Second: > > > >Where can I get a list of all licenses on all software in the base > >system? I know there's at least the BSD License, the GPL, and the LGPL, > >but I'm a little hazy on what else is in there. I'm pretty sure there > >isn't any proprietary closed source software in there, but I wouldn't bet > >any substantial amount of money on it at this point, because I haven't > >really checked into it. > > For the first question, I'd first look at where the utility is. Base > system utilities won't be in /usr/local. Add-on packages and ports > "should" be. > The "pkg_info" utility and all of its switches and options could be useful > too, if your ports database is correct. Thanks. Using what's in /usr/local should have occurred to me. > > For the second question, I've always assumed that /COPYRIGHT applied to > everything in the base system. I'm pretty sure GCC is in the base system (for instance), and it's GPL software. There's no mention of it in /COPYRIGHT at all. Please correct me if I'm mistaken somehow. -- CCD CopyWrite Chad Perrin [ http://ccd.apotheon.org ] Patrick J. LoPresti: "Emacs has been replaced by a shell script which 1) Generates a syslog message at level LOG_EMERG; 2) reduces the user's disk quota by 100K; and 3) RUNS ED!!" pgpcS9KSuNqPy.pgp Description: PGP signature
Re: determining what's in the base system
On Tue, 15 Apr 2008, Chad Perrin wrote: I have two questions. First: Assume you have a FreeBSD system installed that has been running for at least a year, with a bunch of graphical desktop and productivity software installed, and have both installed and uninstalled a lot of software over that time. Now imagine that you want to know whether a given utility was something that came with the base system or was installed by some port or package later on. What's the easiest way to do that (preferably without installing the FreeBSD base system on a computer and checking whether the utility is present)? Second: Where can I get a list of all licenses on all software in the base system? I know there's at least the BSD License, the GPL, and the LGPL, but I'm a little hazy on what else is in there. I'm pretty sure there isn't any proprietary closed source software in there, but I wouldn't bet any substantial amount of money on it at this point, because I haven't really checked into it. For the first question, I'd first look at where the utility is. Base system utilities won't be in /usr/local. Add-on packages and ports "should" be. The "pkg_info" utility and all of its switches and options could be useful too, if your ports database is correct. For the second question, I've always assumed that /COPYRIGHT applied to everything in the base system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: determining what's in the base system
On Wednesday 16 April 2008 01:14:50 Chad Perrin wrote: > Assume you have a FreeBSD system installed that has been running for at > least a year, with a bunch of graphical desktop and productivity software > installed, and have both installed and uninstalled a lot of software over > that time. Now imagine that you want to know whether a given utility was > something that came with the base system or was installed by some port or > package later on. What's the easiest way to do that (preferably without > installing the FreeBSD base system on a computer and checking whether the > utility is present)? If you didn't change LOCALBASE/PREFIX during installation, anything below /usr/local belongs to ports. Only exception would be kernel modules that need to be loaded before /usr is mounted (like graphic card drivers). See hier(7). Also, grep -v '^@' /var/db/pkg/*/+CONTENTS lists all files installed by ports. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"