Michael Biebl, le Tue 31 Jan 2012 07:54:24 +0100, a écrit :
I'd like to get rid of arch specific code in the init script and instead
move the pipe to /run/xconsole and create a symlink in /dev for
backwards compat with existing tools.
Would this work on hurd?
It should work.
(the
On Sun, Jan 29, 2012 at 11:31:58AM -, Justus Winter wrote:
1. File bugs for software that uses MAXPATHLEN and co, do so politely
and explain the issues. Talk directly to upstream and *do not*
mention the Hurd.
Without mentioning there is at least a system out there on which the
issue
Be careful not to upgrade to initscripts 2.88dsf-21 or 2.88dsf-22 is
you want to play safe. They can cause your filesystem to be heavily
trashed, at least it did for me (on two kvm instances, twice on one of
them!):
In an ssh window: (second time, first with -21!)
Preparing to replace sysvinit
Quoting Richard Braun (2012-01-31 09:59:58)
On Sun, Jan 29, 2012 at 11:31:58AM -, Justus Winter wrote:
1. File bugs for software that uses MAXPATHLEN and co, do so politely
and explain the issues. Talk directly to upstream and *do not*
mention the Hurd.
Without mentioning there is at
On Tue, Jan 31, 2012 at 01:06:02PM +0100, Svante Signell wrote:
Be careful not to upgrade to initscripts 2.88dsf-21 or 2.88dsf-22 is
you want to play safe. They can cause your filesystem to be heavily
trashed, at least it did for me (on two kvm instances, twice on one of
them!):
What's your
On Tue, 2012-01-31 at 13:29 +0100, Richard Braun wrote:
On Tue, Jan 31, 2012 at 01:06:02PM +0100, Svante Signell wrote:
Be careful not to upgrade to initscripts 2.88dsf-21 or 2.88dsf-22 is
you want to play safe. They can cause your filesystem to be heavily
trashed, at least it did for me
Hi,
(a proper subject would have helped a bit more...)
Alle martedì 31 gennaio 2012, Svante Signell ha scritto:
Be careful not to upgrade to initscripts 2.88dsf-21 or 2.88dsf-22
is you want to play safe.
In particular, any version of sysvinit = 2.88dsf-19 during the
migration from
Hi!
Another (small) one if some of you guys have time to review some code.
Cheers,
Tanguy
--- old/suckless-tools-38/dmenu/dmenu_path.c2012-01-31 13:02:23.226833682
+0100
+++ suckless-tools-38/dmenu/dmenu_path.c2012-01-31 14:01:10.282784329
+0100
@@ -46,7 +46,9 @@
void
On Tue, Jan 31, 2012 at 12:57 PM, Justus Winter
teyth...@jade-hamburg.de wrote:
Well, fixing fixed-sized buffer issues is a good exercise to improve
ones c skills, but I do not see how it helps anyone to get a foot into
the Hurd project if he fixed a bug in e.g. nautilus or tar.
A social foot
Hi Tanguy,
On Tue, Jan 31, 2012 at 2:13 PM, Tanguy LE CARROUR
tanguy.lecarr...@gmail.com wrote:
Another (small) one if some of you guys have time to review some code.
The patch looks good, you should submit it.
--
Jérémie Koenig j...@jk.fr.eu.org
http://jk.fr.eu.org/
--
To UNSUBSCRIBE,
Hi
2012/1/31 Jérémie Koenig j...@jk.fr.eu.org:
The patch looks good, you should submit it.
Thanks, I'll do that! question: first I submit it to this list as
draft and then what?
For instance, the memstat patch I sent few days ago hasn't been
commented for days... what is the next step?
Source: suckless-tools
Version: 38
Severity: important
Tags: patch
User: debian-hurd@lists.debian.org
Usertags: hurd
Hi,
This patch solves the build problems for GNU/Hurd due to PATH_MAX
issues. The solution is to make dynamic string allocations instead of
using fixed length buffers. The patch
12 matches
Mail list logo
