[KLUG Members] Package Manager Problems

Peter Buxton members@kalamazoolinux.org
Mon, 2 Dec 2002 17:01:15 -0500
Previous message: [KLUG Members] Question on VA linux boxes.
Next message: [KLUG Members] Package Manager Problems
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Nov 29, 2002 at 09:42:12AM -0500, Adam Tauno Williams wrote:


Found in /usr/share/doc/samba/README:

> Samba 2.2 has experimental LDAP code. However, the official Debian
> packages have not been compiled with LDAP support for a good reason:
> if LDAP support is compiled in then the other authentication methods
> (PAM, smbpasswd, etc.) cannot be used, only LDAP will work.

Now, that is Samba 2.2.3a-6 in Debian testing. On Debian unstable we have:

Version: 2.999+3.0.alpha20-4
Depends: debconf, samba-common (= 2.999+3.0.alpha20-4), netbase, logrotate, 
	libacl1 (>= 2.0.10), libc6 (>= 2.3.1-1), libcomerr2, libcupsys2 
	(>= 1.1.15-1), libkrb53, libldap2 (>= 2.0.23-1), libpam0g (>=
	0.76), libpopt0 (>= 1.6.4)

Note the Depends: line. Samba on Debian now requires Kerberos, LDAP 2,
ACL and PAM libs, among others. They have apparently solved the problem.

> 1. I come from a "real" UNIX heritage.  Debians filesystem seemed
> bizarre.  This was before the FSSTD.  Are they tracking that?  I kept
> looking for files and exclaiming "Bloody Hell!!", and all the cubicles
> surrounding mine emptied out.

Debian has a policy to follow the FSSTND. Those files are slowly being
moved to their proper places.

> 2. Feature-per-Feature Debian was a dead looser.  LVM?  Forget it.
> MD? Not in the installer, which makes it pretty worthless.  ACL
> Support?  Nope.  No filesystems beyond what is in the stock kernel,
> but RH doesn't provide any either, but that does eliminate a
> motivation to change.  Integration with LDAP or Kerberos would have
> meant a recompile of most service packages, yeech!  To build anything
> I'd call a server would have involved distro brain surgery.

This is from the boot floppy kernel config about three weeks ago:

CONFIG_BLK_DEV_DAC960=y
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_NBD=m
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y
| CONFIG_MD=y
CONFIG_BLK_DEV_MD=m
CONFIG_MD_LINEAR=m
CONFIG_MD_RAID0=m
CONFIG_MD_RAID1=m
CONFIG_MD_RAID5=m
CONFIG_MD_MULTIPATH=m
| CONFIG_BLK_DEV_LVM=m

[Quote emphasis added.]

http://people.debian.org/~blade/install/

http://www.debian.org/releases/stable/i386/ch-preparing.en.html#s-linux-upgrade


> 3. The whole stable/unstable/testing trees are just confusing.

I agree it is odd.... but, really:

Unstable tracks new versions of stable software; unstable does 
not mean alpha software -- necessarily. If the maintainer thinks a
pre-release will work, as with Samba above, it will make it in.

> Debian didn't seem to provide any nearly as succinct markers-in-time.
> It seems that one could say one was running unstable, but that didn't
> mean anything,  one had to say "unstable as of Aug 12, 2001"

> 4. Do these people live in a world with management?

Why, no, now that you mention it... ;-)

> I'm supposed to list on an audit sheet that I'm running the "unstable"
> version?

So call it 'sid.' That's the other name.

We also have names and version numbers.

"The next release of Debian is codenamed `sarge'  -- no release date has
been set." But that would be 3.1:

| Debian GNU/Linux 3.0 (`woody') -- current stable release 
| Debian GNU/Linux 2.2 (`potato') -- obsolete stable release
| Debian GNU/Linux 2.1 (`slink') -- obsolete stable release
| Debian GNU/Linux 2.0 (`hamm') -- obsolete stable release


And because I KNOW Adam will ask about this:


Package: sendmail
Priority: extra
Section: mail
Installed-Size: 3348
Maintainer: Richard A Nelson (Rick) <cowboy@debian.org>
Architecture: i386
Version: 8.12.6-8
Replaces: mail-transport-agent, sendmail-tls
Provides: mail-transport-agent
Depends: adduser, m4, libc6 (>= 2.2.5-13), libdb3 (>= 3.2.9-17),
 libldap2 (>= 2.0.23-1), liblockfile1 (>= 1.0), libsasl7, libssl0.9.6,
 libwrap0, sysvinit (>= 2.80-1), perl
Suggests: sendmail-doc (>= 8.12.6-8), mail-reader, procmail | mailagent
 | maildrop | deliver, make, logcheck, logrotate, libsasl-modules-plain,
libsasl-digestmd5-plain | libsasl-digestmd5-des, openssl
Conflicts: mail-transport-agent
Filename: pool/main/s/sendmail/sendmail_8.12.6-8_i386.deb
Size: 1045112
MD5sum: 4c6247a1738298314cd9dbb54090edba
Description: A powerful, efficient, and scalable Mail Transport Agent.
 Sendmail is an alternative Mail Transport Agent (MTA) for Debian.
 It is suitable for handling sophisticated mail configurations,
 although this means that its configuration can also be complex.
 Fortunately, easy thing can be done easily, and complex things
 are possible, even if not easily understood ;)  Sendmail is the *ONLY*
 MTA with a Turing complete language under the covers !

 Sendmail provides Security and SPAM/UCE/UBE protection via several means:
  - STARTTLS(SSL) RFC2487 encryption for mail reception/delivery.
  - STARTTLS(SSL) authentication (certificate based) for access/relay
    control.
  - SMTP AUTH (SASL/PAM) authentication for access/relay control.
  - ACCESS database (by IP/host) for access/relay control.
  - Use of varied Realtime Blackhole Lists (RBL) to prevent access.
  - Integration of LOGCHECK rules to fine-tune logging.
  - Inboard POSIX Regular Expression processing of *all* headers.
  - Ability (via MILTER) to scan/change headers *and* body of *ALL* mail
    A site may utilize zero, one, or more MILTERs.
  - Reduced SUID exposures by running SGID smmsp/mail where possible.

 Sendmail provides Performance and Scalability by:
  - Allowing multiple queues, with the ability to tune both interval and
    queue runners on a queue by queue basis.
  - Providing (a Debian exclusive) an easy to configure means of queue-aging
    to improve throughput by not continually retrying failed deliveries.
  - Allowing most all maps/databases to be obtained via LDAP; reducing the
    number of used databases and simplifying the maintenance of Sendmail.
  - Reducing the file I/O where possible by buffering files in memory.

 Sendmail provides site enhanced site configuration/customization by:
  - Allowing the listener (usually port 25) to run as a daemon or via
    INETD.
  - Allowing the queue runner (mail delivery) to run as a daemon or via
    CRON.
  - Automagically updating configuration and databases on upgrades.
  - Providing a Turing complete language for site customization of mail
    handling.
  - Providing a means (MILTER) for a site to scan/change all email - both
    incoming and outgoing.  A site can write their own MILTER, or may use
    any of those found on internet.  To write your own MILTER, you'll need
    to install the optional milter-dev package.
  - Providing extensive documentation via the sendmail-doc (optional)
    package.
  - Providing an inboard Mail Delivery Agent (MDA) (mail.local), but supporting
    procmail, mailagent, maildrop, or deliver automatically if installed.
    Sendmail will also deliver to anythings else (cyrus, etc) if asked to.

 Sendmail includes *no* Mail User Agents (MUA), you'll have to
 pick from the plethora of available MUAs (pine, mutt, vm, etc.)

 This package supports REGEX, DB, NIS, NIS+, LDAP, DNS maps,
 and has enabled TCPWrappers, IPv6, LockFile, SMTP AUTH(SASL),
 STARTTLS(SSL).




-- 
for gpg key: http://killdevil.org/~peter
AIX is Unix from the universe where Spock has a beard.
Previous message: [KLUG Members] Question on VA linux boxes.
Next message: [KLUG Members] Package Manager Problems
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]