gphoto2 / Canon PowerShot A200 / FreeBSD
Has anyone gotten this to work in FreeBSD? In gphoto or anything else?
No real luck on the gphoto mailing list, and I can't get it working.
It seems to be connected fine:
root@knyghtmare:/root# usbdevs
addr 1: UHCI root hub, Intel
addr 2: PowerShot A200, Canon Inc.
Latest version of gphoto in ports doesn't seem to know my camera, from
CVS it claims to, but it doens't seem to work all that well:
root@knyghtmare:/root# gphoto2 --camera "Canon PowerShot A200" --port
"usb:" -P
*** Error ***
An error occurred in the io-library ('Bad parameters'): Could not find
USB device (vendor 0x4a9, product 0x3062). Make sure this device is
connected to the computer.
*** Error (-2: 'Bad parameters') ***
I can send the full debugging output if it's needed at all.
Thanks.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
Re: FreeBSD version of Linux's "passwd -l"
That's from the lock(1) man page, not the pw(8) man page. the relevant section from the pw man page is as follows: USER LOCKING Pw supports a simple password locking mechanism for users; it works by prepending the string `*LOCKED*' to the beginning of the password field in master.passwd to prevent successful authentication. The lock and unlock commands take a user name or uid of the account to lock or unlock, respectively. The -V, -C, and -q options as described above are accepted by these commands. On Sat, 2002-10-19 at 21:01, Bsd Neophyte wrote: > > this is what i pulled from the 'pw' man page about the 'lock' option. > > to me, it doesn't seem as if they do the same thing. > > - > DESCRIPTION > The lock utility requests a password from the user, reads it again for > verification and then will normally not relinquish the terminal until the > password is repeated. There are two other conditions under which it will > terminate: it will timeout after some interval of time and it may be > killed by someone with the appropriate permission. > -- > > whereas the linux version states that it makes the account available for > root only. > > -- > -l > This option is used to lock the specified account and it is available to > root only. The locking is performed by rendering the encrypted password > into an invalid string (by prefixing the encrypted string with an !). > -- > > > --- Ceri Davies <[EMAIL PROTECTED]> wrote: > > On Sat, Oct 19, 2002 at 08:17:53AM -0700, Bsd Neophyte wrote: > > > > > > i'm following a pretty decent IBM tutorial on how to setup a samba > > PDC. > > > in the tutorial the following command is mentioned: > > > > > > passwd -l > > > > pw lock [user] > > > > Check the pw manpage. > > > > Ceri > > > > -- > > you can't see when light's so strong > > you can't see when light is gone > > > __ > Do You Yahoo!? > Yahoo! Autos - Get free new car price quotes > http://autos.yahoo.com > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message > signature.asc Description: This is a digitally signed message part
sendmail woe
I've been having this problem for some time, I thought the upgrade to 4.7 might fix it - it didn't. Neither did using a fresh config file from /usr/src/etc/sendmail. The problem is this: while SMTP works fine, and sendmail otherwise works for the receiving of mail, sendmail doesn't seem to send mail correctly. It appears to be sending it to (the SMTP server on?) localhost.com, instead of locally. Thus I can't send mail via sendmail, or via anything that uses it. The error messages change depending on the state of localhost.com, before it said relaying denied, now it just times out. I have a feeling changing my hostname from domain.tld to sub.domain.tld would be a workaround, but I'm looking for a better solution. I'm 95% sure I'm missing something simple here. Thanks. signature.asc Description: This is a digitally signed message part
Re: CVSUP update from 4.6 -> 4.7
Oops. Yes, you're right, I forgot. On Wed, 2002-10-16 at 09:58, Paulius Bulotas wrote: > On 02 10 16, Tom Carrick wrote: > > > The box is located 3000 Kms away and I can only connect > > > via ssh. > > world, compile kernel, drop to single user, install world, install > > ;) don't drop to single user mode ;) > > you can stop all unneeded services (even sshd, but don't kill your > active session) and then make installworld and so on. And make a backup > of /etc before running mergemaster ;) but not to /tmp if it's cleaned > after every reboot ;) > > Paulius > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message > signature.asc Description: This is a digitally signed message part
Re: CVSUP update from 4.6 -> 4.7
On Wed, 2002-10-16 at 09:27, BigBrother wrote: > > > I have freebsd 4.6 release and I am interesting to > update it to 4.7 via CVSUP > > The box is located 3000 Kms away and I can only connect > via ssh. > > a) How much space is required in order to make a buildworld > (downloading CVSUP, compiling, installing) A few hundred MB is a safe bet. > > b) What is the best failsafe method, so in case I do this and > happen to have an error, my system will continue to operate > on the 4.6? As I said I am too far away to go to fix it there... >From personal experience, update sources, rm -rf /usr/obj/*, compile world, compile kernel, drop to single user, install world, install kernel, reboot. If they both compile, it's a good bet they'll run. You can happily compile the new world and kernel, that is 100% sure to not screw anything up, as they both stay under /usr/obj/. You can do what you want, it's still 4.6 until you install them. > > c) Can somebody point me or give me a sample CVSUP configuration > for updating to the 4.7 release? *default host=cvsup2.uk.FreeBSD.org *default base=/usr/local *default prefix=/usr *default release=cvs tag=RELENG_4_7_0_RELEASE *default delete use-rel-suffix *default compress That's mine. Change the host to a local one is all you should need to do. > > > d) Are there any tips for remote updates/buildworld? I know that is not > suggested but I find too difficult to live with all the critical bugs > that 4.6 has and I would like to get rid of them. uh... be careful? Other than that, I wouldn't know. > > e) Do I have to compile only a kernel on 4.7 or to make a buildworld too > for the new binaries to be replaced? If I compile only a 4.7 kernel and > my binaries are 4.6 will this poses any trouble? Very bad idea to only compile a new kernel. Compile the world and the kernel if you want to be sure they won't screw up somehow. > > > Thanks in advance guys! > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message > signature.asc Description: This is a digitally signed message part
Re: portupgrade problem
That worked great, thanks. Can you give me some explanation on why (and how) this happens, and in what way it messes up? On Tue, 2002-10-08 at 07:35, Adam Weinberger wrote: > try portsdb -fu. the switches are easy enough to remember ::P. > portupgrade dies from time to time, and that command can often get you > back in business. > > -Adam > > > >> (10.07.2002 @ 2115 PST): Tom Carrick said, in 2.0K: << > > I was using portupgrade happily upgrading my ports, when it barfed in > > the middle of something. I don't remember exactly what, I think it could > > have been links or libslang. I don't remember the exact error, only that > > it had something to do with memory. So I assumed there just wasn't > > enough available. I checked with top, and I still had a good 50MB of RAM > > available, and most of my swap space (500MB orso) free. > > > > Fair enough. So I try to continue. It fails on the package upgrade. > > Trying to find out what fails, I tried pkgdb -u. Failed. Same error. I > > tried deleting portupgrade and installing it again, to no effect. > > > > It invariably, depending on the phase of the moon, I suppose, gives one > > of two errors, either: > > > > root@knyghtmare:/root# pkgdb -u > > [Updating the pkgdb in /var/db/pkg ... - 325 > > packages found (-3 +2) > > (...)/usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:435: [BUG] Segmentation > > fault > > ruby 1.6.7 (2002-09-12) [i386-freebsd4] > > Abort (core dumped) > > > > or... > > > > root@knyghtmare:/root# pkgdb -u > > [Updating the pkgdb in /var/db/pkg ... - 325 > > packages found (-3 +2) (...)Cannot allocate memory: Cannot update the > > pkgdb!] > > > > I've tried rebooting. Doesn't seem to help, and it was working fine > > until it barfed on me. > > > > I've tried deleting links and libslang, too, in case it messed the > > database somehow. That's still my best theory, though deleting them > > didn't help. > > > > Anyone have any ideas? > > > >> end of "portupgrade problem" from Tom Carrick << > > > -- > "Oh good, my dog found the chainsaw." > -Lilo, "Lilo & Stitch" > Adam Weinberger > [EMAIL PROTECTED] > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message > signature.asc Description: This is a digitally signed message part
portupgrade problem
I was using portupgrade happily upgrading my ports, when it barfed in the middle of something. I don't remember exactly what, I think it could have been links or libslang. I don't remember the exact error, only that it had something to do with memory. So I assumed there just wasn't enough available. I checked with top, and I still had a good 50MB of RAM available, and most of my swap space (500MB orso) free. Fair enough. So I try to continue. It fails on the package upgrade. Trying to find out what fails, I tried pkgdb -u. Failed. Same error. I tried deleting portupgrade and installing it again, to no effect. It invariably, depending on the phase of the moon, I suppose, gives one of two errors, either: root@knyghtmare:/root# pkgdb -u [Updating the pkgdb in /var/db/pkg ... - 325 packages found (-3 +2) (...)/usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:435: [BUG] Segmentation fault ruby 1.6.7 (2002-09-12) [i386-freebsd4] Abort (core dumped) or... root@knyghtmare:/root# pkgdb -u [Updating the pkgdb in /var/db/pkg ... - 325 packages found (-3 +2) (...)Cannot allocate memory: Cannot update the pkgdb!] I've tried rebooting. Doesn't seem to help, and it was working fine until it barfed on me. I've tried deleting links and libslang, too, in case it messed the database somehow. That's still my best theory, though deleting them didn't help. Anyone have any ideas? signature.asc Description: This is a digitally signed message part
Re: Xlock equivalent for terminal ?
Have you tried lock? ;) On Wed, 2002-10-02 at 00:05, Mike Hogsett wrote: > > It seems silly, but someone where just asked about an Xlock equivalent > program for the console. He would like something which he can call after > throwing startx into the background to lock the virtual console. > > He would like this for both his freebsd boxes and linux boxes since they > both share his environ over NFS. It is more important for the linux end > though because Redhat chowns several things to the user on the console at > login and chowns them back if he logs out of the console (such as the > sounds devices and floppy dev). > > Any ideas ? > > Thanks > > - Mike Hogsett > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message > signature.asc Description: This is a digitally signed message part
