Package: modules
Version: 1.2.8-1
I'm experimenting with the newer 1.3 kernels, so I'm not sure this is really a
bug (yet), although it could be.
The `genksyms' executable is installed in /usr/bin, despite its manual page
belonging to section 8. The 1.3.47 kernel module support at least expects t
On Mon, 18 Dec 1995, Stephen Early wrote:
> xsnow (1.40-0); priority=LOW
I thought about packaging this, but interpreted the copyright as
requiring that it be placed in non-free, so I didn't. Just raising
a concern.
-help
--help
On Mon, 18 Dec 1995, Karl Ferguson wrote:
> > ... relocating the development release ...]
>
> Ian, if you do decide to do number 2, could you please give us a little
> notice by posting to devel beforehand? I just dont want to have to
> delete and re-mirror the 1.0 stuff (as well as the other m
Anders,
I rebuilt sendmail for debugging, with -DNEWDB removed because it did not
find the header db.h, and -DNDBM is there anyway - I think we probably don't
need both. The problem went away. These are my "db" libraries.
Bruce
-rw-r--r-- 1 root root86534 Nov 18 09:16 libdb
On Sun, 17 Dec 1995, Ian Murdock wrote:
> > The mount package contains a "configuration" file /etc/fstab.sample.
> > Would it not be better to include this file in /usr/doc/examples, or
> > does something actually depend on it being in /etc?
>
> As far as I know, nothing depends on it being in /
On Sun, 17 Dec 1995, Ian Murdock wrote:
> Well, we appear to have two options. We can (1) leave the development
> release in an unreadable directory, as it is at present; or (2) move the
> development release back into a readable directory, making it clear that
> it's still under development.
A
Actually, I was thinking of using umsdos rather than minix as the
filesystem for the installation root floppy. I haven't tried it yet.
We'd need a package with the umsdos utilities (there's umssync, which
synchronizes the directory contents with the "extended" directory
after MSDOS has changed them
-BEGIN PGP SIGNED MESSAGE-
xsnow (1.40-0); priority=LOW
Package: xsnow
Version: 1.40
Package_Revision: 0
Maintainer: Stephen Early <[EMAIL PROTECTED]>
Description: Snow in your X server
xsnow brings Christmas to your X server. A nice waste of CPU time...
c74e59f4680e26b2eb6fc321b0f3386
Note that "sendmail" uses db and gdbm, too.
Bruce
--
Bruce Perens <[EMAIL PROTECTED]> Pixar Animation Studios
Q: How many Microsoft engineers does it take to screw in a light bulb?
A: None. They just define darkness as an industry standard.
-BEGIN PGP SIGNED MESSAGE-
xtrlock (2.0-1); priority=LOW
Package: xtrlock
Version: 2.0
Package_Revision: 1
Maintainer: Stephen Early <[EMAIL PROTECTED]>
Description: Minimal X display lock program
xtrlock is a very minimal X display lock program, which uses nothing
except the Xlib libr
On Sun, 17 Dec 1995, Ian Murdock wrote:
> On Sat, 16 Dec 1995, Robert Leslie wrote:
>
> > I wouldn't have noticed these except I found the new xterm didn't log
> > anything into utmp; should this really be the default?
>
> It should log to both utmp *and* wtmp by default. Could this be changed?
> Well, we appear to have two options. We can (1) leave the development
> release in an unreadable directory, as it is at present; or (2) move the
> development release back into a readable directory, making it clear that
> it's still under development.
>
> Personally, I prefer (2). I don't want
I am indebted to Robert Leslie and Karl Ferguson for spotting two stupid
errrors in yesterday's release of efax-07a-3. Thanks, guys.
So here's a new one and it'll hopefully last longer than 24 hours ...
Date: 17 Dec 95 22:39 UT
Source: efax
Binary: efax
Version: 07a-4
Description:
efax: Progr
On Mon, 11 Dec 1995, Owen S. Dunn wrote:
> No symbolic link /usr/X11 is made to /usr/X11R6 when this package is
> installed.
Is this necessary? I thought the FSSTND said it wasn't.
On Sat, 16 Dec 1995, Ian Jackson wrote:
> > 4. The /etc/init.d/functions file will no longer be used.
>
> Please make it exist and be empty so that existing programs don't
> break. It should contain a comment saying that programs shouldn't use
> it.
Also, don't forget to remove the ". /etc/
I agree with Ian J.
I also agree that compatibility between distributions is paramount, but
I'd rather convince Caldera, Red Hat, etc. to be compatible with System V
than change Debian to be incompatible with it. We should make talking to
them the first step in resolving this incompatibility prob
We should consider adding umsdos support to Debian 1.0. Alot of
people ask about it. We shouldn't present umsdos as an alternative to
installing Debian "for real", but we could at least give our users the
option of using it.
(It might also be useful as a "try it before you install it for real"
f
I was just forwarded this.
It was probably intended for the kbd maintainer, which is no longer me.
-- Forwarded message --
Date: Sun, 17 Dec 1995 02:46:05 -0500
From: Chris Fearnley <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Newgroups: comp.os.linux.misc
Subject: (fwd) kbd-0.91 is
On Sat, 16 Dec 1995, Robert Leslie wrote:
> I wouldn't have noticed these except I found the new xterm didn't log
> anything into utmp; should this really be the default?
It should log to both utmp *and* wtmp by default. Could this be changed?
On Wed, 13 Dec 1995, Robert Leslie wrote:
> As long as I've been updating the mount package, I have a question:
>
> The mount package contains a "configuration" file /etc/fstab.sample.
> Would it not be better to include this file in /usr/doc/examples, or
> does something actually depend on it be
On Sun, 10 Dec 1995, Bruce Perens wrote:
> Everybody has problems with truncated uploads, etc. Generally they can't
> fix them by themselves. I wanted to repair this by automating the FTP
> archive process to check against the changes file and then move the file
> into place. Ian Murdock objected
On Sun, 10 Dec 1995 [EMAIL PROTECTED] wrote:
> I'd love that feature too. But that either requires a damn good script,
> or that everybody uses the same .changes format.
I think everyone *should* be using the same format. Bill has addressed
my complaints and suggestions about the old dchanges f
On Wed, 13 Dec 1995, Bruce Perens wrote:
> I'll let Ian Murdock decide what he wants to do about this.
Well, we appear to have two options. We can (1) leave the development
release in an unreadable directory, as it is at present; or (2) move the
development release back into a readable directory
On Sat, 16 Dec 1995, David Engel wrote:
> There are a couple of serious problems with Ray Dassen's latest gdbm
> and db packages. DO NOT install them unless you want run the risk of
> leaving perl, and consequently dpkg, in an unusable state. The same
> problems exist with Ray's readline package
I have a mirror of ftp.debian.org on my machine which I am willing to
make available to people in Europe. The mirror is available by anonymous
ftp to myrddin.chu.cam.ac.uk
This mirror will only be available until June 1996.
Steve Early
[EMAIL PROTECTED]
> Karl Ferguson writes:
> Karl> /var/lib/dpkg/info/efax.postinst: [: too many arguments -
>
> Weird. I tested this a bit yesterday while I implemented it, and of course
> tested the installation on my box before I shipped efax --- in short, it
> doesn't do this on my computer.
>
> Can you t
Anders,
On my system, sendmail seems to get into a non-terminating loop when it
runs the mail queue and when it processes the SMTP "MAIL FROM" command.
Later today I'll have time to build it for debugging.
I'm using version 8.6.12-9 .
Bruce
--
Bruce Perens <[EMAIL PROTECTED]> Pixar Anim
Karl Ferguson writes:
Karl> /var/lib/dpkg/info/efax.postinst: [: too many arguments -
Weird. I tested this a bit yesterday while I implemented it, and of course
tested the installation on my box before I shipped efax --- in short, it
doesn't do this on my computer.
Can you trigger the er
Package: efax
Version: 07a-3
Efax gives this message upon installation:
-
(Reading database ... 11345 files and directories currently installed.)
Preparing to replace efax (using efax-07a-3.deb) ...
Unpacking replacement efax ...
Setting up efax ...
The "efax" package has been installed on y
On Sun, 17 Dec 1995, Michael Alan Dorman wrote:
> This is a documented bug in the original source---I believe I sent a
> patch that could be used to create a xserver-mach32x or something that
> would be compiled to allow users who wanted to to drive their cards at
> something resembling its capabi
Package: xserver-mach32
Version: 3.1.2-2
This is a documented bug in the original source---I believe I sent a
patch that could be used to create a xserver-mach32x or something that
would be compiled to allow users who wanted to to drive their cards at
something resembling its capabilities.
Mike.
On Sun, 17 Dec 1995, Chris Fearnley wrote:
> This is a preliminary release. It seems to work, but I'm disatisfied
> with my handling of httpd configuration (basically there is none - you
> have to edit /etc/httpd/* by hand).
Hmm. That's what kept me from releasing mine.
Maybe we can decide what
Eddie Maddox wrote:
> 1. I didn't have lp installed since the installation parameter screen
> for this said "line printer", not just "printer".
>
> Having been a computer operator in times past I KNOW my little HP Deskjet 500
> is NO "line printer".
I agree that the use of the term "line printer"
On Fri, 15 Dec 1995 [EMAIL PROTECTED] wrote:
> Ian, are you working on an elf version? If not, I would be willing
> to work on it if it's not too complicated. I've never handled a
> package before, so I'd like to start out easy.
Yes, please do. Thanks!
Robert Leslie wrote:
>
> Package: xserver-mach64
> Version: 3.1.2-2
>
> On occasion, apparently at random, certain characters of a particular font
> will become "eroded": the bottom portion of the character will blank, so that
> every newly drawn occurence of the character on the screen only shows
Package: xserver-mach64
Version: 3.1.2-2
This problem is difficult to describe, and difficult to trace or reproduce.
I'm not sure it is specific to the XF86_Mach64 server, but that's the only one
I've used, and it's occurred for all versions of XF86 3.1.2 I've used
(Slackware 2.3.0, Debian 0.93R6,
This is a preliminary release. It seems to work, but I'm disatisfied
with my handling of httpd configuration (basically there is none - you
have to edit /etc/httpd/* by hand). And the server though compiled with
gdbm support doesn't take advantage of the option of dynamicaly linking
in modules.
Package: texbin
Version: 3.1415-4
The man page for tex (and bibtex) has unexpanded macros for a number
of the default search paths (from tex(1)):
TEXFONTSSearch path for font metric (.tfm) files.
Default: @DEFAULT_TFM_PATH@
TEXFORMATS Search
39 matches
Mail list logo
