MAGDALENA HANCOCK | 23 Jun 04:40 2016

Jeff Bailey

Our Company, Nocturne, is an international fast-growing distributing company. Our main goal is to offer various sales, logistic and delivery services to both, individuals and companies, through the world. At this time we have open vacancies in Australia for full-time and part-time.

Please pay attention!

Our employment offer is only for people with AU citizenship or work permission.

Basic tasks for this new posts are:

- customer sales support;

- collaboration with our clients in America, Eastern Europe and Asia;

- keep the data of all the purchases and orders;

- help to our distribution department.

You will have up to 3500 AUD per month for the part-time and 6500 AUD monthly for full-time. Also we offer bonus system.

We have a probation period of time, during which you will be guided and paid.

Conditions are:

- computer or laptop with Internet access,

- basic Excel (the software must be pre-installed),

- perfect writing and social skills,

- positive mood.

If you are interested in working with a strong leadership team, please reply.

Best regards,

STaffing Executive


Dmitry Shachnev | 22 Jun 09:11 2016

dup3 and pipe2 syscalls on kfreebsd

Hi kFreeBSD porters,

While working on Qt packaging, I noticed that it's currently impossible to
use dup3 and pipe2 system calls on kFreeBSD. The linker outputs the following:

  cloexec.o: In function `main':
  cloexec.cpp:(.text.startup+0x2e): warning: dup3 is not implemented and will always fail
  cloexec.cpp:(.text.startup+0xd): warning: pipe2 is not implemented and will always fail

I have two questions about this issue:

1) It looks like upstream FreeBSD supports this since version 10.0.
   Why does it not work in Debian?

2) If it's not easy to get them working, why should the linker accept the
   code using them at all? I.e. why is it a warning, not an error?

   (Yes, I know about --fatal-warnings, but Thiago raised some valid points
   why it is not acceptable in Qt case [1]).


Thanks in advance,

(please CC me in reply if possible)

Dmitry Shachnev
Jon Boden | 20 Jun 12:47 2016

Bug#827733: BusyBox Init + OpenRC

Package: busybox
Version: 1.22.0-19
Tags: patch


With the package added by this patch (busybox-openrc), BusyBox Init can be used as PID 1 as a launcher for
OpenRC (instead of SysV /sbin/init). This has the potential for faster boot times (but I haven't measured
it, see

I've only tested it on ubuntuBSD, but I think it should work fine on Debian too. I've also added Linux and Hurd
versions of inittab.


Jon Boden

ubuntuBSD -- The power of FreeBSD kernel with familiarity of Ubuntu OS! --
Attachment (busybox-openrc.diff): text/x-diff, 5116 bytes
Jon Boden | 20 Jun 09:11 2016

Bug#827718: init: open /dev/console on GNU/kFreeBSD

Package: busybox
Version: 1.22.0-19
Tags: patch

FreeBSD kernel doesn't tell PID 1 the pathname of /dev/console through CONSOLE environment variable like
Linux does. Instead it expects PID 1 to always open /dev/console.

This patch is tested on ubuntuBSD but I think it should work on Debian too (I haven't tested the whole init
yet, but I verified that with my patch it can print to stdout).

I've also sent it to BusyBox bugzilla:


Jon Boden

ubuntuBSD -- The power of FreeBSD kernel with familiarity of Ubuntu OS! --
Attachment (busybox_freebsd.diff): text/x-diff, 630 bytes
Jon Boden | 19 Jun 17:23 2016



What are your plans for the future of init on Debian GNU/kFreeBSD? Are you going to continue with sysvinit
for the time being?

For the upcoming release of ubuntuBSD I'm thinking about using BusyBox + OpenRC
( Do you think this is a good idea?
Is there a particular reason you're staying with sysvinit?

William ML Leslie | 18 Jun 18:25 2016

Re: [Stretch] Status for architecture qualification

In case it isn't clear, the number of users of the architecture is not part of the qualification, it is the amount of maintenance pressure involved. Package maintainers have to put more effort into ensuring builds succeed for release architectures, which detracts from other work that needs to be done. Not being a release architecture is perfectly fine.

And just to bring the topic full circle now, ppc is a release architecture, nobody is suggesting its removal afaict.

On 18/06/2016 2:54 am, "Brock Wittrock" <brockwittrock <at>> wrote:
I run all sorts of PowerPC machines with various versions of Debian and I don't see that coming to end anytime soon.  These are excellent and reliable machines.  Biggest issues/hurdles are just graphics at the moment for both ATI/AMD and Nvidia cards, but even if that is never resolved/fixed or performance dwindles to nothing, I will continue to use these machines in text/console only mode if I have to.  Please do not drop this architecture!


On Fri, Jun 17, 2016 at 3:24 AM, Riccardo Mottola <riccardo.mottola <at>> wrote:

Dan DeVoto wrote:
In addition to the debian powerpc mailing list, powerpc users are active on the Ubuntu forums.  I'm running Debian Sid on a Powerbook and everything works except 3D acceleration.  I don't see a need to drop it.

I hope that my iBook G3 will serve me for years to come! Low power consumption fanless with a SSD disk make superquiet and quite nice!


Dan DeVoto | 17 Jun 06:49 2016

Re: [Stretch] Status for architecture qualification

In addition to the debian powerpc mailing list, powerpc users are active on the Ubuntu forums.  I'm running
Debian Sid on a Powerbook and everything works except 3D acceleration.  I don't see a need to drop it.



On Thu, 6/16/16, Mathieu Malaterre <malat <at>> wrote:

 Subject: Re: [Stretch] Status for architecture qualification
 To: "Hector Oron" <hector.oron <at>>
 Cc: "Niels Thykier" <niels <at>>, "DSA" <debian-admin <at>>, "Debian Security
Team" <team <at>>, "debian-release" <debian-release <at>>,
debian-ports <at>, "Debian Wanna-Build Team" <debian-wb-team <at>>, riku <at>
 Date: Thursday, June 16, 2016, 12:04 AM

 Hi Hector,

 On Thu, Jun 16, 2016 at 2:12
 AM, Hector Oron <hector.oron <at>>
 > While
 working out ArchitectureQualification/Stretch wiki page I
 > believe everything is mostly fine for
 release, however I got a
 > personal
 concern on powerpc architecture. Is it well maintained?
 > it have porters? Does it have
 users? Does it still make sense to carry
 > along?

 The debian-powerpc <at> l.d.o
 mailing list is active so I would say it
 still has some users. I have been using
 partch.d.o for doing some work
 on PowerPC. I
 posted a summary of work people have been doing on this
 port lately:

 However I do agree that true
 PowerPC hardware is actually
 and it is alive mostly thanks to being an ABI using
 32bits integer for PPC64 CPU(s).


Jon Boden | 13 Jun 22:53 2016

Bug#827221: fix bind9 on kfreebsd-amd64

Package: bind9
Version: 1:9.10.3.dfsg.P4-10
Tags: patch


bind9 build fails on kfreebsd-amd64 because threading is disabled:

checking for PKCS11 support... yes
configure: error: PKCS11 requires thread support
debian/rules:50: recipe for target 'stamps/configure' failed
make: *** [stamps/configure] Error 1

In ubuntuBSD we had the same problem and fixed it with this patch:

I think the same patch should work for Debian too.

Jon Boden | 12 Jun 16:51 2016

patch for mysql-5.7

FYI (not in Debian yet):

Jon Boden | 11 Jun 23:25 2016

Bug#827072: kfreebsd-10: use notify-reboot-required

Package: kfreebsd-10
Version: 10.3~svn300087-1
Tags: patch


If it's not too much noise, could you merge this small patch?

notify-reboot-required is the Ubuntu way packages tell the user that a reboot is required (usually after
an upgrade).

Jon Boden | 11 Jun 23:22 2016

Bug#827070: kfreebsd-10: please use LDADD instead of LDFLAGS for aicasm

Package: kfreebsd-10
Version: 10.3~svn300087-1
Tags: patch


When building kfreebsd-10 on ubuntuBSD, at least with current toolchain (and possibly on Debian
eventually), it fails with linker errors because the -lbsd -ldb flags are not with the rest of the flags
(-ll) and for some reason the linker can't find symbols on those libraries (bsd_getopt, etc).

This can be fixed by using LDADD instead. Could you include the patch?

I've also sent the Makefile part to FreeBSD: