Re: Booting Lfs-Version udev_update-20060301 from usb drive.

2006-03-17 Thread Stephen Liu
Hi randhir,

On Thu, 2006-03-16 at 19:56 +, randhir phagura wrote:
 I intend booting the new lfs system from the host system. The host 
system 
 has hda (the main hard drive), hdc (the dvd-rom) and the IBM 
Microdrive 
 mounted on SanDisk adapter connected to USB port of the host. This 
drive is 
 configured as usb-storage in the kernel and host system recognises it

 as'sda'. There is only one partition on this drive i.e. sda1. Grub is

 installed on Microdrive but not setup on the MBR because I intend to 
boot it 
 from the host.


I have been trying couple days to get Grub, the bootload, to work on an
USB pendrive without a breakthrough, making the latter working as an
USB HD.  The BIOS of my motherboard supports;

USB-ZIP
USB-HDD
USB-CDROM
USB-FDD
SCSI
etc.


I have no problem to get a Linux running on a pendrive formatted on
FAT16 ZIP geometry using syslinux to boot minitrc.gz.


The problem in front of me are

1) 
The pendrive must be on FAT16/32 otherwise the BIOS won't detect it.

2)
FAT16/32 does not support symbolic link.

etc.

If you have any breakthrough please keep us posted.  TIA

B.R.
SL


 http://linuxfromscratch.org/mailman/listinfo/blfs-support
 FAQ: http://www.linuxfromscratch.org/blfs/faq.html
 Unsubscribe: See the above information page

-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: Xorg 7.0.0 xlogo linking error

2006-03-17 Thread Simon Scheiwiller
Thus spoke Andrew Benton:
 XpuFreeXmbString is defined (on my system) in
 /usr/include/X11/XprintUtil/xprintutil.h (I installed xorg-7 in /usr).
 X11/XprintUtil/xprintutil.h is included in xlogo-X11R7.0-1.0.1/print.h
 and print.h is included at the top of print.c.

 grep -R XpuFreeXmbString /usr

That file is installed:

[EMAIL PROTECTED]:~# ls -l /usr/include/X11/XprintUtil/
total 12
-rw-r--r-- 1 root root 11095 Mar 17 01:01 xprintutil.h

but somehow it can't even be found by find:

[EMAIL PROTECTED]:~# find / -name 'xprintutil.h'
find: /proc/4219/task: No such file or directory
find: /proc/4219/fd: No such file or directory
/usr/include/firefox-1.0.7/xprintutil/xprintutil.h
/usr/include/thunderbird-1.0.6/xprintutil/xprintutil.h
/usr/X11R6/include/X11/XprintUtil/xprintutil.h

 My guess is that your problem may be because you seem to have installed
 xorg into /usr/X11R6, maybe it's having trouble finding
 X11/XprintUtil/xprintutil.h?

I installed Xorg-6.8.0 before, and now I'm trying to upgrade to Xorg-7.0.0.
I'll try removing the whole /usr/X11R6 stuff and then installing
Xorg-7.0.0 (and probably reinstalling everything that needs X). Probably
the presence of the old files messed everything up.

 If it's any help, you may not need it. I don't install it and xorg-7
 works fine for me.

I just don't like when I get errors like that, because it indicates that
there could be many more problems coming up.

 --
 http://linuxfromscratch.org/mailman/listinfo/blfs-support
 FAQ: http://www.linuxfromscratch.org/blfs/faq.html
 Unsubscribe: See the above information page




-- 
simon scheiwiller
bollstrasse 21
ch-8405 winterthur
+41 78 624 16 73

-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: startx automatically with LFS

2006-03-17 Thread Satish Chebrolu
Try setting the default init level to 5 in /etc/inittab.On 3/17/06, Rik Potts [EMAIL PROTECTED] wrote:










Ive got xorg and kde installed and have rootand augustus users
At the moment when I boot up I get the command line.
I want to be able to boot straight into kde as the augustus user. 
I can do this by logging in as augustus and startx or logging in as root and running kdm.

Can someone suggest a way to get it to go straight into kdm. Then I can adjust kdm to my liking.

I am guessing its down to the init files but am lost to what to do. 

Hope someone can help.
Many Thanks once again
Rik









--http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.htmlUnsubscribe: See the above information page

-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: startx automatically with LFS

2006-03-17 Thread Dan Nicholson
On 3/17/06, Rik Potts [EMAIL PROTECTED] wrote:

 sorry, I did intend on saying in my forst post that I have tried this.

 On the command line it boots to it just says it has entered init level 5 
 instead of 3. No other change.

Rik, could you try to reply to the other post so a new thread isn't
started?  And try to write your mail in text rather than html.  See
the FAQ in the signature for the netiquette stuff.

Anyway, the problem is that BLFS doesn't include a boot script for
kdm.  Sorry.  However, you may be able to kludge up a quick fix if
someone doesn't suggest a proper one.

Download the blfs-bootscripts.  The link is in Chapter 2 of whichever
book you're following.  Unpack the bootscripts and copy init.d/gdm to
~/kdm or wherever.

Change all occurrences of GDM and gdm to KDM and kdm in the file. 
This is where the kludge comes in because I don't actually use kdm, so
I don't know if that script is the proper way to run it.  Probably,
though.

Then, you have to install it and make the symlinks so it's started and
stopped at the right runlevels.

install -v -m754 kdm /etc/rc.d/init.d
ln -svf  ../init.d/kdm /etc/rc.d/rc0.d/K05kdm
ln -svf  ../init.d/kdm /etc/rc.d/rc1.d/K05kdm
ln -svf  ../init.d/kdm /etc/rc.d/rc2.d/K05kdm
ln -svf  ../init.d/kdm /etc/rc.d/rc3.d/K05kdm
ln -svf  ../init.d/kdm /etc/rc.d/rc4.d/K05kdm
ln -svf  ../init.d/kdm /etc/rc.d/rc5.d/S95kdm
ln -svf  ../init.d/kdm /etc/rc.d/rc6.d/K05kdm

Now, kdm should start on runlevel 5.  Let me know if that helps.

--
Dan
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: Bc segmentation fault.

2006-03-17 Thread Dan Nicholson
On 3/17/06, Ag Hatzim [EMAIL PROTECTED] wrote:

 Some examples.
 ##
 [631](~)echo scale=3; 13 / 12 |bc
 1.083
 [632](~)echo scale=3; 13 / 12 |bc -l
 zsh: doneecho scale=3; 13 / 12 |
 zsh: segmentation fault  bc -l
 ##
 Same thing in interactive mode.

 This happens with or without readline support.

I'm getting the same thing here on an lfs-alpha build from 20060312
using gcc-4.0.3.  This is weird.  I'm gonna strace it and see if I can
figure anything out.

My other system is lfs-20061005 abouts, and bc -l works fine there.

 Attached is the built log.

#=  CONFIFURE  =

CONFIFURE? :-)

--
Dan
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: Bc segmentation fault.

2006-03-17 Thread Dan Nicholson
On 3/17/06, Dan Nicholson [EMAIL PROTECTED] wrote:
  [632](~)echo scale=3; 13 / 12 |bc -l
  zsh: doneecho scale=3; 13 / 12 |
  zsh: segmentation fault  bc -l
  ##
  Same thing in interactive mode.

Jeez.  Figured it out, Ag.  Apply

http://www.linuxfromscratch.org/patches/downloads/bc/bc-1.06-fixes-1.patch

Can anyone else confirm this behavior?

--
Dan
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: Bc segmentation fault.

2006-03-17 Thread Ag Hatzim
Dan Nicholson([EMAIL PROTECTED])@Fri, Mar 17, 2006 at 02:48:55PM -0800:
 
 Jeez.  Figured it out, Ag.  Apply
 
 http://www.linuxfromscratch.org/patches/downloads/bc/bc-1.06-fixes-1.patch

That was it Dan,many thanks.

Funny,i search all the web for the fix,and i had it (the patch) in my disk. :)

CONFIFURE? :-)
Fixed :)
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: Booting Lfs-Version udev_update-20060301 from usb drive.

2006-03-17 Thread Alessandro Alocci
Alle 20:56, giovedì 16 marzo 2006, randhir phagura ha scritto:
 I intend booting the new lfs system from the host system. The host system
 has hda (the main hard drive), hdc (the dvd-rom) and the IBM Microdrive
 mounted on SanDisk adapter connected to USB port of the host. This drive is
 configured as usb-storage in the kernel and host system recognises it
 as'sda'. There is only one partition on this drive i.e. sda1. Grub is
 installed on Microdrive but not setup on the MBR because I intend to boot
 it from the host.

 Is there a way to boot the new lfs from my host system grub?

Well, if your BIOS is not able to recognize your usbdisk you can use an initrd
(Initial RAM disk) to load the usb modules before you mount the real
partition (sda1) and use the initrd option of grub.
I have done this to boot a Fedora Core 3 on my laptop from an external
usbdisk but I used a specific howto and mkinitrd for that distro, but I think
it's possible to find a similar solution also for LFS.
Try to document yourself about initrd
(man initrd or less /usr/src/linux-`uname -r`/Documentation/initrd.txt)
and search the net about how to boot linux from an usb storage.
I'll try myself to solve this on weekend and if I can find a working solution
I'll post here.
HTH, Alessandro Alocci
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: Booting Lfs-Version udev_update-20060301 from usb drive.

2006-03-17 Thread randhir phagura

Hi,

Jeff Cousino wrote on Thu, 16 Mar 2006 15:57:


On 3/16/06, randhir phagura [EMAIL PROTECTED] wrote:



Is there a way to boot the new lfs from my host system grub?



I'm pretty sure that grub will only allow you to boot from drives that
are recognized by the BIOS on you machine.


That was somewhat obvious but there should be some way out?

Any ideas please?

RSP


--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: Booting Lfs-Version udev_update-20060301 from usb drive.

2006-03-17 Thread Alessandro Alocci
Alle 00:15, sabato 18 marzo 2006, Alessandro Alocci ha scritto:
 Alle 20:56, giovedì 16 marzo 2006, randhir phagura ha scritto:
  I intend booting the new lfs system from the host system. The host system
  has hda (the main hard drive), hdc (the dvd-rom) and the IBM Microdrive
  mounted on SanDisk adapter connected to USB port of the host. This drive
  is configured as usb-storage in the kernel and host system recognises it
  as'sda'. There is only one partition on this drive i.e. sda1. Grub is
  installed on Microdrive but not setup on the MBR because I intend to boot
  it from the host.
 
  Is there a way to boot the new lfs from my host system grub?

 Well, if your BIOS is not able to recognize your usbdisk you can use an
 initrd (Initial RAM disk) to load the usb modules before you mount the real
 partition (sda1) and use the initrd option of grub.
 I have done this to boot a Fedora Core 3 on my laptop from an external
 usbdisk but I used a specific howto and mkinitrd for that distro, but I
 think it's possible to find a similar solution also for LFS.
 Try to document yourself about initrd
 (man initrd or less /usr/src/linux-`uname -r`/Documentation/initrd.txt)
 and search the net about how to boot linux from an usb storage.
 I'll try myself to solve this on weekend and if I can find a working
 solution I'll post here.
 HTH, Alessandro Alocci

Well, this worked for me:

First of all I have recompiled my kernel with:
Device Drivers - USB Support - 
Support for Host-side USB
EHCI HCD (USB 2.0) support
OHCI HCD support
UHCI HCD (most Intel and VIA) support
USB Mass Storage support
statically compiled into the kernel.

I needed also this:
Device Drivers - Block devices -
Loopback device support
RAM disk support
Initial RAM disk (initrd) support
statically compiled into the kernel.
Then I recompiled and installed the kernel
(mine is 2.6.12.5) and rebooted.

Now we have to build an initrd-tree, we can
build it from scratch (possibly, a more appropriate
solution on this site) but we can also use an already
done script.
A good candidate seems to be the mkinitrd script from
the last slackware distro, so I downloaded this:

mkinitrd-1.0.1-i486-3.tgz

from a slack mirror. Then:

cd /usr/local/src
cp /home/alex/scaricati/mkinitrd-1.0.1-i486-3.tgz .
tar xvzf mkinitrd-1.0.1-i486-3.tgz
install -v -m 755 usr/sbin/mkinitrd /usr/sbin/
install -v -d -m 755 /usr/share/mkinitrd
cp usr/share/mkinitrd/initrd-tree.tar.gz /usr/share/mkinitrd/
# you can also read and install the docs and man page
# about busybox and mkinitrd. Be sure to read
# the script itself to understand how it works.

Now the mkinitrd script is installed and we can
build the initrd-tree, so:

cd /boot
mkinitrd
# Add your disk-device in initrd-tree/rootdev
# (mine is /dev/sda6, correct this with yours)
cat  initrd-tree/rootdev  EOF
/dev/sda6
EOF
# Add the name of the used file-system for the
# previous partition (mine is ext3)
cat  initrd-tree/rootfs  EOF
ext3
EOF

Now, the problem with this solution is that we
have to give time enough to the kernel to discover
the usb-storage before that the initial ram disk
try to mount the real root partition (in my case
/dev/sda6). To solve this I added the line

sleep 12

in initrd-tree/linuxrc, just before this comment:

# Switch to real root partition:

(line 89).
(Yes, I know it's a bit naive, but I have not
a better solution ATM, perhaps someone can suggest
something more appropriate here)
One can tune the previous sleep in case is not
enough; in my case wait for 12 seconds is sufficient.
If someone needs to load also some modules from the
initrd, they have to be copied in 
initrd-tree/lib/modules/`uname -r`
and edit load_kernel_modules, then
chmod 755 load_kernel_modules

Now we have to run the mkinitrd script
again from the /boot directory:

cd /boot
mkinitrd

This time the script should create the real
initrd.gz. We need also to copy the kernel
from the usb-disk partition in the hard-disk.
Now we can instruct grub to boot from sdaX.
I added this to /boot/grub/menu.lst:
(With grub installed in the MBR of /dev/hda)


title USBDISK-BOOT
kernel (hd0,10)/boot/usblfskernel-2.6.12.5 root=/dev/sda6
initrd (hd0,10)/boot/initrd.gz


Again, be sure to correct the previous line with
your correct data.
As you see, this solution requires to have both
the kernel and the initrd image in a disk where grub
can find them, but after that grub should menage to boot
the system installed in the usb-disk.
This let me to reboot from an usb-disk partition.
Well, it seems to be all (hope I haven't forgot
anything or made too much confusion)
Regards, Alessandro Alocci
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page