I know it's not in the book but does anybody have any views on Snort?
Richard
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
I'm just going through LFS 9.3 - extra packages - so am still in chroot.
The error:
libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in M
On 04/03/2014 12:36 PM, Robin wrote:
> I'm just going through LFS 9.3 - extra packages - so am still in chroot.
>
> The error:
>
> libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
> libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
> libtooli
Le 03/04/2014 12:36, Robin a écrit :
> I'm just going through LFS 9.3 - extra packages - so am still in chroot.
>
> The error:
>
> libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
> libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
> libtoolize
On 3 April 2014 12:36, Pierre Labastie wrote:
> Le 03/04/2014 12:36, Robin a écrit :
>> I'm just going through LFS 9.3 - extra packages - so am still in chroot.
>>
>> The error:
>>
>> libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
>> libtoolize: rerunning libtoolize, t
On 3 April 2014 13:10, Robin wrote:
> On 3 April 2014 12:36, Pierre Labastie wrote:
>> Le 03/04/2014 12:36, Robin a écrit :
>>> I'm just going through LFS 9.3 - extra packages - so am still in chroot.
>>>
>>> The error:
>>>
>>> libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.
On 04/02/14 21:50, Bruce Dubbs wrote:
> rhubarbpie...@gmail.com wrote:
>
>
>> My shell is /bin/bash. My bash version is 4.2.45(1) in my 7.4 and 7.5
>> BLFS. Should they be the same?
> I don't recall, but bash-4.2.45 is fine. You are slightly ambiguous
> here. bash behavior changes if it is cal
On 3 April 2014 13:56, Robin wrote:
> On 3 April 2014 13:10, Robin wrote:
>> On 3 April 2014 12:36, Pierre Labastie wrote:
>>> Le 03/04/2014 12:36, Robin a écrit :
I'm just going through LFS 9.3 - extra packages - so am still in chroot.
The error:
libtoolize: Consider ad
Found another link
http://ftp.osuosl.org/pub/blfs/conglomeration/dhcpcd/
--
rob
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
rhubarbpie...@gmail.com wrote:
>
> On 04/02/14 21:50, Bruce Dubbs wrote:
>> What's the output of 'echo $PS1'?
>>
>> How about 'ldd /bin/bash'? Is libreadline.so.6 there?
>
> ldd /bin/bash:
>
> linux-gate.so.1 (0xb7732000)
> libreadline.so.6 => /lib/libreadline.so.6 (0xb76f2000)
>
Robin wrote:
> Found another link
>
> http://ftp.osuosl.org/pub/blfs/conglomeration/dhcpcd/
Yes, that is one of our mirrors.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
There's an error in the book's suggested configure commands:
--libexecdir=/usr/lib/sudo should be --libexecdir=/usr/lib. Both current
books have this error which surely would produce "two" sudo directories;
one below the other.
Richard
--
http://linuxfromscratch.org/mailman/listinfo/blfs-suppor
On 3 April 2014 16:45, Bruce Dubbs wrote:
> Robin wrote:
>> Found another link
>>
>> http://ftp.osuosl.org/pub/blfs/conglomeration/dhcpcd/
>
> Yes, that is one of our mirrors.
>
>-- Bruce
>
>
>
>
> --
> http://linuxfromscratch.org/mailman/listinfo/blfs-support
> FAQ: http://www.linuxfromscratc
On 04/03/14 10:44, Bruce Dubbs wrote:
> rhubarbpie...@gmail.com wrote:
>> On 04/02/14 21:50, Bruce Dubbs wrote:
>>> What's the output of 'echo $PS1'?
>>>
>>> How about 'ldd /bin/bash'? Is libreadline.so.6 there?
>> ldd /bin/bash:
>>
>> linux-gate.so.1 (0xb7732000)
>> libreadline.so.6 =
On Thu, 03 Apr 2014 6:46:05 PM Richard Melville wrote:
> There's an error in the book's suggested configure commands:
> --libexecdir=/usr/lib/sudo should be --libexecdir=/usr/lib. Both current
> books have this error which surely would produce "two" sudo directories;
> one below the other.
>
> R
rhubarbpie...@gmail.com wrote:
>
> On 04/03/14 10:44, Bruce Dubbs wrote:
> Your suggested "~/.bashrc" then "source ~/.bashrc" steps fix the
> prompt. But I still can't source a script and subsequent xterm windows
> show the old prompt.
Edit four files: /etc/profile, /etc/bashrc, ~/.bash_profile
On Thu, Apr 03, 2014 at 09:21:34AM -0500, rhubarbpie...@gmail.com wrote:
>
> This is a stretch, but I should mention I compiled BLFS/X with an older
> kernel than I used in compiling LFS. I found I booted to a blank screen
> after compiling LFS with the 3.13.13 kernel so I reverted to my LFS/BL
On 04/03/14 16:14, Ken Moffat wrote:
> On Thu, Apr 03, 2014 at 09:21:34AM -0500, rhubarbpie...@gmail.com wrote:
>> This is a stretch, but I should mention I compiled BLFS/X with an older
>> kernel than I used in compiling LFS. I found I booted to a blank screen
>> after compiling LFS with the 3.1
On 04/03/14 15:19, Bruce Dubbs wrote:
> rhubarbpie...@gmail.com wrote:
>> On 04/03/14 10:44, Bruce Dubbs wrote:
>> Your suggested "~/.bashrc" then "source ~/.bashrc" steps fix the
>> prompt. But I still can't source a script and subsequent xterm windows
>> show the old prompt.
> Edit four files:
rhubarbpie...@gmail.com wrote:
> I echoed the file names as you suggested and prior to invoking X the
> order is:
>
> /etc/profile
> .bash_profile
> .bashrc
> /etc/bashrc
That is correct.
> However, I saw nothing when starting X.
That's wrong.
So I redirected the output to a
> file. Prior to
On Thu, 03 Apr 2014 4:53:31 PM rhubarbpie...@gmail.com wrote:
> On 04/03/14 16:14, Ken Moffat wrote:
> > On Thu, Apr 03, 2014 at 09:21:34AM -0500, rhubarbpie...@gmail.com wrote:
> >> This is a stretch, but I should mention I compiled BLFS/X with an older
> >> kernel than I used in compiling LFS. I
21 matches
Mail list logo
