ng.
Indeed, in a society where people were more equal (and more relaxed
about sexuality), the porn industry would very likely both be
sanitised and less prosperous.
Regards: David Weinehall
--
/) David Weinehall <[EMAIL PROTECTED]> /) Northern lights wander (\
// Maintainer of
not. We're also not the PTA or the moral police.
> right to look at cartoon tits then that's fine by me. We are trying to
> build an operating system. I think.
Indeed. From that point of view, hotbabe is pretty meaningless.
Then again, so is quake, doom, nethack, etc.
Regards:
27;s leaves or something in the
> default incarnation.
While being all for that series of pictures (nature is beautiful),
I find the package pretty meaningless anyway, so I don't see the point
of including it in Debian in the first place. I do, however, see some
relevance to the di
On Thu, Dec 02, 2004 at 04:07:14PM +0100, Michelle Konzack wrote:
> Am 2004-12-02 08:44:34, schrieb David Weinehall:
>
> > Really, she's 13, and you think it'd do any difference whatsoever to
> > expose her to a pixelled image of a nude woman?! Sheesh. Either
&
oppose it.
Again, have a look at the pictures *before* making comments.
I don't doubt that you have have these opinions; in fact, I suspect most
people here agree with you (I do). It's not really relevant wrt these
pictures, however.
[snip]
Regards: David Weinehall
--
/) Davi
images and I'd be surprised if
> Tollef> you feel them degrade, abuse or exploit females. I think
> Tollef> they are silly and nothing to be upset about. Not porn,
> Tollef> not erotic, just silly.
This part, was written by Tollef though =)
[snip]
Rega
is pornographic is dependant
on the viewer, so most people are unlikely to be offended by the artwork
in hotbabe...
Regards: David Weinehall
--
/) David Weinehall <[EMAIL PROTECTED]> /) Northern lights wander (\
// Maintainer of the v2.0 kernel // Dance across the winter sky //
\) h
res.
This way, we'd both satisfy people using Debian as a base for
embedded and other customised systems, and most (but not all)
porters. Of course some people are never satisfied, but then again,
there is no way to solve this that makes everyone happy.
[1] Hopefully, I might remember incor
, let's not dump even more crap into /etc; it's ugly enough
as it is...
Regards: David Weinehall
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://www.acc.umu.se/~tao/(
rest
for Debian to do so, but since it's obvious from this discussion that
different Debian developers have different opinions on this issue,
it's clearly not in Debian's best interest.
Regards: David Weinehall
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window
n Debian too, but if the bug is caused by
the Ubuntu build environment, then the bug is purely in the package,
and any bugreport would just waste the Debian developer's time, *AND*
risk Ubuntu losing vital information about a bug in their build
environment.
Regards: David
--
/)
aptic
> doesn't show up any matches for helix.
apt-cache search helix-player
yields:
helix-player - the helix audio and video player
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~ // Di
o more binary
packages? manpages (generic stuff for all Debian systems),
manpages-linux (Linux specific things, like sysfs), manpages-linux-dev
(Linux specific programming interfaces).
Regards: David Weinehall
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~
anges are needed to address
> bugs such as #295211 (upstream does not document our libc/kernel
> combination).
What manpages in upstream are non-free? Do we have rewritten
alternatives in Debian, or are those pages simply removed without
replacement?
Regards: David Weinehall
--
/)
On Mon, Feb 20, 2006 at 12:42:08PM +0100, Florian Weimer wrote:
> * David Weinehall:
>
> >> Upstream includes non-free manpages these days, so in reality, we have
> >> already forked. Further Debian-specific changes are needed to address
> >> bugs such as #29521
r
> email and send in 'bug reports' on their @debian.org mailing lists.
> Cheers,
> Kev
echo "[EMAIL PROTECTED]" > .forward+debian-devel
+debian-devel).
Whoops goes the entire list... =)
Regards: David Weinehal
e might
even work with 4k too), but some do, thus you need to patch the kernel
to provide 16k stacks (this is really bad for other reasons).
Regards: David Weinehall
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~ // Diamond-
m today's paper, and the "Fuck off!" newbies sometimes get on an
IRC-channel when asking the wrong question.
The problem is that to alleviate the problem completely, we'd either
have to stop people from writing what they think (mind control),
or have everyone convert to new speak
also supposed to educate their children.
Can't disagree with this one though. But there's always the saying:
"Do as I say, not as I do". And it's always a mistake...
[snip]
Regards: David Weinehall
--
/) David Weinehall <[EMAIL PROTECTED]> /) Northern lig
arameter, it would be nice if Linux did.
netdev@oss.sgi.com <--- patches goes that way.
linux-kernel@vger.kernel.org <--- or possibly that way.
Regards: David Weinehall
--
/) David Weinehall <[EMAIL PROTECTED]> /) Northern lights wander (\
// Maintainer of the
r this
list than 95% of all flame-wars here...
Regards: David Weinehall
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://www.acc.umu.se/~tao/(/ Beautiful hoar-frost (/
--
To U
dom is concerned, both types are equivilently bad. The choice is
> either:
> 1) Distribute the non-free firmware. Our users are happy.
Sure, as long as we distribute it in *non-free* where it belongs.
[snip]
Regards: David Weinehall
--
/) David Weinehall <[EMAIL PROTECTED]
g flame wars by
> getting offensive and doing ad hominem attacks with a very arrogant POV. So,
Pot. Kettle. Black.
[snip]
Regards: David weinehall
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~ // Diamond-white roses of
e ownership/permission support and its
filename munging...
And I somehow doubt that minix is a problem either, these days.
Regards: David Weinehall
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~ // Diamond-white roses of
ware Operations) that work on
this product consists of several DD's (myself being one), plus at least
one person in the NM-queue. Some of our subcontractors are also DD's.
Regards: David Weinehall
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
/
ing them.
Well, the European Parliament is (or has at least been) strongly opposed
to software patents, so it's unlikely that they will pass without some
serious trickery.
NOTE: I'm a Nokia employee and work on the N770 team, but this is by
no means an official statement...
Rega
.
Yup. They'll also have learned that packages are managed by rpm.
We'd better change our package management system.
Regards: David Weinehall
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~ // Diamond-white roses
ly. Unless there are some radical changes,
there won't be more than 6-8 new kernels released 18 months from now.
So we're more looking at 2.6.20.
I totally agree about goes 2.6.xx full out, however. 2.6.11 is already
pretty stable, 2.6.12 promise to be even more so.
Regards: David
ople.debian.org/~ballombe/menu-snapshot>
Sounds great! Do you have a list of the translations available, so that
people who's language is missing can submit a translation?
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~~
at least add a postinst
script that does the migration), then I'm all for a switch to the
new version.
Regards: David Weinehall
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://www.
gram.
Isn't there a risk of causing double work?
Person A reports spam, Blars removes it
Person B reports the same spam, Blars checks again - no spam found
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~~~
ilable in Debian...
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://www.acc.umu.se/~tao/(/ Beautiful hoar-frost (/
--
To UNSUBSCRIBE, email to [EMAIL
the next firmware version is out;
that way we'll avoid the binary only regulatory daemon.
See the following post:
http://marc.theaimsgroup.com/?l=linux-netdev&m=116226285115407&w=1
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
//
the GFDL debacle a manual I could easily refer to, ...
The SuSv3 is to be considered as POSIX these days, so it's available for
free (and even packaged in Debian...)
PS: The equality operator is =.
RegardS: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window
ably a 3rd
> > alternative]".
>
> busybox?
Such a requirement would at least be wonderful for us embedded developers...
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~ // Diamond-whit
On Tue, Nov 14, 2006 at 05:11:27PM +0100, Marco d'Itri wrote:
> On Nov 14, David Weinehall <[EMAIL PROTECTED]> wrote:
>
> > > busybox?
> > Such a requirement would at least be wonderful for us embedded developers...
> But hardly practical, IIRC there ar
p of people that caused it to fail...
> Before this there was a widely agree definition of what
> /bin/sh needs to support and almost no bugs related to this.
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~~
guess, as long as we get rid of crap like [[ ]], <, >, -nt,
-ot, -ef, $RANDOM, $"...", read -e, declare, typeset, function (augh, I
cannot understand why bash even introduced that one), let, source
(again, completely pointless), pushd, popd, &>, {}...
I can probably come up wit
d help to be reminded that I can't really
> depend on very much of the semantics of local from any specific
> implementation.
>
> fname () {
> local a # keep it simple
> a='' # initialize the variable
> use a ...
> }
> is the only s
a sort of
> blessing to using an absolute path in this situation, since coreutils test
> is not quite "any other program that one would expect to be on the PATH"
> simply because in this case the shell isn't going to *look* at the PA
ing "debconf" is *also* not allowed, because it is *also* not a
> "POSIX feature". The point is that "POSIX feature" is *not* a
> specification of anything, given the way that POSIX deals with builtins.
Sorry, but that's a strawman, for two reasons. First, POSI
ds: on."
This proposal has some merit, as long as we do s/POSIX/SuSv3/.
Also, we probably want to make exceptions for find/xargs (to get -0).
[snip]
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
//
ure
it's provided by anything in Debian), the FR-extensions (Fortran
Runtime), most (all?) of the utilities marked as DEVELOPMENT (things
such as compilers, sccs-related commands, cflow, and ctags).
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
//
ate: 6.1
Version table:
6.1 0
500 http://ftp.se.debian.org unstable/contrib Packages
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://www.acc.umu.se/~tao
ly use job-control in your shell-scripts? Interesting...
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://www.acc.umu.se/~tao/(/ Beautiful hoar-frost
1-21 Steve Langasek <[EMAIL PROTECTED]>
> ([EMAIL PROTECTED])~$
>
> Looks that it's signed by itself.
Yes, aren't all keys self-signed?
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~ // Di
>
> Guess what? I used bash on that old hardware when it was shiny and new
> also. Didn't seem to have any problems.
Somehow I doubt that you used today's version of bash (which I bet
is a lot bigger and more memory-consuming due to new features).
Regards: David
--
/) David
On Thu, Nov 23, 2006 at 07:09:49PM +0100, Steinar H. Gunderson wrote:
> On Thu, Nov 23, 2006 at 06:37:52PM +0100, David Weinehall wrote:
> > Somehow I doubt that you used today's version of bash (which I bet
> > is a lot bigger and more memory-consuming due to new features).
On Thu, Nov 23, 2006 at 07:54:46PM +0100, Bill Allombert wrote:
> On Thu, Nov 23, 2006 at 07:41:08PM +0100, David Weinehall wrote:
> >
> > And compared to dash, the difference is vast:
> >
> > -rwxr-xr-x 1 root root 80200 2006-11-21 16:36 /bin/dash
> >
> >
e *much*
> easier. Isn't that enough?
If you just want to avoid things breaking, it's enough. If you want to
be able to use the scripts on an embedded platform, or to take advantage
of the performance boost of using dash instead of bash, it isn't.
Regards: David
--
/) David We
ntial to use only SuSv3 compliant features. I think
rewriting *all* scripts to use only SuSv3 features would be too big of
an ordeal, but just fixing the initscripts, plus all scripts in
essential should be doable.
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my windo
for most users. That doesn't mean we should limit
ourselves to using bash for non-interactive use though.
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://www.
On Thu, Nov 23, 2006 at 11:56:48AM -0800, Thomas Bushnell BSG wrote:
> On Thu, 2006-11-23 at 20:46 +0100, David Weinehall wrote:
> > Well, let's hope people don't use any of the non-SuSv3 features of cat
> > in their shell scripts...
>
> Why? Who cares?
Well,
On Thu, Nov 23, 2006 at 09:48:31PM +0100, Florian Weimer wrote:
> * David Weinehall:
>
> > On Sun, Nov 19, 2006 at 07:13:22PM +0100, Andreas Metzler wrote:
> >> Michelle Konzack <[EMAIL PROTECTED]> wrote:
> >> [...]
> >> > ...and where is SuSv3 in
from bashisms.
You can use whatever bashisms you like when you're working
interactively, that won't hinder dash from executing shells on boot and
elsewhere. Using bashisms in scripts does however cause a problem.
Oh, and there *are* other suitable interactive shells than bash. tcsh,
ksh,
ing-things.
>
> It's easier to eyeball packages that explicitly announce "bash".
> Those could be put to a stress test through:
>
> /bin/dash
> /bin/posh
> ...
>
> If someone feels up to.
I don't really see the point. If the ma
comes down to bad software design on the automake side rather than bad
makefiles).
[snip]
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://www.acc.umu.se/~
il very recently (sometimes between Nov 19th
> and Nov 27h).
>
>
> Regards,
> Frederic
>
> [1] http://www.0d.be/debian/debian-gnome-2.16-status.html
Some entries seem to list newer Debian-versions than upstream
versions... Some watch-fil
up with the right
> search terms even when you supposedly know the right ones.
Wouldn't it be enough to have something like
"Dzongkha, a language spoken in Bhutan" in the long package description?
apt-cache search will pick that up.
regards: David
--
/) David Weinehall <
> >
> I see, you are absolutely right. Thank you for you explanation.
Just out of curiousity, any particular reason why you would want to use
XFree rather than Xorg?
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~~
want to fix certain bugs, you're really out on thin
ice. They might, however, disagree with your opinion that a certain
behaviour is a bug at all...
Regards: David Weinehall
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~
d hack which tries to compensate for a shortcoming
> in dpkg, one that I have been waiting to be fixed since I started
> using Debian nearly ten years ago. I begin to lose my hope.
Did you remember to submit a patch to the bugreport you filed?
Regards: David
--
/) David Weineh
> waste on small systems.
Well, most of those scripts can be fixed quite easily, some require
a bit more work. I hereby promise to help fixing them to the extent
of my capability.
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
//
On Fri, May 19, 2006 at 03:34:17PM +0200, Wouter Verhelst wrote:
> On Fri, May 19, 2006 at 05:45:46AM +0200, David Weinehall wrote:
> > Well, most of those scripts can be fixed quite easily, some require
> > a bit more work. I hereby promise to help fixing them to the extent
>
ures, such as its
> support for setuid files, or its support for postinst scripts that run
> arbitrary code at install time.
Well, if foo depends on foo-data, and foo-data depends on foo, I find
it really hard to see the point of splitting the two into distinctive
packages...
Regards: Dav
On Tue, Jul 25, 2006 at 11:42:39AM +0900, Miles Bader wrote:
> David Weinehall <[EMAIL PROTECTED]> writes:
> > Well, if foo depends on foo-data, and foo-data depends on foo, I find
> > it really hard to see the point of splitting the two into distinctive
> > packages...
On Tue, Jul 25, 2006 at 01:34:47PM +0200, Wouter Verhelst wrote:
> On Tue, Jul 25, 2006 at 04:39:24AM +0200, David Weinehall wrote:
> > On Mon, Jul 24, 2006 at 06:32:54PM -0400, Joey Hess wrote:
> > > Steve Greenland wrote:
> > > > This really seems like somet
ug reports over the next
> | few weeks, but doing this informally first may be simpler. Or maybe not.
>
> I'd like time, please.
Wouldn't we all? =P
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Northern lights wander (\
// Maintainer of the v2.0 ker
and similar, and *woosh* it was Architecture: all.
Skip the let, and *woosh*, it's even POSIX compliant shell script... =)
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Northern lights wander (\
// Maintainer of the v2.0 kernel // Dance across the winter sky //
\)
nto what it is for other OS's (that is, when Debian
reaches world-domination), the main-CD would only contain X-related stuff
+ games... Non really the ideal distribution, eh?!
/David Weinehall
_ _
// David Weinehall <[EMAIL PROTECTED]> /> Northern lights wander \\
// Project MCA Linux hacker// Dance across the winter sky //
\> http://www.acc.umu.se/~tao/
ng in xlib6g that mtools really needs, why not break it out of
xlib6g and make it a separate package?
Oh, and why does xlib6g depend on xfree86-common? Wouldn't it be more
natural the other way around only?
/David Weinehall
_ _
m
mtools and create an extra package with just this file, and make this file
recommended by mtools, and make mtools required by the extra-package.
/David Weinehall
_ _
// David Weinehall <[EMAIL PROTECTED]> /> Northern
we are free to distribute even a patched Pine, as long as we apply an
L at the end of the version#. Not too big a sacrifice, huh? We'll still
have to keep it in the non-free area, of course, as it's a BSD-style
license, but...
I&#x
On Wed, 29 Sep 1999, Thomas Schoepf wrote:
> On Tue, 28 Sep 1999, David Weinehall wrote:
>
> > Thus we are free to distribute even a patched Pine,
>
> No! Anyone is allowed to _locally_ modify Pine, but there's no statement
> about distributing such modified versio
e was upped; I'm
not taking any unnecessary risks...
/David
_ _
// David Weinehall <[EMAIL PROTECTED]> /> Northern lights wander \\
// Project MCA Linux hacker// Dance across the winter sky //
\> http://www.acc.umu.se/~tao/
;t
influence the possibility to edit the file in another program, however.
> - just curious: what other times do you need to change this file type?
The time is stored in the resource-fork on the Mac, and sometimes it gets
screwed (programs that can't transfer dual/multi
On Tue, Jun 03, 2003 at 05:10:24PM +1200, Corrin Lakeland wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Tue, 03 Jun 2003 13:59, Glenn McGrath wrote:
> > If we put the Packages file under some sort of version control (e.g.
> > cvs), bandwidth requirments would be minimised as cvs
f binutils/gcc/etc, it becomes less likely
that libc5 will work properly without serious tinkering).
Regards: David Weinehall
--
/> David Weinehall <[EMAIL PROTECTED]> /> Northern lights wander <\
// Maintainer of the v2.0 kernel // Dance across the winter sky //
\> http://www.acc.umu.se/~tao/
. Afaik it still has quite some
race conditions in the v2.4, and there are still things left that need
to be solved in a nice manner (just ask Alexander Viro...)
[snip]
Regards: David Weinehall
--
/) David Weinehall <[EMAIL PROTECTED]> /) Northern lights wander (\
// Maintainer of the
't fix the bug.
> > 3. bump the supported processor, and rename the port
> > 4. like 3, and also add an i386 distribution which does not support
> >C++ at all
> > 5. like 4, but support C++ in a way incompatible with other Linux
> >distributions in the
for 80386.
There is afaik. Not in widespread use though, and the Linux kernel
hasn't been ported to that hardware. I think we can safely ignore
this hardware without stepping on anyone's toes...
/David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Northern lights wander
thank you very much.
> >
> > Happily, the noninteractive debconf frontend exists.
>
> And getting hundreds of emails after a mass upgrade? No thanks.
man 5 procmailrc
Regards: David Weinehall
--
/) David Weinehall <[EMAIL PROTECTED]> /) Northern lights wander (\
ad continues to take place in L.A. because the
local authorities purchased their quotas (of course, L.A. might be a
bad example, because I know that they _are_ doing their best to reduce
pollution even though it's a tough struggle.)
Regards: David Weinehall
--
/) David Weinehall <[EMAIL PROTECTED]> /) Northern lights wander (\
// Maintainer of the v2.0 kernel // Dance across the winter sky //
\) http://www.acc.umu.se/~tao/(/ Full colour fire (/
also upgrading to wxgtk-python (2.3) or de-installing
> > wxgtk-python (2.2).
>
> Sure you can. dpkg --force-depends -i python_*.deb will do it for you.
>
> If you want something bad enough, and don't mind breaking things, anything's
> possible.
Please, don'
latter happen for the cover
for their album Animals. The pig escaped though, and made it a
beautiful story.
http://www.myputney.co.uk/wandsworth/community-batterseapowerstation.htm
http://www.floydianslip.com/discs/animals.htm
/David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Northern li
package. I am pretty sure the same
thing can be done here, though. And if its manual is licensed under the
GFDL, we'll simply have to make due without the manual, sad but true.
Or have the manual in non-free, whatever feels is most appropriate
(let's not start a discussion about removing
.
[snip]
Pah, let's require all maintainers to be able to fix all
translation-bugs on their own. It should be a requirement to be fluent
in all nuances of all languages to be a maintainer. Right? I mean, you
must be able to fix any bug in the package just because you NMU
a new tran
true debian package in non-free, to benefit truly of the debian tools.
Yes, some (a lot of) non-free, but gratis, software do not allow
redistribution, or imposes limits on the redistribution such that it
cannot be packaged even for non-free.
Regards: David Weinehall
--
/) David Weine
o don't pass up on the chance to
get it signed by someone just because they aren't DD's =)
Regards: David Weinehall
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://w
tart with our base system; hopefully
it's already correct, but you never know, and fixing such bugs as early
in the release cycle as possible is important. Also, branch packages
(for instance perl/php/python/apache/mysql) seems more important to
test at an early stage than leaf packages (ap
to
not actively fix your packages because other things have a higher
priority, but when someone else goes through the trouble of fixing
your packages and submit patches, I think rejecting the patches
is pretty unnecessary.
Having POSIX-clean scripts also ensures tha
ards: David Weinehall
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://www.acc.umu.se/~tao/(/ Beautiful hoar-frost (/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
rch has been orphaned upstream because of Tom Lord's announcement is
> roughly similar to saying that Linux has been orphaned because the 2.0
> kernel series is no longer maintained...
Oh, thanks for the news, I didn't know that.
[snip]
y signed, not built, by official
> Debian Developers.
I don't know about others, but I never sign and upload packages
built by others; I always rebuild packages when I sponsor someone.
I really hope others do the same.
Regards: David Weinehall
--
/) David Weinehall <[EMAIL
K-H is upstream for both udev and hotplug, I'd say
that's probably quite unlikely...
[snip]
Regards: David Weinehall
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://www.acc
r than perl. I don't know about
> zsh.
Well, writing scripts that use /bin/sh or perl means that the init
script will run without any dependencies on optional packages.
zsh is Priority: optional...
And while dash is also optional, all *correctly* written /bin/sh
scripts should work with dash t
e can be relaxed, imho.
Well, it's helpful when you might want to replace grep etc with
its busybox counterparts; for instance, busybox grep doesn't support
-o.
Regards: David Weinehall
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~~~
o the trick.
And until this is corrected, a lot of us won't enable default
installation of Recommendations, simply because our systems get
unnecessarily bloated.
Regards: David Weinehall
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~
On Sat, Aug 27, 2005 at 02:16:39PM -0700, Thomas Bushnell BSG wrote:
> David Weinehall <[EMAIL PROTECTED]> writes:
>
> > And while dash is also optional, all *correctly* written /bin/sh
> > scripts should work with dash too.
>
> That's incorrect. A correctly w
2350k 828642
2350k (+ 828642, I guess) != 8MB...
The 8MB you cite is for compressing, not decompressing.
[snip]
regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) htt
1 - 100 of 182 matches
Mail list logo
