Hi all,
I am looking for a way to build a clean production system. ie system
without development parts.
RATIONALE: I do not need binutils or gcc or something like this on my
router. (if I realy need binutils --- corect me please)
The main idea is to use the development tools from toolchain to bu
With lilo it was posible to say
boot=/dev/md0
root=/dev/md0
in /etc/lilo.conf and lilo will corectly install boot loader over software
raid. (you will need mbr for every disk in raid in this case, but this is
not problem)
How I can install grub loader over /dev/md0 software raid mirror ?
(the lo
"Alexander E. Patrakov" <[EMAIL PROTECTED]> writes:
> Dimitry Naldayev wrote:
>
>>I am looking for a way to build a clean production system. ie system
>>without development parts.
>>
> You have two approaches.
>
> A) [preferred] Use Debian S
Matthew Burgess <[EMAIL PROTECTED]> writes:
> Dan Nicholson wrote:
>
>> So, am I to gather from Matt and DJ that udevstart won't work
>> correctly from udev-084? Or just that it's not installed by default?
>
after I did "/etc/rc.d/init.d/udev start" in chroot I have ruined the host
system by some
"Alexander E. Patrakov" <[EMAIL PROTECTED]> writes:
> Bryan Kadzban wrote:
>
>> It should be easy enough to have only "start" and "restart" targets, and
>> have the "restart" target do a "killall udevd" (or whatever), then
>> simply run "$0" start (perhaps after waiting for a second).
>
> No, that
Hi all,
There is russian web forum dedicated to LFS at the site of Perm Linux Users
Group http://linux.perm.ru/forum/viewforum.php?f=10
---
Dimitry
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information pa
Richard A Downing <[EMAIL PROTECTED]> writes:
> Matthew Burgess wrote:
>> Richard A Downing wrote:
>>> Jeremy Huntwork wrote:
>>> Nothing *depends* on vim, so
>>>
leave it at the end.
>>>
>>>
>>> I depend on vim. Put it at the front.
>>> Only just :-)
>>
>> Actually, if we were to replace
Matthew Burgess <[EMAIL PROTECTED]> writes:
> Randy McMurchy wrote:
>
>> Why is it that the package URL is not listed, but only the location
>> where it *should* be?
>>
>
>> So, why not just list the package URL?
>
> Short answer...it's a historical oversight, I think.
>
> Long answer...
>
> We u
Tyler Packer <[EMAIL PROTECTED]> writes:
[/dev/null]
> {s,c,}fdisk -l /dev/hda says:
> /dev/hda 82220544 bytes, 82MB, 16 heads, 63 sectors, 159 Cylendars
>
> This is BAD! It appears that the disk utils are using the (incorrectly
> reported) physical geometry instead of the logical. I know I
Chris Staub <[EMAIL PROTECTED]> writes:
> I'm just looking for ways to reduce the temp-system in /tools as much
> as possible. I've built LFS systems before without having ncurses
> there and it works fine. I believe the only issue is texinfo - many
> programs in chapter 6 need it to build their i
Hi all,
Look like cross-lfs use diffutils-2.8.7
---
Dimitry
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
"Alexander E. Patrakov" <[EMAIL PROTECTED]> writes:
> 3) links doesn't support UTF-8. So if you are using the en_US locale,
> everything is fine. But in en_US.UTF-8, you will have to change your
> preference.
and... links add extra space left to the text. so I can not cut and paste
from lfs book
Matthew Burgess <[EMAIL PROTECTED]> writes:
> Dimitry Naldayev wrote:
>> Hi all,
>> Look like cross-lfs use diffutils-2.8.7
>
> That's an alpha version of the package. cross-lfs are free to do what
> they want, but the main LFS book will stick with stable
There are some info and man pages in /tools/share/{info,man}
not much but is... so if we want to remove them in chapter 5.31 too, we
need to say something like:
rm -rf /tools/{,share}/{info,man}
---
Dimitry
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfr
This is a quote from http://www.linuxfromscratch.org/lfs/news.html :
Latest SVN Changes
* Manuel Canales Esparcia - 2006/01/13
+ Indented chapter 03.
+ Ported r7273 from trunk.
^^ What is this news entry about?
Is this about a trunk? (but in the c
Matthew Burgess <[EMAIL PROTECTED]> writes:
> Dimitry Naldayev wrote:
>
>> + Ported r7273 from trunk.
>> ^^ What is this news entry about?
>> Is this about a trunk? (but in the case it is unclear why we need porting
>> so
The chapter 3.2 "All Packages" contain not urls of the packages but only
urls their locations. Are there main reason for this?
Why not to put in the book direct urls to packages (as it done in HLFS
book for example)?
RATIONALE: It is not easy to keep the list of packages urls to download
(with wget
17 matches
Mail list logo
