Re: Re [iPAQ] Running initimate under familiar.

On Tue, Mar 12 '02 at 15:01, Matthew Horrobin wrote:
> Goetz, why do you hate Debian so much? I've got so used to using apt-get
> and the search options on http://packages.debian.org that I now find
> RedHat's upgrade options a pain. If you want some tips, tell us the
> things you hate the most on the intimate mailing list.
While I personaly love Trustix's swup, I'll tell you what remembered me
why I hate debian:

a) tried to install Intimate about a month ago and did an apt-get
   update, apt-get upgrade. The effect was that it tried to installe a
   new glibc but realised that some packages still need the old one. The
   result was i could not install the new glibc, but was unable to
   install the devel packages for the old one, too.
   This was before my holiday, and I was unable to compile any c code
   during my holday ...)
b) tried to install ssh yesterday. apt-get install openssh (not found),
   apt-get install ssh ... ssh-2.9.x (forgot it) not found. Did not find
   it on ftp.debian.org cause it's in non-us. found it in
   ftp.de.debian.org somewhere in /debian-non-us/packages/non-us/main/o/
   why isn't it in /debian/releases/unstable
   anyway downloaded it to my pc, in the mean time the ipaq had booted
   familiar, scped it to the ipaq, mounted intimate and chrooted to it,
   used dpkg to install it ... failed, missed openssl
   got libssl to my pc, scped it to the ipaq, insalled it, worked
   installed openssh, but got some other errors due to the fact that I
   only had chrooted intimate, not booted it
   checked sshd_conf, and copied authorised keys to root and the user I
   had created, booted into familiar ... and ssh worked.
c) today I wanted to install the tiny httpd (thttpd), and apt-get
   insisted to install exim, libsasl2, mimetools and some other stuff
   especially, what for heavens sake SHOULD I WANT TO NEED to install a
   mailer (and than WHY exim) if I just wanted a small/simple httpd.
   and why libsasl
d) Once apone a time I wanted to install some software from debian into
   my RPM based PC system, and realised that the one debian patch
   contained various sub patches, most of them I did not want/need. but no
   patch had
   - information where it came from
   - information what it was supposed to be intended to fix
   after spending sometime picking the debian patch appart, I found the
   patch I was interested in, had figuret out what the other patches did,
   that there were new upstream versiones of some of the patches, where
   of at last one fixed a security problem ... all in all I spend about
   half a day extracting one patch for a nifty feature.
   (BTW: I'm talking about the synamic maps features of postfix, added
   by the postfix debian maintainer)
e) deselect is just as broken as a user interface can get.
f) autostarting of services just sucks, but than only Trustix realised
   that less can be more (alias more=less ;-)) and tries to minimase
   inter package dependencies and does not start ANY servies, after you
   installed it.
g) My iPaq has: discard, daytime, time, ssh, http, X11 (+1 I can not
   remember, and for some reasons the route is down) as open ports,
   while I only asked for ssh and http.
       

While I know that there is no common interface for upgrading a RPM based
system, there are various working implementations. IMHO swup did a realy
great job.
And there are SRPMS, with seperated patches, sometimes even with
description where the patches are from and what they are supposed to do.

Maybe I'm just not made for debian, but I now have a working (native)
ARM compile station and will try to build rpm later this week. (iPaq
toying is not my day job, unfortunately)

Cu,
    Goetz.
Received on Wed Mar 13 2002 - 00:49:11 EST