Hello.
I've spent a couple of ours now tryng to get jhalfs (svn trunk) to build
the LFS svn version. But I can't get it done.
- I've built by hand a couple of times already (at the time of 6.3 apprx.)
- I've googled but couldn't find nothing
Is there a step-by-step howto anywhee
Emmanuel Trillaud wrote:
> In the trunk version SVN-200902017 section 3.2
> The download link for the mpfr lib is wrong :
> http://www.mpfr.org/mpfr-current/mpfr-2.4.0.tar.bz2
> SHOULD BE
> http://www.mpfr.org/mpfr-current/mpfr-2.4.1.tar.bz2.
> 2.4.1 is the last version.
...but if I may say so,
Hi.
I wanted to write this for a while already, so here it goes:
Like thomas, we had to adjust the MTU for our interfaces;
we do it per default like this in the ipv4 service script:
= patch start
--- lfs/sysconfig/network-devic
On Wed, Mar 14, 2007 at 03:20:05PM -0700, Dan Nicholson wrote:
> On 3/14/07, Richard Gill <[EMAIL PROTECTED]> wrote:
> >
> > In the latest development branch (SVN-20070314), the
> > bash-3.2-fixes-2.patch creates a problem in bash, as regular
> > expression matches in conditionals don't work anymor
On Thu, Mar 15, 2007 at 01:11:31PM +0100, Jens Stroebel wrote:
> Reading your posts, I got and applied the above-mentioned patch;
> contrary to what I expected, [[ $test =~ $regexpr ]] worked, whereas
> [[ "$test" =~ "$regexp
On Thu, Mar 15, 2007 at 01:12:11PM -0700, Dan Nicholson wrote:
[..snip...]
> > Following up my own post, sorry, but I thought the above incomplete after
> > a bit more testing:
> >
> > It seems like it's OK to "" the left side of the comparison,
> > but not the regex which should
Hi out there.
Due to the mozilla security announcements
( http://www.mozilla.org/security/announce/ )
concerning versions 1.5.0.9, I was inclined to upgrade both to 1.5.0.10.
I had to recognize that, while the pago-patch from BLFS still applies,
the system_nss patch didn't like to
Hello.
I've been trying for some time now to get the shadow-4.0.18.1 source
from ftp://ftp.pld.org.pl/software/shadow/shadow-4.0.18.1.tar.bz2 ;
the site is not resolvable, though.
(
ping ftp.pld.org.pl
ping: unknown host ftp.pld.org.pl
host ftp.pld.org.pl
Host ftp.pld.org.
Hello again;
While keeping track with the changes in the LFS devel book, I came
across the vim-7.0 -> 7.1 update.
The patch-list at
http://www.linuxfromscratch.org/lfs/view/development/chapter03/patches.html
references the URL for the mandir-patch:
http://www.linuxfromscr
Dan Nicholson wrote:
> Yeah, that's about the least reliable server on the internet :) You
> can just use a mirror for now.
>
> http://anduin.linuxfromscratch.org/sources/LFS/lfs-packages/development/shadow-4.0.18.1.tar.bz2
Thanks for the link.
New version now already integrated in the p
Hiya.
In the daily routine of running over vulnerability reports, I
encountered a samba vulnerability report I thouht I'd mention here:
http://www.securityfocus.com/bid/23972
and, corresponding, the release announcement at
http://news.samba.org/
Hello.
I tried to follow the LFS-devel book on udev but ran into the following:
Setup:
- kernel 2.6.21
- udev-111
- 2 network cards; one builtin (broadcomm, using tg3), one connected via
pcmcia (using 8139too)
- first network card is assigned name eth0 via udev-rule
==
On Mon, May 21, 2007 at 06:22:07PM -0400, Bryan Kadzban wrote:
> But if you remove all your rules and reboot, udev will generate new
> rules for all your NICs, so Alexander's suggestion of removing them all
> is a good idea. Just beware that what you want isn't possible.
>
> (Why do you want it,
Bryan Kadzban wrote:
> On Tue, May 22, 2007 at 06:03:39PM +0200, Jens Stroebel wrote:
>> On Mon, May 21, 2007 at 06:22:07PM -0400, Bryan Kadzban wrote:
>>
>>> (Why do you want it, by the way?)
>> That's because we install a laptop with a pcmcia-plugged network
Bryan Kadzban wrote:
> Hmm. I figured they'd show up on a different bus, since it is really a
> different physical bus. Well, whatever. I'd still like to know where
> the device symlink points though. :-)
I'm not sure which one... you mean like:
ls -l /sys/class/net/eth1/device
Bryan Kadzban wrote:
> I'd like to see the results of:
> grep -H . \
> /sys/devices/pci\:00/\:00\:1e.0/:03:01.0/:04:00.0/{,subsystem_}{vendor,device}
/sys/devices/pci:00/:00:1e.0/:03:01.0/:04:00.0/vendor:0x13d1
/sys/devices/pci:00/:00:1e.0/:03:01.0/
Jens Stroebel wrote:
> On Mon, May 21, 2007 at 06:22:07PM -0400, Bryan Kadzban wrote:
>
>> But if you remove all your rules and reboot, udev will generate new
>> rules for all your NICs, so Alexander's suggestion of removing them all
>> is a good idea. Just be
Dan Nicholson wrote:
> I rolled a new snapshot that has a few changes since the last 20070420
> tarball. Please test it out so we can get any fixes in to 6.3. They
> should be entirely backwards compatible with existing scripts.
Hiya.
I maybe should know where to look, but I don't
, 2007 at 12:24:54PM +, DJ Lucas wrote:
> Jens Stroebel wrote:
> > I maybe should know where to look, but I don't...
> > Where is the download location for the new LFS-bootscripts you rolled?
> >
> http://downloads.linuxfromscratch.org/lfs-bootscr
Hello beautiful people :)
I was in a situation which prompted (unfortunately) for lowering the MTU
of a network-device to assure functionality as planned
(r8169 driver, 8168B/8111 NIC)
While looking at the actual bootscripts and searching a bit/asking my
way around,
Hi there.
When updating to e2fsprogs-1.40.6 like LFS devel did, I noticed my
system(s) no longer booting via grub. Slightly inconvenient ;-)
After digging around a while I found that mke2fs has changed the inode
size to 256, making grub effectively unable to read the filesystem t
Alexander E. Patrakov wrote:
Hello,
as explained in http://wiki.linuxfromscratch.org/lfs/ticket/2161 (a blocker),
due to recent changes in e2fsprogs, Grub-0.97 no longer works (cannot read any
files from the resulting filesystem, cannot be installed into MBR, and the book
is thus horribly bro
Hello.
While browsing the wget list generated for the LFS devel book, I noticed
that
http://www.linuxfromscratch.org/patches/lfs/development/db-2.8.1-fixes-1.patch
is not present...
greets,
jens
--
[EMAIL PROTECTED]
23.56.
Dan Nicholson wrote:
Hiya.
> It mostly seems to be working, but there is still a bug in the
> Should-Stop code as well as many other bugs that probably have not
> been uncovered in my limited testing. Please use with caution and
> backup your /etc/init.d and /etc/rc*.d directories
24 matches
Mail list logo