Re: disappearing mount points after install

2000-01-27 Thread Marwan Fayed
On Wed, 26 Jan 2000, Brian D. Moffet wrote: > At 03:59 PM 1/22/00 -0500, you wrote: > >FreeBSD loader does not start up, nor does the kernel (obviously). The > >error message I get back is literally translated as "No O.S." > > on the other versions of Intel Unix I have used dd the master boot bl

Re: disappearing mount points after install

2000-01-23 Thread Marwan Fayed
o contribute to the freebsd project (as long as it doesn't interfere with school, of course ) On Sat, 22 Jan 2000, Thierry Herbelot wrote: > Hello > > [-mobile trimmed] > > Marwan Fayed wrote: > > > > Hello, > > > > I am a seasoned UNIX user but hav

Re: disappearing mount points after install

2000-01-22 Thread Marwan Fayed
OK, I'm glad about fstab and my mount points, but I have already tried using 'a' and then i hit 's' to set bootable before I 'w' to write. I've actually tried this more times than i can count! When I do re-enter the fdisk using install disks though, the slice is no longer marked 'A' for active. P

Re: disappearing mount points after install

2000-01-22 Thread Marwan Fayed
er to buy dinner for whoever is able to solve this one! :-) Marwan On Sat, 22 Jan 2000, Boris Karnaukh wrote: > Marwan Fayed wrote: > > > > My problem is this. I am trying to install 3.3-R on an IBM Thinkpad 365XD > > (although I have received mail from a man in France who is

Re: disappearing mount points after install

2000-01-22 Thread Marwan Fayed
mean I have everyone stumped? ;-) Marwan On Sat, 22 Jan 2000, Thierry Herbelot wrote: > Hello > > [-mobile trimmed] > > Marwan Fayed wrote: > > > > Hello, > > > > I am a seasoned UNIX user but have been using freebsd for only about 6 > > months. I

disappearing mount points after install

2000-01-22 Thread Marwan Fayed
Hello, I am a seasoned UNIX user but have been using freebsd for only about 6 months. I have posted this problem to freebsd-questions with no response so, figuring it must be a bug in the install program i'm going to try here. Oh, I would like to have traced the code to try to find the bug (if on