Tijnema wrote:
> Ok, I see this is all going about nothing..
> if someone says:
>
>> Please do not top post
>>
>
> lines... if you really want to save bandwidth, remove the default sig
> from this mailing list...
>
Umm... the primary thing about top-posting is not bandwidth. It's about
Ok, I see this is all going about nothing..
if someone says:
> Please do not top post
it does have reference to the above mistake right? the top posting is
done there right? So is it really irrelevant information?
And you guys are shouting about 50 lines c'mon, it's not 1000s
lines... if you r
Eric Stout wrote:
> 3: But do not include the entire original!
>
> 4: To prevent hideously long posts with a minimal account of new text, it
> is good Usenet practice to remove the non-relevant parts and optionally
> summarize the relevant parts of the original post, with regard to one's
> reply.
> Get a good mail client which doesn't automatically show all bullshit
> above, like Gmail.
Adjust your attitude.
For personal, legal, and corporate reasons, the only email access I have
that's 24/7 is to run pine on a workstation currently located 4300 miles
north west of me.
Don't try to chang
> >If this is a mailing list: DO NOT TOP POST! why?:
> >http://www.caliburn.nl/topposting.html
>
> If you're advocating not top-posting due to [n]etiquette, how can you not
> advocate trimming replies, when it's IMHO just as important for good
> [n]etiquette?
Not to mention that what he linked to
Rumor has it that Tijnema may have mentioned these words:
>On 8/17/07, Randy McMurchy <[EMAIL PROTECTED]> wrote:
> >
> > Please trim the quoted material to what is relevant.
> >
> > --
> > Randy
> >
>
>Get a good mail client which doesn't automatically show all bullshit
>above, like Gmail.
So you'
On 8/17/07, Randy McMurchy <[EMAIL PROTECTED]> wrote:
> rblythe wrote these words on 08/16/07 16:56 CST:
>
> > [snip 53 lines of stuff having nothing to do with the reply]
> >
> > Please do not top post
>
> Please trim the quoted material to what is relevant.
>
> --
> Randy
>
Get a good mail clien
rblythe wrote these words on 08/16/07 16:56 CST:
> [snip 53 lines of stuff having nothing to do with the reply]
>
> Please do not top post
Please trim the quoted material to what is relevant.
--
Randy
rmlscsi: [bogomips 1003.27] [GNU ld version 2.16.1] [gcc (GCC) 4.0.3]
[GNU C Library stable r
On 8/16/07, rblythe <[EMAIL PROTECTED]> wrote:
> Clyde Forrester wrote:
> > I am proceeding on the principle that sudo is in place for a security
> > reason. If I am doing an end run around all this sudoing then I'm doing
> > an end run around security. Sure, sometimes there's a reason to do that,
Clyde Forrester wrote:
> I am proceeding on the principle that sudo is in place for a security
> reason. If I am doing an end run around all this sudoing then I'm doing
> an end run around security. Sure, sometimes there's a reason to do that,
> but I'm not that good yet. Thanks for the tip for
Shane Shields wrote:
> On Thursday 16 August 2007 9:54:14 pm Alan Lord wrote:
>> Once that is done, you can just type "su" and you will become "root".
>
> Short and sweet.
>
> sudo -i
>
> :)
>
Cool :-)
I never knew that! (Guess I should have RTFMP (Read the Flipping Man Page))
Thanks.
--
ht
On Thursday 16 August 2007 9:54:14 pm Alan Lord wrote:
> Once that is done, you can just type "su" and you will become "root".
Short and sweet.
sudo -i
:)
--
Shane Shields
Registered LFS Compiler: 7582
To drink the WINE of success you must first seek the sayings of source
Anyone sending unwa
I am proceeding on the principle that sudo is in place for a security
reason. If I am doing an end run around all this sudoing then I'm doing
an end run around security. Sure, sometimes there's a reason to do that,
but I'm not that good yet. Thanks for the tip for when I am that good.
For now I
Yes. The 'cd' was the critical part which I overlooked.
The notice was even marked "Important".
Go figure. :-)
Maybe I was subconsciously interpreting the ! icon as "not". As in NOT
Important. :-)
Clyde Forrester
Trent Shea wrote:
> On Thursday 16 August 2007 12:05, Clyde Forrester wrote:
>
Clyde Forrester wrote:
> Now the pickiness. In part 2.3 I'm guessing I should be root when making
> partitions. Maybe I missed it. It doesn't seem to say. Of course I can
> never really be root. I have to sudo wherever it is appropriate.
That's not actually true...
Open a terminal and type:
s
On Thursday 16 August 2007 12:05, Clyde Forrester wrote:
> mkdir -v ../binutils-build
> cd ../binutils-build
> ../binutils-2.16.1/configure yadda yadda yadda
There is an important message in the Chapter 5 Introduction:
Before issuing the build instructions for a package, the package should be
un
Aw, beauty! That worked well!
Except that sudo has a snit fit over "export".
(I should explain that while I'm saying that, that I have a big dippy
grin on my face. The reason being that every time I trip over something
like that, I'm learning yet another thing which will put me on the path
to be
Until you get to the bit where it tells you to set up the lfs user, sudo
everything.
Btw if you want a root shell, sudo su
On Wed, 2007-08-15 at 16:56 -0500, Clyde Forrester wrote:
> I'm on my third attempt at LFS, so I'm going to get picky as I read through.
>
> First some history. My first attem
I'm on my third attempt at LFS, so I'm going to get picky as I read through.
First some history. My first attempt at LFS was from a 64 bit Ubuntu.
Wasn't possible. Second attempt was CLFS and I bogged down. Now I have
32 bit Kubuntu (on a 64 bit AMD).
Now the pickiness. In part 2.3 I'm guessing
19 matches
Mail list logo
