On Fri, Oct 31, 2014 at 11:43:36 +, Steven Chamberlain wrote:
Hi,
kfreebsd-10 migrated last night; is there a chance another upload of
the kernel could go into sid and be aged in before the freeze starts?
Leaving aside the first question, I don't think it would be aged, no.
Cheers,
Hi Steven, hi release@
Julien Cristau jcris...@debian.org writes:
On Fri, Oct 31, 2014 at 11:43:36 +, Steven Chamberlain wrote:
kfreebsd-10 migrated last night; is there a chance another upload of
the kernel could go into sid and be aged in before the freeze starts?
Leaving aside the
I think I agree rushing in a kernel update might not be the best thing
and giving it full 10+ days of testing in unstable is a good idea
Please do upload into unstable now,
but no need to hurry with pushing into testing.
It might be better to wait for final 10.1 and ask release team in one
Hi,
Many thanks for testing on real hardware.
Adding my comments below; I'll further investigate some of the issues
myself, but anyone else is welcome to look into these or the other
points in the original mail:
On 31/10/14 10:41, Herbert Kaminski wrote:
- grub-install was not able to
On 31/10/14 12:29, Christoph Egger wrote:
I think I agree rushing in a kernel update might not be the best thing
and giving it full 10+ days of testing in unstable is a good idea
The upstream changes were IMHO only very small and I'm deferring to
their judgement that they were necessary and
Ahoi!
Christoph Egger christ...@christoph-egger.org writes:
Emilio Pozuelo Monfort po...@debian.org writes:
On 31/10/14 12:43, Steven Chamberlain wrote:
kfreebsd-10 migrated last night; is there a chance another upload of
the kernel could go into sid and be aged in before the freeze starts?
kfreebsd-10_10.1~svn273874-1_kfreebsd-amd64.changes uploaded successfully to
ftp-master.debian.org
along with the files:
kfreebsd-source-10.1_10.1~svn273874-1_all.deb
kfreebsd-10_10.1~svn273874-1.dsc
kfreebsd-10_10.1~svn273874.orig.tar.xz
kfreebsd-10_10.1~svn273874-1.debian.tar.xz
Am Fri, 31 Oct 2014 12:41:46 +
schrieb Steven Chamberlain ste...@pyro.eu.org:
On 31/10/14 10:41, Herbert Kaminski wrote:
- grub-install was not able to install grub if the file system
root was on a logical partition.
I once thought that was a limitation of what the FreeBSD kernel can
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 30 Oct 2014 22:27:51 +
Source: kfreebsd-10
Binary: kfreebsd-source-10.1 kfreebsd-headers-10.1-0
kfreebsd-image-10.1-0-amd64 kfreebsd-image-10-amd64
kfreebsd-headers-10.1-0-amd64 kfreebsd-headers-10-amd64
kfreebsd-10_10.1~svn273874-1_kfreebsd-amd64.changes uploaded successfully to
localhost
along with the files:
kfreebsd-source-10.1_10.1~svn273874-1_all.deb
kfreebsd-10_10.1~svn273874-1.dsc
kfreebsd-10_10.1~svn273874.orig.tar.xz
kfreebsd-10_10.1~svn273874-1.debian.tar.xz
Greetings,
Hello fellow kFreeBSDers,
I have been playing around with Debian/kFreeBSD Wheezy for the past
week and, while it has been a good, solid system, some of the software
is a bit outdated for what I want to do. Naturally, I gave upgrading to
the jessie repositories a try. I updated the APT repository
Hello!
Jesse Smith wrote:
For the most part things went well. My system now has the software I
want and the system is fast and stable.
That's great!
However, I've run into a problem
and I could use some advice. When I try to shutdown/reboot/halt the
system I get a message saying the file
Control: severity -1 normal
On Tue, 28 Oct 2014 11:05:11 + Steven Chamberlain ste...@pyro.eu.org
wrote:
Hi,
On 28/10/14 03:16, Michael Gilbert wrote:
This package currently depends on libjinput-jni, which is currently
not build on the kfreebsds (#657771), so the libjinput-java is
Markus Koschany wrote:
I think it is a bug because we want jinput to be available on all
supported architectures. However the severity should be normal.
Sure, but I just noticed there's already a bug open about that, #657771
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To
Thank you for responding, I do appreciate it.
That's odd. Does /run or /var/run exist?
$ ls -ald /run /var/run
Yes, the /run directory exists. The /var/run directory is a symbolic
link back to /run. Here is a directory listing of /run. As you can see
it is populated with a collection of small
Control: forcemerge 657771 767051
On Fri, 31. Oct 22:36 Steven Chamberlain ste...@pyro.eu.org wrote:
Markus Koschany wrote:
I think it is a bug because we want jinput to be available on all
supported architectures. However the severity should be normal.
Sure, but I just noticed there's
Jesse Smith wrote:
The /run directory appears to be mounted as part of the root (/) file
system. It does not have its own mount point. Should I create one?
No, the initscripts should create it for you. This is probably a clue
to the problem you're seeing (and I'm quite curious to know what it
Jesse Smith wrote:
As a test I manually ran mknod to create the /run/initctl file,
duplicating the command in the mountal.sh script. This causes the
reboot and shutdown commands to pause for a few seconds. Then I get
an error saying the comand timed out trying to write to /run/initctl.
I
Processing commands for cont...@bugs.debian.org:
tags 754237 + wheezy
Bug #754237 {Done: Debian FTP Masters ftpmas...@ftp-master.debian.org}
[src:kfreebsd-9] kfreebsd-9: SCTP kernel memory disclosures (CVE-2014-3953)
Added tag(s) wheezy.
thanks
Stopping processing here.
Please contact me if
Processing commands for cont...@bugs.debian.org:
tags 748743 + wheezy
Bug #748743 [kfreebsd-8] kfreebsd-8: triple fault on execve from 64-bit thread
to 32-bit process
Added tag(s) wheezy.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
748743:
20 matches
Mail list logo
