On Tue, Feb 4, 2014 at 10:04:47 +, Robert Millan wrote:
> On 28/01/2014 22:39, Julien Cristau wrote:
> > I haven't been able
> > to test nv, msm, omap, omapfb or sunffb.
>
> nv builds fine. Thanks for the heads-up.
>
It doesn't seem to be whitelisted in wanna-build, so I'm unable to
binNMU
On 2014-01-30 16:23, Robert Millan wrote:
> On 30/01/2014 00:03, Niels Thykier wrote:
>> @Robert: Re your "Could you elaborate?". I haven't forgotten it, but I
>> out of time - so I will get back to you on that.
>
> It's ok.
>
> I wanted more detail both on the problem and on the solution. You j
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
Processing control commands:
> retitle -1 VGA Newcons is awfully slow
Bug #738188 [kfreebsd-image-11.0-0-amd64] VESA Newcons is awfully slow
Changed Bug title to 'VGA Newcons is awfully slow' from 'VESA Newcons is
awfully slow'
--
738188: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738188
Control: retitle -1 VGA Newcons is awfully slow
Hi Ed,
On 09/02/2014 19:47, Ed Maste wrote:
> On what hardware (or VM) do you experience this? On my Thinkpad X220
> the console is acceptably performant in both VGA-mode (at boot) and
> i915 (after starting X), with a FreeBSD-CURRENT kernel from t
On 12 February 2014 12:23, Robert Millan wrote:
> On 12/02/2014 12:09, Steven Chamberlain wrote:
>> There are a few reasons to keep sysvinit scripts maintained for jessie:
>> 1. for smoother upgrades from wheezy
>> 2. in order to backport jessie packages to wheezy
>> 3. for non-Linux (or non-syste
Processing control commands:
> tag -1 help
Bug #738486 [freebsd-nfs-common] freebsd-nfs-common: NFSv4 non-functional due
to missing nfsuserd and nfscbd
Added tag(s) help.
--
738486: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738486
Debian Bug Tracking System
Contact ow...@bugs.debian.org
On 09/02/2014 12:56, Markus Koschany wrote:
> Switching between virtual terminals and X works flawlessly after I
> loaded the intel drivers manually.
What about switching from one VT to another? (no X involved)
--
Robert Millan
--
To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org
w
Control: tag -1 help
Hi Roger,
Unfortunately we're very short on manpower to add new features. Do you
think you'd be able to help with this one?
On 09/02/2014 22:11, Roger Leigh wrote:
> Package: freebsd-nfs-common
> Version: 9.2+ds1-1+b1
> Severity: important
>
> Dear Maintainer,
>
> It does
On 12/02/14 13:18, Robert Millan wrote:
> Or maybe backward compat? I hear some of the new init implementations
> support SysV.
SysV init scripts?
I thought this was obvious, or maybe I misunderstand what you mean.
*All* of the init systems that were discussed by the TC, even systemd
(for now), c
On 12/02/2014 12:40, Steven Chamberlain wrote:
> Although, come jessie+1, I wonder how upgrades will be handled, if
> sysvinit scripts go away.
Maybe Pre-Depends. Or maybe have written instructions to install
the new init by hand, like we often do for kernels.
Or maybe backward compat? I hear som
On 12/02/14 12:23, Robert Millan wrote:
> If we have to support it anyway, is it really worth spending effort on
> Upstart/OpenRC for Jessie?
Right, sysvinit is a viable and easy option for jessie; having any
other init systems working is a bonus.
At least we know now that we need to concentrate
On 12/02/2014 12:09, Steven Chamberlain wrote:
> There are a few reasons to keep sysvinit scripts maintained for jessie:
> 1. for smoother upgrades from wheezy
> 2. in order to backport jessie packages to wheezy
> 3. for non-Linux (or non-systemd) ports
>
> So ports are not the only reason. And y
Forwarded Message
From: Svante Signell
To: debian-h...@lists.debian.org
Subject: Re: Init system for non-Linux ports
Date: Wed, 12 Feb 2014 13:02:45 +0100
On Wed, 2014-02-12 at 10:45 +, Robert Millan wrote:
> On 29/01/2014 09:26, Petr Salinger wrote:
> What is the current s
On 12/02/14 10:45, Robert Millan wrote:
> I'm a bit afraid that even if sysvinit itself stays mostly fine, the scripts
> written for
> it could turn into a bunch of bitrot.
There are a few reasons to keep sysvinit scripts maintained for jessie:
1. for smoother upgrades from wheezy
2. in order to
On 12/02/14 12:04, Svante Signell wrote:
> I fear that it is currently broken since one of the latest patches. Do
> you have a (scrappable) pre-installed image I can download, ala:
> http://people.debian.org/~sthibault/hurd-i386/
Yes, Aurelien Jarno has kindly made these:
> http://blog.aurel32.ne
On 29/01/2014 09:26, Petr Salinger wrote:
>> 1. stay with sysvinit
>> 2. switch to OpenRC unconditionally
>> 3. switch to Upstart unconditionally
>> 4. switch to Upstart only if Linux uses it by default, otherwise OpenRC
>> 5. further discussion
>>
>> Please rank the above putting your preferred op
17 matches
Mail list logo
