Re: AMD64 Desktop Support
Chad Leigh -- Shire.Net LLC wrote: You can always run the 32bit i386 version on the AMD motherboard if you find out that the above stuff doesn't work so well. I don't use FreeBSD as a desktop so I cannot comment on that part but amd64 issues with flash etc does not mean you have to buy a P4 or other Intel chip based system. Not really anything against Intel here, just thought that the AMD might be worth looking at. Just so much of what is available for purchase for either platform seems to have issues with hardware support. Thanks for the feedback just the same. -- In theory, there is no difference between theory and practice. In practice, there is. - Yogi Berra ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: AMD64 Desktop Support
Mark Kane wrote: Hi. I'm using an Athlon64 3000+ (and the amd64 version of FreeBSD) as my main workstation. I also have another workstation with the same CPU running the i386 version. Here's my opinions: Flash - The 32 bit Linux binary of Flash 7 works in linux-firefox or linux-opera fine in i386 or amd64. The 32 bit Linux version of Flash 6 works somewhat with linuxpluginwrapper and the native Firefox on the i386 version of FreeBSD, although I've found it to be somewhat unstable and crashed quite a bit. There's also a project Gnash that is an open source Flash player, but I have not tried that one yet. Acrobat - The Linux binary of Acrobat 7 works for sure in the i386 version of FreeBSD. I have not tested it on my amd64 one (I just use xpdf), but the port's Makefile says it works and I don't see why it would have a problem. nVidia Drivers - Work great in the i386 version of FreeBSD. Does not work on the amd64 version yet ( http://www.nvnews.net/vbulletin/showthread.php?t=41545 ). Java - Got it to work on i386 version of FreeBSD (interfacing with browser not attempted, just for OpenOffice), but have not needed to or attempted on my amd64 box. I'm not sure if it's even possible for amd64 or not (as the Makefile I looked at shows only for i386), but someone else will know. For my purposes, there really isn't much that the amd64 version cannot do that the i386 version can. I would like the nVidia driver to work since I have a decent video card, but the Flash and Java I don't really care about much anymore. I use the native Firefox compiled from ports for my browsing and just fire up linux-opera whenever I need to see a Flash site. Unfortunately, those items are pretty important to me. Kind of the point of the mail. I appreciate the feedback, and I am aware of some of the work arounds you mentioned. I use JEdit daily, as well as a couple of other Java apps. The nVidia driver thing stinks too. I had that running on my PC before the crash, and really liked it. Me personally, I prefer AMD hardware over Intel and would get the Athlon64 regardless of if I run in i386 or amd64 mode FreeBSD. I don't have any bias towards either company. My focus is spending my money on what will actually work. Starting to feel like I'll be looking at the Pentium-D processors. I've got a laptop with a dual core Pentium and it works pretty sweet. However, be sure to check your AMD64 hardware against the compatibility list before buying. I had to buy a replacement motherboard real quickly one day after one failed and I didn't fully check out the list before buying. When I got it, it turns out the onboard NIC and sound didn't work with FreeBSD in i386 or amd64 mode. I already had a NIC and sound card ready to go from the previous machine, but now both PCI slots on the Micro-ATX motherboard are taken and unfortunately I can't put in a SCSI card. I've been looking over spec pages like crazy for various motherboards, with particular attention on network and audio. The amd64 motherboard list is here. Note that amd64 in this case means the hardware itself and not the OS version, so if it's not listed here then the i386 version probably will not work either with that hardware (I found that out the hard way): http://www.freebsd.org/platforms/amd64/motherboards.html For sound cards, I have found the Sound Blaster stuff to work well with FreeBSD so far. I'm running an Augidy 2 Platinum in my main machine and it works better than on Windows (had tons of skipping problems that never could be solved -- thought it was a bad card but moving to FreeBSD eliminated them). The cheaper SB LIVE cards work too, and some of my machines have onboard which work great also. Hope that helps. :) Any and all feedback is appreciated. For as nice as the AMD64 processor may be, sounds like things are a ways off before the software has fully caught up. Thanks, -- In theory, there is no difference between theory and practice. In practice, there is. - Yogi Berra ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: AMD64 Desktop Support
Andy Reitz wrote: In 64-bit mode, that does appear to be the case. However, it sounds like you could purchase an AMD64-based processor, and have everythign work fine in 32-bit mode. Then later down the road, as the software evolves, you could upgrade FreeBSD to be 64-bit and be set. Just a thought, I was thinking along those lines as well, but then the money starts to kick in. The dual core Pentium is a much lower price than the dual AMD64. By the time the software is truly ready to go 64-bit, I think I'd be better off buying a system at that point. Maybe they'll be selling quads by then :) Later on, -- In theory, there is no difference between theory and practice. In practice, there is. - Yogi Berra ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
AMD64 Desktop Support
Bit of a dilemma here with my primary desktop machine suddenly up and dieing on me. I'm now in the market to slap together a new PC I've started with looking at picking up an AMD64 based system. After Googling around for a while I still have some concerns I haven't been able to address. Probably just not looking the right places. Mostly I'm worried about some of the proprietary stuff like Flash, Acrobat, nVidia Drivers, Java, and the like not working. Is anyone out there actively using the AMD64 processor as a desktop machine? Are any of these 32-bit apps going to prove to be a show stopper for me? The alternative appears to be the P4 with all the motherboards I've seen using audio devices that aren't supported. Still, I'd rather buy an old sound card and have all the software at least functional. Any advice out there? Thanks, -- In theory, there is no difference between theory and practice. In practice, there is. - Yogi Berra ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade across NFS
Sergey Matveychuk wrote: Michael Collette wrote: This problem only occurs when using portupgrade. Both pkg_delete and pkg_deinstall work without error. Also, everything else in the process that portupgrade goes through appears to work properly. Just that /var/db/pkg directory won't delete when NFS mounted. Have you tried the last (2.1.1) version? I've fixed a few problems and one of them looks like yours. But it's not relate to NFS however. No luck. I was back on 2.0.1 which I upgraded with pkg_delete and pkg_add. Still the exact same error with deleting the /var/db/pkg directory. Like I mentioned earlier, we've been going through the source code on this, libraries and all. If you'd like to toss some tweaks for me to test out off list I'd be one very motivated tester here. This glitch may really complicate my network setup here, so doing whatever it takes to fix this is high on my priority list. Just a thought for an ugly hack, but might it be possible to force a check for that directory after it has supposedly been deleted, and if it exists manually delete it? Thanks for getting back with me on this. Going to continue to muck around with things a bit here to see if we can stumble across something that helps. Later on, -- Michael Collette IT Manager TestEquity LLC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade across NFS
Sergey Matveychuk wrote: Michael Collette wrote: No luck. I was back on 2.0.1 which I upgraded with pkg_delete and pkg_add. Still the exact same error with deleting the /var/db/pkg directory. Let's make it clean. You have /var/db/pkg as nfs mounted? You can't remove /var/db/pkg/portname directory? Got one bad bit of information from my previous post. The problem DOES exist when just performing a pkg_deinstall. Apparently the one test I based my earlier post on wasn't repeatable. The problem is not with the portupgrade script itself. Dug in quite a bit further with this today. When pkg_deinstall calls to pkg_delete a .nfs file is created which is showing as being actively accessed by the ruby process. This file vanishes once pkg_deinstall quits. Due to that file, even attempting a rm -rf on that directory will fail within pkg_deinstall. For testing this out, we added a cheap hack to the portupgrade script immediately after the call to pkg_deinstall that just removes the directory once pkg_deinstall has ended. This works, but has no logic or error checking at this point. The pkg_deinstall script does not report that it didn't complete, so the main portupgrade script just keeps on going as though there were no errors. With that being said, what I believe needs to happen in the short term is to have a check within the portupgrade script where if the pkg_deinstall returns successful and the /var/db/pkg directory still exists, delete it. This would be right around line 1721. Obviously the more correct thing to do here would be to correct pkg_deinstall's behavior. That looks like it may be quite a bit more clever to do, thus my recommendation for fixing portupgrade now, and revisit pkg_deinstall later. I'm just concerned that the real problem may have more to do with the ruby engine and NFS than this script, which may take many months to correct. Later on, -- Michael Collette IT Manager TestEquity LLC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
portupgrade across NFS
I've got a setup here where I need to run portupgrade on a different box from the one where the port is actually going to. I have all the NFS exports setup on the target box and mount points on the installer. Almost everything is working... except the reason for this posting. When portupgrade attempts to remove the entry in /var/db/pkg for the old port, it fails to remove the directory. It does remove all the contents of the directory, but not the directory itself. This problem only occurs when using portupgrade. Both pkg_delete and pkg_deinstall work without error. Also, everything else in the process that portupgrade goes through appears to work properly. Just that /var/db/pkg directory won't delete when NFS mounted. Apparently other folks have had this problem before as I discovered upon googling about. The following PR touches on the matter. http://www.freebsd.org/cgi/query-pr.cgi?pr=32668 Been staring at Ruby code I don't fully understand for the better part of 2 days now, and I don't understand why this glitch is happening. It looks like portupgrade simply calls to pkg_deinstall, which is a wrapper for pkg_delete. Logically if the last 2 work, then portupgrade should as well, but obviously it doesn't. Anyone out there able to make any sense of that Ruby code? Is there something we can patch in there to get this tid bit functional? Thanks, -- Michael Collette IT Manager TestEquity LLC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Automating Drive Formatting
I'm looking for some way to script together an automatic formatting of a hard drive. Having a fair amount of difficulty locating some good information on doing this. For example, let's say there's an unknown IDE drive that's at least 40G in size. On that drive I want to create 1 partition with 3 labels. 2 of the labels get 10G, and the 3rd gets whatever is left. My reason for doing this is that we've set up a couple of servers that are running diskless, but are bogging down a bit with getting everything via NFS. I'm trying to get a diskless box note the installed drive, check to see if it's in the format I expect, and if not perform the bsdlabel, newfs, and all that. I know the basic info is somewhere accessible, or sysinstall wouldn't have this stuff available. Just need a shove in the right direction please. Thanks, -- Michael Collette IT Manager TestEquity Inc [EMAIL PROTECTED] http://www.testequity.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Permissions for Linux apps via LDAP
I now have 2 different Linux applications that refuse to start because getpwuid_r() won't return a user ID. Both acroread7 and realplayer are dead in the water for me. I'm using pam_ldap authentication, which works great for all my native FreeBSD apps. How do I get the Linux apps to perform a similar lookup now? I'm not seeing any pam_ldap or nss_ldap linux ports, which would seem to mean that simply changing the nsswitch.conf file in the /compat/linux area won't do me much good. I could live without realplayer working, but acroread is a pretty critical application for my end users. It also looks like this will be a growing trend for Linux applications in the future. Do we need to port new Linux pam modules into play, or is there some simpler method for fixing this? Thanks, -- When you come to a fork in the roadTake it - Yogi Berra ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PDF file editor
It's no Acrobat, but KWord can open up a pdf to allow you to edit it. It has to be a pretty simple pdf or the formatting will get messed up though. For original documents, both KWord and OpenOffice.org Writer both produce excellent output. For fancier work, Scribus is the app. Lastly, since you mentioned fill it in I'm guessing you may have a pdf form that you just want to fill in the blanks? If that's the case, the print/acroread port allows you to fill in forms just like the Windows version. On Fri, 21 Jan 2005 00:58:11 -0300 (ART), E. J. Cerejo [EMAIL PROTECTED] wrote: Is there a port that allows you to edit a pdf file or fill it in? -- When you come to a fork in the roadTake it - Yogi Berra ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Time sync with NTP questions
On my network I have a machine in my DMZ I wish to use NTP to synchronize to a public server for it's time. I then want to have another machine in my private network synchronize time to this box in the DMZ. From there I want to have all my other machines in my private network to sync in to it. Boy I hope that makes sense. Just in case, a fun filled ASCII diagram Public NTP Server | DMZ Server | Private Server | All the rest of my servers All my boxes are running 5.3-STABLE. I have my DMZ box connecting to public NTP servers through my firewall now. That part works great. Able to ntpdate and run ntpd. My private server is able to both ntpdate and ntpd to a public server. What I can't seem to get going here is to have the private server synchronize to the DMZ server with NTP. Also can't get other machines sync in with what I want to be my primary NTP server on the private network. Heck, I can't seem to get any two FreeBSD boxes to sync with eachother. I've also been trying to get this to play with two boxes on the same subnet. I can get one box to sync to another using timed, but I can't seem to get ntp to work. I conistently get... no server suitable for synchronization found The client side can query what I'd like to be the ntp server with ntpq, but ntpdate or ntp -q always fail. The client IS able to ntpdate to a public server. The server has the following rc.conf flags... ntpdate_enable=YES ntpdate_flags=ntp.ucsd.edu ntpd_enable=YES ntpd_flags=-A -c /etc/ntp.conf -p /var/run/ntpd.pid -f /etc/ntp/ntpd.drift /etc/ntp.conf looks very similar too... server ntp.somedomain.com restrict ntp.somedomain.com mask 255.255.255.255 nomodify notrap noquery restrict 192.168.1.0 mask 255.255.255.0 notrust nomodify notrap restrict 127.0.0.1 driftfile /etc/ntp/ntp.drift There's actually 5 public NTP servers configured in my real ntp.conf and they all seem to work. 192.168.1.0 is, of course, where my clients would query this server. So what am I missing here to make a working NTP server for my network?? Thanks, -- In theory, there is no difference between theory and practice. In practice, there is. - Yogi Berra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OpenOffice on a diskless workstation
Got this one figured out finally. Just need to have the following lines in rc.conf: nfs_client_enable=yes rpc_lockd_enable=yes rpc_statd_enable=yes rpcbind_enable=yes The clever bit that kept throwing me was needing to have the nfs client enabled. Once that was in play both lockd and statd actually ran. Geesh! Michael Collette wrote: After running through a stack of little pitfalls in trying to get a diskless client running from a 5-CURRENT server I'm down to the last nasty here. Hopefully someone might be able to help out. OpenOffice apparently doesn't want to run across an NFS share unless a link_relative option is given in the exports file. http://digitaldistribution.com:8080/oocommunity/FAQs/faqinstall/faqinstall/35 Sure enough, OpenOffice simply won't run from an NFS export on my diskless client. Unless I can get this part of the equation playing this diskless client project is dead in the water for me. OpenOffice is just too critical an app. Is there some way to get a similar behavior to link_relative working? Is there a better route to take with getting OpenOffice to work across NFS? Thanks, -- In theory, there is no difference between theory and practice. In practice, there is. - Yogi Berra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
OpenOffice on a diskless workstation
After running through a stack of little pitfalls in trying to get a diskless client running from a 5-CURRENT server I'm down to the last nasty here. Hopefully someone might be able to help out. OpenOffice apparently doesn't want to run across an NFS share unless a link_relative option is given in the exports file. http://digitaldistribution.com:8080/oocommunity/FAQs/faqinstall/faqinstall/35 Sure enough, OpenOffice simply won't run from an NFS export on my diskless client. Unless I can get this part of the equation playing this diskless client project is dead in the water for me. OpenOffice is just too critical an app. Is there some way to get a similar behavior to link_relative working? Is there a better route to take with getting OpenOffice to work across NFS? Thanks, -- Michael Collette [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
USB Drive on Current
Yet another user out here trying to get a USB flash drive working. I've got a number of other USB devices working nicely, like an HP printer and a Logitech mouse. Uncounted hours have gone into getting a USB flash drive to work though. First problem here is that my system doesn't seem to recognize that a drive has been inserted. After running through edits on umass.c, usbdevs, and scsi_da.c I managed to get a 32M ACDC drive to work. Problem is, it only works on boot up. It detects when I detach the drive, but no further notice upon putting it back in. I've tried 2 other USB drives, and none of them seem to be detected upon insertion. These same drives I've had luck with getting to work on 4.10 on an identical PC. What's the magic I'm missing here? Running with: FreeBSD 5.2-CURRENT #0: Tue Jun 1 12:27:50 PDT 2004 I have usbd and devd running from rc.conf. Applicable Kernel Entries # SCSI peripherals device scbus # SCSI bus (required for SCSI) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass# Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) # USB support device uhci# UHCI PCI-USB interface device ohci# OHCI PCI-USB interface device usb # USB Bus (required) #device udbp# USB Double Bulk Pipe devices device ugen# Generic device uhid# Human Interface Devices device ukbd# Keyboard device ulpt# Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse device urio# Diamond Rio 500 MP3 player device uscanner# Scanners Thanks, -- In theory, there is no difference between theory and practice. In practice, there is. - Yogi Berra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Mounting SMB with Kerberos
There's a bit of info concerning Samba acting as a server with Kerberos authentication out on the web. I'm needing to go the other way with this though. I need to mount on a FreeBSD box an SMB share with Kerberos authentication. In this case, FreeBSD is acting as the client. I didn't see any references to this in the mount_smbfs man page, nor have I had much luck in tracking any information down on the web. Is this even possible? So you know, this is not trying to connect to a Windows server. Unfortunately this does have to be SMB to the box I'm trying to connect to. Thanks, -- In theory, there is no difference between theory and practice. In practice, there is. - Yogi Berra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Really Crazy SMTP Problem
Eric, Not knowing what all you've got configured exactly, here's a couple of possible guesses to weed out the basics. Can you do a reverse DNS lookup on your mail server? In other words, perform a whois on the IP address and get a legit domain name. Many servers require this in order to keep out obvious spammers. You should also triple check and make sure that you have SMTP open to come back to you from the outside world. SMTP requires open ports coming in as well as going out. Check your TCP Wrappers and whether or not IPFW or IPFilters is in the mix. Later on, Eric Harrison wrote: Hi, I've been trying everything I can think of to locate the source of this problem and I finally gave up and need some help. This is the situation: I have a server running FreeBSD 4.7-RELEASE. I installed Postfix on the machine like I have done at least 20 other times on different machines and got everything configured like it should be. I noticed quickly that it wasn't delivering mail to any remote mail servers so I checked my mail queue and discovered that most of the servers were either refusing the connection or not responding. This was a little strange so I spent about a day checking the postfix configuration, assuming I had just messed something up. I finally came to the conclusion that everything was configured properly and then had the bright idea to try to manually connect to the external mail servers to see if I could connect. This is where it gets wierd. $telnet smtp.ADDRESSWITHHELD.com 25 Trying xxx.xxx.xxx.x... telnet: connect to address xxx.xxx.xxx.x: Connection refused telnet: Unable to connect to remote host I thought this to be rather odd, but thought the worst had happened and I had somehow gotten a blacklisted IP (possibly used previously by a Spammer or something). So I tried a server I knew to NOT be running any type of blacklist filtering (one of my other servers that I knew the config on) and had the SAME result. Connection refused. The other machines on the network running mail servers seem to not be having any problems like this, and I talked to my host to see if anything was reported, and he claiimed it was a misconfiguration of my mail server. Knowing this not to be the case, I am stumped. If ANYONE has any information or insight, you would be a lifesaver. Thanks, Eric Harrison -- In theory, there is no difference between theory and practice. In practice, there is. - Yogi Berra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: identifying my network address
David Banning wrote: I am running an Xwindow on a windows box. I need a script to tell me what my network address is so that I can set my DISPLAY varible correctly eg: 192.168.1.2:0.0 Any idea what command would be useful for this purpose? It's ugly. It won't work if you multiple NICs. It may just work for what you need just the same. echo `ifconfig | grep broadcast | cut -d -f2`:0.0 This takes the output of ifconfig and parses it just a wee bit with grep and cut. I use something very similar to this in a script that changes my network settings for my laptop on the fly. Let me know if this works for ya. Later on, -- Outside of a dog, a book is man's best friend. Inside of a dog, it's too dark to read. - Groucho Marx To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
FTP gone weird
Having a heck of a time with what I thought would be a pretty simple cron job
of pulling down a web log via FTP. In the process, I've run into a wall of
port problems.
The Scenario:
I'm running an ssh session looped back to itself so as to configure a tunneled
port forward from localhost:2121 to remoteserver:21
My cron job calls a small shell script that puts together the proper file name
to get for the day, then issues the following command...
ftp ftp://${USER}:${PW}@${SITE}:${PT}${REMDIR}${FILE}
The site and port vars are set to localhost:2121 to go through the tunnel.
When I run this script from a command line, it works exactly as I would
expect it to. From cron, I get the following error...
Data connection to 127.0.0.1:49159 is not allowed when control connection is
from 10.10.10.10:3553!
The from IP is faked for this example. The actual error has the routeable IP
address of this box. The port numbers both increment on each attempt.
The end goal here is to just automate an FTP download through an SSH tunnel.
The remote machine is not running sftp, nor do I have admin rights to it.
SSH forwarding is pretty much my only option there.
Any ideas?
Later on,
--
Outside of a dog, a book is man's best friend. Inside of a dog, it's too dark
to read.
- Groucho Marx
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
Re: FTP gone weird
On the recommondation of an off list response I attempted using some other
tools instead of ftp. Tried fetch, wget, and even curl. wget didn't like
the port forwarding, cron or not.
Both fetch and curl work off the command line. They also don't produce an
error when run from cron. Neither one is actually getting the file though.
What in the heck is it about cron that goofs these ports up??
Later on,
Michael Collette wrote:
Having a heck of a time with what I thought would be a pretty simple cron
job
of pulling down a web log via FTP. In the process, I've run into a wall
of port problems.
The Scenario:
I'm running an ssh session looped back to itself so as to configure a
tunneled port forward from localhost:2121 to remoteserver:21
My cron job calls a small shell script that puts together the proper file
name to get for the day, then issues the following command...
ftp ftp://${USER}:${PW}@${SITE}:${PT}${REMDIR}${FILE}
The site and port vars are set to localhost:2121 to go through the
tunnel. When I run this script from a command line, it works exactly as I
would
expect it to. From cron, I get the following error...
Data connection to 127.0.0.1:49159 is not allowed when control connection
is from 10.10.10.10:3553!
The from IP is faked for this example. The actual error has the routeable
IP
address of this box. The port numbers both increment on each attempt.
The end goal here is to just automate an FTP download through an SSH
tunnel. The remote machine is not running sftp, nor do I have admin rights
to it. SSH forwarding is pretty much my only option there.
Any ideas?
Later on,
--
Outside of a dog, a book is man's best friend. Inside of a dog, it's too dark
to read.
- Groucho Marx
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
Re: Printing with CUPS
On Tuesday 01 October 2002 05:09 am, Carl-Johan Kihlbom wrote: On tisdag, okt 1, 2002, at 13:55 Europe/Stockholm, Michael Collette wrote: Carl-Johan Kihlbom wrote: Hi! I'm trying to get my FreeBSD computer to act as a print server. I'm not having much success though. I'm running 4.6.2-STABLE and I've installed cups-base-1.1.14 via /stand/sysinstall. I started cupsd manually with /usr/local/sbin/cupsd, and I can access the web interface at http://localhost:631/. There I added my HP Deskjet 970 CXi connected via USB successfully, and was able to print a test page from the web interface. However, I seem to be missing a lot of important files. I have almost none of the lp* binaries in /usr/sbin/. I.e. no lpstat, lpinfo, lpadmin, etc. All I have is: When you're looking in /usr/sbin, what you're seeing are the default lpr tools that came with FreeBSD. Cups is all in /usr/local/bin. The easiest way to correct your problem is to remove execute permissions from the /usr/sbin files. I have no lp* files in /usr/local/bin. So that's not it. Locate lpinfo returns nothing. Carl-Johan, When you do the following command, are you seeing the same stuff I am here? metrol [~] pkg_info | grep cups cups-1.1.15.1 The Common UNIX Printing System cups-base-1.1.15.1_4 The Common UNIX Printing System cups-lpr-1.1.15.1_1 The CUPS BSD and system V compatibility binaries cups-pstoraster-7.05.5 GNU Postscript interpreter for CUPS printing to non-PS You need all 4 of those ports installed. I'll bet you don't have the cups-lpr port in there. Probably the missing ingredient. Even still, my previous post is still valid. If you don't change the permissions of the lp files in /usr/sbin, you're going to have a rather confused system. Later on, -- Outside of a dog, a book is man's best friend. Inside of a dog, it's too dark to read. - Groucho Marx To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
NEdit dead outta nowhere
Normally I'm using NEdit a LOT. It's my primary editor for darn near everything I do under FreeBSD. Just this evening NEdit decided to die on me with the error messages listed below. So far I've attempted the removal of NEdit's config files. I've forced a reinstall of open-motif, gettext and NEdit in the hopes that something may have needed to be recompiled, as was the case when open-motif was recently updated. The only thing I can think of that was a serious change to my system was a recent make world on STABLE the other night. I honestly don't recall if I'd tried to use NEdit since then, as I've been mucking around with lots of offline stuff and trying out some other editors. All of my core apps are up to date with cvs as of this evening. My uname info... 4.7-PRERELEASE FreeBSD 4.7-PRERELEASE #0: Wed Sep 11 20:53:48 PDT 2002 Does anyone know what any of the following means?? Should I get in and rebuild world again from a fresh cvsup? Errors when launching NEdit from a command line... translation table syntax error: Unknown keysym name: osfActivate ... found while parsing ':KeyosfActivate: ManagerParentActivate()' String to TranslationTable conversion encountered errors translation table syntax error: Unknown keysym name: osfBeginLine ... found while parsing ':KeyosfBeginLine: ManagerGadgetTraverseHome()' String to TranslationTable conversion encountered errors translation table syntax error: Unknown keysym name: osfActivate ... found while parsing ':KeyosfActivate: ManagerParentActivate()' String to TranslationTable conversion encountered errors translation table syntax error: Unknown keysym name: osfHelp ... found while parsing ':KeyosfHelp: ManagerGadgetHelp()' String to TranslationTable conversion encountered errors translation table syntax error: Unknown keysym name: osfActivate ... found while parsing ':KeyosfActivate: PrimitiveParentActivate()' String to TranslationTable conversion encountered errors translation table syntax error: Unknown keysym name: osfHelp ... found while parsing ':KeyosfHelp: Help()' String to TranslationTable conversion encountered errors translation table syntax error: Unknown keysym name: osfActivate ... found while parsing ':KeyosfActivate: PrimitiveParentActivate()' String to TranslationTable conversion encountered errors translation table syntax error: Unknown keysym name: osfCancel ... found while parsing ':KeyosfCancel: MenuEscape()' String to TranslationTable conversion encountered errors Cannot convert string FONTLIST to type FontStruct translation table syntax error: Unknown keysym name: osfActivate ... found while parsing ':KeyosfActivate: PrimitiveParentActivate()' String to TranslationTable conversion encountered errors translation table syntax error: Unknown keysym name: osfSelect ... found while parsing ':KeyosfSelect: ArmAndActivate()' String to TranslationTable conversion encountered errors translation table syntax error: Unknown keysym name: osfPrimaryPaste ... found while parsing ':m KeyosfPrimaryPaste:cut-primary()' String to TranslationTable conversion encountered errors translation table syntax error: Unknown keysym name: osfSelect ... found while parsing ':KeyosfSelect: ManagerGadgetSelect()' String to TranslationTable conversion encountered errors translation table syntax error: Unknown keysym name: osfSelect ... found while parsing ':KeyosfSelect: MenuBarGadgetSelect()' String to TranslationTable conversion encountered errors translation table syntax error: Unknown keysym name: osfActivate ... found while parsing ':KeyosfActivate: ManagerParentActivate()' String to TranslationTable conversion encountered errors translation table syntax error: Unknown keysym name: osfHelp ... found while parsing ':KeyosfHelp: MenuHelp()' String to TranslationTable conversion encountered errors translation table syntax error: Unknown keysym name: osfSelect ... found while parsing ':KeyosfSelect: KeySelect()' String to TranslationTable conversion encountered errors translation table syntax error: Unknown keysym name: osfSelect ... found while parsing ':KeyosfSelect: KeySelect()' String to TranslationTable conversion encountered errors translation table syntax error: Unknown keysym name: osfCancel ... found while parsing 'KeyosfCancel:MenuEscape()' String to TranslationTable conversion encountered errors translation table syntax error: Unknown keysym name: osfSelect ... found while parsing ':KeyosfSelect: ArmAndActivate()' String to TranslationTable conversion encountered errors translation table syntax error: Unknown keysym name: osfActivate ... found while parsing ':KeyosfActivate: PrimitiveParentActivate()' String to TranslationTable conversion encountered errors translation table syntax error:
Re: NEdit dead - XFree86 Libs!!!
Just a quick follow up to additional attempts to correct this problem. Turns out my installed copy of GCC was a wee bit out of date. One port revision back at most, but notable never the less. So, I got real desperate here and did the following... portupgrade gcc Then pulled down a fresh cvsup of STABLE and rebuilt world. Deleted both open-motif and nedit. Ran the nedit portinstall, which brought in open-motif as a dependency all proper like. Didn't fix a darn thing :( Then I got to looking over Weston's list of apps also exhibiting this problem looking for what in the heck was common. Only thing I could see was XFree86-libraries. I'd recently updated mine via ports, so I decided to go pull down the package from one of the FreeBSD mirrors and try that instead. Sure 'nuff! I don't know what it is, but there is something seriously wrong with how those libraries are built from the ports tree. NEdit now works properly. JEdit no longer sees the same errors it was getting. The package I installed was: XFree86-libraries-4.2.1_1.tgz Which appears to be the very same version I had installed from the port. The package works, the port doesn't. If time permits, I'll run a pkg_delete on the libraries and try the compile again. Now that I got my editor back up and running, I gots to get some of my real work done! :) Later on, Michael Collette wrote: Normally I'm using NEdit a LOT. It's my primary editor for darn near everything I do under FreeBSD. Just this evening NEdit decided to die on me with the error messages listed below. So far I've attempted the removal of NEdit's config files. I've forced a reinstall of open-motif, gettext and NEdit in the hopes that something may have needed to be recompiled, as was the case when open-motif was recently updated. The only thing I can think of that was a serious change to my system was a recent make world on STABLE the other night. I honestly don't recall if I'd tried to use NEdit since then, as I've been mucking around with lots of offline stuff and trying out some other editors. All of my core apps are up to date with cvs as of this evening. My uname info... 4.7-PRERELEASE FreeBSD 4.7-PRERELEASE #0: Wed Sep 11 20:53:48 PDT 2002 Does anyone know what any of the following means?? Should I get in and rebuild world again from a fresh cvsup? Errors when launching NEdit from a command line... translation table syntax error: Unknown keysym name: osfActivate ... found while parsing ':KeyosfActivate: ManagerParentActivate()' String to TranslationTable conversion encountered errors translation table syntax error: Unknown keysym name: osfBeginLine ... found while parsing ':KeyosfBeginLine: ManagerGadgetTraverseHome()' String to TranslationTable conversion encountered errors translation table syntax error: Unknown keysym name: osfActivate ... found while parsing ':KeyosfActivate: ManagerParentActivate()' String to TranslationTable conversion encountered errors translation table syntax error: Unknown keysym name: osfHelp ... found while parsing ':KeyosfHelp: ManagerGadgetHelp()' String to TranslationTable conversion encountered errors translation table syntax error: Unknown keysym name: osfActivate ... found while parsing ':KeyosfActivate: PrimitiveParentActivate()' String to TranslationTable conversion encountered errors translation table syntax error: Unknown keysym name: osfHelp ... found while parsing ':KeyosfHelp: Help()' String to TranslationTable conversion encountered errors translation table syntax error: Unknown keysym name: osfActivate ... found while parsing ':KeyosfActivate: PrimitiveParentActivate()' String to TranslationTable conversion encountered errors translation table syntax error: Unknown keysym name: osfCancel ... found while parsing ':KeyosfCancel: MenuEscape()' String to TranslationTable conversion encountered errors Cannot convert string FONTLIST to type FontStruct translation table syntax error: Unknown keysym name: osfActivate ... found while parsing ':KeyosfActivate: PrimitiveParentActivate()' String to TranslationTable conversion encountered errors translation table syntax error: Unknown keysym name: osfSelect ... found while parsing ':KeyosfSelect: ArmAndActivate()' String to TranslationTable conversion encountered errors translation table syntax error: Unknown keysym name: osfPrimaryPaste ... found while parsing ':m KeyosfPrimaryPaste:cut-primary()' String to TranslationTable conversion encountered errors translation table syntax error: Unknown keysym name: osfSelect ... found while parsing ':KeyosfSelect: ManagerGadgetSelect()' String to TranslationTable conversion encountered errors translation table syntax error: Unknown keysym name: osfSelect ... found while parsing ':KeyosfSelect
Re: How to best way to upgrade to KDE3 from ports ?
Sean O'Neill wrote: I just noticed that the KDE2 ports are no longer in the ports tree. What the best way to upgrade to KDE3 from ports ? Do I need to delete KDE2 first and then install KDE3 ? This is one of those to bring out the big stick for... pkg_delete -rf qt-* Not a command to be taken lightly. It will kill Qt, and ALL things depending upon it. Yes, even if you have Qt2 only apps. Qt2 and Qt3 don't live nicely together on the same box. If you have apps you rely upon that are Qt only, such as QCad or Kvirc, they up and break at this point. There are some efforts to get these apps up to their respective Qt3 versions, but I know some of them are far from straight forward porting projects. Assuming Qt2 isn't an issue, just pop on over to /usr/ports/x11/kde3 and do the make install. You might want to consider grabbing the packages, as this is a LONG compile. You can find more details concerning this kinda stuff over at... http://freebsd.kde.org/ Later on, -- Outside of a dog, a book is man's best friend. Inside of a dog, it's too dark to read. - Groucho Marx To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
USB Manual Reset
Is there some way to manually reset the USB? I've managed to find several folks asking this via searching around in Google, but no answers anywhere to be found. I've already asked this question over on the mobile list, but nobody seems to know. At to why someone would want to do this? Well, I've got this here laptop that seems to up and forget how to talk to the USB ports after coming out of sleep mode. If I perform a full reboot of the system, it picks up on the USB device I have hooked up, and works perfectly. That is, until the next visit to sleep mode. Simply restarting usbd doesn't do it. No documentation that I've been able to track down discusses this at all. Any suggestions at all would be appreciated. Thanks, -- Outside of a dog, a book is man's best friend. Inside of a dog, it's too dark to read. - Groucho Marx To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
