hellekin escribió:
# Devuan News Issue LX
[...]
this is your news, and you can make it! Moreover, we don't really
know who's reading, and whether this newsletter fulfills an actual
need. We'd appreciate feedback about how we could better the
newsletter -- what works, what doesn't and what'
Le 01/02/2016 01:24, Go Linux a écrit :
On Sun, 1/31/16, Didier Kryn wrote:
Subject: Re: [DNG] systemd is haunting me
To: dng@lists.dyne.org
Date: Sunday, January 31, 2016, 5:12 PM
Le 31/01/2016 23:59, Go Linux a écrit :
> So how did packagekit get in there?
I'm afraid it
A suggestion / request:
Can Mailman predict the URL under which Lurker will archive the message
it is processing "on the fly", or is there even a variable available?
Quoting and referencing "third party" messages would be so much easier,
if mails contained their own Lurker URL in the signature!
On Mon, 1 Feb 2016 10:37:47 +0100
Didier Kryn wrote:
> You should use --no-install-recommends in apt-get. It is
> possible to configure apt-get to proceed like this by default but
> I've no expertise in how to configure it. In synaptic, you can set
> this behaviour in config/preferences/gene
Le 01/02/2016 12:09, Florian Zieboll a écrit :
florian@nulldevice:~$ cat /etc/apt/apt.conf.d/01norecommend
APT::Install-Recommends "0";
APT::Install-Suggests "0";
#APT::AutoRemove::RecommendsImportant "0";
Synaptic will override this setting, if the relevant option is checked.
Apparently s
On Mon, 1 Feb 2016 12:47:51 +0100
Didier Kryn wrote:
> Apparently synaptic keeps its config in its own config file
> /etc/apt/apt.conf.d/99synaptic. Do you mean synaptic reads all config
> files in order, and since 99synaptic is the last, it can override all
> previous settings?
For the
On 02/01/2016 09:24 AM, Noel Torres wrote:
>
> For familiar reasons I'm not able to continue working in the beautiful
> Devuan News work I started, but I love to know that it continues alive.
> Reading it is my main point of connection with the Devuan community and
> as such I need it to continue.
Florian Zieboll wrote:
> For the fun of it, I just ran an "apt-get install --install-recommends
> --no-install-recommends" and it chose to not install the recommends.
> The same with contradicting lines in apt.conf(.d/*):
>
> APT::Install-Recommends "0";
> APT::Install-Recommends "1";
>
> Thi
On 02/01/2016 10:49 AM, Florian Zieboll wrote:
>
> Can Mailman predict the URL under which Lurker will archive the message
> it is processing "on the fly", or is there even a variable available?
>
> Quoting and referencing "third party" messages would be so much easier,
> if mails contained thei
On Mon, 1 Feb 2016 13:13:43 +
Simon Hobson wrote:
> Florian Zieboll wrote:
>
> > As with any of these newish "*.d/" folders, you can just
> >
> > $ cat apt.conf.d/* > apt.conf && rm -r apt.conf.d/
> >
> > without any consequences regarding the configuration. AFAIU this is
> > all about
Le 01/02/2016 14:13, Simon Hobson a écrit :
Florian Zieboll wrote:
For the fun of it, I just ran an "apt-get install --install-recommends
--no-install-recommends" and it chose to not install the recommends.
The same with contradicting lines in apt.conf(.d/*):
APT::Install-Recommends "0";
Didier Kryn writes:
> Le 31/01/2016 14:28, Edward Bartolo a écrit :
>> The question is how do memory managers succeed to remain efficient and
>> yet cope with memory allocation of so many different sizes?
>
> I doubt they're efficient.
>
> If you really need an efficient memory allocator -
Rainer Weikusat writes:
[...]
> A more problematic (for some definition of problematic) situation is
> when there are many objects of different sizes and if objects whose
> size is identical have vastly differing lifetimes. This introduces
> so-called 'external fragmentation' into the malloc hea
Le 01/02/2016 17:16, Rainer Weikusat a écrit :
Rainer Weikusat writes:
[...]
A more problematic (for some definition of problematic) situation is
when there are many objects of different sizes and if objects whose
size is identical have vastly differing lifetimes. This introduces
so-called 'e
On Mon, Feb 01, 2016 at 05:36:38PM +0100, Didier Kryn wrote:
[cut]
>
> Note that if you manage your memory pool as an array then
> allocation and deallocation are extremely fast and can be done
> without consuming a single byte for book-keeping. I think this
> almost trivial allocator actual
Didier Kryn writes:
> Le 01/02/2016 17:16, Rainer Weikusat a écrit :
>> Rainer Weikusat writes:
>>
>> [...]
>>
>>> A more problematic (for some definition of problematic) situation is
>>> when there are many objects of different sizes and if objects whose
>>> size is identical have vastly differi
KatolaZ writes:
> On Mon, Feb 01, 2016 at 05:36:38PM +0100, Didier Kryn wrote:
>
> [cut]
>
>>
>> Note that if you manage your memory pool as an array then
>> allocation and deallocation are extremely fast and can be done
>> without consuming a single byte for book-keeping. I think this
>> alm
Steve Litt writes:
> On Sun, 31 Jan 2016 18:20:12 -0500
> Steve Litt wrote:
[...]
> ===
> #!/bin/sh
> lineno=${1:-1}
>
> fn=`mktemp`
>
> ip -o link | \
> cut -d ' ' -f2 | \
> grep ^w | \
> tr -d : > $fn
>
> maxdev=`wc -l $fn | cut -d ' ' -f 1`
> if
On Mon, 1 Feb 2016 15:58:36 +0100
Didier Kryn wrote:
> On my laptop the file 99synaptic contains only one line:
> APT::Install-Recommends "false";
>
> If all the files are read by all apt tools, then the setting
> meant for synaptic applies to all apt tools. If i'd purge synaptic,
> th
Le 31/01/2016 23:59, Go Linux a écrit :
I must check
for default-jre and gimp because both are pretty usefull.
Yep, default-jre, default-jre-headless and gimp are installed. If I
try to remove libsystemd0, it only requires to remove also gvfs,
gvfs-daemons and gvfs-fuse, but, as explained
On Sat, 2016-01-30 at 17:03 +, Nuno Magalhães wrote:
> +1
> seems like kindergarten in here
Think this is the best response yet in this overlong thread. Somebody
said something kinda childish and offtopic and a polite corrective
nudge to be a bit more adult was called for and should have end
Le 01/02/2016 17:52, Rainer Weikusat a écrit :
there's a known upper bound for the maximum number of objects which will
be needed
Some applications need to asynchronously create and destroy large
numbers of objects while the total number of objects at any given time
remains bounded. Creatin
When running the alpha4 install for my x686, it displays the error,
"e100/d101m_ucode.bin nonfree driver missing" and invites me to install it from
a floppy. But the installation continues and downloads the installation
programs it needs, stopping before setting up users to again reques
Didier Kryn writes:
> Le 01/02/2016 17:52, Rainer Weikusat a écrit :
>> there's a known upper bound for the maximum number of objects which will
>> be needed
>
> Some applications need to asynchronously create and destroy large
> numbers of objects while the total number of objects at any give
John Morris writes:
> On Sat, 2016-01-30 at 17:03 +, Nuno Magalhães wrote:
>
>> +1
>> seems like kindergarten in here
>
> Think this is the best response yet in this overlong thread. Somebody
> said something kinda childish and offtopic and a polite corrective
> nudge to be a bit more adult w
Le 01/02/2016 22:38, Rainer Weikusat a écrit :
Didier Kryn writes:
Le 01/02/2016 17:52, Rainer Weikusat a écrit :
there's a known upper bound for the maximum number of objects which will
be needed
Some applications need to asynchronously create and destroy large
numbers of objects while
On Mon, Feb 01, 2016 at 04:59:37PM +, Rainer Weikusat wrote:
[cut]
>
> The original slab allocator was implemented by Jeff Bonwick for the
> SunOS kernel (5, not 4) and it decidedly didn't work in this way. It
> used type-segregated, linked free lists and was based on some kind of
> underlyi
On Mon, 1 Feb 2016 15:36:26 -0600
TN wrote:
> When running the alpha4 install for my x686, it displays the
> error, "e100/d101m_ucode.bin nonfree driver missing" and invites me
> to install it from a floppy.
Debian does not include proprietary (non-free) software and I don't
know about the
Hi all,
It seems you can delete EFI vars if you're not careful. Someone found that
executing "rm -rf --no-preserve-root /" also deleted EFI vars, turning his MSI
Notebook into a brick.
It also seems mounting these is hardcoded into systemd:
https://bbs.archlinux.org/viewtopic.php?id=207549
efib
On 02/01/2016 06:12 PM, Wim wrote:
> Hi all,
>
> It seems you can delete EFI vars if you're not careful. Someone found
> that executing "rm -rf --no-preserve-root /" also deleted EFI vars,
> turning his MSI Notebook into a brick.
>
> It also seems mounting these is hardcoded into systemd:
>
> h
On 02/01/2016 08:59 PM, Clarke Sideroad wrote:
> On 02/01/2016 06:12 PM, Wim wrote:
>> Hi all,
>>
>> It seems you can delete EFI vars if you're not careful. Someone found
>> that executing "rm -rf --no-preserve-root /" also deleted EFI vars,
>> turning his MSI Notebook into a brick.
>>
>> It also
On 02/02/16 01:58, Didier Kryn wrote:
Le 01/02/2016 14:13, Simon Hobson a écrit :
Florian Zieboll wrote:
For the fun of it, I just ran an "apt-get install --install-recommends
--no-install-recommends" and it chose to not install the recommends.
The same with contradicting lines in apt.conf(.d
On 02/02/16 00:13, Simon Hobson wrote:
Florian Zieboll wrote:
For the fun of it, I just ran an "apt-get install --install-recommends
--no-install-recommends" and it chose to not install the recommends.
The same with contradicting lines in apt.conf(.d/*):
APT::Install-Recommends "0";
APT::
On 01/02/16 22:47, Didier Kryn wrote:
Le 01/02/2016 12:09, Florian Zieboll a écrit :
florian@nulldevice:~$ cat /etc/apt/apt.conf.d/01norecommend
APT::Install-Recommends "0";
APT::Install-Suggests "0";
#APT::AutoRemove::RecommendsImportant "0";
Synaptic will override this setting, if the relevan
34 matches
Mail list logo
