Matthew Burgess wrote:
I suspect it'd be quicker just starting from scratch
Here's a wonderful snippet from the latest release of cdrtools
So, another case of NIH syndrome. Rather than report bugs/offer patches
to existing projects (tar vs. star, make vs. smake, etc.) he goes and
rei
Ken Moffat wrote:
Debian has now forked cdrkit (get it from your local debian pool,
the diff on top of pre3 only affects some of the debian/ files).
I wonder how long it'll take them to clean it up? I suspect it'd be
quicker just starting from scratch (and just don't support anything that
On Monday 04 September 2006 22:32, tom wrote:
> In file included from
> /sources/php-5.1.4/ext/mbstring/oniguruma/regerror.c:37:
> /usr/lib/gcc/i686-pc-linux-gnu/4.0.2/include/varargs.h:4:2: error:
> #error "GCC no longer implements ."
> /usr/lib/gcc/i686-pc-linux-gnu/4.0.2/include/varargs.h:5:2: e
On Tue, 5 Sep 2006 09:39:07 +0300 "Angel Tsankov"
<[EMAIL PROTECTED]> wrote:
> The addition of this feature is desired since the glibc 2.3.4
> installation (from LFS 6.1.1) calls mkdir with relative paths to create
> directories in /usr/share/local.
If you've followed the advice from the hint yo
On Tue, 5 Sep 2006 09:39:07 +0300 "Angel Tsankov"
<[EMAIL PROTECTED]> wrote:
> The addition of this feature is desired since the glibc 2.3.4
> installation (from LFS 6.1.1) calls mkdir with relative paths
You'll have a hard time convincing me of that. No glibc version I've ever
installed did thi
As a user of architectures other than x86, cdrecord itself is a
pain in the proverbial to build. I switched to dvdrtools-0.3.1 some
months ago - works great provided I remember to specify speed, but
the project seems to be inactive.
Debian has now forked cdrkit (get it from your local debian po
On 9/4/06, Brandon Peirce <[EMAIL PROTECTED]> wrote:
One _advantage_ of the coreutils version is that is implements a -c switch
which the shadow version doesn't. (More about -c later.)
The shadow version implements -c to pass a command. su would be pretty
crippled without it.
[06:59 AM [EMAI
> Throw an "exit" on the end of that, your root password on the front, giving:
> START FILE
> 123456
> ./configure --prefix=/usr
> make
> make install
> exit
> END FILE
>
> Then simply call:
> echo build-package-name.txt | su
What will happen if I do not append an 'exit' at the end of the file?
On 9/5/06, Angel Tsankov <[EMAIL PROTECTED]> wrote:
> Throw an "exit" on the end of that, your root password on the front, giving:
> START FILE
> 123456
> ./configure --prefix=/usr
> make
> make install
> exit
> END FILE
>
> Then simply call:
> echo build-package-name.txt | su
What will happen i
Throw an "exit" on the end of that, your root password on the front, giving:
START FILE
123456
./configure --prefix=/usr
make
make install
exit
END FILE
Then simply call:
echo build-package-name.txt | su
What will happen if I do not append an 'exit' at the end of the file?
--
http://linuxfromsc
I think then that I will stay pure, even if laggard. 6.2 can wait.
At least I am expanding my Linux skills as I go. When I decided to
start this I was
drawing on some rusty Unix recollections from 20+ years ago at
university.
Paul
On 5-Sep-06, at 05:32, Ken Moffat wrote:
On Mon, Sep 04,
On Mon, Sep 04, 2006 at 08:56:12PM -0400, Paul Fanning wrote:
>
> Thanks Ken,
>
> I did not realize I had fallen so far behind. As you can probably
> guess, I have been progressing intermittently, and occasionally
> backwards, using the LiveCD 6.1.1. I am now trying to figure out
> whether
12 matches
Mail list logo
