Re: Best way to get a system on current?
On Fri, Oct 12, 2001 at 11:36:30AM -0500, Bob Willcox wrote: On Fri, Oct 12, 2001 at 09:20:35AM -0700, David Wolfskill wrote: Might help if you provided a pointer to the problems you had in the upgrade from -STABLE case. For that matter, a bit more detail on the install failed to mount the filesystems for the install from -CURRENT snapshot case would be of interest, as well. As for the snapshot install, since it's errors were only written to the screen I have to work from memory here as well. I believe the first complaint had to do with the filesystems to be mounted (/mnt/usr, for example) not specified in fstab. Since all of the mounts to /mnt failed, the system fails pretty soon apparently running out of space in /. Ahh, so I'm not the only one that ran into this problem. I thought I'd balked something up myself, so I did some extensive fiddling to try and rectify the problem. I got it working eventually by issuing newfs manually on each of the new partitions, mounting them on their respective /mnt mount points (i.e. /mnt, /mnt/var, /mnt/usr, etc), then symlinking these back to their root mount point equivalents (/var, /var/tmp, /usr, etc). I actually did all of this while the sysinstall dialog was still up on the first terminal -- once I'd fiddled with all the mount points and selected to try and install the bin distribution again, it worked. Not exactly an elegant solution, unfortunately. It'd be interesting to hear if anyone else has this problem. Thanks, Bob Regards, Trent. -- Trent Nelson - Software Engineer - [EMAIL PROTECTED] A man with unlimited enthusiasm can achieve almost anything. --unknown To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Best way to get a system on current?
Hi All, I am interested in what is the best way to get a test system running current? I have tried both upgrading from 4.4-stable (ran into kernel build problems) and installing from the 5.0-20011011-CURRENT snapshot (install failed to mount the filesystems). I decided that I would query the net-wisdom prior to investigating either of these approached any further, though. BTW, before y'all (note, I live in Texas) beat me up for not reading the freebsd-current mailing list, I would like to point out that I have read it but didn't found anything apparent that addresses this (and that's not to say that it's not there, just that I didn't find it...pointers to any oversight on my part are welcomed). Any suggestions?? Thanks, Bob -- Bob Willcox Putt's Law: [EMAIL PROTECTED]Technology is dominated by two types of people: Austin, TXThose who understand what they do not manage. Those who manage what they do not understand. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Best way to get a system on current?
On Fri, Oct 12, 2001 at 09:20:35AM -0700, David Wolfskill wrote: Might help if you provided a pointer to the problems you had in the upgrade from -STABLE case. For that matter, a bit more detail on the install failed to mount the filesystems for the install from -CURRENT snapshot case would be of interest, as well. In my case, I just followed the instructions in /usr/src/UPDATING, and it worked (once I fabricated a replacement kernel config file). Unfortunately, the actual specifics on what failed on the upgrade attempt were lost on the attempted snapshot install. However from memory, the problem was that the kernel build failed (the make buildworld was successful). It appeared that the make buildkernel was using header files from the current system, rather than the /usr/src/sys tree, when building, but I'm not certain. Note that, now that I think somemore about it, I may have _not_ have created a new kernel config file. (I usually do, but don't recall doing it this time.) Consequently, I may have been trying to use the 4.4 kernel file that I had for this system. I really wouldn't expect that to work. If that's the case, I can start all over again with this approach (install 4.4 and upgrade). As for the snapshot install, since it's errors were only written to the screen I have to work from memory here as well. I believe the first complaint had to do with the filesystems to be mounted (/mnt/usr, for example) not specified in fstab. Since all of the mounts to /mnt failed, the system fails pretty soon apparently running out of space in /. Thanks, Bob Cheers, david -- David H. Wolfskill[EMAIL PROTECTED] As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. -- Bob Willcox Putt's Law: [EMAIL PROTECTED]Technology is dominated by two types of people: Austin, TXThose who understand what they do not manage. Those who manage what they do not understand. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Best way to get a system on current?
On Fri, Oct 12, 2001 at 11:15:34AM -0500, Bob Willcox wrote: I am interested in what is the best way to get a test system running current? I have tried both upgrading from 4.4-stable (ran into kernel build problems) It would be nice to see the problems you experienced. One is supose to be able to update from 4.4-stable to 5-CURRENT. Do you still have the error output (and the exact sequence of commands that produced it)? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Best way to get a system on current?
On Fri, Oct 12, 2001 at 11:16:18AM -0700, David O'Brien wrote: On Fri, Oct 12, 2001 at 11:15:34AM -0500, Bob Willcox wrote: I am interested in what is the best way to get a test system running current? I have tried both upgrading from 4.4-stable (ran into kernel build problems) It would be nice to see the problems you experienced. One is supose to be able to update from 4.4-stable to 5-CURRENT. Do you still have the error output (and the exact sequence of commands that produced it)? No, unfortunately the output is long gone (lost in the subsequent attempt to install the 5.0-current snapshot). I'm planning on recreating the snapshot install failure (or getting it right this time and having the install work:-). If I still can't install the snapshot, I will resort to installing 4.4 and trying the upgrade again. I do remember that it was in the make buildkernel step that I had the problem (the make buildworld was successful). A compile failed due to what looked like it was using the wrong header files (from /usr/include/sys). If this should recur, I will save the output. Note that I may have used the old 4.4 kernel config file for this though. Next time I plan on using the GENERIC config file. Thanks, Bob -- Bob Willcox Putt's Law: [EMAIL PROTECTED]Technology is dominated by two types of people: Austin, TXThose who understand what they do not manage. Those who manage what they do not understand. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
