* Speakup with LFS?
@ Zachary Kline
` Doug Sutherland
` Georgina Joyce
0 siblings, 2 replies; 3+ messages in thread
From: Zachary Kline @ UTC (permalink / raw)
To: Speakup is a screen review system for Linux.
Hiya,
I was wondering if anybody on here had experience building an LFS system with Speakup in the new kernel. I have a good idea of how to go about doing it, but don't want to end up with a system that won't talk from boot when I need to try it. What I was thinking is that since a symbolic link can cross filesystems, I could temporarily change /usr/src/linux to point to the directory of my LFS kernel unpacking.
I could then do a CVS checkout--using my existing Linux system, of course, since LFS doesn't come with CVS. I'd then just change the symlink.
Would this work?
Thanks muchly,
Zack.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Speakup with LFS?
Speakup with LFS? Zachary Kline
@ ` Doug Sutherland
` Georgina Joyce
1 sibling, 0 replies; 3+ messages in thread
From: Doug Sutherland @ UTC (permalink / raw)
To: Speakup is a screen review system for Linux.
Zach,
You build speakup on LFS the same way you build it anywhere else.
What you described should work, although I would recommend
adding CVS to your LFS, building it from source, of course :)
-- Doug
^ permalink raw reply [flat|nested] 3+ messages in thread
* RE: Speakup with LFS?
Speakup with LFS? Zachary Kline
` Doug Sutherland
@ ` Georgina Joyce
1 sibling, 0 replies; 3+ messages in thread
From: Georgina Joyce @ UTC (permalink / raw)
To: 'Speakup is a screen review system for Linux.'
Hi
Yes I used a link while I had one terminal that was chrooted into the newly built lfs partition:
Ln -s /mnt/lfs/usr/src/linux-2.6.21.5 /usr/src/linux
But you could also use the host system to build a new kernel and even boot the host with a new kernel to ensure that it is satisfactory. When you have a working tree tar it up and move the tar ball across and extract it, run make and make modules_install and make the necessary amendments to the boot loader configuration file. I can't remember what switches I used on the compression of the speakup patched tree but a quick look at the tar man page will give an idea. Not sure if I used anything more than tar -czf linux-2.6.21.5 linux-2.6.21.5-with_CVS_speakup.tar.gz
I guess that there are even more ways you could undertake this task.
Good luck, lfs is a very rewarding process.
Actually, I'm being asked by Ken Moffat how they could make their blfs book more accessible to us speakup users, so if you have any ideas, let me know and I'll pass them on.
HTH
Gena
Amateur Call: M 0 E B P
VOIP / IM: gena1959uk
-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca] On Behalf Of Zachary Kline
Sent: Friday, June 22, 2007 8:29 PM
To: Speakup is a screen review system for Linux.
Subject: Speakup with LFS?
Hiya,
I was wondering if anybody on here had experience building an LFS system with Speakup in the new kernel. I have a good idea of how to go about doing it, but don't want to end up with a system that won't talk from boot when I need to try it. What I was thinking is that since a symbolic link can cross filesystems, I could temporarily change /usr/src/linux to point to the directory of my LFS kernel unpacking.
I could then do a CVS checkout--using my existing Linux system, of course, since LFS doesn't come with CVS. I'd then just change the symlink.
Would this work?
Thanks muchly,
Zack.
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
__________ NOD32 2348 (20070623) Information __________
This message was checked by NOD32 antivirus system.
http://www.eset.com
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~ UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
Speakup with LFS? Zachary Kline
` Doug Sutherland
` Georgina Joyce
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).