Weblogs for GoodTimes
apt-cache search linux xen
I pick what looks like the latest one out of the list
apt-get source linux-image-2.6.18-5-xen-686
I get a line that looks like
Get:1 http://ftp.us.debian.org unstable/main linux-2.6 2.6.22-6 (dsc) [4825B]
Get:2 http://ftp.us.debian.org unstable/main linux-2.6 2.6.22-6 (tar) [57.4MB]
Interesting...it is bringing down 2.6.22, must be matching what I currently have installed...
Ok, that's done
dpkg-source -x linux-2.6_2.6.22-6.dsc
dpkg-source: extracting linux-2.6 in linux-2.6-2.6.22
dpkg-source: unpacking linux-2.6_2.6.22.orig.tar.gz
dpkg-source: applying ./linux-2.6_2.6.22-6.diff.gz
now...what i kind of think should happen next is
make menuconfig...will that take my current working configuration into account?
I was helping a friend with a debian install over the phone and after giving him my sources.list file he asked me where he'd find new ones. Well, apt-get.org was mentioned, but what he wanted to know was how to reconfigure his sources.list file with the standard debian listings since his cd install only left him with repositories on the cd (he didn't want to hit the network during his install so he didn't choose anything else)
Anyway, I remembered that you could type a command (which I believe was apt-setup) to get back to that screen during the installation where you chose from a list
anyway, apt-setup appears to be gone, and looking around online I found this discussion http://www.debianhelp.org/node/3756 but that didn't end conclusively.
I don't really need this, as I edit my sources.list by hand, it's just nagging at me
over and over and over again in my logs. But...why?
configured sendmail per instructions (and i really followed them this time)
i keep getting these in my logs
Milter (spfmilter): local socket name /var/run/spfmilter/spfmilter.sock unsafe
Milter (spfmilter): to error state
so, i checked the process table and sure enough, there was no spfmilter process running
if i restarted it using init.d/spfmilter
i'd have the process running and i'd see messages in the logs about spfmilter doing it's thing
but eventually, i'd get more messages in my logs and spfmilter would be dead
from a console, i ran it this way
/usr/sbin/spfmilter --debug --nodaemon --user spfmilter --pidfile /var/run/spfmilter/spfmilter.pid --markonly /var/run/spfmilter/spfmilter.sock 2>&1 | tee spfmilter.log
and eventually, got this to the console
*** glibc detected *** double free or corruption (fasttop): 0x08054530 ***
that's the story so far...
Now, that i've gone back to the standard package and still had the same problem (greylisting not working), I wondered about my earlier diagnosis. Unfortunately, I didn't keep very good notes then (something i'm hoping this blog helps with) so I can't re-diagnos without considerable effort, and i'm not willing to do it, so there. But without those notes, I just know that I got it all to work using a custom package and some config tweaking.
So, I figured, I'd start over. After a few hours of half-assed configuring and reading of man pages and googling I realized that no one had my particular issue as I was describing it. That usually means I didn't read the documentation right or I need to submit a bug.
I opted for the former
so anyway, it turns out that the GREY_CLIENT_ARGS= settings must be set GREY_CLIENT_ARGS=-Gon in order for greylisting to work with sendmail
i had read it as if I just set GREY_ENABLE=on it would be enough. That will turn it on, but sendmail won't know about it. Sendmail knows about it through the milter interface (dccm), THE CLIENT PROGRAM. And the only way to tell dccm about it during startup is by setting GREY_CLIENT_ARGS.
It is spelled out very clearly in the dcc-common file in /etc/default "to turn on greylisting in the dccm and dccifd DCC clients.". But it took me a while to put it all together that (it seems so simple and straightforward now that i wonder what my problem was. I can only imagine it was my mistaken belief that the DCC server got out in front of sendmail. While this flies in the face of everything I know about servers and such it's an example of how a bad beginning assumption can waste a while lot of time).
There are a couple of startup bugs in the DCC packages, but they've been reported and fixes will be coming out, so using this with sendmail is really easy if you are clear headed.
oh yeah, cuz it detects everything out of the box...
unfortunately, my standard deb machine doesn't have audio configured correctly...
...yet another project
which starts out with
" Why Marillat's repository doesn't work ? Because now the repository is here debian-multimedia.org"
ok, so after some cursory reading, i find i need sources.list to have
deb http://www.debian-multimedia.org stable main
deb-src http://www.debian-multimedia.org sid mai
and i see a avi tool that will fit the bill (wasn't i after centelerra when i started though?)
anyway, avidemux is now available to me, so i'll try it out
avidemux: Depends: libartsc0 (>= 1.5.0-1) but 1.4.3-0ubuntu1 is to be installed
Depends: libasound2 (> 1.0.10) but 1.0.9-2 is to be installed
Depends: libc6 (>= 2.3.6-6) but 2.3.5-1ubuntu220.127.116.11 is to be installed
Depends: libcairo2 (>= 1.0.2-2) but 1.0.2-0ubuntu1.1 is to be installed
Depends: libdirectfb-0.9-24 but it is not installable
Depends: libfaac0 (>= 1.24+cvs20060416) but it is not going to be installed
Depends: libfaad2-0 (>= 2.0.0+cvs20060416) but it is not going to be installed
Depends: libgcc1 (>= 1:4.1.0) but 1:4.0.1-4ubuntu9 is to be installed
Depends: libglib2.0-0 (>= 2.10.0) but 2.8.3-0ubuntu1 is to be installed
Depends: liblame0 (>= 3.96.1-1) but it is not going to be installed
Depends: libmozjs0d but it is not installable
Depends: libogg0 (>= 1.1.3) but 1.1.2-1 is to be installed
Depends: libpango1.0-0 (>= 1.12.1) but 1.10.1-0ubuntu1 is to be installed
Depends: libstdc++6 (>= 4.1.0) but 4.0.1-4ubuntu9 is to be installed
Depends: libvorbis0a (>= 1.1.2) but 1.1.0-1ubuntu1 is to be installed
Depends: libvorbisenc2 (>= 1.1.2) but 1.1.0-1ubuntu1 is to be installed
Depends: libxml2 (>= 2.6.23) but 2.6.21-0ubuntu1 is to be installed
Depends: libxvidcore4 (>= 1:1.0.0-0.0) but it is not going to be installed
why does it always have to be so hard?
so far, i've done the following
apt-cache search video edit
apt-cache search avi edit
and so far, no promising leads
kino crashes. not sure why
i found this page http://www.robfisher.net/video/ which now has me looking into centelerra...
which brought me to this page http://www.ftconsult.com/twiki/bin/view/Cinelerra/Debian
which brought me to this page http://www.kiberpipa.org/~minmax/cinelerra/builds/
i made the sources.list changes recommended on the site for my p4
deb ftp://ftp.nerim.net/debian-marillat/ unstable main
but the unstable wouldn't load. so i removed it and did an update
now i'm getting
W: GPG error: ftp://ftp.nerim.net sid Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 07DC563D1F41B907
dammit, i can never remember the key stuff
hmmm, nothing seemed to have happened...meaning, i can't just apt-get install centelerra (dammit, now i have to read)
Since i'm not willing to switch away from sendmail, I found that the dcc server package has greylisting capabilities
However, I wasn't able to get the default dcc install to do it
I had to download the source package and make a tweak, install that package and then put it on hold
the problem is...i don't remember the tweak!!!
i'll have to diff the source and figure out what the patch is...
...and then backtrack to figure out why I couldn't get it working the first time.
The problem is, since I have it working now, this project is very low priority...