Josip Rodin wrote: > On Mon, Apr 10, 2000 at 08:42:23PM +0200, Eric Delaunay wrote: > > > > > There is a new memory-testing program, GPL, around, called MemMXtest, > > > > > and > > > > > it seems that it would make an useful addition to hwtools. It sure > > > > > behaved > > > > > much nicer than Memtest that's available in hwtools already, at least > > > > > on > > > > > my machine. > > > > > > > > > > The MemMXtest homepage is at > > > > > http://panic.et.tudelft.nl/~costar/memmxtest > > > > > > > > I hope it's only for woody ;-) > > > > I'm waiting for potato to be released before splitting out scsi progs > > > > from > > > > hwtools into my new scsitools package, so feel free to add it into > > > > current > > > > hwtools package if you want it rather soon. > > > > > > Yes, it's for woody, but I don't see why we shouldn't upload it now... > > > > For the split, I need to upgrade my PC box to potato at least to be able > > to do some testing (it's running slink atm). I also need to figure out > > how scsidev and devfs could work together, if it's ever possible. > > Anyway, I'm afraid I won't work very hard until I'll upgrade my PC box to > > something newer than my old P90 (I'm looking for an Athlon 700 or so)... > > maybe be next month :-)) > > I'm running mostly up-to-date potato. If you could send me your patches so > far, I could split it. If not that, then just tell me what needs to be done > (which utilities to move to another package) and I'll try to do it.
I've wrote preliminary support for scsidev at boot time but 1/ it needs more test and 2/ it requires freeramdisk to be available in /bin or /sbin (I filed a bug against util-linux to request for its inclusion). Therefore the scripts are not yet ready for distribution. I also built a 0.6-1 release of hwtools without scsi support but I can just upload full sources because it only builds on i386 and I cannot compile it atm because my PC is still running slink. Perhaps I can better send you the package and let you compile and upload it? Anyway I guess I can upload my first release of scsitools package without boot time support for scsidev. It works at least on my sparc. It will conflict with hwtools << 0.6 but I don't know whether it should also replaces hwtools? Another point is: what to do with closing bugs? I upgraded scsidev to 2.10 in scsitools so it should fix 4 bug reports (#46622, #47340, #48306, #30554). However is it right to include a Closes: line in the changelog of scsitools? They're closing bugs of another package! Or should I reassign the bugs to scsitools (hmm, not yet registered in Debian) or even close them by hand? Any advice? -- Eric Delaunay | S'il n'y a pas de solution, c'est qu'il n'y [EMAIL PROTECTED] | a pas de problème. Devise Shadok.
