Password file updating

1999-01-03 Thread Philip Inglesant
Apologies if this has been discussed before, but I have a little programming problem that I need solving. We use a client/server system to send encoded messages from a machine that allows our customer service people to add new users, change password, etc. on various servers controlled from a sing

Re: PPS Timing Interface and ONCORE GPS Clock / NTPD

1999-01-03 Thread Marty Cawthon
I was using ntp-4.0.98a. After reading your message I understand the source of my trouble. I downloaded and compiled ntp-4.0.98d This ntp-4.0.98d is now working OK. I normally read the -Stable Mailing List, but missed your message because I unsubscribed temporarily to reduce email while travelli

Re: easyboot far into disk

1999-01-03 Thread Zhihui Zhang
On Fri, 5 Nov 1999, Mike Smith wrote: > > > partition, and I was unable to boot FreeBSD. What I did: wipe out FreeBSD > > > partition; use Partition Magic 4.0 to move the Win98 partition to the end > > > of the disk; reinstall FreeBSD in the newly empty 3 GB partition at the > > > front of

Re: VLAN support in -stable? (fwd)

1999-01-03 Thread Chad R. Larson
During an off-line discussion, a friend of mine wrote: >>> I have just come across a big problem using vlans on a FreeBSD box. >>> The mtu on the vlan interfaces is only 1496 bytes, the problem is >>> that any packets destined for the Interface larger than this are >>> just thrown away. The solu

Re: PPS Timing Interface and ONCORE GPS Clock / NTPD

1999-01-03 Thread John Hay
You don't say which version of ntp you are using. If you are using something older than ntp-4.0.98b, please read the message I sent on Oct 16 to freebsd-stable with the subject line: HEADS UP: ntpd users If you are using ntp-4.0.98b or later tell me and I will look into it, because it is working

PPS Timing Interface and ONCORE GPS Clock / NTPD

1999-01-03 Thread Marty Cawthon
SUMMARY: ONCORE GPS Clock source for NTPD on FreeBSD was working with 3.3-Stable (Oct 8 1999). With 3.3-Stable (Nov 4 1999) NTPD fails with a 'time_pps_setparams: Inappropriate ioctl for device' message. It seems that '/dev/pps' may have been changed to '/dev/lppps0' REFERENCE: http://phk.fr

Re: easyboot far into disk

1999-01-03 Thread Randy Bush
> You misremember; it has to be on the first disk, but it can be in any > primary partition there. doh. thanks. game over. randy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message

Re: easyboot far into disk

1999-01-03 Thread Mike Smith
> > partition, and I was unable to boot FreeBSD. What I did: wipe out FreeBSD > > partition; use Partition Magic 4.0 to move the Win98 partition to the end > > of the disk; reinstall FreeBSD in the newly empty 3 GB partition at the > > front of the disk. Now both FreeBSD and Win98 boot OK. >

Re: easyboot far into disk

1999-01-03 Thread Jim King
At 07:28 AM 11/5/1999 -0800, Randy Bush wrote: > >> i did flash a new bios, and it did install up there at 10-13g. it just > >> won't boot. > > I had a similar problem, on a newish Dell PC (less than a year old) with a > > 16 GB drive. I had a 13 GB Win98 partition followed by a 3 GB FreeBSD > >

Re: easyboot far into disk

1999-01-03 Thread Randy Bush
>> i did flash a new bios, and it did install up there at 10-13g. it just >> won't boot. > I had a similar problem, on a newish Dell PC (less than a year old) with a > 16 GB drive. I had a 13 GB Win98 partition followed by a 3 GB FreeBSD > partition, and I was unable to boot FreeBSD. What I d

Re: easyboot far into disk

1999-01-03 Thread Jim King
At 10:48 PM 11/4/1999 -0800, Randy Bush wrote: > >>> - Boot the install floppy. > >> i presume you mean the kern.flp floppy. > >>> When the little spinning widget appears > >>> and stops, hit the spacebar. At the 'boot:" prompt, type > >>> wd(0,a)/boot/loader > >> Disk error 0x1 (lba=0x

Re: easyboot far into disk

1999-01-03 Thread Mike Smith
> >>> - Boot the install floppy. > >> i presume you mean the kern.flp floppy. > >>> When the little spinning widget appears > >>> and stops, hit the spacebar. At the 'boot:" prompt, type > >>> wd(0,a)/boot/loader > >> Disk error 0x1 (lba=0x1388b3c) > >> Disk error 0x1 (lba=0x1388b