> "Joey" == Joey Hess <[EMAIL PROTECTED]> writes:
Joey> Karl M. Hegbloom:
>> Since the output from cron jobs is mailed anyhow, as it should
>> be, I think that all cron scripts should report in as they are
>> run, and that this should be made a standard. Here's why.
Joey>
> Are there any objections to moving the file into /boot?
Is there really any reason to take us farther away from the standard that
everyone else uses? Its just one more gotcha that'll tick a newbie off
when they follow their slackware friends advice, dl the kernel source, and
just have a
-BEGIN PGP SIGNED MESSAGE-
As the official version of perl 5.004 is finally out (I must admit I
haven't installed the debian package yet, but I run webservers with lots
of perl CGI and can't afford to break them), I have a few questions,
comments, and thoughts.
1. In building my own perl
Hi,
>>"jwalther" == jwalther <[EMAIL PROTECTED]> writes:
>> Are there any objections to moving the file into /boot?
jwalther> Is there really any reason to take us farther away from the
jwalther> standard that everyone else uses? Its just one more gotcha
jwalther> that'll tick a newbie off when
Hi,
>>"jwalther" == jwalther <[EMAIL PROTECTED]> writes:
>> Are there any objections to moving the file into /boot?
jwalther> Is there really any reason to take us farther away from the
jwalther> standard that everyone else uses? Its just one more gotcha
jwalther> that'll tick a newbie off whe
Hi,
Well, with 5.004, CGI-modules is obsolete, and so the
misnaming of the CGI modules package is a solved issue
;-). (Unless. of course, there is a hew-and-cry about removing the
package, I'd suggest removing CGI-modules from hamm).
As for the description issue, even the one l
On 19 May 1997, Manoj Srivastava wrote:
> Well, with 5.004, CGI-modules is obsolete, and so the
> misnaming of the CGI modules package is a solved issue
> ;-). (Unless. of course, there is a hew-and-cry about removing the
> package, I'd suggest removing CGI-modules from hamm).
No real ob
On 19 May 1997, Manoj Srivastava wrote:
> Less blather this time. Yes, ther reason is that /boot
> contains other useful information about the kernels ensconced there,
> (like System.map, and psdatabase) but is missing one piece: exactly
> what is configured into the kernel (which can be
Basically, mailx conflicts with smail.
dpkg: error processing xmysql (--configure):
dependency problems - leaving unconfigured
Setting up smail (3.2-3) ...
Error: system's FQDN hostname (citytel_prct40.citytel.net) doesn't match
RFC1035 syntax; cannot configure the mail system.
dpkg: error proce
Im sure there used to be a mysql package. the mysql db libs are in, and
xmysql front end is in the distro where the fundamental package? is it
being worked on? Im positive I installed it ages ago... foolish me for
uninstalling it, now its not there anymore.
Is there any reason that snarf pa
The following message is a list of items to be completed for the upcoming
releases of Debian GNU/Linux. If something is missing, incorrect, or you want
to take responsibility for one or more items, please send email to:
Brian White <[EMAIL PROTECTED]>
This document was last modified at Time-stam
9020: e2fsprogs- fsck.ext2: can't load library 'libcom_err.so.2'
9127: seyon- seyon depends on X11R6 instead of xlib6
9256: vrweb- Unresolved dependency report for vrweb
9258: sgml-tools - Unresolved dependency report for sgml-tools
9259: j1
> "Brian" == Brian Mays <[EMAIL PROTECTED]> writes:
Brian> rxvt (and rxvt-xpm) always exports the variable "COLORTERM"
Brian> so that programs can check for color support.
> "John" == John Goerzen <[EMAIL PROTECTED]> writes:
John> Unfortunately, I know of no programs that ma
This is why changing the default prompt for everyone is not a good
idea. You guys can't even agree on what you want the new prompt to
be. And if you want my personal preference, any prompt longer than
'$ ' is too long. If I want to know what directory I'm in, I just
pwd.
Instead of arguing back
Nicolás Lichtmaier <[EMAIL PROTECTED]> writes:
> Most people that adopt Linux come from DOS. Linux is expanding the UNIX
> users base. I come from DOS-OS/2 too. I used Slackware, and I changed
> because it was a mess. Current newbies that start with RH won't change to
> Debian, they don't need to
The difference is that RedHat's X configurator configures not only X,
but also mail, news, printers, networking, etc. It's a configurator
that runs under X -- not really a configurator for XFree86.
If we are wanting to go that way; fine. I have no problem with it.
As long as we don't go so far a
>Anybody should know that before typing "rm -rf *" or an equivolent,
>you THINK FIRST, every time.
The problem does not arise when you type rm the first time but after you
have some confidence and you think you know what you are doing.
Everybody knows what you should think first. But who does aft
Oh, I see. Nevermind then -- what you're saying is that the "X
configurator" is at the level of an X based dselect -- so that's the
problem of the "diety" team, right? (Thus it's not something I need
to be particularly concerned with.) Thanks... _Mark_
--
TO UNSUBSCRIBE FROM THIS MAILING LIST
>
> *** ***
> *** Release of Bo is HOLDING for CRITICAL BUGS!***
> *** ***
> *** There is one remaining critical bug that must be resolved before
Hi,
> 2. I installed shadowing as it suggested - started installing packages
> merrily. I also installed and configured NIS - however, I cannot log in
> any in my personal account - though I can finger anyone without trouble. I
> deinstalled shadow by doing a shadowconfig off and that still didn
At 09:26 AM 19/05/97 +0100, Philip Hands wrote:
>> 2. I installed shadowing as it suggested - started installing packages
>> merrily. I also installed and configured NIS - however, I cannot log in
>> any in my personal account - though I can finger anyone without trouble. I
>> deinstalled shadow
> Anybody should know that before typing "rm -rf *" or an equivalent,
> you THINK FIRST, every time.
And AFTER you type it.
The prompt doesn't make the slightest difference when the death knell sounds:
rm: .o: No such file or directory
and it dawns on you there was an extra space in the last
> Hi,
>
> > 2. I installed shadowing as it suggested - started installing packages
> > merrily. I also installed and configured NIS - however, I cannot log in
> > any in my personal account - though I can finger anyone without trouble. I
> > deinstalled shadow by doing a shadowconfig off and tha
In your email to me, Christoph, you wrote:
>
> >
> > *** ***
> > *** Release of Bo is HOLDING for CRITICAL BUGS!***
> > *** ***
> > *** There is
On Mon, 19 May 1997 [EMAIL PROTECTED] wrote:
> On 19 May 1997, Manoj Srivastava wrote:
>
> > Less blather this time. Yes, ther reason is that /boot
> > contains other useful information about the kernels ensconced there,
> > (like System.map, and psdatabase) but is missing one piece: exac
"Scott K. Ellis" <[EMAIL PROTECTED]> writes:
> My main concern is that they neither bunch up on the dpkg select screen,
> nor is it easy to search for perl modules in dselect (I'd like to be able
> to find all the perl modules by searching on perl).
BTW, I maintain alias and www-search (and libwww
On 19 May 1997, John Goerzen wrote:
> I agree with most of what you are saying; however, I think you sorta
> missed the point I was trying to make (which is probably my fault
> because I didn't make it very clearly )
=)
> My problem is not so much with changing root's default prompt on new
> in
On May 19, Nicolás Lichtmaier wrote
> On Mon, 19 May 1997, Christoph Lameter wrote:
>
> > > So I say: PS1="[\\u] \\h:\\w\\$ " =D
> > Too long. But better than nothing.
>
> It isn't too long...!
>
> [nick] newton:~/src/deb/lftp-0.11.1$
> [nick] newton:~/src/deb/lftp-0.11.1$
> [nick] newt
Hi,
>>"Jean" == Jean Pierre LeJacq <[EMAIL PROTECTED]> writes:
Jean> I agree with the basic concept but shouldn't this be placed in
Jean> /etc instead of /boot. /etc defines the configuration for the
Jean> host after all.
The config file, which shall reside in the kernel-image
package,
On May 19, Brian C. White wrote
> 9259: j1 - Unresolved dependency report for j1
A fixed version of j1 is sitting in ~moth on master.debian.org
and has been since last week.
When I uploaded it, Incoming was not writeable, so I uploaded
a copy to my home directory and sent email to
On Mon, 19 May 1997, Brian Mays wrote:
> This is why changing the default prompt for everyone is not a good
> idea. You guys can't even agree on what you want the new prompt to
> be. And if you want my personal preference, any prompt longer than
> '$ ' is too long. If I want to know what direct
On Tue, 20 May 1997, Nicolás Lichtmaier wrote:
> I think that this is the kind of thinking that is killing Debian.
>
> 1) Newbie setting doesn't mean annoying settings.
> 2) `real men' like you can change those settings.
> 3) Configuration packages is an awful idea that goes against the idea
> > *** ***
> > *** Release of Bo is HOLDING for CRITICAL BUGS!***
> > *** ***
> > *** There is one remaining critical bug that must be resolved be
In article <[EMAIL PROTECTED]>,
Adrian Bridgett <[EMAIL PROTECTED]> wrote:
>I think that it would be a good idea to allow users to install to a UMSDOS
>partition. I am sure there are a lot of people who would quite like to try
>out Linux, but are frightened of the install process.
>
>Imagine a fu
Hi,
[This may well be orthogonal, or in addition to, the solutions discussed]
Maybe we could offer some example of tips and tricks? My
preffered prompt mechanism sets the xterm title to (like right now)
[EMAIL PROTECTED]:~/var/tmp
with a short prompt of '__> ', or the above bec
Have a look at the bug report. I dont know why no one has marked it as
done yet. There is a file lists in the but report ending in .dpkg-tmp
evidently from a crash. Dont be buerocratic about releasing 1.3.
On Tue, 20 May 1997, Brian White wrote:
>> > ***
Does anyone know what this error message indicates?
[EMAIL PROTECTED] ~/debian/build/tmp>dpkg-source -x xkobo_1.9-3.dsc
dpkg-source: extracting xkobo in xkobo-1.9
patch: .dpkg-orig is not a regular file--can't patch
dpkg-source: failure: patch gave error exit status 2
I can extract the sourc
On Tue, 20 May 1997, Enrique Zanardi wrote:
> On Tue, 20 May 1997, Nicolás Lichtmaier wrote:
>
> > I think that this is the kind of thinking that is killing Debian.
> >
> > 1) Newbie setting doesn't mean annoying settings.
> > 2) `real men' like you can change those settings.
> > 3) Configur
> "EZ" == Enrique Zanardi <[EMAIL PROTECTED]> writes:
EZ: The problem with that approach is that many of those "newbie"
EZ: settings are just a matter of taste. We don't want to set a
EZ: thousand of those parameters in hundreths of different config
EZ: files that will have to
> Include the multi-thread support patch for the Objective-C runtime lib (???)
According to Scott Christley <[EMAIL PROTECTED]> (de-facto
maintainer of the gcc Objective-C runtime), the Objective-C runtime should
be kept in sync with the gstep-base included in the release.
bo includes gstep-b
On Mon, 19 May 1997, Mark W. Eichin wrote:
> Is there a web page or other document that explains what our strategy
> for libc6 is? I'm not talking about random comments on the list, I
> mean something nailed down that I can refer to...
>
> In particular, I've got a few issues to work out.
>
-BEGIN PGP SIGNED MESSAGE-
Scott Ellis, in an immanent manifestation of deity, wrote:
>As the official version of perl 5.004 is finally out (I must admit I
>haven't installed the debian package yet, but I run webservers with lots
>of perl CGI and can't afford to break them), I have a few q
On Tue, 20 May 1997, Tom Lees wrote:
> > 3) can I drop the a.out-only "dlltools" package now? :-)
>
> No. It is needed to build a.out versions of, e.g. svgalib. Some older
> binary-only programs only come in a.out format (Doom, for example) :(.
Yes, it can be dropped _(;
1/ Doom comes with
> this since he asked for it a while back. The upgrade to libc6 for perl
> can't happen until there is a libgdbm compatible with it though since I
> refuse to break everyone's dbm interfaces. I'll also be able to release
Great - as soon as I get some consensus on package naming, I'll try to
put
> No. xlib6 should be for libc6 (more long-term solution). Then create an
> xlib6-libc5. How we handle the dependencies for this, I don't know. Fix
But then anyone "upgrading" xlib6 (the 6 for x11r6, not libc6!) will
end up with a libc6 version; Is that what we want to happen?
> > alt-xlib6-dev
> 1/ Doom comes without any source, so dlltools won't be of any use.
Irrelevant -- *aout-svgalib* is what needs dlltools, not doom itself.
> Debian still support a.out executables _execution_ but not a.out
> _development_ anymore...
I guess I could believe that as long as the a.out developmen
Gregor Hoffleit <[EMAIL PROTECTED]> writes:
> The remaining question the thread model to be enabled in the patched objc
> runtime. The patched runtime can be compiled for e.g. PCthreads,
> LinuxThreads or no threads at all. Who is to decide this ?
As I understand it, Debian is trying to stand
On Wed, 14 May 1997, Christian Schwarz wrote:
> On Sun, 11 May 1997, Chris Walker wrote:
>
> > Would some mechanism of saying "when this bug is closed notify me as
> > well" eg by sending a specially formulated e-mail, or perhaps some web
> > interface. This might be useful, as in general I pro
On May 21, Chris Walker wrote
If I could get notification on a bug that I was particularly
concerned with, I guess I'd use it about once a quarter.
[That's about how often I run into bugs of that nature.]
It would probably save me about 8-16 hours per quarter.
--
Raul
--
TO UNSUBSCRIBE FROM
49 matches
Mail list logo
