My New JHALFS Build is Gone...Missing...Not There

2010-07-18 Thread Dan McGhee
Yes all of that is true. I awoke this morning with thoughts of configuring grub and building the kernel so that I could move on to BLFS. When I mounted the partition upon which I had built jhalfs, there was nothing on it but /jhalfs. That directory contained another directory `jhalfs-2.3.2`

Re: My New JHALFS Build is Gone...Missing...Not There

2010-07-18 Thread emteeoh
with BlackBerry -Original Message- From: Dan McGhee Sender: lfs-support-boun...@linuxfromscratch.org Date: Sun, 18 Jul 2010 10:06:53 To: LFS Support List Reply-To: LFS Support List Subject: My New JHALFS Build is Gone...Missing...Not There Yes all of that is true. I awoke this morning

Re: My New JHALFS Build is Gone...Missing...Not There

2010-07-18 Thread Thomas Pegg
On 7/18/2010 11:06 AM, Dan McGhee wrote: > Yes all of that is true. I awoke this morning with thoughts of > configuring grub and building the kernel so that I could move on to > BLFS. When I mounted the partition upon which I had built jhalfs, > there was nothing on it but /jhalfs. That directo

Re: My New JHALFS Build is Gone...Missing...Not There

2010-07-18 Thread Dan McGhee
On 07/18/2010 01:21 PM, Thomas Pegg wrote: > On 7/18/2010 11:06 AM, Dan McGhee wrote: >> Here's how I ran jhalfs: >> >> 1. untarred the archive in my home directory >> 2. ran make and configured jhalfs >> >> > These first two steps are fine. If you haven't already wiped out and > started o

Re: My New JHALFS Build is Gone...Missing...Not There

2010-07-18 Thread linux fan
On 7/18/10, Dan McGhee wrote: > I've started again and that's the way I ran except that, again, I > want it to stop after Ch. 6 so I ran > NOT: make mk_CHROOT make BREAKPOINT=mk_CHROOT If you want it to stop after finishing target mk_CHROOT BREAKPOINT is all caps and no typos allowed -- ht

Re: My New JHALFS Build is Gone...Missing...Not There

2010-07-18 Thread Bruce Dubbs
Dan McGhee wrote: > Before I power down tonight, I'm going > to back the build up. I might be an old dog, but I sure can learn new > tricks. :) Why power down? $ w 13:20:09 up 436 days, 17:12, 1 user, load average: 0.21, 0.24, 0.18 Different system: $ w 19:22:35 up 395 days, 14:19, 1

Re: My New JHALFS Build is Gone...Missing...Not There

2010-07-18 Thread Dan McGhee
On 07/18/2010 02:19 PM, linux fan wrote: > On 7/18/10, Dan McGhee wrote: > > >> I've started again and that's the way I ran except that, again, I >> want it to stop after Ch. 6 so I ran >> >> > NOT: make mk_CHROOT > > make BREAKPOINT=mk_CHROOT > > If you want it to stop after finishing

Re: My New JHALFS Build is Gone...Missing...Not There

2010-07-18 Thread Dan McGhee
On 07/18/2010 02:23 PM, Bruce Dubbs wrote: > Dan McGhee wrote: > > > >> Before I power down tonight, I'm going >> to back the build up. I might be an old dog, but I sure can learn new >> tricks. :) >> > Why power down? > There's no technical reason. It's a habit I have when I go to be

Re: My New JHALFS Build is Gone...Missing...Not There

2010-07-18 Thread Thomas Pegg
On 7/18/2010 2:48 PM, Dan McGhee wrote: > > Good to know. Thanks. I started again with GMT, but it's not hard to > change--unless the build disappears. :) > > Thomas, thanks for the help. I just may have stumbled on to "doing it > right" this time. Right now, jhalfs has been cooking for about an ho

Re: My New JHALFS Build is Gone...Missing...Not There

2010-07-19 Thread Dan McGhee
On 07/18/2010 10:44 PM, Thomas Pegg wrote: > Something else to note is that by default jhalfs's default build > directory is /mnt/build_dir not /mnt/lfs. > That one I didn't miss. But thanks for pointing it out. Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.l

JHALS BUILD COMPLETE [Was: My New JHALFS Build is Gone...Missing...Not There]

2010-07-19 Thread Dan McGhee
On 07/18/2010 10:06 AM, Dan McGhee wrote: > [After a completed build and a reboot] When I mounted the partition upon > which I had built jhalfs, > there was nothing on it but /jhalfs. That directory contained another > directory `jhalfs-2.3.2` Yes, it's the untarred package. It wasn't > there y