I submitted a patch for the bug #221988. Does anyone know when it
will be considered? If this bug could be fixed in the Sarge release
(I don't know if this is possible), this would really be fine.
Thanks,
--
Vincent Lefèvre [EMAIL PROTECTED] - Web: http://www.vinc17.org/
100% accessible
, the text look smaller, but sometimes a line is clearly
missing (for instance, when this is the top line). There had been
a discussion in French here:
From: Vincent Lefevre [EMAIL PROTECTED]
Newsgroups: fr.comp.infosystemes.www.navigateurs
Subject: Re: IE et le png
Date: Fri
On 2009-05-09 22:20:47 -0700, Steve Langasek wrote:
According to popcon, only about 68% of Debian users have exim4
installed, and 18% have postfix installed. I don't think that's much
of a lead for exim4, considering most of the exim4 installs are
probably due solely to its status as a
On 2009-07-24 15:49:15 +, brian m. carlson wrote:
On Fri, Jul 24, 2009 at 08:31:55AM -0700, Russ Allbery wrote:
zsh has also historically been fairly buggy in corner cases as
/bin/sh and requires explicit commands to make it
Bourne-compatible. Autoconf has had to add a bunch of
On 2009-07-25 09:53:06 +0200, Steve Langasek wrote:
On Fri, Jul 24, 2009 at 10:38:51AM -0500, Manoj Srivastava wrote:
On Fri, Jul 24 2009, Steve Langasek wrote:
What's the advantage of having it be zsh? Is zsh faster than
dash? Or is the only savings the elimination of the 84k dash
I'm not the bug reporter, but...
On 2009-01-11 20:21:59 +, Roger Leigh wrote:
% dpkg -S /usr/bin/basename
coreutils: /usr/bin/basename
This may be a bit more complex when the file is a symlink to an
alternative. Concerning the man pages, packages sometimes install
symlinks, and it isn't
Hi,
The .desktop file distributed with the evince package
(/usr/share/applications/evince.desktop) contains:
Exec=evince %U
meaning that the user's $PATH is taken into account. In general,
taking $PATH into account is recommended, but IMHO, this should
not be the case here, because of the
On 2008-07-09 14:46:22 +0200, Vincent Zweije wrote:
On Wed, Jul 09, 2008 at 01:14:25PM +0200, Vincent Lefevre wrote:
|| The .desktop file distributed with the evince package
|| (/usr/share/applications/evince.desktop) contains:
||
||Exec=evince %U
||
|| meaning that the user's $PATH
According to
http://packages.qa.debian.org/t/tar.html
tar 1.20-1 entered unstable on 2008-04-17, so several months before the
freeze. And http://release.debian.org/migration/testing.pl?package=tar
gives no good reasons for which tar is not in testing yet:
* trying to update tar from 1.19-3
On 2011-02-04 19:02:33 +0100, Tollef Fog Heen wrote:
]] Yaroslav Halchenko
| /usr/lib64 - /usr/lib
Not really, apart from some broken software that will look for stuff
there and be confused if it doesn't exist. I think we should drop it.
Thanks would be a good thing. Otherwise users
On 2011-02-11 21:46:29 +0900, Norbert Preining wrote:
On Fr, 11 Feb 2011, Roger Leigh wrote:
XeTeX and XeLaTeX allow native UTF-8 input. Should be made the
default, IMO, given how obsolete and broken the standard TeX
encodings are. Being able to write in actual text rather than
Please
On 2011-02-11 15:33:49 +0500, Andrey Rahmatullin wrote:
On Fri, Feb 11, 2011 at 11:14:42AM +0100, Miroslav Kure wrote:
However, I'm curious: is there a lot of software that is broken with
Unicode, particularly with the UTF-8 encoding? I can't remember anything
much in recent times.
On 2011-02-11 15:02:02 +0100, Adam Borowski wrote:
On Fri, Feb 11, 2011 at 02:30:24PM +0100, Vincent Lefevre wrote:
On 2011-02-11 15:33:49 +0500, Andrey Rahmatullin wrote:
On Fri, Feb 11, 2011 at 11:14:42AM +0100, Miroslav Kure wrote:
However, I'm curious: is there a lot of software
On 2011-02-12 17:44:27 -0800, Steve Langasek wrote:
How do we square that with the FHS, then? The FHS says:
If directories /libqual or /usr/libqual exist, the equivalent
directories must also exist in /usr/local.
That seems to require /usr/local/lib64 even if we *don't* include
On 2011-02-14 16:43:11 +, Ian Jackson wrote:
When LC_CTYPE=en_GB.utf-8, programs which attempt to print unicode
characters to stdout should use UTF-8. That's what LC_TYPE means.
So, cat, grep, etc. are all broken. :)
--
Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/
On 2011-02-14 13:11:04 -0800, Russ Allbery wrote:
Perl is specifically documented to not do this for backward compatibility
reasons. In Perl, which is the one I know best, you are required to
decode input and encode output if you want to have UTF-8 handling.
Or better, use the -C option.
On 2011-02-16 01:34:51 +0100, Adam Borowski wrote:
On Wed, Feb 16, 2011 at 01:01:07AM +0100, Vincent Lefevre wrote:
On 2011-02-14 16:43:11 +, Ian Jackson wrote:
When LC_CTYPE=en_GB.utf-8, programs which attempt to print unicode
characters to stdout should use UTF-8. That's what
On 2011-03-25 01:15:54 +0100, Vincent Lefevre wrote:
It is your responsibility to set an appropriate time limit for
guessnet.
This doesn't solve the problem: it makes the boot longer. By
longer and unreliable. The 4-second maximum delay is still not
sufficient. So, to have some margin, I
reassign 619520 ethtool
severity 619520 normal
thanks
On 2011-03-25 09:18:04 +, Debian Bug Tracking System wrote:
Processing commands for cont...@bugs.debian.org:
reassign 619520 guessnet
Bug #619520 [general] eth0 is not activated early enough, causing a delay in
the Ethernet
On 2011-04-04 17:31:18 +0400, Stanislav Maslovski wrote:
On Mon, Apr 04, 2011 at 05:35:10PM +0530, Josselin Mouette wrote:
It seems to be a common belief between some developers that users should
have to read dozens of pages of documentation before attempting to do
anything.
I’m happy
Hi,
On 2011-04-05 20:37:39 +0300, Andrew O. Shadoura wrote:
Hello,
On Tue, 5 Apr 2011 14:31:40 +0200
Vincent Lefevre vinc...@vinc17.net wrote:
[About the general problem of documentation]
The problem is to find the correct tools and the correct
documentation. For instance, imagine
On 2011-04-06 11:22:07 +0100, Simon McVittie wrote:
Not everything in /etc/shells is POSIXy enough to be /bin/sh. The
*csh family aren't Bourne shells, and while zsh is a very nice
Bourne-ish interactive shell, in its default configuration it isn't
POSIX-compliant.
When invoked as sh, zsh
On 2011-04-06 07:24:30 +0200, Josselin Mouette wrote:
There are several hacks to do that (like guessnet or laptop-net), but I
don’t think this can work correctly in the general case with IPv4.
FYI, I had used laptop-net in the past, but it has been removed
from Debian:
On 2011-04-06 18:26:45 +0300, Andrew O. Shadoura wrote:
If you do `ifdown`, either manually or by unplugging the cable, the
problem doesn't appear to exist. Calling ifupdown may be inserted into
the suspend/resume scripts.
I wonder why this isn't done by default.
--
Vincent Lefèvre
Bug #302907 in libstroke0-dev has been open and had a (working) patch
for 6 years. The maintainer has never replied or done anything else
concerning this bug.
Could this bug be eventually fixed?
--
Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/
100% accessible validated
On 2011-05-27 00:17:45 +0200, Michael Biebl wrote:
Am 26.05.2011 23:26, schrieb Luk Claes:
There are some good reasons to keep some specific *.la files around,
Just curious: what are these reasons / use case for keeping la files?
They are at least read by libtool. For instance, when
On 2011-05-30 12:16:13 +0100, Simon McVittie wrote:
libtool .la files are useful if:
* you're linking against a library installed in a directory that isn't
searched by the dynamic linker by default (e.g. installing a local
library in --prefix=$HOME, and a program that links that library
On 2009-12-28 14:34:39 +1100, Brian May wrote:
Also, FQDNs are really not applicable to, say laptops, which
frequently change from one network to another. Or some desktops
even. I notice on this Ubuntu laptop `hostname` == `hostname -f`
perhaps for this reason.
FQDNs are also applicable to
On 2009-12-27 14:22:53 -0800, Steve Langasek wrote:
No, the hostname should be set on a *separate* line, mapped to 127.0.1.1,
as we've been doing for years now. Setting an equivalence between localhost
and the hostname causes all manner of problems due to hostname
canonicalization.
Shouldn't
On 2009-12-28 12:52:12 -0800, Steve Langasek wrote:
That would seem to fit with the rest of the page. I guess a bug
report is in order?
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562890
--
Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/
100% accessible validated (X)HTML
On 2009-12-28 23:41:38 +, Sam Morris wrote:
Details in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=316099. I
do wonder, however, why the system hostname has to appear in /etc/hosts
at all? Programs that want to find it out can read /etc/hostname
directly, after all. And wtf is
On 2009-12-29 00:21:45 +, Sam Morris wrote:
On Tue, 29 Dec 2009 01:03:12 +0100, Vincent Lefevre wrote:
Programs may need the FQDN, even without any network connection (for
instance, even local mail messages should have a Message-Id). And
/etc/hostname doesn't necessarily contain
On 2009-12-29 01:47:40 +0100, Vincent Lefevre wrote:
On 2009-12-29 00:21:45 +, Sam Morris wrote:
As for mail, we already appear to have an /etc/mailname file for MTAs and
MUAs to use for finding out the 'canonical' name of the host for message-
IDs and the like.
/etc/mailname
On 2009-12-28 20:56:03 -0800, Steve Langasek wrote:
On Tue, Dec 29, 2009 at 01:47:40AM +0100, Vincent Lefevre wrote:
As for mail, we already appear to have an /etc/mailname file for MTAs and
MUAs to use for finding out the 'canonical' name of the host for message-
IDs and the like
On 2009-12-29 14:09:49 +0100, Jeremiah Foster wrote:
On one of my machines apticron uses a call to hostname -f, which
fails, while uname -n succeeds.
uname -n doesn't necessarily return the FQDN.
xvii% uname -n
xvii
xvii% hostname
xvii
xvii% hostname -f
xvii.vinc17.org
xvii% cat /etc/hostname
On 2009-12-29 18:49:00 +0100, Gabor Gombas wrote:
On Tue, Dec 29, 2009 at 02:52:44PM +0100, Vincent Lefevre wrote:
When the machine is correctly configured (i.e. really has a FQDN),
hostname -f is reliable.
No, it is not. hostname -f can return one value only, while a host may
have dozens
On 2009-12-29 17:44:31 +0100, Milan P. Stanic wrote:
Mutt in testing/unstable use /etc/mailname.
But not the official Mutt version.
--
Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/
100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/
Work: CR INRIA -
On 2009-12-29 10:45:17 -0800, Russ Allbery wrote:
Vincent Lefevre vinc...@vinc17.org writes:
Even if Debian has its own patches to match its policy, end users are
still allowed to compile software from upstream (this is what I do for
Mutt, because I have my own patches), and they expect
On 2009-12-29 14:18:47 -0800, Russ Allbery wrote:
Vincent Lefevre vinc...@vinc17.org writes:
When I compile Mutt or any other portable software (e.g. conforming to
POSIX), I don't mind if such software isn't integrated with the Debian
system. I just want it work according to the POSIX spec
On 2009-12-29 20:23:31 -0800, Russ Allbery wrote:
I'm having a hard time figuring out what you think the canonical name of
my laptop could possibly be, given that it has no static IP address and no
DNS entry.
It doesn't need to have a static IP, nor a DNS entry.
In practice, it's whatever
On 2009-12-30 11:56:13 +0100, Gabor Gombas wrote:
On Tue, Dec 29, 2009 at 10:31:25PM +0100, Vincent Lefevre wrote:
Then you need to configure your machine according to the spec, i.e.
you need a single FQDN / canonical name / official name of the host.
If getaddrinfo(AI_CANONNAME) fails
On 2009-12-30 15:31:12 -0200, Henrique de Moraes Holschuh wrote:
On Tue, 29 Dec 2009, Vincent Lefevre wrote:
On 2009-12-29 17:44:31 +0100, Milan P. Stanic wrote:
Mutt in testing/unstable use /etc/mailname.
But not the official Mutt version.
Who lets you configure the correct domain
On 2009-12-30 11:54:57 -0800, Russ Allbery wrote:
Vincent Lefevre vinc...@vinc17.org writes:
stanford.edu is definitely wrong. First it's just a domain name, not a
FQDN (as required by the mailname(5) man page).
stanford.edu is an RFC 1035 FQDN.
RFC 1035 (from /usr/share/doc/RFC/links
On 2009-12-30 15:33:05 -0200, Henrique de Moraes Holschuh wrote:
Better correct myself here. POSIX provides a way for apps to query the
canonical host name, but DOES NOT REQUIRE IT TO BE A FQDN.
So, it provided the notion of a special name, the canonical host name.
In practice, it has to
On 2009-12-31 14:10:46 +0100, Mike Hommey wrote:
On Thu, Dec 31, 2009 at 02:02:36PM +0100, Vincent Lefevre wrote:
POSIX says:
If the AI_CANONNAME flag is specified and the nodename argument is
not null, the function shall attempt to determine the canonical name
corresponding
On 2009-12-31 16:35:58 +0100, Iustin Pop wrote:
This is a personal opinion, but having the canonical name rely on
“hostname --fqdn” is not a favorite of mine: hostname needs the resolver
to be working and functioning (e.g. it talks to your nameservers if
/etc/hosts doesn't contain your
On 2009-12-31 12:37:25 -0800, Russ Allbery wrote:
Vincent Lefevre vinc...@vinc17.org writes:
On 2009-12-30 11:54:57 -0800, Russ Allbery wrote:
Vincent Lefevre vinc...@vinc17.org writes:
stanford.edu is definitely wrong. First it's just a domain name, not a
FQDN (as required
On 2009-12-31 14:34:34 -0800, Russ Allbery wrote:
Uh, no. That statement implies nothing of the sort; identification is not
necessarily unique.
I suggest that you look in a dictionary.
I've been participating in standardization of network protocols through
the IETF for more than a decade
On 2010-02-27 21:03:04 +0100, Josselin Mouette wrote:
We are talking of programs that you will not have the idea to run with
the command line unless you know what they do. Programs that are usually
run through a graphical menu.
They are sometimes found by shell completion. Moreover, before
On 2010-03-04 17:12:15 +0100, Bill Allombert wrote:
On Thu, Mar 04, 2010 at 04:32:45PM +0100, Josselin Mouette wrote:
Because, of course, the user is too stupid to click the “Help” menu
inside the application.
Because the users have not yet decided if they want to start the application
On 2010-03-05 17:41:25 +, brian m. carlson wrote:
Allowing any format viewable in Debian potentially requires the
average user to install lots of random packages just to view basic
documentation on invoking a program. Also, providing, for example, PDF
documentation as the sole form for a
On 2010-03-05 11:04:48 +0100, Josselin Mouette wrote:
Command-line switches are documented where you expect them to be
documented: in command-line switches, with the standard --help option.
This is nonsense. Not all commands understand --help.
--
Vincent Lefèvre vinc...@vinc17.net - Web:
On 2010-03-05 10:56:21 +0100, Daniel Leidert wrote:
Of course it does not happen, that evolution crashes for specific
mails and then keeps crashing on every new start, because it opens the
same mail. The only way to fix this, is to start with a different
component. Do you need the bug report
On 2010-03-10 13:52:15 +0100, Wouter Verhelst wrote:
Or it might have a gzipped PDF file, which is even more annoying,
for it requires me to copy, uncompress, read, remove the
documentation.
zxpdf from xpdf-reader can handle it. But I wonder why the need for
two separate commands while the
On 2010-04-19 18:05:30 -0500, Gunnar Wolf wrote:
The reasons not to want a document printed are quite easy to
understand, but the mechanism is flawed. Given the setting you
mention, you can just slap a red banner stating Confidential, do not
print. If it is on a corporate setting, just state
On 2010-05-26 00:18:23 +0200, David Weinehall wrote:
You're getting things the wrong way around. The version of dash that
will be put in experimental will be the correct one, the one in unstable
will be the crippled one. The reason things fails isn't because of
dash, but because of sloppy
On 2010-07-12 19:33:15 +0100, Julien Cristau wrote:
We don't have nvidia hardware, so maybe our perception is flawed. If
people think we should keep that driver, please explain why. If the
reason is nouveau doesn't work for me, we'll ignore your reply unless
it comes with a
On 2010-08-28 20:54:42 +1000, Brian May wrote:
When the solution is easy I don't see why we don't just do it.
br...@andean:~$ i=cat's meow.tar.gz
br...@andean:~$ echo `basename $i .tar.gz`
cat's meow
(yes, the nested quotes don't seem to matter)
They matter if you have consecutive
Hi,
On 2011-06-27 11:54:53 +0100, Steve Langasek wrote:
Work is ongoing to formulate a proper, distribution-neutral interface for
querying the correct multiarch path for a system. In the meantime, if you
are an upstream affected by this issue, or a maintainer of a package whose
upstream is
On 2011-06-27 15:42:47 +0100, Steve Langasek wrote:
On Mon, Jun 27, 2011 at 03:31:24PM +0200, Vincent Lefevre wrote:
How libraries are searched is not clear, but depending on how this
is done, there may be compatibility issues when the user installs
software in his home directory, in case
On 2011-06-27 15:59:27 +0100, Simon McVittie wrote:
If by fat binaries you mean executables,
No, I meant libraries (the term fat binary is used by the GMP library,
but is here restricted to x86 subarchs).
If by fat binaries you mean shared libraries, they could either go in
/usr/lib, or go in
On 2011-06-28 09:54:34 +0100, Steve Langasek wrote:
On Tue, Jun 28, 2011 at 02:05:05AM +0200, Vincent Lefevre wrote:
http://gcc.gnu.org/ml/gcc-help/2010-11/msg00341.html
This particular issue will not occur with multiarch, because
/usr/lib/arch will never be a symlink to /usr/lib
On 2011-06-28 10:34:14 +0100, Steve Langasek wrote:
On Tue, Jun 28, 2011 at 07:40:03AM +0200, Hendrik Sattler wrote:
Am Montag, 27. Juni 2011, 16:20:23 schrieb Steve Langasek:
So this:
So it should be a matter of changing that to print this instead on
Debian
multiarch: $ gcc
On 2011-08-15 23:29:17 -0400, James Vega wrote:
You mean like lesspipe(1)? Seems like it might need to be updated to
handle *.xz, but other than that looks like it fits the bill.
lesspipe(1) from the less package is a bit primitive. How about using
Wolfgang Friebel's version, which already
Hi,
On 2012-03-02 05:11:58 +, Ben Hutchings wrote:
I'm therefore intending to warn about this with the following NEWS
entry in the linux-image metapackages:
Index: debian/linux-image.NEWS
===
--- debian/linux-image.NEWS
On 2012-03-05 16:42:50 +0100, Reinhard Tartler wrote:
Friendly discussion with the maintainer of debian-multimedia.org to
not replace libraries such as libavcodec and friends have failed
ultimatively (BTW, that is part of the reason why we've ended up with
an epoch of '4', dmo uses epoch '5');
On 2012-03-08 12:35:53 +, Philipp Kern wrote:
On 2012-03-08, Vincent Lefevre vinc...@vinc17.net wrote:
It's worse than that. Security support is non-existent, and users
don't know that. An example: [… non-free package …]
Well, non-free in Debian proper doesn't have security support
On 2012-03-08 15:42:49 +, Ben Hutchings wrote:
Since 'at' is going to be updated in stable, I added a versioned
'Breaks' instead.
But since there may be other problems than with at, announcing
the change in the NEWS file would have probably be a good idea.
Things that an admin was usually
On 2012-03-18 00:53:37 +0800, Thomas Goirand wrote:
disclaimerI know almost nothing about systemd/disclaimer
I'd like people to think twice before opt-in for systemd. I just
taked with a friend working for redhat, and he told me how much
he hates it. He told me that if *anything* goes wrong
On 2012-03-29 02:43:33 +0200, Carlos Alberto Lopez Perez wrote:
$ sudo apt-get remove network-manager*
$ sudo apt-get install wicd wicd-curses wicd-gtk
^ wicd-kde ?
$ wicd-curses
And enjoy your network without the NM mess :)
Well, wicd has its own
On 2012-03-29 11:15:30 +0100, Philip Hands wrote:
I'd only use either to make flipping between wireless networks something
where I don't need to keep the comandline incantations in my head
anyway, so the last thing I need is NM noticing that I've plugged or
unplugged an ethernet cable, and
On 2012-03-29 13:07:56 -0700, Russ Allbery wrote:
Well, it seems like you should file bugs if you can, because a lot of
these are not universal problems and therefore probably aren't known
issues.
I did several months ago:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637267
On 2012-03-29 23:23:52 -0400, Chris Knadle wrote:
On Thursday, March 29, 2012 04:09:57, Vincent Lefevre wrote:
Well, wicd has its own bugs, such as preventing a laptop from
suspending.
Hmm. That sucks. I'd like to debug why you're running into this. However
I've been using wicd
On 2012-03-30 08:39:38 +0200, Salvo Tomaselli wrote:
Well, wicd has its own bugs, such as preventing a laptop from
suspending.
are you talking about a bug from 2008 that has been fixed for ages?
https://bugs.launchpad.net/wicd/+bug/306210
No, this is not the same bug (in my case, wicd is
On 2012-03-30 19:43:48 +0200, Carlos Alberto Lopez Perez wrote:
On 30/03/12 12:29, Vincent Lefevre wrote:
I don't know what's going on exactly, but from the logs, it seems
that when suspending, the connection is ended (as expected), but
then, wicd tries to reconnect, and this may interrupt
On 2012-03-30 10:44:07 -0700, Russ Allbery wrote:
Vincent Lefevre vinc...@vinc17.net writes:
On 2012-03-29 13:07:56 -0700, Russ Allbery wrote:
Well, it seems like you should file bugs if you can, because a lot of
these are not universal problems and therefore probably aren't known
On 2012-03-31 01:16:42 +0200, Vincent Lefevre wrote:
On 2012-03-30 10:44:07 -0700, Russ Allbery wrote:
I don't think your diagnosis of this is correct, in that I don't think
wicd is what's doing this. I was getting things like that with Network
Manager as well, and usually rebooting my
On 2012-03-31 05:42:41 +0200, Carlos Alberto Lopez Perez wrote:
On 31/03/12 01:03, Vincent Lefevre wrote:
On 2012-03-30 19:43:48 +0200, Carlos Alberto Lopez Perez wrote:
Check that you don't have GLAN/WLAN or something like that enabled on
/proc/acpi/wakeup
xvii:~ cat /proc/acpi/wakeup
On 2012-05-01 18:55:20 +0300, Riku Voipio wrote:
On Tue, May 01, 2012 at 12:48:10AM -0400, Chris Knadle wrote:
I think it would be useful to describe what issue(s) there are concerning
8BITMIME and why this is important. I've found some information [1] about
this, but it isn't clear what
On 2012-05-02 15:00:36 +0200, Andrew Shadura wrote:
Hello,
On Wed, 2 May 2012 10:06:31 +0100
Jon Dowland j...@debian.org wrote:
On Wed, May 02, 2012 at 08:44:12AM +0200, Andrew Shadura wrote:
No it doesn't if 8BITMIME annouces are turned off!
If exim receives an 8 bit mail, even if
On 2012-05-02 20:23:41 -0400, Scott Kitterman wrote:
Vincent Lefevre vinc...@vinc17.net wrote:
On 2012-05-02 15:00:36 +0200, Andrew Shadura wrote:
Hello,
On Wed, 2 May 2012 10:06:31 +0100
Jon Dowland j...@debian.org wrote:
On Wed, May 02, 2012 at 08:44:12AM +0200, Andrew Shadura
On 2012-05-25 14:49:14 +0100, Will Daniels wrote:
On 25/05/12 13:52, Ted Ts'o wrote:
So what? If you write to a normal file system, it goes into the page
cache, which is pretty much the same as writing into tmpfs. In both
cases if you have swap configured, the data will get pushed to disk;
On 2012-05-30 12:08:29 +0200, Josselin Mouette wrote:
Le samedi 26 mai 2012 à 23:02 +0200, Carlos Alberto Lopez Perez a
écrit :
With tmpfs on /tmp you are breaking many applications that assume that
they have enough space to write on /tmp like the flash player ( see
Debian bug #666096 )
On 2012-06-03 08:21:34 +0200, Bernhard R. Link wrote:
Try to see it from the other side: I don't understand why you would a
like a service not started by default. The daemon is there to be run,
so running it is the most sensible approach in almost all cases[1].
Well, a mail server daemon must
On 2012-07-14 22:59:35 +0200, Tollef Fog Heen wrote:
Due to those drawbacks, I've wondered why people don't just disable
NetworkManager on their system instead of bothering with workarounds
like the above or dpkg -P --force-depends and similar.
Sorry for being late in the discussion. I also
On 2012-07-18 15:01:43 +0200, Adam Borowski wrote:
On Wed, Jul 18, 2012 at 02:18:12PM +0200, Vincent Lefevre wrote:
Sorry for being late in the discussion. I also think that having
NetworkManager disabled for those who do not want to use it is
a good solution. But I think that if other
On 2012-07-18 21:32:31 +0100, Wookey wrote:
+++ Andrei POPESCU [2012-07-18 20:56 +0300]:
One of the reasons I'm using network-manager instead of wicd or even
plain ifupdown is the possibility to switch (more or less) seamlessly
between wired and wifi.
wicd does this just fine too. Tell
On 2012-07-22 11:43:14 +0200, Wouter Verhelst wrote:
ENABLE/DISABLE switches are *ugly*,
I disagree. ENABLE/DISABLE switches have some advantages: they are
more readable than a set of symlinks, allow all the settings of some
service to be grouped in a single place, and can be managed more
easily
On 2012-07-22 14:11:41 +0100, Roger Leigh wrote:
On Sun, Jul 22, 2012 at 01:50:58PM +0200, Vincent Lefevre wrote:
I disagree. ENABLE/DISABLE switches have some advantages: they are
more readable than a set of symlinks, allow all the settings of some
service to be grouped in a single place
Hi Michael,
On 2012-07-22 16:25:15 +0200, Michael Stapelberg wrote:
Quoting Vincent Lefevre (2012-07-22 15:53:13)
I don't think there's anything wrong with enhancing the way that
sysvinit works, as long as the user can still use the update-rc.d
method.
There is: update-rc.d is a defined
On 2012-07-22 16:40:48 +0200, Wouter Verhelst wrote:
On Sun, Jul 22, 2012 at 01:50:58PM +0200, Vincent Lefevre wrote:
On 2012-07-22 11:43:14 +0200, Wouter Verhelst wrote:
ENABLE/DISABLE switches are *ugly*,
I disagree. ENABLE/DISABLE switches have some advantages: they are
more
On 2012-07-23 14:49:35 +0900, Miles Bader wrote:
Based on a glance at the source, it seems like the math libraries were
changed in lots of little ways between 2.13 and 2.16 [and it looks
like the FPU-twiddling that made expf slow in 2.13 has been _added_ to
the generic version of the exp
On 2012-07-23 10:21:04 +0200, Tollef Fog Heen wrote:
]] Vincent Lefevre
OK, if Debian plans to support other init systems, that's fine.
It already does.
Not really, or at least not in a nice way, because sysvinit is
an essential package. Also, I don't see any init system that
provides
On 2012-07-23 07:23:40 -0300, Henrique de Moraes Holschuh wrote:
On Mon, 23 Jul 2012, Vincent Lefevre wrote:
so that if you want to make things more consistent, you should
get rid of /etc/default entirely.
/etc/default is used for a lot more than just enabling/disabling services
On 2012-07-23 15:26:29 +0200, Vincent Lefevre wrote:
No, I just mean that configuration of some service should be
in a limited number of places. But if you agree that it's fine
for /etc/default to override config setup somewhere else, then
there should not be any problem with ENABLE/DISABLE
On 2012-07-23 15:55:27 +0200, Tollef Fog Heen wrote:
]] Vincent Lefevre
On 2012-07-23 10:21:04 +0200, Tollef Fog Heen wrote:
]] Vincent Lefevre
OK, if Debian plans to support other init systems, that's fine.
It already does.
Not really, or at least not in a nice way
On 2012-07-23 17:59:21 +0100, Roger Leigh wrote:
On Mon, Jul 23, 2012 at 03:26:29PM +0200, Vincent Lefevre wrote:
No, I just mean that configuration of some service should be
in a limited number of places. But if you agree that it's fine
for /etc/default to override config setup somewhere
On 2012-07-24 13:45:08 +0900, Miles Bader wrote:
Vincent Lefevre vinc...@vinc17.net writes:
By correct, I mean that the result is somewhat acceptable (not
that the result is correctly rounded and the rounding direction is
honored), instead of getting completely wrong values or even
On 2012-07-24 08:16:43 +0200, Tollef Fog Heen wrote:
]] Vincent Lefevre
On 2012-07-23 15:55:27 +0200, Tollef Fog Heen wrote:
]] Vincent Lefevre
On 2012-07-23 10:21:04 +0200, Tollef Fog Heen wrote:
]] Vincent Lefevre
OK, if Debian plans to support other init
On 2012-07-24 12:26:33 +0200, Tollef Fog Heen wrote:
If the package description had said that, it would have been
less confusing. It's strange for a package description to focus
on non-native features!
I don't know what you mean by non-native features. Support for SysV
init scripts is
1 - 100 of 396 matches
Mail list logo
