Re: Bulding 3.0.1 Under Ubuntu 10.04 i386
Please keep me on the Cc: list, as I'm not subscribed. Sorry :( I have to pick this up again, as I screwed up last time and not much happened since I started this thread. Won't bother the subsurface mailing list with debian packaging details. On Fri, 1 Mar 2013, Christian PERRIER wrote: Old debian source packages (subsurface-1.2-1 and libdivecomputer-0.1.0), could also be of some value. I'm really looking forward to see latest subsurface/libdivecomputer in debian, as soon as it can be done. It'll most probably be unstable, but This thread is interesting. I faced about the same challenges when working on packaging pYtrainer for Debian (Pytrainer is a Python application for sports tracking, mostly used by runners and bikers). Thanks for the insight. Yeah, it seems to be very difficult to find someone interested of packaging this stuff and also _work_ it :( Last offer came from Dmitrijs. Are you still willing to do the packiging work Dmitrijs? That was the point : doing the work in Debian guaranteed that our quality criteria did benefit to the quality of the resulting packages and this, up to derived distro users. There are certainly probably 10, or 20, or 30 more users of Pytrainer packages on Ubuntu systems than Debian systems. But, indeed, all those can use this nice software because we did prepare the packages with our Debian culture in mind (the original culprit for these packages is Noèl Köthe, not me, by the way). Yes, those were my thoughts too when I brought subsurface up. So, yes, if people are interested in getting this diving software ported and well-supported in many deb-based distros as possible, I would highly recommend doing the work in Debian. Please folks, pick this up. Two easy packages to maintain, with active upstreams and very interested to make the packaging work easier. That would even be a good way to discover that those Debian weirdos are not all pizza eaters and beer drinkers and that some might even dive very well, just like some Debian weirdos happen to run or bike not so badly...:-) Yes, I'm still hoping to find an interested diver and debian developer/maintainer too, willing to pick this up. There's some interesting development here (thanks to Yannick): On Fri, 1 Mar 2013, Yannick Brosseau wrote: | | Hi, | | I'm not sure if anybody was actually working on it, but I've built | package for debian (sid) if it can be of any use for somebody. | | I only did a simple update of the packaging currently available in debian. | | The packaging git are here: | http://git.dorsal.polymtl.ca/~ybrosseau?p=pkg-libdivecomputer | http://git.dorsal.polymtl.ca/~ybrosseau?p=pkg-subsurface | | And the files: | http://www.dorsal.polymtl.ca/~ybrosseau/debian/libdivecomputer-dev_0.3.0-1_amd64.deb | http://www.dorsal.polymtl.ca/~ybrosseau/debian/libdivecomputer0_0.3.0-1_amd64.deb | http://www.dorsal.polymtl.ca/~ybrosseau/debian/subsurface_3.0.1-1_amd64.deb | The rest of the source are available: | http://www.dorsal.polymtl.ca/~ybrosseau/debian/ AFAICT, those packages need some small polishing work. How about joining the pkg-running umbrella? It's quite some time that stuff we maintain in this team is more sport stuff than running stuff anyway. Yes, I finally found that list (it's pkg-running-devel, isn't it?) and I had a look. Sadly, it looks more like a spam-box than a development mailinglist. Can anything be done about that? I'd gladly join that list if that would help to push the packaging work ahead. Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.deb.2.02.1303031027450.11...@znkvzvyvna.pvv.fr
Re: Subsurface maintaince in Debian [was Re: Bulding 3.0.1 Under Ubuntu 10.04 i386]
On Sun, 3 Mar 2013, Sylvestre Ledru wrote: As a Debian Developer and as a professional diver, I am interested to help on this. That sounds great. Thanks for volunteering. I have been in touch with Khalid to help him on this and he replied: No problem for to co-maintaince I'm sorry, but I've been very busy the last few months. As Christian proposed, I am sure we can be move this package in the sport team. By all means. Will join that list shortly. Would you, please, do the honors ;) Cristian, if you want, we can work together to improve the package and maintain new releases for Jessie. Of course. Which means new packages will go to unstable/experimental. Would it be possible to make back-porting to wheezy as painless as possible? But, bare in mind, although I can often find my way around debian packages, I'm neither a maintainer nor a developer. But I'll try to do whatever I can. I hope some other people on the subsurface list want to help too. FYI, I reported some bugs on these two packages: http://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=nosrc=libdivecomputer Adding a symbol list file may probably be a good idea, I guess, bu you know better. http://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=nosrc=subsurface Yes. I read the comments. The upstream maintainers expressed their wish to have subsurface statically built against libdivecomputer, as ABI changes occured frequently, but if you think package maintenance is easier with shared linking, I'm almost sure there'll not be too many protests :) Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.deb.2.02.1303031735530.11...@znkvzvyvna.pvv.fr
Re: Bug#701536: RM: subsurface -- RoQA; unmaintained package, maintainer MIA
On Sun, 3 Mar 2013, John Paul Adrian Glaubitz wrote: The maintainer seems MIA since June 2012, not responding to bug reports nor direct mails. The two most recent upstream releases not packaged. Why would this be a reason to *remove* a package? Especially after such a short time. The package hasn't even been orphaened. Well, short time is relative to how slow/fast things move. In this case, upstream is _not_ moving slow, I would say :) I have seen packages in Debian which haven't received updates from the maintainer after much longer periods. True, but let's not focus too much on that, please. This is a little bit different. Dirk, Linus and many more working with upstream are pushing things forward at higer pace than average. This doesn't necessarrialy mean the maintainer is MIA. True. But nothing happened for many moons :) Debian is run by volunteers and sometimes, people are busy with more important things in life. Aren't we all? Volunteers and trying to also cope with the important things in life? The good thing with such a large community is that there's a lot of backup. This doesn't mean that anyone has the right to immediately remove their packages from Debian. True. But that doesn't mean either everyone is happy seeing things stalling? I suppose Khalid will be happy to continue to work on the package again once he finds the time. I certainly hope so. But, unfortunatelly, there was no sign of life from Khalid for a, relatively, long time. No RFHs either, AFAICT. I don't see any need (and I think it's impolite) to pressure him in such a way. I appologise, in that case. But that was not my intent. My intent is to find a debian maintainer/developer that has the time to work on these 2 packages. Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.deb.2.02.1303031809350.11...@znkvzvyvna.pvv.fr
Re: Bug#701536: RM: subsurface -- RoQA; unmaintained package, maintainer MIA
On Sun, 3 Mar 2013, John Paul Adrian Glaubitz wrote: The license issue was just an example (hence the braces). The reasoning is that the Debian packaging is supposed to be independent of upstream, especially since we cannot always follow upstream, during a freeze, for example. Assume we have version 3.0 in Debian and upstream has 3.5 and we're frozen. During the freeze, someone discovers a nasty bug in subsurface which is considered RC (release critical) in Debian, but gets fixed in 3.5.1 upstream. What about upstream keeping stuff on release branches (3.0, 3.0.2, 3.5, and so on)? And doing that sort of backporting patches themselfs? How much would that help with packaging? I am aware that you could probably avoid this problem with branches, but I think it would just make things difficult. Debian cannot simply be up-to-date with upstream and thus upstream shouldn't maintain the Debian-specific part. Alright. Package maintenence stuff separated from upstream source stuff. Did I get that right? Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.deb.2.02.1303032210170.11...@znkvzvyvna.pvv.fr
Re: Bulding 3.0.1 Under Ubuntu 10.04 i386
Please Cc:, not subscribed to the debian-devel@lists.debian.org list. Hi there! Linus Torvalds is highly involved in this project :) On Thu, 28 Feb 2013, Dirk Hohndel wrote: The problem is that our target audience are divers, not hackers. Agreed. Someone who can build from those sources can just build from git Check. But many people (even people running Linux) aren't comfortable building their own binaries. I wouldn't be that sure, but ok, check. And for those I try to make their lives easier. Of course. Where do you get all that energy from? I'm impressed. Really. To me that means I need the Ubuntu packages - and those apparently can neatly be built with Launchpad (a couple of us are working on that right now). That's good. You say ubuntu, but how many ubuntu derivatives are there? And who's ubuntu getting maintained packages from? Don't get me wrong. It's better with one alternative than no alternative at all. Debian? No non-hacker is running Debian, I guess :-) Not so. Both my wife and one of my dauthers (non-hackers, as you might expect) are using debian ;) And they're happy with that too, AFAICT. They got a choice and an offer they couldn't refuse, I guess. No support at all, or all support they need. Hard to refuse ;) Real men don't click (tm), I know, but they're not men, and definitely not hackers. Managed to get one debian maintainer involved, at some point, Cc:ed, but I guess he can't live up to that honor we need so badly right now :( Yes, I'm trying to provoke him. So in reality it really is Ubuntu that I try to cover here. That's great. Sorry, I don't know if I can help much there but, by all means, try me. In the meantime, I'll try to figure out some other way to get a debian maintainer attracted. Attempting that right now. That'll make all debian derivatives happier too. And that's the beauty of that. Are there more debian users and divers watching this list? Could we join forces? Ideas? There might be things that could be adjusted in the upstream source that may make distributions binaries packiging more attractive and easier to maintain. I'm sure upstream will try to accomodate. I think it's a shame for such a great distribution (been using it for more than 15 years now) to miss such an opportunity. Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.deb.2.02.1302281956590.16...@znkvzvyvna.pvv.fr
Re: Bulding 3.0.1 Under Ubuntu 10.04 i386
On Thu, 28 Feb 2013, Robert Wolfe wrote: Um, forgot about me already, hmm? :) But, of course not. Do you want to be Cc:ed? And yes, libdivecomputer-3.0.1 in .DEB format That should probably be: subsurface-3.0.1 and libdivecomputer-0.3.0 I presume. Can you make the source packages available too to Dmitrijs? It's: subsurface_3.0.1-x.debian.tar.gz and libdivecomputer_0.3.0-x.debian.tar.gz or similar, I'm thinking about. Dmitrijs, Old debian source packages (subsurface-1.2-1 and libdivecomputer-0.1.0), could also be of some value. I'm really looking forward to see latest subsurface/libdivecomputer in debian, as soon as it can be done. It'll most probably be unstable, but Dmitrijs, could you please try to make them as painless as possible portable to wheezy? If you need info/insights, please don't hesitate to ask on subsurf...@hohndel.org. The recommended way (by upstream) is to build statically against libdivecomputer. And, AFAICT, that's what debian distributed subsurface 1.2-1 does. Another thing worth mentioning is that I asked for subsurface/libdivecomputer to be orphaned/removed because they're unmaintained. You may want to have a look at bug: http://bugs.debian.org/701536 Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.deb.2.02.1302282337560.16...@znkvzvyvna.pvv.fr
Re: Kernel weirdness
On Sun, 5 Oct 2003, Rob wrote: I've installed the kernel-image-2.4.22-1-686 package. Until now, I've been running the 2.4.18-bf2.4 kernel. Though I didn't change what modules I load, with this new kernel package have come a whole bunch of new modules that are being loaded. I've run modconfig and removed them, but they continue to to load at boot. This insane behaviour is caused by initrd: , | # cat /initrd/loadmodules | modprobe -k vesafb /dev/null 21 | modprobe -k unix 2 /dev/null | modprobe -k ide-mod | modprobe -k pdc202xx_new /dev/null 21 | modprobe -k adma100 /dev/null 21 | modprobe -k aec62xx /dev/null 21 | modprobe -k alim15x3 /dev/null 21 | modprobe -k amd74xx /dev/null 21 | modprobe -k cmd640 /dev/null 21 | modprobe -k cmd64x /dev/null 21 | modprobe -k cs5530 /dev/null 21 | modprobe -k cy82c693 /dev/null 21 | modprobe -k generic /dev/null 21 | modprobe -k hpt34x /dev/null 21 | modprobe -k hpt366 /dev/null 21 | modprobe -k ns87415 /dev/null 21 | modprobe -k opti621 /dev/null 21 | modprobe -k pdc202xx_old /dev/null 21 | modprobe -k piix /dev/null 21 | modprobe -k rz1000 /dev/null 21 | modprobe -k sc1200 /dev/null 21 | modprobe -k serverworks /dev/null 21 | modprobe -k siimage /dev/null 21 | modprobe -k sis5513 /dev/null 21 | modprobe -k slc90e66 /dev/null 21 | modprobe -k triflex /dev/null 21 | modprobe -k trm290 /dev/null 21 | modprobe -k via82cxxx /dev/null 21 | modprobe -k ide-probe-mod | modprobe -k ide-disk ` Up to kernel-image-2.4.20 a more moderate approach was chosen: , | # cat /initrd/loadmodules | modprobe -k vesafb /dev/null 21 | modprobe -k unix 2 /dev/null | modprobe -k ide-mod | modprobe -k ide-probe-mod | modprobe -k ide-disk ` I was going to put the whole blame on hotplug, but I would have been wrong. I still think it's weird it starts from /etc/rcS.d _and_ all run levels (except 0 and 6). Cheers, Cristian
Re: Kernel weirdness
On Fri, 10 Oct 2003, Mark Ferlatte wrote:
Cristian Ionescu-Idbohrn said on Fri, Oct 10, 2003 at 06:42:53PM +0200:
On Sun, 5 Oct 2003, Rob wrote:
I've installed the kernel-image-2.4.22-1-686 package. Until now, I've
been running the 2.4.18-bf2.4 kernel. Though I didn't change what
modules I load, with this new kernel package have come a whole bunch of
new modules that are being loaded. I've run modconfig and removed them,
but they continue to to load at boot.
This insane behaviour is caused by initrd:
The behavior is not insane. Prior to 2.4.20, the IDE driver was
monolithic. As of 2.4.21, it got split into a bunch of chipset specific
drivers. The kernel maintainer wisely decided to not change the
existing functional behavior of the kernel, and so loads all of those
drivers anyway since he doesn't know which of them you are using.
With all due respect for the our kernel maintainer, Herbert Xu, throwing
up all those ide-driver modules (on a scsi only box, or anywhere else) is
IMHO insane :(
If it really bothers you, make a new initrd.img with only the IDE driver
that you need.
At least provide some sort of hook one could use to cleanup that module
jungle. Ideally, automatic detection of what is usable ('cat /proc/pci |
grep -i ide' or lspci?) and removal of the useless junk, would be an
elegant solution to this problem.
Cheers,
Cristian
Re: Kernel weirdness
On Fri, 10 Oct 2003, Derek Broughton wrote: From: Cristian Ionescu-Idbohrn [EMAIL PROTECTED] On Sun, 5 Oct 2003, Rob wrote: I've installed the kernel-image-2.4.22-1-686 package. Until now, I've been running the 2.4.18-bf2.4 kernel. Though I didn't change what modules I load, with this new kernel package have come a whole bunch of new modules that are being loaded. I've run modconfig and removed them, but they continue to to load at boot. This insane behaviour is caused by initrd: mkinitrd it's not that hard to change Shouldn't need to change anything, if it can be done right from the start. Cheers, Cristian
having troubles adding info to 1 and/or 2 an existing bug(s)
Please CC, as I don't subscribe to this list. Tried to get this info through a couple of times now, but no joy :( Posted to [EMAIL PROTECTED], but no answer :( Chopped some parts. Left the essencial, I hope. And yes, I know the latest apt-listbugs version provides an alternative way (a server in Japan) to get the buglist info. On Thu, 28 Aug 2003, Cristian Ionescu-Idbohrn wrote: Date: Thu, 28 Aug 2003 08:28:32 +0200 (CEST) From: Cristian Ionescu-Idbohrn [EMAIL PROTECTED] Reply-To: Cristian Ionescu-Idbohrn [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: apt-listbugs: 302 Found [snip] All right, Some more info. This is what apt-listbugs requires from bugs.debian.org: , | Hypertext Transfer Protocol | GET /~taru/apt-listbugs/index.db-critical.gz HTTP/1.1\r\n | Request Method: GET ` And this is what it gets back from bugs.debian.org: , | Hypertext Transfer Protocol | HTTP/1.1 302 Found\r\n | Date: Thu, 28 Aug 2003 05:19:26 GMT\r\n | Server: Apache/1.3.26 (Unix) Debian GNU/Linux PHP/4.1.2\r\n | Location: http://bugs.debian.org/apt-listbugs.html\r\n | Connection: close\r\n | Transfer-Encoding: chunked\r\n | Content-Type: text/html; charset=iso-8859-1\r\n | \r\n | Data (232 bytes) | | 64 63 20 0d 0a 3c 21 44 4f 43 54 59 50 45 20 48 dc ..!DOCTYPE H | 0010 54 4d 4c 20 50 55 42 4c 49 43 20 22 2d 2f 2f 49 TML PUBLIC -//I | 0020 45 54 46 2f 2f 44 54 44 20 48 54 4d 4c 20 32 2e ETF//DTD HTML 2. | 0030 30 2f 2f 45 4e 22 3e 0a 3c 48 54 4d 4c 3e 3c 48 0//EN.HTMLH | 0040 45 41 44 3e 0a 3c 54 49 54 4c 45 3e 33 30 32 20 EAD.TITLE302 | 0050 46 6f 75 6e 64 3c 2f 54 49 54 4c 45 3e 0a 3c 2f Found/TITLE./ | 0060 48 45 41 44 3e 3c 42 4f 44 59 3e 0a 3c 48 31 3e HEADBODY.H1 | 0070 46 6f 75 6e 64 3c 2f 48 31 3e 0a 54 68 65 20 64 Found/H1.The d | 0080 6f 63 75 6d 65 6e 74 20 68 61 73 20 6d 6f 76 65 ocument has move | 0090 64 20 3c 41 20 48 52 45 46 3d 22 68 74 74 70 3a d A HREF=http: | 00a0 2f 2f 62 75 67 73 2e 64 65 62 69 61 6e 2e 6f 72 //bugs.debian.or | 00b0 67 2f 61 70 74 2d 6c 69 73 74 62 75 67 73 2e 68 g/apt-listbugs.h | 00c0 74 6d 6c 22 3e 68 65 72 65 3c 2f 41 3e 2e 3c 50 tmlhere/A.P | 00d0 3e 0a 3c 2f 42 4f 44 59 3e 3c 2f 48 54 4d 4c 3e ./BODY/HTML | 00e0 0a 0d 0a 30 0d 0a 0d 0a ...0 ` which it seems is unable to handle :( The text on that page: http://bugs.debian.org/apt-listbugs.html says: You are using a program called apt-listbugs. This program is called automatically, by apt, when packages get upgraded. However, this program was written, without consulting the BTS maintainers, nor consideration of the increased load(both bandwidth and cpu) on the BTS machine. Because of this, all cgi requests by apt-listbugs are being redirected to this page. We are sorry for this inconvience. Is there any alternative server which can deliver the data? Although I understand the reasons (I read #207415), IMHO this was a poor decision, as it does not provide an alternative. IMO, apt-listbugs increased popularity shows it is an great tool which enables people to use Debian unstable, with lesser risk for rendering their boxes useless because of occasional fatal bugs in new/upgraded packages. Cheers, Cristian
Re: Where to find cdda_inteface.h and cdda_paranoia.h in ?
Retrieve the relevant Contents-${ARCH}.gz file and search:
# wget ftp://ftp.se.debian.org/debian/dists/unstable/Contents-i386.gz
# zgrep cdda_interface.h Contents-i386.gz
Cheers,
Cristian
On 1 Jan 2001, Christian Marillat wrote:
MM == Michael Meding [EMAIL PROTECTED] writes:
[...]
http://www.debian.org/distrib/packages
[...]
MM that was really funny. I am still laughing. Of course a quick search in
there
MM revealed nothing poping up for cdda. But I did the search before I posted
to
MM the list.
MM Anyway,
MM I still haven't been able to locate the desired files. Anybody would be so
MM kind as to point me to the corresponding package ?
Very strange. I've find that in unstable :
usr/include/cdda_interface.hsound/libcdparanoia0-dev
usr/include/cdda_paranoia.h sound/libcdparanoia0-dev
would anyone like to package Secret Agent
http://www.vibe.at/tools/secret-agent/ GPL Secret Agent stores your secrets in a secure manner. Its main use at the moment is with GnuPG (an e-mail encryption/signation solution compatible to OpenPGP), or PGP 2.6. You can store your passphrase with Secret Agent, and have it provide that passphrase to GnuPG or PGP everytime it is needed. Happy New Year, Cristian
Re: Another Grub question/problem
On 28 Dec 2000, Brian May wrote: Hamish == Hamish Moffatt [EMAIL PROTECTED] writes: Hamish On Wed, Dec 27, 2000 at 03:23:52PM +1100, Brian May wrote: still haven't tried 2.2.18. The video= options seems to be completely ignored, and Linux boots up as if it wasn't there. Hamish Did you check /proc/cmdline to see if grub actually passed Hamish it to the kernel? cat /proc/cmdline mem=131008K root=/dev/hda1 video=0x319 I am having similar problems on this diskless NFS-Root system, too,\ where I have tried all the suggested combinations. Right now: cat /proc/cmdline auto rw root=/dev/nfs video=788 nfsaddrs=192.168.87.130:192.168.87.129:192.168.87.129:255.255.255.0: ^ Am I seeing double or there's something wrong here?
wmaker build and AM_PROG_LIBTOOL
I'm now getting regular X freezes. Only thing I can pick up is: /usr/bin/X11/WindowMaker fatal error: got signal 11 (Segmentation fault) from ~/.xsession-errors. Trying to rebuild an unstripped wmaker from source, but automake makes my life miserable: aclocal aclocal: configure.in: 15: macro `AM_PROG_LIBTOOL' not found in library make: *** [aclocal.m4] Error 1 Can anybody point me in the right direction? It says: not found in library. What library is the right library? Cheers, Cristian
Re: wmaker build and AM_PROG_LIBTOOL
Answering my own question. Needed to install: libtool, libltdl0, libltdl0-dev, libproplist0-dev (maybe a little overdone). Cheers, Cristian On Mon, 25 Dec 2000, Cristian Ionescu-Idbohrn wrote: I'm now getting regular X freezes. Only thing I can pick up is: /usr/bin/X11/WindowMaker fatal error: got signal 11 (Segmentation fault) from ~/.xsession-errors. Trying to rebuild an unstripped wmaker from source, but automake makes my life miserable: aclocal aclocal: configure.in: 15: macro `AM_PROG_LIBTOOL' not found in library make: *** [aclocal.m4] Error 1 Can anybody point me in the right direction? It says: not found in library. What library is the right library?
Re: System sees only 65M of memory
Art, On Wed, 30 Aug 2000, Art Edwards wrote: I just purchased two Athalon-based systems, each with 768M of ram. However, under debian (potato runnin kernel 2.2.17) the OS sees only 65 M of memory. I have tried to use the append command mem=768M but it still sees only 65 M? Does anyone have any ideas? You don't mention the MB your Athlons sit on. Anyhow, I did not yet find one Athlon MB that a kernel finds how much memory is really plugged on. I had/have that trouble with all Athlon MB I touch (gigabyte, abit, aopen). Always have to add the append=mem=...m line to lilo.conf. You mention you use 768 Mb. I guess that is 3x256 or 1x512 + 1x256. Is there an empty first/last memory slot there? In that case you could try to move the memory sitting in the current last/first to the empty slot, start, enter the bios setup, save and check again. ALWAYS enter the bios setup and save, if you change anything in the HW. You'll most surely have to have the append=mem=... line in lilo.conf anyway. You might also want to check the memory with the excellent memtest86 tool http://reality.sgi.com/cbrady_denver/memtest86/ Another thing to try might be to put one memory card at a time. Bad memory in not unusual. Good luck, and please let me know if you make any progress. Cheers, Cristian -- I respect faith, but doubt is what gets you an education. -- Wilson Mizner -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: imap mailbox killer
Sorry I couldn't answer yout letters earlier. I had to repair my mailbox. I also had to involve and help the system administrators to go through all the IMAP mailboxes and filter out all the messages with suspect headers. Looks better now, thanks. I don't know much about the IMAP intrinsics, but here is the story of what happend (comming from an uninitiated user ;-). Looks like all boxes get an extra message inserted. It looks something like this: ,- | From MAILER-DAEMON Wed Aug 30 09:54:25 2000 | Delivery-Date: Thu May 11 21:51:47 2000 | Date: Thu, 11 May 2000 21:51:47 +0200 (MET DST) | From: Mail System Internal Data [EMAIL PROTECTED] | Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA | X-IMAP: 0928135936 033614 | Status: RO | X-Status: | X-Keywords: | X-UID: 2 | | This text is part of the internal format of your mail folder, and is not | a real message. It is created automatically by the mail system software. | If deleted, important folder data will be lost, and it will be re-created | with the data reset to initial values. `- I don't know if it's the IMAP daemon or the pine client who is responsible for this. One (or several) of Juhapekka message header entries, probably this: ,- | X-Keywords: =?iso-8859-1?Q?kettutyt=F6t=2C_Sanna_Sillanp=E4=E4=2C_IKL=2C_Jammu_Silta?= | =?iso-8859-1?Q?vuori=2C_ryss=E4=2C_somali=2C_lesbo=2C_homo=2C_lesbian=2C?= | =?iso-8859-1?Q?_anarchism=2C_nazi=2C_communism=2C_CIA=2C_bomb=2C_nuclear?= | =?iso-8859-1?Q?=2C_Semtex=2C_satan=2C_traitor=2C_pedophile?= `- caused the daemon (or the client) screw up the magic. I ended up with a magic message looking like this: ,- | From MAILER-DAEMON Wed Aug 30 16:36:48 2000 | Date: 30 Aug 2000 16:36:48 +0200 | From: Mail System Internal Data [EMAIL PROTECTED] | Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA | Message-ID: [EMAIL PROTECTED] | X-IMAP: 0967646162 000339 =?iso-8859-1?Q?kettutyt=F6t=2C_Sanna_Sillanp=E4=E4=2C_IKL=2C_Jammu_Silta?= | Status: RO | | This text is part of the internal format of your mail folder, and is not | a real message. It is created automatically by the mail system software. | If deleted, important folder data will be lost, and it will be re-created | with the data reset to initial values. `- and a lot of NULL characters preceeding a few (5-6) of the messages in some boxes. Hope this helps to find the problem. There's definitely a BUG lurking somewhere. Cheers, Cristian On Thu, 31 Aug 2000, Juhapekka Tolvanen wrote: On Thu, 31 Aug 2000, +00:52:25 EEST (UTC +0300), Cristian Ionescu-Idbohrn [EMAIL PROTECTED] pressed these keys: Package: imap Version: 4.7c-1 (Juhapekka Tolvanen's messages may be found on these mailing lists: debian-devel@lists.debian.org,debian-legal@lists.debian.org) Man, you got great headers on your messages! Maybe the problem is caused by my X-Keywords-header, that serves as spook line (Hello, NSA! :-) ). I shortened it. Do you still have that problem? There might be bug in either Pine or IMAP(D) or both. -- I respect faith, but doubt is what gets you an education. -- Wilson Mizner
Re: imap mailbox killer
Funny side effect of the bug, here is the new magic message in my mailbox :-) Check out the X-IMAP: entry: ,- | From MAILER-DAEMON Thu Aug 31 17:15:15 2000 | Date: 31 Aug 2000 17:15:15 +0200 | From: Mail System Internal Data [EMAIL PROTECTED] | Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA | Message-ID: [EMAIL PROTECTED] | X-IMAP: 0967708347 84 lesbo, homo, lesbian, anarchism, nazi, communism, CIA, bomb, nuclear, Semtex, satan, traitor, pedophile | Status: RO | | This text is part of the internal format of your mail folder, and is not | a real message. It is created automatically by the mail system software. | If deleted, important folder data will be lost, and it will be re-created | with the data reset to initial values. `- Cheers, Cristian -- I respect faith, but doubt is what gets you an education. -- Wilson Mizner
imap mailbox killer
Package: imap Version: 4.7c-1 (Juhapekka Tolvanen's messages may be found on these mailing lists: debian-devel@lists.debian.org,debian-legal@lists.debian.org) Man, you got great headers on your messages! I don't know if it was your intension, but you managed to totally screw up my inbox (no hard feelings)! The IMAP daemon went crazy trying to make sense of that box and put it's holy counts on the Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA. Is this a security hole? Anybody else suffering from it? Cristian -- I respect faith, but doubt is what gets you an education. -- Wilson Mizner
