On 8/17/07, Randy McMurchy <[EMAIL PROTECTED]> wrote:
> Clyde Forrester wrote these words on 08/16/07 17:53 CST:
>
> > One point, it would appear, is that if my working directory is an
> > isolated subdirectory, and if it's something experimental which goes
> > bad, then I can simply step out of th
Clyde Forrester wrote these words on 08/16/07 17:53 CST:
> One point, it would appear, is that if my working directory is an
> isolated subdirectory, and if it's something experimental which goes
> bad, then I can simply step out of the isolated working directory and
> nuke it from orbit.
Corr
Tijnema wrote:
> On 8/17/07, Randy McMurchy <[EMAIL PROTECTED]> wrote:
>
>> Tijnema wrote these words on 08/16/07 17:33 CST:
>>
>>
>>> Not with the instructions "copy-and-pasted" from the book ;)
>>>
>>> And btw, it will give a lot of trouble :P it will overwrite each
>>> makefile, log file
lists wrote these words on 08/17/07 17:35 CST:
> true, but typing ./configure is easier than typing
> /path/to/source/tree/configure
I suppose. But my reply wasn't about what was easiest. It was to
point out that the post I replied to was not accurate.
--
Randy
rmlscsi: [bogomips 1003.27] [GN
On 8/17/07, Randy McMurchy <[EMAIL PROTECTED]> wrote:
> Tijnema wrote these words on 08/16/07 17:33 CST:
>
> > Not with the instructions "copy-and-pasted" from the book ;)
> >
> > And btw, it will give a lot of trouble :P it will overwrite each
> > makefile, log files and build files from the previ
Clyde Forrester wrote these words on 08/16/07 17:42 CST:
> So... (bottom posting, of course)... (sorry if I'm being dense)...
> normally I would be in the newly unpacked foo.1.2.3 directory, and doing
> my configure, make, make install? Whereas in chapter 5, by creating a
> foo-build directory
Tijnema wrote:
> On 8/17/07, Clyde Forrester <[EMAIL PROTECTED]> wrote:
>
>> Now that I've given it some more thought: Why does one cd to the newly
>> created package directory after unpacking it (in Chapter 5)? Is it
>> simply to make sure that the directory exists? Or is it the stub end of
>>
Tijnema wrote these words on 08/16/07 17:33 CST:
> Not with the instructions "copy-and-pasted" from the book ;)
>
> And btw, it will give a lot of trouble :P it will overwrite each
> makefile, log files and build files from the previous package etc,
> ending up with one big directory of 1000s of
Randy McMurchy wrote:
> Tijnema wrote these words on 08/16/07 17:25 CST:
>
>
>> Well, you need to be in that directory to be able to run configure,
>> make and all other instructions ;-)
>>
>
> Technically, that is not true. With most packages (properly packaged
> ones anyway), you can run
On 8/17/07, Randy McMurchy <[EMAIL PROTECTED]> wrote:
> Tijnema wrote these words on 08/16/07 17:25 CST:
>
> > Well, you need to be in that directory to be able to run configure,
> > make and all other instructions ;-)
>
> Technically, that is not true. With most packages (properly packaged
> ones
Tijnema wrote these words on 08/16/07 17:25 CST:
> Well, you need to be in that directory to be able to run configure,
> make and all other instructions ;-)
Technically, that is not true. With most packages (properly packaged
ones anyway), you can run the build commands from anywhere you like.
Yo
On 8/17/07, Clyde Forrester <[EMAIL PROTECTED]> wrote:
> Now that I've given it some more thought: Why does one cd to the newly
> created package directory after unpacking it (in Chapter 5)? Is it
> simply to make sure that the directory exists? Or is it the stub end of
> some larger general proced
Now that I've given it some more thought: Why does one cd to the newly
created package directory after unpacking it (in Chapter 5)? Is it
simply to make sure that the directory exists? Or is it the stub end of
some larger general procedure that I should be more familiar with?
Just wondering.
Cl
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
oh, sorry.
--
Hirofumi Momose <[EMAIL PROTECTED]>
On Thu, 16 Aug 2007 08:07:51 +0100
Alan Lord <[EMAIL PROTECTED]> wrote:
> Hirofumi Momose wrote:
> > Hello,
> > I am a newbie to CLFS.
> >
> wrong list - this is for LFS. You need to post this on the clfs-support
> list.
>
> Alan
>
>
>
>
Hirofumi Momose wrote:
> Hello,
> I am a newbie to CLFS.
>
wrong list - this is for LFS. You need to post this on the clfs-support
list.
Alan
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information
24 matches
Mail list logo
