On Tue, 19 Aug 2014 21:49, pentako...@openmailbox.org said:
In the installation i have this message and fail :
gpg: WARNING: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
Well, read the FAQ - although I am not sure that our new FAQ still has
an
On Sat, 13 Nov 2010 21:38, r...@debian.org said:
Yeah, that is a problem. Last weekend I tried to port it but I have a
lack of understanding how the Debian packages are supposed to work
together; in particular the kernel headers and the various system
libraries like libgeom etc.
For that
On Sat, 13 Nov 2010 14:58, r...@debian.org said:
I disagree. This puts an additional burden on the user. Adding SUID
I can't see why encrypting the swap puts an additional burden on the
user or on the machine. If you need to swap/page something you are in
either of these situations:
- The
On Thu, 5 Aug 2010 12:30, a...@debian.org said:
This is worse. It's even locally and I either never noticed that
because I use kfreebsd remotely most time (despite having that screen
on my desk) or it's an regression.
Emacs 22 works fine though.
I had the same problem for a long time. Now
On Mon, 10 May 2010 01:50, anar...@koumbit.org said:
Ah! I didn't see those packages, they're not part of the official
archive!
Maybe not anymore - I didn't checked.
PS: it seems you were able to compile PPP with a lot more features than
I did. Did you patch the source or did it
On Sun, 9 May 2010 00:27, anar...@koumbit.org said:
That I just don't understand at all... Are you using userland PPP? From
what I can tell here, there's no ppp binary bundled with any kFreeBSD
package I know of, I don't see how creating the lock directory changes
I am using this:
On Sun, 21 Mar 2010 20:22, anar...@koumbit.org said:
Could you clarify this? Are you saying I duplicated existing work and
that you already had userland ppp working? Is it with upstream's
usr.sbin/ppp?
Yeah, I have userland ppp working as a client. It was a mere
mkdir /var/spool/lock
How
On Sun, 21 Mar 2010 01:28, anar...@koumbit.org said:
As far as I know, there's currently no possibility of doing PPP or PPPoE
in Debian GNU/kFreeBSD. I'd like to see that fixed.
I am using PPP for quite some time now with my UMTS stick. The gotcha
is that the lock directory is a different one
On Mon, 1 Mar 2010 18:53, t...@mirbsd.de said:
with a bunch of GNU packages. The FSF likes to do Vendor lock-in,
That is somewhat unfair. For one you can't speak of vendor lock-in in a
FS project, second and more important is that glibc is the core of GNU
(the OS) and third glibc is very much
Hi!
I prepared a patch against the Debian source to include devd and
acpiconf. I am not a DD and thus I have no experience creating
packages; in particular the conf files are missing. What needs to be
included are these files:
/etc/devd.conf
/etc/devd/asus.conf
/etc/rc.suspend
On Thu, 17 Dec 2009 12:23:23 +0100, Robert Millan wrote:
Just a quick tip: you don't need to include all upstream files in your
patch, as those end up in the orig tarball. Modifiing the get-orig-source
routine in debian/rules should be enough.
Okay. I have not looked to closely at the rules
On Tue, 15 Dec 2009 23:10:07 +0100, Aurelien Jarno wrote:
As far as I know, no one is working on that. Ideally this should be
integrated to the freebsd-utils source package (possibly producing new
binary packages), but this is probably a detail, the most important job
being to port it to
Hi!
I worked on devd and now I am able run the rc.suspend and rc.resume
scripts on my X31. To make that really useful I also ported acpiconf.
I added new functions pidfile_* to libbsd and would like to know how
to proceed: Create a Debian patch or talk to upstream and get it into
their repo
On Wed, 16 Dec 2009 16:09:19 +0100, Guillem Jover wrote:
I was in the process to release a new upstream release for libbsd, and
can include those functions. I'll then proceed with an upload to
Debian.
Find below a patch against the debian source.
* debian/control (Description):
Hi!
Looking at the freebsd kernel event system I obviously came across the
devd. Are there any plans to include it or is the plan to port the
Linux udev system to kfreebsd?
Looking at devd.conf and its usage I have to say that I really like
it; in contrast to udev (or whatever the current
--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
/* chvt.c - change virtual terminal for [k]freebsd
Copyright (C) 2009 Werner Koch
This file is free software; as a special exception the author gives
unlimited permission to copy and/or distribute it, with or without
16 matches
Mail list logo
