On Feb 20, 2012, at 6:02 PM, Bruce Dubbs wrote:
For most distros, modules are the biggest reason to have an initramfs --
plus the fact that they want a one size fits all methodology. In a way,
this is the antithesis of LFS where we generally build a custom kernel
and rarely need an
On Tue, Feb 21, 2012 at 12:41 AM, Qrux qrux@gmail.com wrote:
On Feb 20, 2012, at 6:02 PM, Bruce Dubbs wrote:
For most distros, modules are the biggest reason to have an initramfs --
plus the fact that they want a one size fits all methodology. In a way,
this is the antithesis of LFS
On Wed, Feb 1, 2012 at 12:47 PM, Qrux qrux@gmail.com wrote:
On Jan 31, 2012, at 1:26 PM, Bruce Dubbs wrote:
You know I added kvm-qemu to BLFS a couple of days ago, right?
I added a BLFS-style markdown page:
https://github.com/qrux/xlapp/blob/master/README-blfs.md
It tries to
On Feb 21, 2012, at 3:16 AM, Nathan Coulson wrote:
On Wed, Feb 1, 2012 at 12:47 PM, Qrux qrux@gmail.com wrote:
On Jan 31, 2012, at 1:26 PM, Bruce Dubbs wrote:
You know I added kvm-qemu to BLFS a couple of days ago, right?
I added a BLFS-style markdown page:
I want to start contributing to the BLFS book, but I'm not really sure how to
commit changes. I have downloaded a copy of BLFS using svn and have made my
changes to the relevant xml-files and general.ent. I have also generated a html
version using tidy and verified that everything looks ok.
On Tue, 2012-02-21 at 20:15 +0100, Ragnar Thomsen wrote:
I want to start contributing to the BLFS book, but I'm not really sure how to
commit changes. I have downloaded a copy of BLFS using svn and have made my
changes to the relevant xml-files and general.ent. I have also generated a
html
On Tue, 21 Feb 2012 20:15:25 +0100
Ragnar Thomsen ragnarthom...@hotmail.com wrote:
I want to start contributing to the BLFS book, but I'm not really sure how to
commit changes. I have downloaded a copy of BLFS using svn and have made my
changes to the relevant xml-files and general.ent. I
Qrux wrote:
On Feb 20, 2012, at 6:02 PM, Bruce Dubbs wrote:
For most distros, modules are the biggest reason to have an
initramfs -- plus the fact that they want a one size fits all
methodology. In a way, this is the antithesis of LFS where we
generally build a custom kernel and rarely
Nathan Coulson wrote:
modules, I personally would want to exclude this so I can upgrade
kernel/initramfs separately on my own build/projects.
That is a very good point.
I feel that for
the BLFS book though, that most people would want to include kernel
modules, and if we are only
Jeremy Huntwork wrote:
As an example, look at this init:
https://github.com/jhuntwork/LightCube-OS/blob/master/packages/mkinitramfs/init.in
Well that's certainly easier than dracut. I would want to add UUID and
LABEL capabilities.
And the script that creates the image:
On 2/21/12 2:49 PM, Bruce Dubbs wrote:
As an example, look at this init:
https://github.com/jhuntwork/LightCube-OS/blob/master/packages/mkinitramfs/init.in
Well that's certainly easier than dracut. I would want to add UUID and
LABEL capabilities.
Actually, the UUID stuff just works the
On 2/21/12 3:03 PM, Jeremy Huntwork wrote:
On 2/21/12 2:49 PM, Bruce Dubbs wrote:
As an example, look at this init:
https://github.com/jhuntwork/LightCube-OS/blob/master/packages/mkinitramfs/init.in
Well that's certainly easier than dracut. I would want to add UUID and
LABEL capabilities.
Jeremy Huntwork wrote:
On 2/21/12 3:03 PM, Jeremy Huntwork wrote:
On 2/21/12 2:49 PM, Bruce Dubbs wrote:
As an example, look at this init:
https://github.com/jhuntwork/LightCube-OS/blob/master/packages/mkinitramfs/init.in
Well that's certainly easier than dracut. I would want to add UUID
On Tuesday 21 February 2012 02:49:20 pm Bruce Dubbs wrote:
Jeremy Huntwork wrote:
As an example, look at this init:
https://github.com/jhuntwork/LightCube-OS/blob/master/packages/mkinitramf
s/init.in
Well that's certainly easier than dracut. I would want to add UUID and
LABEL
Baho Utot wrote:
Where does this leave this
http://www.linuxfromscratch.org/hints/downloads/files/Root_FS_on_RAID+encryption+LVM.txt
It's still there. The initramfs page in the book will probably
reference it.
Note that LVM2 and mdadm are already in the book. I don't think dmraid
is
On Mon, Feb 20, 2012 at 05:43:51PM -0800, Fernando de Oliveira wrote:
Em 19-02-2012 16:51, Ken Moffat escreveu:
That's good, but I'm only interested in LFS-7.0 (or later) for the
book. We've upgraded libguile, glib, gtk and a host of other
things. OTOH, I know you upgrade your old
At the moment, we have two varieties of tags for past LFS-releases
: built (known to build, but has not been tested), and checked
(builds, and works properly). Am I alone in wondering if there is a
case for something in the middle, such as 'builds, and seems to
work'?
For packages I usually
Ken Moffat wrote:
At the moment, we have two varieties of tags for past LFS-releases
: built (known to build, but has not been tested), and checked
(builds, and works properly). Am I alone in wondering if there is a
case for something in the middle, such as 'builds, and seems to
work'?
On Feb 21, 2012, at 3:43 PM, Bruce Dubbs wrote:
Ken Moffat wrote:
At the moment, we have two varieties of tags for past LFS-releases
: built (known to build, but has not been tested), and checked
(builds, and works properly). Am I alone in wondering if there is a
case for something in the
On Tue, Feb 21, 2012 at 05:43:29PM -0600, Bruce Dubbs wrote:
I don't do a lot of user testing if it's not a package I usually use.
If the program starts, then it works as far as I'm concerned. We may
have a configuration problem, but that can be fixed if we find it. It's
not our purpose
On Tue, Feb 21, 2012 at 03:58:37PM -0800, Qrux wrote:
I think this, too, and I would call it 'run'. To put correctness first, I
would advocate this hierarchy:
* Tested
Compiles, executes, passes regression (if it doesn't work from here, talk to
the maintainer of the package,
Jeremy Huntwork wrote:
As an example, look at this init:
https://github.com/jhuntwork/LightCube-OS/blob/master/packages/mkinitramfs/init.in
And the script that creates the image:
https://github.com/jhuntwork/LightCube-OS/blob/master/packages/mkinitramfs/mkinitramfs.orig
Very interesting.
On 2/21/12 8:51 PM, Bruce Dubbs wrote:
I was able to use
menuentry BLFS Dev (LFS-7.0-Feb14) initrd, Linux 3.0.4 {
linux /vmlinuz-3.0.4-lfs-20120214
root=UUID=54b934a9-302d-415e-ac11-4988408eb0a8 ro
initrd /initrd.img-no-kmods
}
and it worked the first time.
Nice!
One interesting thing
On 2/21/12 8:51 PM, Bruce Dubbs wrote:
Very interesting. I took your scripts and hacked them a bit. I set it up
Oh, one other thing that I was going to do at some point but also hadn't
gotten around to yet was to pull in the required dynamic libs, well,
dynamically. Perhaps parse output from
Jeremy Huntwork wrote:
On 2/21/12 8:51 PM, Bruce Dubbs wrote:
Very interesting. I took your scripts and hacked them a bit. I set it up
Oh, one other thing that I was going to do at some point but also hadn't
gotten around to yet was to pull in the required dynamic libs, well,
dynamically.
AFAIK, mii-tool is now deprecated.
Net-tools is nice, IMO, because it offers ifconfig, but mii-tool can't report
speeds above 100Base-T.
URL:
http://www.kernel.org/pub/software/network/ethtool/ethtool-3.2.tar.gz
It's fairly CMMI.
I propose keeping net-tools, but also adding ethtool
26 matches
Mail list logo
