Hello Debian kFreeBSD folks,
We'll publish a FreeBSD quarterly update in early October for work in
July-September, and I'd be very happy to have a Debian kFreeBSD entry
in there. Please reply to me if you're willing to put one together.
-Ed
-- Forwarded message --
Dear FreeBSD C
On 30 June 2015 at 17:17, Steven Chamberlain wrote:
> Hi!
>
> So I think we may want to build kfreebsd-10 using clang-3.6, to keep
> consistency with kfreebsd-11, and so that we rely on fewer clang
> releases to be maintained simultaneously in Debian.
Note that upstream FreeBSD 11 will soon switc
On 11 May 2015 at 14:37, Steven Chamberlain wrote:
>
> We were actually able to build our package of the FreeBSD kernel on
> GNU/Linux, and the binary would match what we built on GNU/kFreeBSD.
> (Which I think is the ultimate in securing against attacks on the
> build/development systems).
Ideal
On 30 September 2014 16:35, Steven Chamberlain wrote:
>
> We need to communicate better the state of kfreebsd and advancements
> since wheezy; we haven't done a 'bits' email in a long time. It is
> probably in much better state than most people realise.
I'd love see a kFreeBSD submission in the
On 20 August 2014 15:56, Steven Chamberlain wrote:
> Hi,
>
> I've tested for this vt(4) issue in upstream's own kernel build from:
> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/10.0-STABLE
> and it is affected as well. It is only a problem when using Qemu with
> the "-enable-kvm" option (an
On 20 August 2014 09:38, Steven Chamberlain wrote:
>
> Is there someplace to get 'official' upstream 10-STABLE kernels? Mine
> are built with Debian's usual config and packaging, and Clang 3.4. Thanks!
You can grab a snapshot build from:
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/10.0-ST
> On 22/07/14 19:58, Jan Henke wrote:
>> I am experiencing a strange problem with the current kFreeBSD weekly
>> image. Whenever the system is writing to the screen in text mode (e.g.
>> directly after selecting one entry in GRUB: "Copyright") you can
>> literally watch every single character p
On 12 February 2014 09:05, Robert Millan wrote:
> There's a small glitch during VT switch: immediately after pressing the
> keys, screen is redrawn, but where you'd normally see the login prompt,
> blurry characers are drawn. After a fraction of a second, these are replaced
> with proper glyphs. S
On 8 February 2014 08:49, Robert Millan wrote:
> Package: kfreebsd-image-11.0-0-amd64
> Version: 11.0~svn260666-1
> Severity: important
>
> With Newcons it becomes practically impossible to use the console. When
> using the default VESA driver, both VT switching and text scrolling
> become terribl
On 19 December 2013 06:33, Robert Millan wrote:
> On 19/12/2013 04:21, Ed Maste wrote:
>> On 18 December 2013 19:58, Robert Millan wrote:
>>>
>>> We could also try making it play nice with VTs. Maybe enabling
>>> newcons helps. Also, there's some disabled
On 18 December 2013 19:58, Robert Millan wrote:
>
> We could also try making it play nice with VTs. Maybe enabling
> newcons helps. Also, there's some disabled WIP code in radeonkms
> which is aimed at this purpose (I haven't tested it).
Restoring vty switching is one of the benefits that Newcons
On 16 October 2013 18:57, Sandro Knauß wrote:
> Hi,
>
> today I got the information, that FreeBSD has a working port for owncloud-
> client:
> http://svnweb.freebsd.org/ports/head/deskutils/mirall/
This uses the FreeBSD libinotify port, a ktrace-based implementation
of the inotify API.
--
To UN
This is fixed in stable/9 in r255443. The offending commit was already
reverted from the 9.2 branch prior to 9.2-RC3 for other reasons.
On 10 September 2013 07:31, Steven Chamberlain wrote:
> Package: src:kfreebsd-9
> Version: 9.2~svn253912-1
> Severity: grave
> Tags: security upstream
>
> ht
On 30 May 2013 07:41, Steven Chamberlain wrote:
> openjdk-7 has built now on kfreebsd-amd64!
Nice job!
Do you have a link to the patch set? I'm curious about the extent of
the changes, and how much overlap they have with the FreeBSD port
diffs.
-Ed
--
To UNSUBSCRIBE, email to debian-bsd-req
For now at least, the message can just be ignored.
Unfortunately there's no clean way to address it - the thread at
http://lists.freebsd.org/pipermail/svn-src-all/2013-May/068590.html
has some of the context.
--
To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org
with a subject of "uns
On Mon, Jun 13, 2011 at 09:11:41AM +0200, Lennart Poettering wrote:
> Nah, I will not work on this. Netlink is Linux specific -- it cannot be
> made on the legacy kernels, and I don't care for the legacy kernels
> anyway and won't spend time on them.
At the BSDCan conference last month we had som
On Fri, Apr 01, 2011 at 01:56:26AM +0200, Cyril Brulebois wrote:
> Hi,
>
> Kostya Berger (01/04/2011):
> > are there any plans to support the nouveau driver in kFreeBSD?
>
> no, as it needs KMS, which is Linux-only:
> http://en.wikipedia.org/w/index.php?title=Kernel_mode-setting&redirect=no
On Wed, Jan 26, 2011 at 09:14:44PM +0100, Mats Erik Andersson wrote:
> It is my firm belief that GNU/kFreeBSD will need activated
> support for file system quotas.
If you mean "kFreeBSD should ship with a quota-enabled kernel" then I'd
say go for it. The reason we don't have it on in upstream Fr
On Mon, Sep 13, 2010 at 10:55:54PM +0200, Tuco wrote:
> Btw FreeBSD handbook
> (http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html#KERNELDEBUG-OBTAIN)
> says dumpon and savecore are needed to save and restore crash dumps so
> I ported them and added them to freebsd-utils in c
On Mon, Sep 13, 2010 at 02:50:25PM +0200, Petr Salinger wrote:
> fails (panic in swapper) similarly also for me.
Can you add the following options to the kernel config and recompile,
to help track down the problem:
# Compile with kernel debugger related code.
options KDB
# Print a stac
> Same problem. This could be complicated. It appears as FreeBSD
> developers haven't tested with recent GCC at all (their last upgrade
> was to GCC 4.2).
Yes, FreeBSD is stuck on GCC 4.2.1 for the system compiler right now, as
it is the last GPLv2 version. In general I'd think it's beneficial fo
On Thu, Aug 05, 2010 at 01:16:21PM -0400, Tuco wrote:
> I found this problem when running uname inside a 32-bit chroot, 'uname
> -m' prints amd64! This often breaks configure scripts and build
> systems.
>
> With this glibc patch, uname corrects the output after it has been
> obtained with sysctl
22 matches
Mail list logo
