Hi,
Zbigniew Jędrzejewski-Szmek:
> > And it doesn't appear to regulate the system clock frequency, which
> > basically makes it an inaccurate dumb SNTP client which steps the clock when
> > it synchronises.
> Please see
> http://cgit.freedesktop.org/systemd/systemd/tree/src/timesync/timesyncd-man
On Mon, Dec 01, 2014 at 10:58:45PM +, Roger Lynn wrote:
> On 29/11/14 13:30, Vincent Bernat wrote:
> > ❦ 29 novembre 2014 12:41 GMT, Alastair McKinstry
> > :
> >> One concern I'd have is the lack of flexibility to produce a cut-down
> >> system. The option of "a dedicated init=/custom-progr
On 29/11/14 13:30, Vincent Bernat wrote:
> ❦ 29 novembre 2014 12:41 GMT, Alastair McKinstry
> :
>> One concern I'd have is the lack of flexibility to produce a cut-down
>> system. The option of "a dedicated init=/custom-program", but lack of
>> an ntpd, for example, because ntp has been absorbe
On Sun, 2014-11-30 at 21:48 +0800, Paul Wise wrote:
> On Sun, Nov 30, 2014 at 3:11 AM, Ben Hutchings wrote:
>
> > working upstream
>
> Are there any vendors of ARM-based devices who are doing that?
Most of the SoC vendors seem to be doing *some* work to get their chips
supported upstream, but I
On Sun, Nov 30, 2014 at 3:11 AM, Ben Hutchings wrote:
> working upstream
Are there any vendors of ARM-based devices who are doing that?
--
bye,
pabs
https://wiki.debian.org/PaulWise
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? C
On Sat, 2014-11-29 at 17:10 +0100, Simon Richter wrote:
> Hi,
>
> On 29.11.2014 08:37, Tollef Fog Heen wrote:
>
> > I'm not Simon, but one valid argument I've heard is that embedded stuff
> > has a tendency to get stuck on old vendor kernels, something that
> > doesn't work so well when systemd u
Hi,
On 29.11.2014 13:41, Alastair McKinstry wrote:
> I'm heartened that some developers are doing the work to make
> non-systemd remain a
> viable option in debian, but for it not to degenerate into "the systemd
> way / the less maintained
> and tested non-systemd way", we need to promote the API
Hi,
On 29.11.2014 08:37, Tollef Fog Heen wrote:
> I'm not Simon, but one valid argument I've heard is that embedded stuff
> has a tendency to get stuck on old vendor kernels, something that
> doesn't work so well when systemd uses newer kernel interfaces.
Correct, and I don't see the situation i
❦ 29 novembre 2014 12:41 GMT, Alastair McKinstry
:
> One concern I'd have is the lack of flexibility to produce a cut-down
> system. The option of "a dedicated init=/custom-program", but lack of
> an ntpd, for example, because ntp has been absorbed into systemd's
> orbit and other ntpd's bitro
> Why, precisely, do you foresee future problems with embedded systems
> development? Personally, I'm looking forward to a much easier time
> building future embedded systems using systemd, or the occasional
> too-small-for-anything-else embedded system (that couldn't run standard
> sysvinit or D
Hi,
Tollef Fog Heen:
> I'm not Simon, but one valid argument I've heard is that embedded stuff
> has a tendency to get stuck on old vendor kernels, something that
> doesn't work so well when systemd uses newer kernel interfaces.
>
That attitude is unfortunately not limited to "traditional" embedd
]] Josh Triplett
> Simon Richter wrote:
> > On 28.11.2014 09:43, Svante Signell wrote:
> > > The official name of the Debian fork is devuan: https://devuan.org
> > > It will be interesting to see how many Debian Maintainers and
> > > Developers will jump the ship and join them (in addition to th
Simon Richter wrote:
> On 28.11.2014 09:43, Svante Signell wrote:
> > The official name of the Debian fork is devuan: https://devuan.org
> > It will be interesting to see how many Debian Maintainers and
> > Developers will jump the ship and join them (in addition to the
> > users). Future will tel
13 matches
Mail list logo
