Re: [DNG] Studying C as told. (For help)
Hi,
Steve Litt wrote:
<<
> Bitwise Operators:
>
> Pg 63:
> /* getbits: get n bits from position p */
>
> unigned int getbits(unsigned int x, int p, int n)
> {
>return (x >> (p + 1 - n)) & ~(~0 << n);
> }
Stuff like this is the reason I soon abandoned K&R as a learning tool,
and used it only to determine the official behavior of C.
>>
It was a mental struggle but I understood it. Bitwise operations can
be useful in some circumstances. I remember when I was still a youth,
I used to find an irresistible challenge in any examination question
saying, "the proof of this formula is beyond the scope of this exam".
This book will offer its challenges like those 'irresistible formulae'
of my youth, but those challenges, should eventually ripen my C coding
ability.
Steve Litt wrote:
<<
Save your brainpower for pointers to functions. That's actually
massively useful, and extremely difficult.
>>
I assume these are whatDelphi Pascal offers as procedural pointers.
They are an extremely powerful programming feature that gives
polymorphic-like properties to code.
Here is the result of your "temptation":
#include
int (*fn_ptr)(int a);
int func1(int a) {
return a*a;
}
int func2(int b) {
return b/2;
}
int main() {
fn_ptr = &func1;
printf("12 passed to func1 is: %d\n", fn_ptr(12));
fn_ptr = &func2;
printf("12 passed to func2 is: %d\n", fn_ptr(12));
return 0;
}
Irrwahn wrote:
<<
IMHO the people that (ab)used Dijkstra's famous essay (with
the original title "A Case Against the Goto Statement") as
the foundation of some kind of religion did him and the
programming community as a whole a bad service. For the
interested, David Tribble's "Go To Statement Considered
Harmful: A Retrospective"[4] makes for a good read.
>>
I use goto in one circumstance that helps make code simple to write
and understand. This is when code makes a series of tests with every
test causing the execution flow to jump down to the same point.
The pseudo-code is something like this: [ Note that code is jumping
always down ]
if test1 ready goto A;
if test2 ready goto A;
if test3 ready goto A;
...
if testN ready goto A;
more code here
Lable A:
execution continues from here
This can still be done by something like this:
do {
if (test1) break;
if (test2) break;
if (test3) break;
...
if (testN) break;
more code here
} while (0);
execution continues from here
Edward
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Studying C as told. (For help)
On Sat, 25 Jun 2016 01:21:33 +0200 Irrwahn wrote: > For the > interested, David Tribble's "Go To Statement Considered > Harmful: A Retrospective"[4] makes for a good read. > > > [1] NB: "break" and "continue" are just "goto" in disguise. > > [2] For example in the notorious case of releasing resources > in reverse order of allocation in the event of an error. > > [3] Lame attempt at translating a witticism once made by a > German politician. > > [4] http://david.tribble.com/text/goto.html Ugh! I knew to be skeptical when the author, in the 3rd paragraph, called the evilness of goto a "myth". Agenda alert! First of all, we all need to get on the same page as to what we're talking about. By my definitions, "break" and "continue" and for that matter exit(1) or exit 1 and exceptions are in no way gotos in disguise. They're program counter alterations that break modularity (which goto does too), but break it in a very predictable and reasonably unharmful way. Real goto statements, with labels you can put anywhere, are extremely prone to utter destruction of modularity. I know: I started programming with gotos, because I started designing with flowcharts. With a flowchart based design, flow control ricochets around like a laser pen in a house of mirrors. If you like systemd, you'll love flowchart based design. And of course, the way to implement flowchart based design in code is with gotos. The Flowchart fellows of the 1960s/70's were clever: In many cases too clever for their own good. They were clever enough to make it, but not to debug it. And because the functional decomposition design method that I replaced flowcharts with was much more productive, they lost out in the marketplace to more productive programmers. If you want to see my opinion on gotos and flowcharts, and how I came upon this opinion, go to http://www.troubleshooters.com/lpm/200310/200310.htm, search for "Whomping Out the Code", and read the next two paragraphs. If one uses gotos, one must be VERY careful. It's called spaghetti programming for a reason. Then there's the old excuse "well, you might need to escape a deeply nested loop. No problem, encapsulate the outer loop from which you want to escape in a function, and use the return statement wherever you want to bust out of the nested loop. If some cleanup needs to be done before the loop-bust, call the cleanup as another function. Or if you want to bust out of the whole program, use exit() or an exception. Just don't use a goto with a label. Because someday some well meaning but dumb maintenance programmer will put code between the end of the outer loop and the label, and then all hell will break loose. If you look at the article's annotated Dijkstra essay, Dijkstra repeatedly says "goto statement", not just "goto" as a concept. He wasn't talking about break, nor continue, nor return, nor an exception. Break, continue, return, exit() and exceptions perform a jump without a corresponding "return from subroutine", which is unmodular and unstructured, but they jump to places specified by their placement in the program, not specified by some label the programmer can place absolutely anywhere. I'm not kidding: My programming ability improved by over an order of magnitude when I stopped using goto statements with moveable labels, and in my opinion anyone wanting to use a goto with a moveable label should explain in detail why he can't achieve the same result with structures such as break, continue, return, exit(), an exception, or the real structured solution: Loops with flags that can be turned false, and if statements such that nothing from the current loop is executed after the flag is turned false. SteveT Steve Litt June 2016 featured book: Troubleshooting: Why Bother? http://www.troubleshooters.com/twb ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Studying C as told. (For help)
I think, In this discussion about 'goto' we are forgetting one important fact about it. This is, the fact that 'goto' is simply a jump and a corresponding lable. This makes 'goto' jumps possible at any point in code which is absolutely not necessary. Evolving from simple 'goto' and lable statements, got rid of many situations where goto would have made code difficult to conceptualise as composed of modules. The idea behind goto is not absolutely technical but a consequence of how our minds work. Goto was replaced by functions, break, continue and exit: the reason is that way the human mind can more efficiently organize and visualise code parts according to its local purpose. I think, we should not forget that our brains are essentially pattern recognizing "neural computers": goto breaks recognition of those patterns rendering code a mess of unrelated bits, hence the term, spaghetti code. Edward On 25/06/2016, Steve Litt wrote: > On Sat, 25 Jun 2016 01:21:33 +0200 > Irrwahn wrote: > >> For the >> interested, David Tribble's "Go To Statement Considered >> Harmful: A Retrospective"[4] makes for a good read. >> >> >> [1] NB: "break" and "continue" are just "goto" in disguise. >> >> [2] For example in the notorious case of releasing resources >> in reverse order of allocation in the event of an error. >> >> [3] Lame attempt at translating a witticism once made by a >> German politician. >> >> [4] http://david.tribble.com/text/goto.html > > Ugh! > > I knew to be skeptical when the author, in the 3rd paragraph, called > the evilness of goto a "myth". Agenda alert! > > First of all, we all need to get on the same page as to what we're > talking about. By my definitions, "break" and "continue" and for that > matter exit(1) or exit 1 and exceptions are in no way gotos in disguise. > They're program counter alterations that break modularity (which goto > does too), but break it in a very predictable and reasonably unharmful > way. Real goto statements, with labels you can put anywhere, are > extremely prone to utter destruction of modularity. I know: I started > programming with gotos, because I started designing with flowcharts. > > With a flowchart based design, flow control ricochets around like a > laser pen in a house of mirrors. If you like systemd, you'll love > flowchart based design. And of course, the way to implement flowchart > based design in code is with gotos. The Flowchart fellows of the > 1960s/70's were clever: In many cases too clever for their own good. > They were clever enough to make it, but not to debug it. And because > the functional decomposition design method that I replaced flowcharts > with was much more productive, they lost out in the marketplace to more > productive programmers. > > If you want to see my opinion on gotos and flowcharts, and how I came > upon this opinion, go to > http://www.troubleshooters.com/lpm/200310/200310.htm, search for > "Whomping Out the Code", and read the next two paragraphs. If one uses > gotos, one must be VERY careful. It's called spaghetti programming for > a reason. > > Then there's the old excuse "well, you might need to escape a deeply > nested loop. No problem, encapsulate the outer loop from which you want > to escape in a function, and use the return statement wherever you want > to bust out of the nested loop. If some cleanup needs to be done > before the loop-bust, call the cleanup as another function. Or if you > want to bust out of the whole program, use exit() or an exception. Just > don't use a goto with a label. Because someday some well meaning but > dumb maintenance programmer will put code between the end of the > outer loop and the label, and then all hell will break loose. > > If you look at the article's annotated Dijkstra essay, Dijkstra > repeatedly says "goto statement", not just "goto" as a concept. He > wasn't talking about break, nor continue, nor return, nor an exception. > Break, continue, return, exit() and exceptions perform a jump without a > corresponding "return from subroutine", which is unmodular and > unstructured, but they jump to places specified by their placement in > the program, not specified by some label the programmer can place > absolutely anywhere. > > I'm not kidding: My programming ability improved by over an order of > magnitude when I stopped using goto statements with moveable labels, > and in my opinion anyone wanting to use a goto with a moveable label > should explain in detail why he can't achieve the same result with > structures such as break, continue, return, exit(), an exception, or > the real structured solution: Loops with flags that can be turned > false, and if statements such that nothing from the current loop is > executed after the flag is turned false. > > SteveT > > Steve Litt > June 2016 featured book: Troubleshooting: Why Bother? > http://www.troubleshooters.com/twb > ___ > Dng mailing list > Dng@lists.dyne.org > https://mai
Re: [DNG] Studying C as told. (For help)
On Sat, Jun 25, 2016 at 09:27:40AM +0200, Edward Bartolo wrote:
[cut]
>
> execution continues from here
>
> This can still be done by something like this:
> do {
> if (test1) break;
> if (test2) break;
> if (test3) break;
> ...
> if (testN) break;
>
> more code here
> } while (0);
>
> execution continues from here
>
This can be even achieved using the switch/case statement
HND
KatolaZ
--
[ ~.,_ Enzo Nicosia aka KatolaZ - GLUGCT -- Freaknet Medialab ]
[ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ]
[ @) http://kalos.mine.nu --- Devuan GNU + Linux User ]
[ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ]
[ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ]
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] polkit - which one?
The outcome of this thread was that session management is possible without policykit, at the expense of few little hacks. Unfortunately, without policykit, the users are not allowed to mount removable media like usb memory sticks. Few years ago the permissions were handled in udev rules, but nowadays udev rules have shrinked to one rule in 70-persistent-net.rules. Seems that everything else is now done by default in udev and permissions are delegated to policykit. It might still be possible to manage permissions in udev, but I didn't try and re-installed policykit1, at least temporarily. Devuan's policykit1 doesn't depend on systemd, sure, but it remains a relatively obscure thing with its own configuration meta-language AFAIR, and it goes in the way in places where simple file permission would do a perfect job. It is clear, however, that some mechanism is needed to allow normal users to mount removable disk partitions and the traditional file permissions paradigm falls short in this case. Is there any other case? I guess when one double-clicks the removable media's icon, Xfec4 invokes /usr/bin/pkexec to get the permission. pkexec seems to be the CLI interface to Policykit. Therefore it might be possible to substitute Policykit with a hand-crafted script named /usr/bin/pkexec, invoking sudo, for example. Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Studying C as told. (For help)
Irrwahn: ... > [4] http://david.tribble.com/text/goto.html As an mental exercise, look at part II in the above, and make programs for if/while etc. with labels and goto's. E.g. a general loop is loop_init(); loop_start: loop_pre(); if (condition()) goto loop_start; else goto loop_end; loop_post(); loop_end: for a while loop, init and pre are empty for loop, pre is empty do-while, init and post are empty break is goto loop_end, continue is goto loop_start. Regards, /Karl Hammar --- Aspö Data Lilla Aspö 148 S-742 94 Östhammar Sweden +46 173 140 57 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Studying C as told. (For help)
John Morris: ... > Or you are doing the sort of things most C code written these days > does. My last C program was taking to an RFID writer over a serial > port to implement ISO 28560 standard library article tags. Bit > fiddling is useful when the storage available on a typical RFID tag is > less than a tweet. I have examples in: http://turkos.aspodata.se/git/c/libaspoprotocol/ for anyone interested. Regards, /Karl Hammar --- Aspö Data Lilla Aspö 148 S-742 94 Östhammar Sweden +46 173 140 57 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Fwd: Studying C as told. (For help)
om: Edward Bartolo
Hi,
On 25/06/2016, KatolaZ wrote:
> On Sat, Jun 25, 2016 at 09:27:40AM +0200, Edward Bartolo wrote:
>
> [cut]
>
>>
>> execution continues from here
>>
>> This can still be done by something like this:
>> do {
>> if (test1) break;
>> if (test2) break;
>> if (test3) break;
>> ...
>> if (testN) break;
>>
>> more code here
>> } while (0);
>>
>> execution continues from here
>>
>
> This can be even achieved using the switch/case statement
>
> HND
>
> KatolaZ
Switch/case mandates "case constant-expression:" which is far more
restrictive compared to a series of if statements. 'If' can take ANY
expression as its control expression. This makes a whole difference in
its applicability field. I am NOT saying a switch statement is to be
avoided. In fact, in the source code of simple-netaid-backend, I used
it.
Edward
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Studying C as told. (For help)
Hi,
With a switch statement execution continues immediately after the
switch. My example also involved a chunk of code that followed the
series of if statements that was also skipped by the goto jump. A
switch statement cannot jump a successive number of lines but my
little example can. In fact, I used it back in 1995 when I programmed
an expression evaluator.
Edward
On 25/06/2016, Edward Bartolo wrote:
> om: Edward Bartolo
> Hi,
>
> On 25/06/2016, KatolaZ wrote:
>> On Sat, Jun 25, 2016 at 09:27:40AM +0200, Edward Bartolo wrote:
>>
>> [cut]
>>
>>>
>>> execution continues from here
>>>
>>> This can still be done by something like this:
>>> do {
>>> if (test1) break;
>>> if (test2) break;
>>> if (test3) break;
>>> ...
>>> if (testN) break;
>>>
>>> more code here
>>> } while (0);
>>>
>>> execution continues from here
>>>
>>
>> This can be even achieved using the switch/case statement
>>
>> HND
>>
>> KatolaZ
>
> Switch/case mandates "case constant-expression:" which is far more
> restrictive compared to a series of if statements. 'If' can take ANY
> expression as its control expression. This makes a whole difference in
> its applicability field. I am NOT saying a switch statement is to be
> avoided. In fact, in the source code of simple-netaid-backend, I used
> it.
>
> Edward
>
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] polkit - which one?
Am Sat, 25 Jun 2016 12:00:02 + schrieb Didier Kryn : Salut Didier! > Unfortunately, without policykit, the users are not allowed > to mount removable media like usb memory sticks. Few years ago the > permissions were handled in udev rules, but nowadays udev rules have > shrinked to one rule in 70-persistent-net.rules. Interesting. As for mounting without udev, i know there is spacefm which does it using its own mounting routine called udevil. Ok, it's not Thunar, but for all desktops using pcmanfm spacefm would be a nearly 1:1 substitute, if not even an improvement ... ;) Cheers. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] samba-libs package in Debian now depends on libsystemd0
The creeping continues. How difficult is it to repackage samba-libs without libsystemd0? Arthur. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Studying C as told. (For help)
Hi,
<<
A
switch statement cannot jump a successive number of lines but my
little example can.
>>
Rereading my previous email, I think this is a mistake on my part. A
switch's default clause can be used to execute such a number of lines.
The only thing that a switch cannot do is use a non-constant object as
its case control value.
I am sending this to avoid readers responding to explain something a
short reading about the switch statement can easily teach within a few
minutes.
Edward
On 25/06/2016, Edward Bartolo wrote:
> Hi,
>
> With a switch statement execution continues immediately after the
> switch. My example also involved a chunk of code that followed the
> series of if statements that was also skipped by the goto jump. A
> switch statement cannot jump a successive number of lines but my
> little example can. In fact, I used it back in 1995 when I programmed
> an expression evaluator.
>
> Edward
>
> On 25/06/2016, Edward Bartolo wrote:
>> om: Edward Bartolo
>> Hi,
>>
>> On 25/06/2016, KatolaZ wrote:
>>> On Sat, Jun 25, 2016 at 09:27:40AM +0200, Edward Bartolo wrote:
>>>
>>> [cut]
>>>
execution continues from here
This can still be done by something like this:
do {
if (test1) break;
if (test2) break;
if (test3) break;
...
if (testN) break;
more code here
} while (0);
execution continues from here
>>>
>>> This can be even achieved using the switch/case statement
>>>
>>> HND
>>>
>>> KatolaZ
>>
>> Switch/case mandates "case constant-expression:" which is far more
>> restrictive compared to a series of if statements. 'If' can take ANY
>> expression as its control expression. This makes a whole difference in
>> its applicability field. I am NOT saying a switch statement is to be
>> avoided. In fact, in the source code of simple-netaid-backend, I used
>> it.
>>
>> Edward
>>
>
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] samba-libs package in Debian now depends on libsystemd0
On Sat, 25 Jun 2016 18:20:19 +0930 Arthur Marsh wrote: > The creeping continues. > > How difficult is it to repackage samba-libs without libsystemd0? > > Arthur. My only Windows computer gets fired up less than two hours per month, so I have no need for Samba. I've long ago forgotten most of the Samba I knew, but at the turn of the century I knew a fair amount about it: http://www.barnesandnoble.com/w/samba-unleashed-steve-litt/1100840306 Back in those days, the only Samba code I saw that could have related to the init was the init scripts, and those weren't compiled in. Today I'd imagine there's an option for smbd and nmbd and any other Samba background processes to issue one of those systemd calls saying "I'm ready", and if so, you'd need a tiny shim to make Samba think you're giving it that functionality. Of course, I haven't used Samba in 15 years, and everything changes. SteveT Steve Litt June 2016 featured book: Troubleshooting: Why Bother? http://www.troubleshooters.com/twb ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] samba-libs package in Debian now depends on libsystemd0
On 25/06/16 15:25, Steve Litt wrote: On Sat, 25 Jun 2016 18:20:19 +0930 Arthur Marsh wrote: The creeping continues. How difficult is it to repackage samba-libs without libsystemd0? Arthur. My only Windows computer gets fired up less than two hours per month, so I have no need for Samba. I've long ago forgotten most of the Samba I knew, but at the turn of the century I knew a fair amount about it: http://www.barnesandnoble.com/w/samba-unleashed-steve-litt/1100840306 Back in those days, the only Samba code I saw that could have related to the init was the init scripts, and those weren't compiled in. Today I'd imagine there's an option for smbd and nmbd and any other Samba background processes to issue one of those systemd calls saying "I'm ready", and if so, you'd need a tiny shim to make Samba think you're giving it that functionality. Of course, I haven't used Samba in 15 years, and everything changes. SteveT Steve Litt June 2016 featured book: Troubleshooting: Why Bother? http://www.troubleshooters.com/twb ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng It is probably easier than that, the Samba 'configure' code has a '--without-systemd' switch. Just need to alter debian/rules etc Rowland ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] How to stop udev from re-ordering devices
Rainer Weikusat wrote: > I can neither count on being 'in control of hardware' nor on 'people > editing configuration files'. Then apologies, it appears I misunderstood your position. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] samba-libs package in Debian now depends on libsystemd0
On Sat, 25 Jun 2016 15:27:54 +0100 Rowland Penny wrote: > It is probably easier than that, the Samba 'configure' code has a > '--without-systemd' switch. > > Just need to alter debian/rules etc > > Rowland * * \ o / \|/ | C O O L / \ _ / \/ / - My suspicion is that the --without-systemd switch represents a huge defeat for Lennart and the Redhats. When Debian decided to switch in the summer of 2014, the systemd cartel were strutting and boasting that they would soon own the world. Now, 2 years later, Samba, a bedrock "killer app" for Linux, still has a --without-systemd compile option. If Redhat had truly succeeded in their plans, such an option would be unneeded and useless in 2016. SteveT Steve Litt June 2016 featured book: Troubleshooting: Why Bother? http://www.troubleshooters.com/twb ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] samba-libs package in Debian now depends on libsystemd0
On 25/06/16 17:34, Steve Litt wrote: On Sat, 25 Jun 2016 15:27:54 +0100 Rowland Penny wrote: It is probably easier than that, the Samba 'configure' code has a '--without-systemd' switch. Just need to alter debian/rules etc Rowland * * \ o / \|/ | C O O L / \ _ / \/ / - My suspicion is that the --without-systemd switch represents a huge defeat for Lennart and the Redhats. When Debian decided to switch in the summer of 2014, the systemd cartel were strutting and boasting that they would soon own the world. I don't really know how to tell you this, but the switch (along with its opposite '--with-systemd') was added to Samba by a red-hat employee. Rowland Now, 2 years later, Samba, a bedrock "killer app" for Linux, still has a --without-systemd compile option. If Redhat had truly succeeded in their plans, such an option would be unneeded and useless in 2016. SteveT Steve Litt June 2016 featured book: Troubleshooting: Why Bother? http://www.troubleshooters.com/twb ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] samba-libs package in Debian now depends on libsystemd0
Steve Litt wrote: > On Sat, 25 Jun 2016 15:27:54 +0100 > Rowland Penny wrote: > > > > It is probably easier than that, the Samba 'configure' code has a > > '--without-systemd' switch. > > > > Just need to alter debian/rules etc > > > > Rowland > >* * > \ o / > \|/ > | C O O L > / \ _ > / \/ >/ > - > > My suspicion is that the --without-systemd switch represents a huge > defeat for Lennart and the Redhats. When Debian decided to switch in > the summer of 2014, the systemd cartel were strutting and boasting that > they would soon own the world. > > Now, 2 years later, Samba, a bedrock "killer app" for Linux, still has > a --without-systemd compile option. If Redhat had truly succeeded in > their plans, such an option would be unneeded and useless in 2016. Hi Steve, Most everyone makes their code configurable. Only a few desktop developers, who need a lot of pixie dust, and e.g. Debian packagers, who tend to choose the --with-systemd options, or depend on other modules that require systemd. I got a different perspective on Red Hat when I listened to a short talk by Daniel Sterling, "Big Data on Little Linux," covering the many issues that arise in trying to grind through large data sets using Linux and NFS. Red Hat was called out as providing less buggy kernels and drivers needed when pushing the envelope. https://www.youtube.com/watch?v=QG9FIFKDKOU Joel > SteveT > > Steve Litt > June 2016 featured book: Troubleshooting: Why Bother? > http://www.troubleshooters.com/twb > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng -- Joel Roth ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Work with lists.dyne.org
Hi all! I've a question about how to work with the list: Is there a way to search an archive of lists and/or single messages for certain topics. Background: Some time ago i asked about overheating and i got some very helpful replies - but unfortunately i lost the file where i saved them :-( Thanks a lot in advance! ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Work with lists.dyne.org
W dniu 25.06.2016 o 19:19, emnin...@riseup.net pisze: Hi all! I've a question about how to work with the list: Is there a way to search an archive of lists and/or single messages for certain topics. Background: Some time ago i asked about overheating and i got some very helpful replies - but unfortunately i lost the file where i saved them :-( Thanks a lot in advance! ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng Hi, You could search archive here https://lists.dyne.org/lurker/list/dng.en.html Regard, Paweł ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] samba-libs package in Debian now depends on libsystemd0
Le 25/06/2016 18:34, Steve Litt a écrit : On Sat, 25 Jun 2016 15:27:54 +0100 Rowland Penny wrote: >It is probably easier than that, the Samba 'configure' code has a >'--without-systemd' switch. > >Just need to alter debian/rules etc > >Rowland * * \ o / \|/ | C O O L / \ _ / \/ / - My suspicion is that the --without-systemd switch represents a huge defeat for Lennart and the Redhats. When Debian decided to switch in the summer of 2014, the systemd cartel were strutting and boasting that they would soon own the world. Now, 2 years later, Samba, a bedrock "killer app" for Linux, still has a --without-systemd compile option. If Redhat had truly succeeded in their plans, such an option would be unneeded and useless in 2016. Yet I would prefer if there was a --with-systemd option and the default was without :-) Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
