OK, so how about we host the book list on lopsa.org? Perhaps under
LOPSA Community? Call the page "Guide to SA Body of Knowledge" ?
How's that sound?
What would that mean for future edits of the page? Would changes have
to go through the LOPSA tech team?
Best,
-at
_
On Tue, Feb 1, 2011 at 20:58, Doug Hughes wrote:
> On 2/1/2011 9:06 PM, da...@lang.hm wrote:
>> On Tue, 1 Feb 2011, Steven Kurylo wrote:
>>
>>> It sounds like a wiki, editable by lopsa members, is called for here.
>>>
>>> Though its probably better starting with small specifics (like listing
>>
On Wed, 2 Feb 2011, Craig Miskell wrote:
> da...@lang.hm wrote:
>> On Tue, 1 Feb 2011, da...@lang.hm wrote:
>>> On Wed, 2 Feb 2011, Craig Miskell wrote:
And it wouldn't hurt for the Editors, or suitable qualified and
acknowledged
Experts to initiate articles/pages with their underst
On Mon, Jan 31, 2011 at 10:02 PM, Mark McCullough wrote:
>
> On 2011 Jan 31, at 20:24, da...@lang.hm wrote:
>> on a desktop you may want to allow users to install things themselves (but
>> then again you may not, it depends on the organization), but on servers you
>> almost never want to allow t
On Tue, Feb 1, 2011 at 7:59 PM, Steven Kurylo
wrote:
>
> It sounds like a wiki, editable by lopsa members, is called for here.
>
> Though its probably better starting with small specifics (like listing
> books, like the swap discussion), because I feel we may end up
> debating all day what the bou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
da...@lang.hm wrote:
> On Tue, 1 Feb 2011, da...@lang.hm wrote:
>> On Wed, 2 Feb 2011, Craig Miskell wrote:
>>> And it wouldn't hurt for the Editors, or suitable qualified and
>>> acknowledged
>>> Experts to initiate articles/pages with their understan
On Tue, 1 Feb 2011, Doug Hughes wrote:
> On 2/1/2011 9:06 PM, da...@lang.hm wrote:
>> On Tue, 1 Feb 2011, Steven Kurylo wrote:
>>
The guide would also define what system administration is, what the
boundaries of the field are, and what other fields are adjacent to system
administrat
On Tue, 1 Feb 2011, da...@lang.hm wrote:
> On Wed, 2 Feb 2011, Craig Miskell wrote:
>
>> da...@lang.hm wrote:
>>> On Tue, 1 Feb 2011, Steven Kurylo wrote:
It sounds like a wiki, editable by lopsa members, is called for here.
Though its probably better starting with small specifics (
On 2/1/2011 9:06 PM, da...@lang.hm wrote:
> On Tue, 1 Feb 2011, Steven Kurylo wrote:
>
>>> The guide would also define what system administration is, what the
>>> boundaries of the field are, and what other fields are adjacent to system
>>> administration.
>>>
>>> This is something I've been meanin
On Wed, 2 Feb 2011, Craig Miskell wrote:
> da...@lang.hm wrote:
>> On Tue, 1 Feb 2011, Steven Kurylo wrote:
>>> It sounds like a wiki, editable by lopsa members, is called for here.
>>>
>>> Though its probably better starting with small specifics (like listing
>>> books, like the swap discussion),
On Tue, 1 Feb 2011, Stephen P. Schaefer wrote:
> On Mon, 31 Jan 2011 17:09 -0800, da...@lang.hm wrote:
>
>>
>> checkinstall will watch what the make install step would do, and capture
>> the changes into a package (either .deb or .rpm)
>>
>
> THANK YOU! I hadn't heard of checkinstall before and I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
da...@lang.hm wrote:
> On Tue, 1 Feb 2011, Steven Kurylo wrote:
>> It sounds like a wiki, editable by lopsa members, is called for here.
>>
>> Though its probably better starting with small specifics (like listing
>> books, like the swap discussion), b
On Tue, 1 Feb 2011, Steven Kurylo wrote:
>> The guide would also define what system administration is, what the
>> boundaries of the field are, and what other fields are adjacent to system
>> administration.
>>
>> This is something I've been meaning to write but haven't gotten to yet.
>>
>> Here's
> The guide would also define what system administration is, what the
> boundaries of the field are, and what other fields are adjacent to system
> administration.
>
> This is something I've been meaning to write but haven't gotten to yet.
>
> Here's the first part, the literature.
It sounds like
On Tue, Feb 1, 2011 at 12:00 PM, Craig Miskell wrote:
>
> Aaron McCaleb wrote:
>> How is any novice supposed to know that one course of action is
>> preferable to another? How is any novice supposed to know that they
>> should trust one source of information in one circumstance vs. another
>> sou
On Mon, 31 Jan 2011 17:09 -0800, da...@lang.hm wrote:
>
> checkinstall will watch what the make install step would do, and capture
> the changes into a package (either .deb or .rpm)
>
THANK YOU! I hadn't heard of checkinstall before and I'll give it a
whirl on my very next opportunity. Do yo
On Tue, 1 Feb 2011, Aaron McCaleb wrote:
On Tue, Feb 1, 2011 at 15:43, Michael Ryder wrote:
Incidentally... there has got to be a repository somewhere of *nix
best practices? Is there?
If there is, then as Dave hinted, I would guess at least 70% of the
information in such a collection is o
On Tue, 1 Feb 2011, John H. Robinson, IV wrote:
> Aaron McCaleb wrote:
>> On Tue, Feb 1, 2011 at 15:43, Michael Ryder wrote:
>>> Incidentally... there has got to be a repository somewhere of *nix
>>> best practices? ?Is there?
>>
>> If there is, then as Dave hinted, I would guess at least 70% of
On Tue, 1 Feb 2011, Paul Graydon wrote:
> On 02/01/2011 11:24 AM, da...@lang.hm wrote:
>>
>> agreed, espcially because for every "Thou shall always..." there is going
>> to be some situation where different constrainsts mean that the best thing
>> to do for that particular situation is to violate
Aaron McCaleb wrote:
> On Tue, Feb 1, 2011 at 15:43, Michael Ryder wrote:
> > Incidentally... there has got to be a repository somewhere of *nix
> > best practices? ?Is there?
>
> If there is, then as Dave hinted, I would guess at least 70% of the
> information in such a collection is out of date
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Graydon wrote:
> On 02/01/2011 11:24 AM, da...@lang.hm wrote:
>> agreed, espcially because for every "Thou shall always..." there is going
>> to be some situation where different constrainsts mean that the best thing
>> to do for that particular s
On Tue, Feb 1, 2011 at 15:43, Michael Ryder wrote:
> Incidentally... there has got to be a repository somewhere of *nix
> best practices? Is there?
>
If there is, then as Dave hinted, I would guess at least 70% of the
information in such a collection is out of date. :( So much of the
stuff tha
On 02/01/2011 11:24 AM, da...@lang.hm wrote:
>
> agreed, espcially because for every "Thou shall always..." there is going
> to be some situation where different constrainsts mean that the best thing
> to do for that particular situation is to violate the rule.
>
> In addition, some rules become in
On Tue, Feb 1, 2011 at 4:24 PM, wrote:
> If you know the "Why" of the rule you can do so with your eyes open,
> making the decision on the pros and cons of doing so. If the "Why" is "I
> was told to in my training class" you can't do so, and people tend to go
> one of two ways:
> ...
> In additio
On Wed, 2 Feb 2011, Craig Miskell wrote:
> Aaron McCaleb wrote:
>> How is any novice supposed to know that one course of action is
>> preferable to another? How is any novice supposed to know that they
>> should trust one source of information in one circumstance vs. another
>> source in a differ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aaron McCaleb wrote:
> How is any novice supposed to know that one course of action is
> preferable to another? How is any novice supposed to know that they
> should trust one source of information in one circumstance vs. another
> source in a differe
On Mon, Jan 31, 2011 at 22:46, wrote:
> Building from source is unrepeatable because you haven't
> purchased a Deterministic FSM - you're running a Dell. Those are not
> instructions - think of them as guidelines. =;^)
Deterministic Flying Spaghetti Monster? only kidding!
Michael Ryder wrote:
27 matches
Mail list logo
