goli...@devuan.org writes:
> Dear dev1ers,
>
> The Devuan 3 Beowulf Beta release is now ready for review.
[...]
> In solidarity,
>
> The Devuan Devs
Great news. Thanks a lot.
___
Dng mailing list
Dng@lists.dyne.org
Steve Litt writes:
[...]
> FreeDesktop.Org doesn't like me doing 90 minutes of programming
> (and actually Lego(R) block assembly). Their preferred method goes
> something like this:
>
> * Use Gnome.
> * Find Gnome software that solves your problem:
> - Ask your LUG
> - Ask on
- the sole purpose of this text is for the amusement of people who ever
had to find a (preferably simple) solution for a complicated problem -
Problem I had to deal with since yesterday: Some Debian 10 system (use
of systemd mandated) installation I've created was to be captured by a
certain
Steve Litt writes:
> goli...@devuan.org wrote:
>
>> Just great! So how can we keep off this cloudflare thing?
>>
>> https://www.theregister.co.uk/2020/02/25/mozilla_turns_on_dns_over_https_by_default_for_usa/
>
> "Another relevant question is whether further centralisation [SIC] of
> the
Dimitris via Dng writes:
> On 1/28/20 6:46 PM, Rainer Weikusat via Dng wrote:
>> run ntpdate from
>
> i've witnessed cases in the past where ntpd wasn't time-syncing
> correctly, and ntpdate saved the date/time.
> so, IMHO, there's nothing wrong with ntpdate.
There's nothi
"Dr. Nikolaus Klepp" writes:
> Just for your amusement: systemd breaks linuxcnc on RPi4 - who's not
> into machining will most likely not see the fun part of it, but anyway
> :)
>
> https://www.youtube.com/watch?v=RDKaFJmB254
Not particularly funny --- the systemd timesync service is a C
goli...@devuan.org writes:
> Greetings all. Let's start the new year with something from the
> Debian forums that might make you shake your head and chuckle. Poor
> newbie on Windoze hasn't a clue just how funny his last para is:
>
> "The problems? The resulting bootable drive isn't booting in
Bernard Rosset via Dng writes:
> Thank you for those precious steps on how to swap a kernel version in
> an ISO!
[...]
Something I should have mentioned as well: The installation kernel needs
(at least) support for initramfs/initrd, the RAM block device and
devtmpfs compiled in order to boot
After spending the time since 2016 with waiting how things will turn
out, a dying disk and certain recent Debian moves prompted me to stop
using this system (after 21 years) and migrate to the current, stable
Devuan instead[*]. Thank you for keeping the system I had been using all
these years
Hendrik Boom <hend...@topoi.pooq.com> writes:
> On Wed, Jan 04, 2017 at 10:00:29PM +0000, Rainer Weikusat wrote:
>> I'm running a caching resolver locally because that "always works"
>> (unless blocked by the ISP which may become mandatory in the UK 'soon'
>>
Steve Litt writes:
> On Tue, 3 Jan 2017 11:06:53 +0100
> Jaromil wrote:
>
>> On Mon, 02 Jan 2017, Jaromil wrote:
>>
>> > what a pity Debian has switched to Google's DNS by default.
>>
>> for the record and the sake of historical correctness:
>>
Adam Borowski <kilob...@angband.pl> writes:
> On Tue, Nov 08, 2016 at 04:00:10PM +0000, Rainer Weikusat wrote:
>> It's pretty easy to fix this:
>>
>> - assign a sequence number to each driver load event reflecting
>> the device detection order
&
Simon Hobson writes:
> Nate Bargmann wrote:
>> After I thought about it some, there is a certain logic to udev's
>> behavior but it would seem to make more sense if the network adapter is
>> on a hot-pluggable interface (PCMCIA, USB, etc.), or is in addition
Rowland Penny writes:
[...]
> Finally, in desperation, I ran 'dmesg | grep eth0' and found my problem:
>
> root@server:~# dmesg | grep eth0
> [0.921998] r8169 :02:00.0 eth0: RTL8168b/8111b at 0xc9006000,
> 00:1d:60:fc:29:e6, XID 1800 IRQ 41
> [
Steve Litt writes:
> Miroslav Rovis wrote:
>
>> Hi!
>>
>> I read this great Devuan ML whenever I have time, and am still so
>> excited to be using Devuan some day,
>
> To refresh everyone's memory, Miroslav sent a lot of email, including
Brad Campbell writes:
> On 16/08/16 00:09, Rick Moen wrote:
>> Quoting Adam Borowski (kilob...@angband.pl):
>>
>
>>
>>> Or, the first disk gets assigned a different position.
>>
>> Which happens when exactly? Because you're screwing around with
>> swapping in and out
dev writes:
> On 08/10/2016 04:26 AM, Didier Kryn wrote:
>> Hello. Thanks to a friendly help, I've found a few mails and
>> articles which deserve to be read:
>>
>> Udev on non-systemd is a dead-end:
>
> So.. then.. basically any Linux distro which uses udev to
Rowland Penny (by way of Rowland Penny
) writes:
> So, a user was complaining over on the Samba mailing list, that the
> Samba wiki page about creating a new AD DC wasn't much use with fedora.
>
> I set up fedora 24 and tried to give it a fixed ip
hellekin writes:
> Dear Devuan supporters,
>
> We've been talking[0] to unixstickers.com for original, high-quality
> Devuan stickers giving back a percentage of the proceeds to the project
> as part of https://devuan.org/os/shopping. Our choice are narrowed down
> to three
Hendrik Boom writes:
> On Wed, Jul 27, 2016 at 10:34:55AM -0700, Rick Moen wrote:
>> By the way, what specifically does 'entangle it with unwanted
>> systemd-isms' actually _mean_, and what does that have to do with
>> whatever-the-heck-it-was that Rainier said? Once
Hendrik Boom <hend...@topoi.pooq.com> writes:
> On Tue, Jul 26, 2016 at 11:01:04AM -0700, Rick Moen wrote:
>> Quoting Rainer Weikusat (rweiku...@talktalk.net):
>> > Rick Moen <r...@linuxmafia.com> writes:
>> > > Quoting Rainer Weikusat (rweiku...@t
- resent after someone made Spamhaus remove the @talktalk.net e-mail
blacklisting entry -
Didier Kryn <k...@in2p3.fr> writes:
> Le 26/07/2016 12:59, Rainer Weikusat a écrit :
>> Didier Kryn <k...@in2p3.fr> writes:
>>> Le 25/07/2016 01:29, Rainer Weikusat a écrit
Didier Kryn writes:
> Le 25/07/2016 23:35, fsmithred a écrit :
>> Either way, it
>> looks like libsystemd is passively providing code for something else to
>> use.
> Calling a function does not mean that this function passively
> provides code to the caller.
But the library
Jaromil <jaro...@dyne.org> writes:
> On Sun, 24 Jul 2016, Rainer Weikusat wrote:
>> Didier Kryn <k...@in2p3.fr> writes:
>> > Le 22/07/2016 18:21, Brian Nash a écrit :
>> >> For example, when I discovered multithreading, all my programs used it
>&
Didier Kryn <k...@in2p3.fr> writes:
> Le 25/07/2016 01:29, Rainer Weikusat a écrit :
>> Sleeping on a contended mutex is implemented in this way. But that's
>> supposed to be an exceptional case.
>
> This is why, while advertizing itself as a cool "don't care&qu
Rick Moen <r...@linuxmafia.com> writes:
> Quoting Rainer Weikusat (rweiku...@talktalk.net):
>
>> I didn't expect you to stop the attempt to get a 'religious angle' into
>> this just because I pointed out that your interpretation was completely
>> wrong.
&
Didier Kryn <k...@in2p3.fr> writes:
> Le 24/07/2016 22:31, Rainer Weikusat a écrit :
>> Didier Kryn <k...@in2p3.fr> writes:
>>> Le 22/07/2016 18:21, Brian Nash a écrit :
>>>> For example, when I discovered multithreading, all my programs used it
>
Rick Moen <r...@linuxmafia.com> writes:
> Quoting Rainer Weikusat (rweiku...@talktalk.net):
>
>> That's neither 'abstract' nor 'teleological' as you yourself nicely
>> demonstrated by immediately coming up with an equivalent but different
>> term after reinte
Didier Kryn writes:
> Le 22/07/2016 18:21, Brian Nash a écrit :
>> For example, when I discovered multithreading, all my programs used it
>> in some way, even when it was unnecessary.
>
> I sometimes use multithreading, but never mutexes. Mutex can be
> harmless if there's only
Rick Moen writes:
[...]
>> Systemd is vendor lock-in and there is no other way to explain it when
>> "apache2-common" cannot be installed due to libsystemd0 dependency.
>
> Ah, _libsystemd0_. Thanks for the clarification. You were not talking
> about a dependency that
Didier Kryn <k...@in2p3.fr> writes:
> Le 08/07/2016 15:25, Rainer Weikusat a écrit :
>> The internal SRI software exception was caused during execution
>> of a data conversion from 64-bit floating point to 16-bit signed
>> integer value. The floating point num
Nate Bargmann writes:
> I may have swerved into the solution:
>
> ACTION=="add", KERNEL=="ttyUSB*", KERNELS=="1-1.4:1.0", SYMLINK+="ttyUSB99"
>
>
> Time will tell if it survives a reboot...
I think you shouldn't use the devpath in here as this means the rule
won't match anymore if
Rainer Weikusat <rweiku...@talktalk.net> writes:
> Didier Kryn <k...@in2p3.fr> writes:
>> Le 07/07/2016 23:57, Rainer Weikusat a écrit :
>>> Didier Kryn <k...@in2p3.fr> writes:
>>>> Le 07/07/2016 19:25, Rainer Weikusat a écrit :
>>>>&
Didier Kryn <k...@in2p3.fr> writes:
> Le 07/07/2016 23:57, Rainer Weikusat a écrit :
>> Didier Kryn <k...@in2p3.fr> writes:
>>> Le 07/07/2016 19:25, Rainer Weikusat a écrit :
>>>> The conversion happened implicitly as part of an assignment and the Ad
Didier Kryn <k...@in2p3.fr> writes:
> Le 07/07/2016 19:25, Rainer Weikusat a écrit :
>> The conversion happened implicitly as part of an assignment and the Ada
> There isn't implicit conversion in Ada.
I vaguely imagine writing somewhat more than 'the Ada runtime threw an
Didier Kryn <k...@in2p3.fr> writes:
> Le 04/07/2016 17:20, Rainer Weikusat a écrit :
>> Didier Kryn <k...@in2p3.fr> writes:
>>> Le 03/07/2016 23:17, Hendrik Boom a écrit :
>>>> On Fri, Jun 24, 2016 at 01:36:14PM -0400, Peter Olson wrote:
>>>>
Didier Kryn writes:
> Le 03/07/2016 23:17, Hendrik Boom a écrit :
>> On Fri, Jun 24, 2016 at 01:36:14PM -0400, Peter Olson wrote:
>>
>>> Can I download your compiler that fixes all my mistakes? I could really
>>> use such a tool.
>> Yes, as a matter of fat you can -- almost.
>>
Albert van der Horst writes:
[...]
>>> Another habit I have is to avoid a statement like:
>>>
>>> if (abc == 42)
>>>
>>> and write it as
>>>
>>> if (42 == abc)
>>>
>>> instead.
>>
>> That's a habit of many people who either believe to be master yoda
>> ('Your
Simon Hobson <li...@thehobsons.co.uk> writes:
> Rainer Weikusat <rweiku...@talktalk.net> wrote:
>> That's you're preferred set of workarounds.
>
> I suspect that we're all in "violent agreement" that different users
> (or types of users) have different pref
Peter Olson <pe...@peabo.com> writes:
> On 2016-06-24 12:17, Rainer Weikusat wrote:
>> Peter Olson <pe...@peabo.com> writes:
>>>> On June 23, 2016 at 10:48 AM Edward Bartolo <edb...@gmail.com> wrote:
>>>> if (count > 0)
>>>>
Didier Kryn <k...@in2p3.fr> writes:
> Le 23/06/2016 09:05, Simon Hobson a écrit :
>> Rainer Weikusat<rweiku...@talktalk.net> wrote:
>>
>>> >Reportedly, Linux hotplug already had the same problem.
>> OK, that's what I'd have been seeing in the past th
Simon Hobson <li...@thehobsons.co.uk> writes:
> Rainer Weikusat <rweiku...@talktalk.net> wrote:
>
>> Reportedly, Linux hotplug already had the same problem.
>
> OK, that's what I'd have been seeing in the past then.
>
>> During initialization, the kernel walk
Simon Hobson <li...@thehobsons.co.uk> writes:
> Rainer Weikusat <rweiku...@talktalk.net> wrote:
>> In absences of post hoc driver shuffling, these names *are not*
>> random.
[...]
> You've posted a statement that says drivers are loaded in a
> non-deterministic
KatolaZ writes:
[...]
> and the reason is that arrays in C are just syntactic sugar around
> memory addresses. This has nothing to do with polymorphism or generic
> programming, and is indeed much lower-level and more basic than
> that. Simply put, arrays do not
Adam Borowski writes:
> On Tue, Jun 21, 2016 at 03:13:21PM +0200, Irrwahn wrote:
>> On Tue, 21 Jun 2016 14:42:46 +0200, Edward Bartolo wrote:
>> [...]
>> > if ((c >= 'a' && c <= 'z') || (c >= 'A' && c <= 'Z')) {
>> [...]
>> You should *never* assume that the latin letters
Simon Hobson writes:
[...]
> All in all, the easiest way by far is to use stable and user(admin)
> set names for interfaces !
This is going to bite you in the posterior in case of canned OS
installations intended to be usable on a wide range of differently
configured
Edward Bartolo writes:
> I am saving your program for future study as its level is beyond the
> current level I am at. I am still at page 34 ("The C programming
> language" (Kernighan & Ritchie))
This is based on another simple idea, namely, instead of using a simple
Edward Bartolo writes:
[...]
> On page Page 34 Exercise 1-9
> "Write a program to copy its input to its output, replacing each
> string of blanks one ore more blanks by a single blank."
>
> I wrote the following, tested it, and seems to work, but I think it is
> too
This is published here in the hope that it is useful for someting.
The basic design of udev is similar to that of a forking server: There's
a parent process listening for uevents from the kernel on a netlink
socket which passes these events to worker processes for actual
processing. In case no
command (halt or reboot) which
ultimatively triggers a reboot system call (=> reboot(2)) causing the
kernel to initiate a system reboot or poweroff.
>
> Edward
>
> On 18/06/2016, Rainer Weikusat <rweiku...@talktalk.net> wrote:
>> Lars Noodén <lars.noo...@gmail.com> writ
Lars Noodén writes:
> On 06/17/2016 09:36 PM, KatolaZ wrote:
> [snip]
>> Unfortunately, system initialisation is really a bit more complicated
>> than that, whether you like it or not.
> [snip]
>
> Is there a concise summary somewhere of what system initialization
>
KatolaZ writes:
> On Fri, Jun 10, 2016 at 09:39:49AM -0400, Greg Olsen wrote:
>> On 2016-06-10 08:59, Simon Walter wrote:
>>[snip]
>> > > I will give the templates a go now.
>>
>> >I had some issues:
>> >perl: warning: Setting locale failed.
>> >perl: warning: Please
Greg Olsen writes:
[...]
> Rainer, since it wasn't in your previous example, I'm curious to know
> your opinion on the use of "bridge_waitport 0" ?
This is processed by the following code in
/etc/network/if-pre-up.d/bridge:
if [ "$IF_BRIDGE_WAITPORT"
Simon Walter writes:
> On 06/10/2016 03:55 PM, Greg Olsen wrote:
>> On 2016-06-10 06:34, Greg Olsen wrote:
>> [snip]
>> > The only side-effect are the extra messages during ifup with
>> > "bridge_ports none":
>> >
>> > iface testbr1 inet static
>> > bridge_ports
Simon Walter writes:
> After some testing, I have a question about an option in
> /etc/default/shorewall:
> wait_interface
> If I add the bridge interface to that line, shorewall will not start
> unless a container is brought up. I suppose that is why I was thinking
> of
Didier Kryn writes:
> Le 08/06/2016 12:49, KatolaZ a écrit :
>> Killing all the processes at logout should be easily doable using
>> cgroups (which existed much before Poettering got his bachelor
>> degree), and is indeed easily doable with screen, nohup, and hundred
>> of similar
dev writes:
>>> On Wed, 08 Jun 2016, Edward Bartolo wrote:
>>> fortunately they have a link to offer to non-subscribers, I'm not sure
>>> it will expire, however see here
>>> https://lwn.net/SubscriberLink/690151/721a817ed6377ec3/
>
>
> FTFA:
> "Lennart Poettering sees process
Jaromil writes:
> On Wed, 08 Jun 2016, Edward Bartolo wrote:
>> In short, I am afraid making assumptions the tempest will settle
>> down, is a mistake.
>
> the tempest is raging out there. today there is a fine piece by Corbet
> resuming the state of affairs on LWN, which I got
Klaus Hartnegg writes:
> All programmers please read this, and treat it as a list of things not to do.
>
> https://lists.dns-oarc.net/pipermail/dns-operations/2016-June/014964.html
Hmm ... while this is certainly the usual reimplementation no one to
whom d-bus
Simon Walter <si...@gikaku.com> writes:
> On 06/06/2016 08:48 PM, Rainer Weikusat wrote:
>> Simon Walter <si...@gikaku.com> writes:
>>> On 06/05/2016 12:16 AM, Rainer Weikusat wrote:
>>>> Simon Walter <si...@gikaku.com> writes:
[...]
>>>&
Simon Walter <si...@gikaku.com> writes:
> On 06/05/2016 12:16 AM, Rainer Weikusat wrote:
>> Simon Walter <si...@gikaku.com> writes:
>>
>> [...]
>>
>>> I am adding containers (LXC) and
>>> virtual network to the box, I think I will add an ta
Florian Zieboll writes:
> Simon Hobson wrote:
>> Florian Zieboll wrote:
>>
>> > Seriously, what else besides dependencies on other daemons that
>> > have to be running and some testing for the existence of certain
>> > (everything is)
Rainer Weikusat <rweiku...@talktalk.net> writes:
> Simon Walter <si...@gikaku.com> writes:
>> I am working on some cdist scripts for setting up some network interfaces.
>>
>> So far I am modifying the /etc/network/interfaces and then bring down
>> and up the
Simon Walter writes:
> I am working on some cdist scripts for setting up some network interfaces.
>
> So far I am modifying the /etc/network/interfaces and then bring down
> and up the interfaces. For a while now /etc/init.d/networking has a
> warning that it is deprecated. I
Rainer Weikusat <rweiku...@talktalk.net> writes:
[...]
> I'll certainly fix any CVE-level issue I consider to be relevant for my
> use cases
While we're at that: There's a bunch of (very likely harmless) buffer
overflows in the bsect_common function (bsect.c), namely this here:
Haines Brown writes:
> I installed 64bit jessie on a new HDD, and initially used the 3.16.0
> kernel. Then I installed the 4.50 kernel and ran into trouble.
>
> kernel:[25090.816205] NMI watchdog: BUG: soft lockup - CPU #7
> stuck for 22!s
>
Jaromil <jaro...@dyne.org> writes:
> On Mon, 30 May 2016, Rainer Weikusat wrote:
>
>> I have no plans to use anything but lilo unless that's a technical
>> requirement. It boots. That's all I want from it.
>
> having dealt with it recently, what is your opinion on th
Hendrik Boom writes:
> On Sun, May 29, 2016 at 08:37:08PM +0100, dev1fanboy wrote:
>>
>> Also worth pointing out that lilo is without an upstream maintainer
>> as of recently.
>
> I'm happily using lilo to boot my server.
JFTR: I've recently (last week) added a
KatolaZ writes:
[...]
> And here you find an educated explanation, directly from "The Mind"
> who is driving the revolution of this centrury:
>
> https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/message/XW7V5A3RAWYCACU2ZMPA27ARRLIZUI37/
That's
Didier Kryn <k...@in2p3.fr> writes:
> Le 25/05/2016 18:55, Rainer Weikusat a écrit :
>> Linux has the nice policy of never changing a public ABI, hence, there's
>> no problem in this respect
>
> Good to know. Although this is not true for kernel internals (if
>
Didier Kryn writes:
> Le 24/05/2016 12:50, Jaromil a écrit :
> > >>Emacs is a somewhat old-fashioned/ traditional[*] Lisp implemenation
> >[*] It doesn't support lexical scoping.
> >
>>> >
>>> >No idea what that means. I like emacs for text editing and don't use it
Rainer Weikusat <rweiku...@talktalk.net> writes:
> Hendrik Boom <hend...@topoi.pooq.com> writes:
>> On Tue, May 24, 2016 at 08:40:37PM +0100, Rainer Weikusat wrote:
>
> [same as below but worded differently]
>
>>>
>>> ... and what the Lisp 1.5 FUN
Hendrik Boom <hend...@topoi.pooq.com> writes:
> On Wed, May 25, 2016 at 03:22:01PM +0100, Rainer Weikusat wrote:
>
>>
>> The LISP "alist" implementation is, as we noted earlier, an
>> example of the "deep access" approach". The &quo
Hendrik Boom <hend...@topoi.pooq.com> writes:
> On Tue, May 24, 2016 at 08:40:37PM +0100, Rainer Weikusat wrote:
[same as below but worded differently]
>>
>> ... and what the Lisp 1.5 FUNCTION was about was to enable solving the
>> so-called 'upward funarg pr
Hendrik Boom <hend...@topoi.pooq.com> writes:
> On Tue, May 24, 2016 at 02:47:04PM +0100, Rainer Weikusat wrote:
>> Didier Kryn <k...@in2p3.fr> writes:
>> > Le 23/05/2016 23:29, Rainer Weikusat a écrit :
>> >> Rainer Weikusat <rweiku...@talktal
Jaromil writes:
[...]
> maybe its all relative and we are
> all fanatics in the eyes of Vim users :^)))
Confused people having confused opinions ...
[rw@doppelsaurus]~#dpkg -l | grep 'ii *[^ ]*vim\? '
ii nvi 1.81.6-8.2
Didier Kryn <k...@in2p3.fr> writes:
> Le 23/05/2016 23:29, Rainer Weikusat a écrit :
>> Rainer Weikusat <rweiku...@talktalk.net> writes:
>>
>> [...]
>>
>>> Emacs is a somewhat old-fashioned/ traditional[*] Lisp implemenation
>> [*] It do
Rainer Weikusat <rweiku...@talktalk.net> writes:
[...]
> Emacs is a somewhat old-fashioned/ traditional[*] Lisp implemenation
[*] It doesn't support lexical scoping.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bi
Didier Kryn writes:
> Le 23/05/2016 19:49, Jaromil a écrit :
>> I have no use for a PDF
>> viewer that can't print. Else I'd just use Emacs for that too ;^)
>> ___
>
> Indeed it does! I didn't even thought to try that. Looks like one
Virgin Media chose to sell its ADSL customers to the highest bidder last
year (which happened to be TalkTalk) and as consequence of this, the
@virginmedia.com address I used to suscribe to the list will be going
away at the end of this month. Because of this, I've changed to
subscription address
I have to build one of these things as part of packaging 'our' kernel
(for more streamlined installations, ie, without compiling a dedicated
kernel for each). I remember reading various criticisms about the
impenetrable obscurity of the mechanism/ arrangement here in the past
but so far, it seems
Mitt Green writes:
> LOL that self-centric poof[1], that tells people
> what to do[2], has #gnome in one row with #geek[3].
> Don't forget to add #mentallychallenged,
> Laurent Bigotville.
>
> [1]:https://twitter.com/bigonbe
While "maybe the initsystem you use shouldn't
Rainer Weikusat <rainerweiku...@virginmedia.com> writes:
> John Morris <jmor...@beau.org> writes:
>> On Wed, 2016-05-04 at 21:41 +0100, Arnt Gulbrandsen wrote:
>>> Malloc() is very simple: You ask for memory and get it. The negative
>>> side
>>> of
poitr pogo <lepo...@gmail.com> writes:
> On 5/6/16, Rainer Weikusat <rainerweiku...@virginmedia.com> wrote:
>
> (...)
>> I'm dealing with a program where every allocation failure is
>> meticolously passed up the call stack so that the top-most function can
>&
John Morris writes:
> On Wed, 2016-05-04 at 21:41 +0100, Arnt Gulbrandsen wrote:
>> Malloc() is very simple: You ask for memory and get it. The negative
>> side
>> of that simplicity is that if you're out of memory (and that happens
>> occasionally if a server is run close to
Simon Walter <si...@gikaku.com> writes:
> On 05/05/2016 11:11 PM, Rainer Weikusat wrote:
>> Simon Walter <si...@gikaku.com> writes:
>>
>> [...]
>>
>>> On 05/05/2016 05:45 AM, Rainer Weikusat wrote:
>>>> It greatly reduces the number o
Hendrik Boom <hend...@topoi.pooq.com> writes:
> On Thu, May 05, 2016 at 07:49:04AM +0100, Simon Hobson wrote:
>> Rainer Weikusat <rainerweiku...@virginmedia.com> wrote:
>>
>> > But leaving these two general remarks aside, I don't quite unders
Simon Walter <si...@gikaku.com> writes:
[...]
> On 05/05/2016 05:45 AM, Rainer Weikusat wrote:
>> It greatly reduces the number of "low-quality" (or rather, "no quality")
>> bug reports I receive as I don't (usually) get frantic phone calls at
>> 3
Hendrik Boom <hend...@topoi.pooq.com> writes:
> On Wed, May 04, 2016 at 09:45:24PM +0100, Rainer Weikusat wrote:
>> Stephanie Daugherty <sdaughe...@gmail.com> writes:
>> > Process supervision is something I'm very opinionated about. In a number of
>> > hi
Stephanie Daugherty writes:
> Process supervision is something I'm very opinionated about. In a number of
> high availability production environments, its a necessary evil.
>
> However, it should *never* be an out of the box default for any
> network-exposed service, Service
Robert Storey writes:
> For whatever it's worth, I'm fully supportive of the idea of defaulting to
> a simpler init system such as S6, Epoch, Runit, you-name-it. I can't speak
> for anyone else, of course, but I tend to think the sort of people who are
> attracted to
parazyd writes:
> The current init system is old. Ancient. We should all agree on it.
The current init system is younger than me. Despite I'm 43 (and will be
44 in a few months), people still want to see a proof of me being
already 18 with annoying regularity (although the
Jaromil writes:
[...]
> Can you come up with an alternative to 'cloud' which keeps generic,
> since cloud-init is not openstack specific?
Stormbringer?
___
Dng mailing list
Dng@lists.dyne.org
Nate Bargmann writes:
> * On 2016 29 Apr 15:29 -0500, Hendrik Boom wrote:
>> On Fri, Apr 29, 2016 at 11:31:29AM -0400, Steven W. Scott wrote:
>> > Alas, some are, some aren't and it seems to depend on manufacturer. Android
>> > is a wild-west with tens of thousands of different
Didier Kryn <k...@in2p3.fr> writes:
> Le 29/04/2016 16:46, Rainer Weikusat a écrit :
>> Didier Kryn <k...@in2p3.fr> writes:
>>> Le 28/04/2016 21:23, Rainer Weikusat a écrit :
>>>> as manually running debootstrap in
>>>> two steps
Didier Kryn <k...@in2p3.fr> writes:
> Le 28/04/2016 21:23, Rainer Weikusat a écrit :
>> as manually running debootstrap in
>> two steps on the same system doesn't do anything the single-step
>> debootstrap wouldn't also do
>
> But it's not the same system.
Didier Kryn <k...@in2p3.fr> writes:
> Le 28/04/2016 15:34, Rainer Weikusat a écrit :
>> Didier Kryn <k...@in2p3.fr> writes:
>>> Le 27/04/2016 23:29, Haines Brown a écrit :
>>>> I found I had to bind mount /sys before I could install grub2.
>
Didier Kryn writes:
> Le 27/04/2016 23:29, Haines Brown a écrit :
>> I found I had to bind mount /sys before I could install grub2.
>
> A few tricks:
>
> It is most of the times necessary to bind-mount /proc and /sys
> when working in a chroot. Depending what you do, /dev
Haines Brown writes:
> On Wed, Apr 27, 2016 at 06:05:56PM +0200, Didier Kryn wrote:
>> Le 27/04/2016 17:47, Haines Brown a écrit :
>> >
>> >I'm doing a cross install of devuan Alpha 4 onto a newly partitioned
>> >hard disk (/dev/sda1) in same box as my running Debian Wheezy
Haines Brown writes:
[...]
> # LANG=C.UTF-8 chroot /mnt/debinst /bin/bash
> /bin/bash: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version
>`GLIBC_2.15' not found (required by /bin/bash)
> /bin/bash: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version
>
1 - 100 of 558 matches
Mail list logo