Re: apcupsd vs FreeBSD-5.2.x
Hi, - Original Message - From: "Peter Risdon <[EMAIL PROTECTED]>" To: To Stacey Roberts Date: Tue, 27 Jul, 2004 22:56 BST Subject: Re: apcupsd vs FreeBSD-5.2.x > Stacey Roberts wrote: > >Hi Peter, > > > >- Original Message - > >From: "Peter Risdon <[EMAIL PROTECTED]>" > >[snip] > >>So you'd want: > >> > >>link cuaa1 usv > > > > > >Okay, I understand. And I take it that if the serial signalling cable is > >actually connected to (labeled) serial port 1, then the corresponding > >device tobe used here would be cuaa0? > > > > > > The numbering of serial ports in FreeBSD starts at 0, so what would be > called com1 in DOS/Windows is cuaa0 in FreeBSD. Yes, I knew this.., > > If the numbering of the ports on your computer follows the same pattern, > then serial port 1 would map to cuaa0. Thanks for that clarification. I just thought that the pkg-message using cuaa1 was somewhat strange as this is in effect serial 2 and not the first serial interface. I would have thought that the example would have used the first (cuaa0) for the example by default. Cheers for this. Regards, Stacey > > > Peter. > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" pgpKywdmwa90E.pgp Description: PGP signature
Re: apcupsd vs FreeBSD-5.2.x
Stacey Roberts wrote: Hi Peter, - Original Message - From: "Peter Risdon <[EMAIL PROTECTED]>" [snip] So you'd want: link cuaa1 usv Okay, I understand. And I take it that if the serial signalling cable is actually connected to (labeled) serial port 1, then the corresponding device tobe used here would be cuaa0? The numbering of serial ports in FreeBSD starts at 0, so what would be called com1 in DOS/Windows is cuaa0 in FreeBSD. If the numbering of the ports on your computer follows the same pattern, then serial port 1 would map to cuaa0. Peter. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: apcupsd vs FreeBSD-5.2.x
Hi Peter, - Original Message - From: "Peter Risdon <[EMAIL PROTECTED]>" To: To Stacey Roberts Date: Tue, 27 Jul, 2004 21:00 BST Subject: Re: apcupsd vs FreeBSD-5.2.x > Stacey Roberts wrote: > >Hi Peter, > > Thanks for the reply. > > > >>Stacey Roberts wrote: > >> > >>>[snip] > >>>The other problem I've got is that with the instruction to create a soft > >>>link > >>>for /dev/usv, on reboot, that soft link is of course disappears, so I > >> > >>have to > >> > >>>manually recreate that soft link again, before (again) manually starting > >>>apcupsd from cmdline. > >> > >>You need to make an appropriate entry in devfs.conf for any > >>customisation of /dev to persist beyond a reboot with FreeBSD 5. - > >>something like: > >> > >>link target name > > > > > >Ah.., yes.., Do you mind checking my syntax, please? According to your > >suggestion, I'd be adding: > > > >link /dev/cuaa1 /dev/usv > > > >to /etc/devfs.conf, and that should be it? > > No - look at the file, there are sample entries there: > > # Commonly used by many ports > linkacd0cdrom > linkcuaa0 pilot > > So you'd want: > > link cuaa1 usv Okay, I understand. And I take it that if the serial signalling cable is actually connected to (labeled) serial port 1, then the corresponding device tobe used here would be cuaa0? > > > > > > >Whislt I'm keen to try this out, could I then ask the obvious question, > >is there some reason why in apcupsd.conf I am not allowed to simply > use /dev/cuaa1? > > > > I'm afraid I'm not sufficiently familiar with this software to answer. > But it would almost certainly be less problematic to stick with the > suggested link. I understand., seems to be there for what I imagine to be for some good reason. This has been really helpful, Peter. Thanks again. Regards, Stacey > > >Thanks again for taking the time. > > My pleasure, hope it helps. > > Peter. > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" pgp6lXncUcKKK.pgp Description: PGP signature
Re: apcupsd vs FreeBSD-5.2.x
Stacey Roberts wrote: Hi Peter, Thanks for the reply. Stacey Roberts wrote: [snip] The other problem I've got is that with the instruction to create a soft link for /dev/usv, on reboot, that soft link is of course disappears, so I have to manually recreate that soft link again, before (again) manually starting apcupsd from cmdline. You need to make an appropriate entry in devfs.conf for any customisation of /dev to persist beyond a reboot with FreeBSD 5. - something like: link target name Ah.., yes.., Do you mind checking my syntax, please? According to your suggestion, I'd be adding: link /dev/cuaa1 /dev/usv to /etc/devfs.conf, and that should be it? No - look at the file, there are sample entries there: # Commonly used by many ports linkacd0cdrom linkcuaa0 pilot So you'd want: link cuaa1 usv Whislt I'm keen to try this out, could I then ask the obvious question, >is there some reason why in apcupsd.conf I am not allowed to simply use /dev/cuaa1? I'm afraid I'm not sufficiently familiar with this software to answer. But it would almost certainly be less problematic to stick with the suggested link. Thanks again for taking the time. My pleasure, hope it helps. Peter. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: apcupsd vs FreeBSD-5.2.x
Hi Peter, Thanks for the reply. - Original Message - From: "Peter Risdon <[EMAIL PROTECTED]>" To: To Stacey Roberts Date: Tue, 27 Jul, 2004 20:12 BST Subject: Re: apcupsd vs FreeBSD-5.2.x > Stacey Roberts wrote: > > > >[snip] > >The other problem I've got is that with the instruction to create a soft > >link > >for /dev/usv, on reboot, that soft link is of course disappears, so I > have to > >manually recreate that soft link again, before (again) manually starting > >apcupsd from cmdline. > > You need to make an appropriate entry in devfs.conf for any > customisation of /dev to persist beyond a reboot with FreeBSD 5. - > something like: > > link target name Ah.., yes.., Do you mind checking my syntax, please? According to your suggestion, I'd be adding: link /dev/cuaa1 /dev/usv to /etc/devfs.conf, and that should be it? Whislt I'm keen to try this out, could I then ask the obvious question, is there some reason why in apcupsd.conf I am not allowed to simply use /dev/cuaa1? Thanks again for taking the time. Regards, Stacey > > > > >Is there something that I've missed out somewhere that is causing apcupsd > >not to start automatically on reboot? > > > > I imagine this is the same problem. > > Peter. > > > > > >If there is any more information I should post that would of use to anyone > >wanting to assist, please let me know. > > > >Thanks for the time. > > > >Regards, > > > >Stacey pgpRsr12podE2.pgp Description: PGP signature
Re: apcupsd vs FreeBSD-5.2.x
Stacey Roberts wrote: [snip] The other problem I've got is that with the instruction to create a soft link >for /dev/usv, on reboot, that soft link is of course disappears, so I have to manually recreate that soft link again, before (again) manually starting apcupsd from cmdline. You need to make an appropriate entry in devfs.conf for any customisation of /dev to persist beyond a reboot with FreeBSD 5. - something like: link target name Is there something that I've missed out somewhere that is causing apcupsd not to start automatically on reboot? I imagine this is the same problem. Peter. If there is any more information I should post that would of use to anyone wanting to assist, please let me know. Thanks for the time. Regards, Stacey ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"