> This turned out to be almost trivial...simply a few mods, instead of servicing
> requests after connect, it fork()s and lets the child service that connection
> while the parent loops and waits fo rthe next connect. [I think I changed
> 10 lines of code total]
Yeah, but this means each seperat
Greetings! I've built a private lprng-3.4.2 package for bo here at
our company, as the stock version in the kernel has a terible memory
problem. This may be useful for others, so perhaps it would be a good
idea to do a non-maintainer release to bo-unstable? I've writen the
maintainer, but haven'
I sent a message to the maintainer , but haven't heard back.
Is this something broken on my system ? I tried forcing removal
of all my tetex packages and reinstalling.
I get this when trying to install tetex-bin .
Setting up tetex-bin (0.9-5) ...
/usr/bin/texconfig: No
Hi,
I have finally managed to compile this so I am going to package it for debian
unless someone speaks up.
Thanks,
Luis.
--
Luis Francisco Gonzalez <[EMAIL PROTECTED]>
PGP Fingerprint = F8 B1 13 DE 22 22 94 A1 14 BE 95 8E 49 39 78 76
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subjec
Hi,
I am trying to compile one file called xpriv.c which belongs to the
Radio Track install ! Unfortunally i get that:
xpriv.c: In function `give_up_root`:
xpriv.c:30: `uid_t` undeclared (first use this function)
xpriv.c:30: (Each undeclared iden
On 5 Jun, Brandon Mitchell wrote:
> On Fri, 5 Jun 1998, Steve Tonnesen wrote:
>
>> I'm getting unresolved symbol errors when cardmgr tries to insmod the
>> 3c589_cs module for my 3Com PCMCIA ethernet card. Is this a problem with
>> the boot disks, and/or is there a solution for this? The laptop
It appears that an old /etc/texmf/texmf.cnf was not being removed
and the installation of tetex-bin would not overwrite it.
I'm not sure if this was my fault or if I tried to do a normal
upgrade and it went wrong. ( i did use apt once without sufficient disk
space, and this broke a
I ran through my first x86 install today, and had a wierd problem.
After pounding my bios into properly detect both c and d drives, I
started the install using loadlin planning to avoid floppies
altogether. However, when the time came to select a partition to find
the resc1440.bin for drivers, it
"Luis" == Luis Francisco Gonzalez <[EMAIL PROTECTED]> writes:
Luis> Hi, I have finally managed to compile this so I am going to
Luis> package it for debian unless someone speaks up.
Brian Basset said he was working on this, back on Feburary 23, but I
have not been able to reach him to confirm th
Does anyone have any definite information on the Corel Network
computers? Is anyone else interested in doing a Debian port?
The pictures of these machines look really sexy, and I've heard that
rumors that they have decent performance and near $1k prices (with
video input and two ethernet ports).
Nuno Carvalho wrote:
> I am trying to compile one file called xpriv.c which belongs to the
>Radio Track install ! Unfortunally i get that:
>
>
>xpriv.c: In function `give_up_root`:
>xpriv.c:30: `uid_t` undeclared (first use this function)
On Fri, Jun 05, 1998 at 10:53:43PM -0400, Dan Jacobowitz wrote:
> I ran through my first x86 install today, and had a wierd problem.
> After pounding my bios into properly detect both c and d drives, I
> started the install using loadlin planning to avoid floppies
> altogether. However, when the
I did not announce this in public but I have an almost working twin
package which I built for my own use. I just need to get a few details
about shared libraries straight. I'm going to Washington this weekend so
I won't be able to finish it till sometime next week.
If someone else wants to be
--On Sat, Jun 6, 1998 12:17 am +0100 "Edward Betts"
<[EMAIL PROTECTED]> wrote:
>
> Debian 2 ships with Gimp 1 take that redhat :-)
>
Huh?
Who managed a new major version during a depp freeze?
/+---+-\
| Jelibean aka | [EMAI
--On Fri, Jun 5, 1998 3:26 pm +0200 "Marcus Brinkmann"
<[EMAIL PROTECTED]> wrote:
>
> Hello!
>
> This is thereply I got from RMS about the copyright freeness issue.
>
> I think it is clear that we should lay the license freeness issue ad acta.
> Debian should include all licenses in whole, and
On Sat, Jun 06, 1998 at 02:50:56AM +0100, Luis Francisco Gonzalez wrote:
> Hi,
> I have finally managed to compile this so I am going to package it for debian
> unless someone speaks up.
Thank you for doing this, Luis!
Marcus
--
"Rhubarb is no Egyptian god."Debian GNU/Linuxfinge
On Sat, Jun 06, 1998 at 11:54:26AM +0100, Jules Bean wrote:
> --On Fri, Jun 5, 1998 3:26 pm +0200 "Marcus Brinkmann"
>
> > [Marcus asked:]
> > It seems to imply, that I'm not allowed to derive a new license, using
> > portions of the GPL (even when changing the name). Is that correct?
>
-BEGIN PGP SIGNED MESSAGE-
On Sat, 6 Jun 1998, Marcus Brinkmann wrote:
> I think:
>
> * We should treat documentation under the same terms as software, as we need
> it to use the software successfully and we'll have the same benefits of free
> documentation as we have of free software.
"Jules Bean" <[EMAIL PROTECTED]> writes:
> > Debian 2 ships with Gimp 1 take that redhat :-)
>
> Huh?
>
> Who managed a new major version during a depp freeze?
It's not a major new version, it's the final release of the 0.99.xx
series; it would be very silly to release hamm with 0.99.xx and not
On Sat, Jun 06, 1998 at 09:55:57AM +0100, Enrique Zanardi wrote:
>
> Not yet. A few questions: Which filesystem type has hdc1? Which version of the
> boot-floppies were you using? I assume hdc2 and hdc3 were properly detected
> in previous steps (initialize swap & initialize linux partition), righ
I would like to recommend that linux 2.0.34 be made available as a
part of hamm. This is because 2.0.34 is a bugfix-only upgrade to
2.0.33.
However, I don't think we have enough experience with 2.0.34 to
eliminate 2.0.33 from the distribution. So both should be available.
--
Raul
--
To UNSU
On Fri, Jun 05, 1998 at 06:54:26PM -0400, Brandon Mitchell wrote:
> On Fri, 5 Jun 1998, Steve Tonnesen wrote:
>
> > I'm getting unresolved symbol errors when cardmgr tries to insmod the
> > 3c589_cs module for my 3Com PCMCIA ethernet card. Is this a problem with
> > the boot disks, and/or is ther
Gene,
I downloaded the binutils-m68k-palmos-coff package. However, it
appears that it requires some gcc packages that you orphaned awhile
back. I'd like to adopt those packages but can't seem to find the
original sources anywhere. I'd rather start from what you've done so
far instead of startin
Raul Miller <[EMAIL PROTECTED]> writes:
> I would like to recommend that linux 2.0.34 be made available as a
> part of hamm. This is because 2.0.34 is a bugfix-only upgrade to
> 2.0.33.
>
> However, I don't think we have enough experience with 2.0.34 to
> eliminate 2.0.33 from the distribution.
Dan Jacobowitz wrote:
>
> I ran through my first x86 install today, and had a wierd problem.
> After pounding my bios into properly detect both c and d drives, I
> started the install using loadlin planning to avoid floppies
> altogether. However, when the time came to select a partition to find
Martin Mitchell wrote:
> I second this, 2.0.34 has undergone much testing in prereleases and is a
> further refinement of the stable branch of the kernel tree.
Let's be clear about what this means. We need to compile the kernel and all
packages that depend on it, pcmcia-modules, boot-floppies, etc.
Hi,
I've recently reported two critical bugs with sendmail 8.9.0:
1) it completely breaks incoming UUCP mail
2) it completely breaks outgoing Majordomo messages
#1 I solved easily, and fortunately, UUCP saves off failed messages.
#2 has caused numerous lost messages.
I have yet to receive any
Luis Francisco Gonzalez <[EMAIL PROTECTED]> wrote:
> Let's be clear about what this means. We need to compile the kernel
> and all packages that depend on it, pcmcia-modules, boot-floppies,
> etc. (We could, I guess live with the boot-floppies being 2.0.33 but
> given that there is a mismatch betwe
John Goerzen <[EMAIL PROTECTED]> writes:
> I downloaded the binutils-m68k-palmos-coff package. However, it
> appears that it requires some gcc packages that you orphaned awhile
> back. I'd like to adopt those packages but can't seem to find the
> original sources anywhere. I'd rather start from
Michael Meskes writes:
> mpsql (2.0-1) unstable; urgency=low
> .
>* Initial Release.
>* Based on version 2.0b1.
Hm, assuming the "b1" means it's beta stuff, I think it would be
better to keep it in the Debian version. Changing the version number
is confusing. Yes, I now it's a pain
On Sat, Jun 06, 1998 at 12:28:24PM -0400, LeRoy D. Cressy wrote:
> Where or what is your /dev/hdb drive? Is your hdb drive your
> cdrom? If so, it should be detected. I don't know if the
> cdrom has been compiled as a module, if so they must be loaded from the
> drivers
> disk.
hdb is my cdr
Hi,
Looks to me like kernel 2.0.34 is more than just a bugfix release. The
aic7xxx/pci driver changed *completely* with the result that my adaptec
2940AU no longer seems to work. I'd agree with the suggestion that 2.0.33
be kept around a bit longer.
J. Goldman
--
To UNSUBSCRIBE, email to [EMA
Bob> The changelog for mirror 2.8-15 included:
Bob>
Bob> * Applied patch by Adam Heath <[EMAIL PROTECTED]> to allow restarts
Bob> on partially downloaded files (fixes #19239)
Bob>
Bob> I would like to see this feature continued if it isn't in 2.9-1
Bob> by default.
Looks l
How about ship Hamm with 2.0.33 as setup but include what's necessary for
2.0.34 the way Bo has 2.0.29 but includes the stuff for 2.0.30
--
http://benham.net/index.html
-BEGIN GEEK CODE BLOCK-
Version: 3.1
GCS d+(-) s:+ a29 C++$ UL++> P+++$ L++> E?
On Sat, 6 Jun 1998, Jesse Goldman wrote:
> Hi,
>
> Looks to me like kernel 2.0.34 is more than just a bugfix release. The
> aic7xxx/pci driver changed *completely* with the result that my adaptec
> 2940AU no longer seems to work. I'd agree with the suggestion that 2.0.33
> be kept around a bit lo
Currently the version of glibc in frozen is older than the version in Slink.
Does this mean we plan to release Hamm with that prerelease of glibc?
Or are we planning on including 2.0.8 when it's released?
If we plan to include 2.0.8 we really ought to push the latest prerelease into
frozen to tes
> Currently the version of glibc in frozen is older than the version in Slink.
> Does this mean we plan to release Hamm with that prerelease of glibc?
> Or are we planning on including 2.0.8 when it's released?
>
> If we plan to include 2.0.8 we really ought to push the latest prerelease into
> fr
<[EMAIL PROTECTED]>(Alex Yukhimets) writes:
> > Currently the version of glibc in frozen is older than the version
> > in Slink. Does this mean we plan to release Hamm with that
> > prerelease of glibc? Or are we planning on including 2.0.8 when
> > it's released?
> >
> > If we plan to include
Ian Jackson wrote:
> The way I see this working is that there is only one per-host local
> database, but you preload it with the information you want before you
> start the installation. That way databases from other hosts and
> things like that are just special kinds of preloading.
Yes, that's t
> > There is a good reason to include recent glibc into frozen - latest
> > JDK-1.1.6 does not work with glibc from hamm.
>
> Umm, that's not a good reason. Certainly nothing like a good enough
> reason to justify us shipping with an *out of date* pre-release.
Sorry?
What I tried to say is that
<[EMAIL PROTECTED]> (Alex Yukhimets) writes:
> > > There is a good reason to include recent glibc into frozen - latest
> > > JDK-1.1.6 does not work with glibc from hamm.
> >
> > Umm, that's not a good reason. Certainly nothing like a good enough
> > reason to justify us shipping with an *out of
Martin Mitchell <[EMAIL PROTECTED]> writes:
> I believe the binutils-m68k-palmos-coff package was derived from my
> binutils-m68k-linux package, and the same goes for gcc-m68k-linux.
> If you need to rebuild the palmos gcc source packages from them, it should
> be fairly easy, just substitute palmo
On Tue, Jun 02, 1998 at 02:52:50PM +0300, Shaya Potter wrote:
> For the fact that we would need to write a parser for all our conf files. I
> think that might be overkill, as many of our conf files are probably just
> some files with a variable or two. i.e. the structure of the config file is
> c
Hi,
> Yes, AIC7XXX is a problem with 2.0.34. This probably means that 2.0.35 will
> be
> forthcoming.
I've had no problems whatsoever with my AIC7880 onboard UW SCSI
controller. It handles my SCSI-3 hard drive, SCSI-2 CD-ROM Drive and my
SCSI-1 DAT/DDS-2 tape drive just fine. Nevertheless,
On Wed, Jun 03, 1998 at 02:03:39AM +0200, Michael Dietrich wrote:
> hi,
>
> today i tried to build my first debian package but run immidiatly in
> an error. i did (nearly ;-) everything as told by the script 'making a
> debian package' but after the command build i got the messages:
> no utm
On Thu, Jun 04, 1998 at 08:42:15AM -0500, Stephen Carpenter wrote:
>
> While perusing around reading e-mail and jumping in on ocasional discussions
> I noticed some mention of the possibility of cutting down on some of the less
> importnat discussions an dhelping get hamm out...
>
> I remember th
On Thu, Jun 04, 1998 at 05:18:27PM -0600, LaMont Jones wrote:
> I intend to package VMailer (Wietse Venema's mail transport agent, see
> http://www.porcupine.org/vmailer). In keeping with Wietse's desires,
> the package will not be available until he releases it...
... and I was just hoping to se
Crashme is a program that runs random code in an attempt to crash your os. I
lack net access at the moment, so I don't know where it is or what license
it uses, but I think it would be nice to put this in debian, just so
interested parties can pound on their systems. I don't intend to package it
my
[EMAIL PROTECTED] wrote:
> Package: xbase
> Version: 3.3.2.1-1
> Severity: critical
>
> XFree86 3.3.2.2 has been released. According to
> http://www.xfree86.org/3.3.2/RELNOTES3.html#3 :
> :3.3.2 patch 2 (aka 3.3.2.2) fixes some security bugs, a denial of service
> :problem with xdm, a few gcc 2.8.
On Sat, 6 Jun 1998 [EMAIL PROTECTED] wrote:
> > > There is a good reason to include recent glibc into frozen - latest
> > > JDK-1.1.6 does not work with glibc from hamm.
> >
> > Umm, that's not a good reason. Certainly nothing like a good enough
> > reason to justify us shipping with an *out of
On Sat, Jun 06, 1998 at 06:18:19PM -0400, Ossama Othman wrote:
> > Yes, AIC7XXX is a problem with 2.0.34. This probably means that 2.0.35
> > will be
> > forthcoming.
> I've had no problems whatsoever with my AIC7880 onboard UW SCSI
> controller. It handles my SCSI-3 hard drive, SCSI-2 CD-ROM
> Crashme is a program that runs random code in an attempt to crash your os. I
> lack net access at the moment, so I don't know where it is or what license
> it uses, but I think it would be nice to put this in debian, just so
> interested parties can pound on their systems. I don't intend to pack
Alex Yukhimets wrote:
> Well, this way is probably OK for dh_testroot, but "id -u" is absolutely
> non-portable thing across different UNIX platforms... :(
Good enough for dh_testroot, I think this is in debhelper 0.90.
--
see shy jo
I'm on a long trip, pardon any delays in my reply.
--
To
Manoj Srivastava wrote:
> Brederlow> The size file should be generated by the server. Here are
> Brederlow> the reasons:
>
> I am (perhaps unnecessarily) worried about time requirements
Considering that we plan to eventually have lintian run automatically on
packages before they get move
Joey Hess <[EMAIL PROTECTED]> wrote:
> How is it possible to check for block sizes with lintian? And what do you
> expect a maintainer to do if they use a different block size and lintian
> dislikes that? Reformat?
To deal with block sizes we'll need to abandon (or upgrade) du.
To find out what b
Raul Miller <[EMAIL PROTECTED]> wrote:
> To deal with block sizes we'll need to abandon (or upgrade) du.
Argh.. please ignore this sentence, it makes no sense.
--
Raul
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Sat, 6 Jun 1998, Raul Miller wrote:
> A brutally simplistic mechanism for representing the data would
> provide a different sizes file for each different block size
> we support. Optimizations are possible but may not be worth the
> effort.
This is getting out of hand, do we really need to c
Jason Gunthorpe <[EMAIL PROTECTED]> wrote:
> This is getting out of hand, do we really need to consider slack space
> when calculating if the user has enough room to install!?
No, what we mostly need is an estimate.
--
Raul
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsub
58 matches
Mail list logo