Re: Frustration
Fernando Pinguelo wrote: I am writing to you because I need to vent. I have tried installing version 5.3 of FreeBSD on a Pentium III machine. I thought I succeeded in doing it so, but when I tried to build xOrg I realized that I did not have all the ports installed and that some other dependencies were also missing. I realized then that the installation had not been as successful as I first thought. So, I tried to re-install the ports from the CD, since I didn't have an Internet connection to that machine. Well, I kept getting more and more hardware/software errors. I then tried to upgrade FreeBSD to version 6.1. And that was what I did; I tried. Well, I kept getting more errors, as usual. The more I tried to install/reinstall/upgrade/fix FreeBSD, the more I was realizing that anything that had to do with FreeBSD that could go wrond would go wrong, be it the software installation or hardware behavior. The amount of work and headache that I have been experiencing to move a single 'inch' towards a working Unix environment has been enourmously frustating. The worst part of it all is that I have not accomplished anything tangible at all. I think now it is time for this boy to abandon the 'Unix' bandwagon for good and move back to MS Windows. At least I will be able to concentrate on doing real productive work, instead of dealing with temperamental hardware and software every time I touch the PC. Good luck to those heroic individuals who stick with the configuration fight to the end. I failed to see the 'Power to Serve'. Congratulations! You have found FreeBSD's built-in intelligence test feature. If you don't have the intelligence to email this list for help *while* you are having the problems, then you win the right to be stuck with Windows for ever. Enjoy! Average time to install FreeBSD (~7 installs in last 12 months): 30 minutes or less Average time to install MS Windows (1 install in last 12 months): at least 4 hours; required me to copy drivers from a CD to a floppy; required megabytes of fixes despite being the most recent release; nearly had catch 22 where ethernet wouldn't work without update, but update couldn't be obtained without ethernet. Joy. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Frustration
On 6/30/06, Fernando Pinguelo [EMAIL PROTECTED] wrote: I am writing to you because I need to vent. I have tried installing version 5.3 of FreeBSD on a Pentium III machine. I thought I succeeded in doing it so, but when I tried to build xOrg I realized that I did not have all the ports installed and that some other dependencies were also missing. I realized then that the installation had not been as successful as I first thought. So, I tried to re-install the ports from the CD, since I didn't have an Internet connection to that machine. Well, I kept getting more and more hardware/software errors. I then tried to upgrade FreeBSD to version 6.1. And that was what I did; I tried. Well, I kept getting more errors, as usual. The more I tried to install/reinstall/upgrade/fix FreeBSD, the more I was realizing that anything that had to do with FreeBSD that could go wrond would go wrong, be it the software installation or hardware behavior. The amount of work and headache that I have been experiencing to move a single 'inch' towards a working Unix environment has been enourmously frustating. The worst part of it all is that I have not accomplished anything tangible at all. I think now it is time for this boy to abandon the 'Unix' bandwagon for good and move back to MS Windows. At least I will be able to concentrate on doing real productive work, instead of dealing with temperamental hardware and software every time I touch the PC. Good luck to those heroic individuals who stick with the configuration fight to the end. I failed to see the 'Power to Serve'. Hi, I don't know your level of proficiency with unix but from your email I think you're taking the initial steps. You tried to build a Lego without all the pieces and with no instructions. You should start with an already built machine and start your way down from there. With this in mind I recomend you to install for example PC-BSD(1). It's FreeBSD all the way, but for what you want, a desktop solution, a custom built FreeBSD. -- Joao Barros ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Frustration
In response to Fernando Pinguelo [EMAIL PROTECTED]: I am writing to you because I need to vent. I have tried installing version 5.3 of FreeBSD on a Pentium III machine. I thought I succeeded in doing it so, but when I tried to build xOrg I realized that I did not have all the ports installed and that some other dependencies were also missing. I realized then that the installation had not been as successful as I first thought. So, I tried to re-install the ports from the CD, since I didn't have an Internet connection to that machine. Well, I kept getting more and more hardware/software errors. I then tried to upgrade FreeBSD to version 6.1. And that was what I did; I tried. On the offhand chance that you are _not_ a troll, let me explain what the problem here is. You come from the Windows world. The first problem is that the Windows world has very little culture: you buy the software and are expected to use it. The FreeBSD culture is an integral part of the software itself. You are expected to ask questions and get helpful answers. The community goes to great lengths to generate helpful documentation and answer questions in a timely manner. By not using the community as designed, you effectively used the software incorrectly. As a result, it didn't work for you. The second major difference between the Windows world and the FreeBSD culture is that in Windows, you get error messages that read something like operation failed: error 0xffcb2c -- which is useless to diagnose a problem. In the FreeBSD world, you will get extremely _specific_ and helpful error messages that will lead you directly to the source of the problem (OK, not always, but we try). I noticed that you complained of errors, but didn't tell us what any of the errors were. Based on my experience with users, that probably means that you didn't bother to read them yourself. Again, this is using the software differently than it is designed to be used, and will likely result in failure. If you've already decided to give up and aren't willing to try again: farewell and good luck. If you ever change your mind, we'll still be here. -- Bill Moran Collaborative Fusion Inc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Frustration
--- Joao Barros [EMAIL PROTECTED] wrote: On 6/30/06, Fernando Pinguelo [EMAIL PROTECTED] wrote: I am writing to you because I need to vent. I have tried installing version 5.3 of FreeBSD on a Pentium III machine. I thought I succeeded in doing it so, but when I tried to build xOrg I realized that I did not have all the ports installed and that some other dependencies were also missing. I realized then that the installation had not been as successful as I first thought. So, I tried to re-install the ports from the CD, since I didn't have an Internet connection to that machine. Well, I kept getting more and more hardware/software errors. I then tried to upgrade FreeBSD to version 6.1. And that was what I did; I tried. Well, I kept getting more errors, as usual. The more I tried to install/reinstall/upgrade/fix FreeBSD, the more I was realizing that anything that had to do with FreeBSD that could go wrond would go wrong, be it the software installation or hardware behavior. The amount of work and headache that I have been experiencing to move a single 'inch' towards a working Unix environment has been enourmously frustating. The worst part of it all is that I have not accomplished anything tangible at all. I think now it is time for this boy to abandon the 'Unix' bandwagon for good and move back to MS Windows. At least I will be able to concentrate on doing real productive work, instead of dealing with temperamental hardware and software every time I touch the PC. Good luck to those heroic individuals who stick with the configuration fight to the end. I failed to see the 'Power to Serve'. Hi, I don't know your level of proficiency with unix but from your email I think you're taking the initial steps. You tried to build a Lego without all the pieces and with no instructions. You should start with an already built machine and start your way down from there. With this in mind I recomend you to install for example PC-BSD(1). It's FreeBSD all the way, but for what you want, a desktop solution, a custom built FreeBSD. -- Joao Barros ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] That or try desktop-bsd so it's still a pure BSD system. I've experienced all the problems with Windows that you could imagine, my favorite is not being able to swap hard drives into a new machine and get the thing to boot, especially with a Plug N Play OS. I've had a million problems with BSD, and with Linux, Dos, and OS/2. anytime you learn something new things can be messed up. I bet your problem is you kept changing your mind with sysinstall, it got confused and never let your choose your distribution, and now its all messed up. That usually messed up my installations in the begining. Windows is cool, but I can't remotely login to windows over a SSH session on my Treo and run update my system while I'm on the road for work. *BSD is the future, because Microsoft won't be able to release their garbage too much longer and be taken seriously. Especially now that they have gotten into the anti-spyware market. Why pay for a license to an OS that I need to pay for another license from the same company to make the OS secure I think RTFM is in order, I know it sounds cold but I've taken the time to read countless man pages to figure out my problems. Remember BSD isn't setup for you out of the box, that would violate the spirit of Unix; but its got thousands of help files built in to the system. You can't say that about windows, their help is useless average joe BSD user venting back ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Frustration
Being an experienced BSD user who on a daily basis gives support to other people using BSD, wether FreeBSD, OpenBSD or NetBSD, I hardly think this has to do with FreeBSD. This rather sounds like a typical MS whiner, who hasn't really got around to actually understand what he is doing. In some situations there are hardware complications, which again hasn't got anything to do with FreeBSD but rather is based upon hardware vendores keeping others than MS from using their hardware. Long story short, stop whining and just go back to MS Windows. Nobody cares! On Thu, 29 Jun 2006 22:51:00 -0400 Fernando Pinguelo [EMAIL PROTECTED] wrote: I am writing to you because I need to vent. I have tried installing version 5.3 of FreeBSD on a Pentium III machine. I thought I succeeded in doing it so, but when I tried to build xOrg I realized that I did not have all the ports installed and that some other dependencies were also missing. I realized then that the installation had not been as successful as I first thought. So, I tried to re-install the ports from the CD, since I didn't have an Internet connection to that machine. Well, I kept getting more and more hardware/software errors. I then tried to upgrade FreeBSD to version 6.1. And that was what I did; I tried. Well, I kept getting more errors, as usual. The more I tried to install/reinstall/upgrade/fix FreeBSD, the more I was realizing that anything that had to do with FreeBSD that could go wrond would go wrong, be it the software installation or hardware behavior. The amount of work and headache that I have been experiencing to move a single 'inch' towards a working Unix environment has been enourmously frustating. The worst part of it all is that I have not accomplished anything tangible at all. I think now it is time for this boy to abandon the 'Unix' bandwagon for good and move back to MS Windows. At least I will be able to concentrate on doing real productive work, instead of dealing with temperamental hardware and software every time I touch the PC. Good luck to those heroic individuals who stick with the configuration fight to the end. I failed to see the 'Power to Serve'. Bye, Fernando ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Frustration
On 6/29/06, Fernando Pinguelo [EMAIL PROTECTED] wrote: I am writing to you because I need to vent. I have tried installing version 5.3 of FreeBSD on a Pentium III machine. I thought I succeeded in doing it so, but when I tried to build xOrg I realized that I did not have all the ports installed and that some other dependencies were also missing. I realized then that the installation had not been as successful as I first thought. When you did the install, did you do a standard install, or did you try to do a custom install? The warning that says a custom install is for experts is for real. [...] Good luck to those heroic individuals who stick with the configuration fight to the end. I failed to see the 'Power to Serve'. I moved to FreeBSD because in my experience it has been much easier to install than Windows. I installed WIndows XP and FreeBSD 6.1 on a laptop last week and the FreeBSD install was much easier. It actually had working drivers for the laptop (unlike Windows). Perhaps if you had posted some of your problems to the list you could have been helped. Oh, well. - Bob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Frustration
On 6/30/06, Rico Secada [EMAIL PROTECTED] wrote: Being an experienced BSD user who on a daily basis gives support to other people using BSD, wether FreeBSD, OpenBSD or NetBSD, I hardly think this has to do with FreeBSD. This rather sounds like a typical MS whiner, who hasn't really got around to actually understand what he is doing. In some situations there are hardware complications, which again hasn't got anything to do with FreeBSD but rather is based upon hardware vendores keeping others than MS from using their hardware. Long story short, stop whining and just go back to MS Windows. Nobody cares! Part of the FreeBSD experience is the comunity and you're not helping. I care, most probably someone else cares. Please don't talk for the comunity by stating nobody cares. -- Joao Barros ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Frustration
Rico Secada wrote: Being an experienced BSD user who on a daily basis gives support to other people using BSD, wether FreeBSD, OpenBSD or NetBSD, I hardly think this has to do with FreeBSD. This rather sounds like a typical MS whiner, who hasn't really got around to actually understand what he is doing. In some situations there are hardware complications, which again hasn't got anything to do with FreeBSD but rather is based upon hardware vendores keeping others than MS from using their hardware. Long story short, stop whining and just go back to MS Windows. Nobody cares! On Thu, 29 Jun 2006 22:51:00 -0400 Fernando Pinguelo [EMAIL PROTECTED] wrote: I am writing to you because I need to vent. I have tried installing version 5.3 of FreeBSD on a Pentium III machine. I thought I succeeded in doing it so, but when I tried to build xOrg I realized that I did not have all the ports installed and that some other dependencies were also missing. I realized then that the installation had not been as successful as I first thought. So, I tried to re-install the ports from the CD, since I didn't have an Internet connection to that machine. Well, I kept getting more and more hardware/software errors. I then tried to upgrade FreeBSD to version 6.1. And that was what I did; I tried. Well, I kept getting more errors, as usual. The more I tried to install/reinstall/upgrade/fix FreeBSD, the more I was realizing that anything that had to do with FreeBSD that could go wrond would go wrong, be it the software installation or hardware behavior. The amount of work and headache that I have been experiencing to move a single 'inch' towards a working Unix environment has been enourmously frustating. The worst part of it all is that I have not accomplished anything tangible at all. I think now it is time for this boy to abandon the 'Unix' bandwagon for good and move back to MS Windows. At least I will be able to concentrate on doing real productive work, instead of dealing with temperamental hardware and software every time I touch the PC. Good luck to those heroic individuals who stick with the configuration fight to the end. I failed to see the 'Power to Serve'. Bye, Fernando Whatever floats your boat. Also, if you want to complain about this in the future, I suggest using another method maybe, like a blog or diary since most people don't really earnestly take what you write in email to heart, esp. when you complain about a topic on a list which advocates that topic. Then again this shouldn't have really been written to this list, anyhow since this is a complaint and not a question =P. Next time you should ask before giving up as well; you'd be amazed at how diligently people would try to assist you with your issue. -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Frustration
On Fri, 30 Jun 2006 13:45:02 +0100, Joao Barros [EMAIL PROTECTED] wrote: On 6/30/06, Fernando Pinguelo [EMAIL PROTECTED] wrote: I am writing to you because I need to vent. I have tried installing version 5.3 of FreeBSD on a Pentium III machine. I thought I succeeded in doing it so, but when I tried to build xOrg I realized that I did not have all the ports installed and that some other dependencies were also missing. I realized then that the installation had not been as successful as I first thought. First off, a note to Fernando Pinguelo: putting entire paragraphs onto single lines of text makes it a real pain to edit replies properly. Please avoid the practice when posting to mailing lists. So, I tried to re-install the ports from the CD, since I didn't have an Internet connection to that machine. Well, I kept getting more and more hardware/software errors. I then tried to upgrade FreeBSD to version 6.1. And that was what I did; I tried. My guess is that Fernando has pointed out the source of his troubles in the first sentence on the above line of text. Installing the ports tree from the CD-R/RW does *not* mean installing the *source code* of the ports tree. What is actually installed is a partial directory tree with a few small files in the top directory of each port. Among other matters, these files contain the information the ports subsystem needs to *locate and download (i.e., via fetch(1))* a recent version of the source code for each port, as well as to download and apply any patches made available since that version of the source code was finalized for placement onto one or more servers. In other words, without an Internet connection, he can't get the source code in order to build it. Scott Bennett, Comm. ASMELG, CFIAG ** * Internet: bennett at cs.niu.edu * ** * A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army. * *-- Gov. John Hancock, New York Journal, 28 January 1790 * ** ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Frustration
On Fri, 30 Jun 2006 22:40:09 +0100 Joao Barros [EMAIL PROTECTED] wrote: On 6/30/06, Rico Secada [EMAIL PROTECTED] wrote: Being an experienced BSD user who on a daily basis gives support to other people using BSD, wether FreeBSD, OpenBSD or NetBSD, I hardly think this has to do with FreeBSD. This rather sounds like a typical MS whiner, who hasn't really got around to actually understand what he is doing. In some situations there are hardware complications, which again hasn't got anything to do with FreeBSD but rather is based upon hardware vendores keeping others than MS from using their hardware. Long story short, stop whining and just go back to MS Windows. Nobody cares! Part of the FreeBSD experience is the comunity and you're not helping. It's about helping people who want and need help, not people who whine! I care, most probably someone else cares. Well, go ahead then, care all you want! But please do so somewhere else! Not on this list! Please don't talk for the comunity by stating nobody cares. I do talk for the comunity by stating nobody cares. This list is about helping. Not venting! Nobody from the comunity cares about that! -- Joao Barros ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Frustration
On Fri, 30 Jun 2006 22:40:09 +0100 Joao Barros [EMAIL PROTECTED] wrote: On 6/30/06, Rico Secada [EMAIL PROTECTED] wrote: Being an experienced BSD user who on a daily basis gives support to other people using BSD, wether FreeBSD, OpenBSD or NetBSD, I hardly think this has to do with FreeBSD. This rather sounds like a typical MS whiner, who hasn't really got around to actually understand what he is doing. In some situations there are hardware complications, which again hasn't got anything to do with FreeBSD but rather is based upon hardware vendores keeping others than MS from using their hardware. Long story short, stop whining and just go back to MS Windows. Nobody cares! Part of the FreeBSD experience is the comunity and you're not helping. It's about helping people who want and need help, not people who whine! I care, most probably someone else cares. Well, go ahead then, care all you want! But please do so somewhere else! Not on this list! Please don't talk for the comunity by stating nobody cares. I do talk for the comunity by stating nobody cares. This list is about helping. Not venting! Nobody from the comunity cares about that! -- Joao Barros ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Frustration
On Jun 30, 2006, at 6:33 PM, Rico Secada wrote: On Fri, 30 Jun 2006 22:40:09 +0100 Joao Barros [EMAIL PROTECTED] wrote: On 6/30/06, Rico Secada [EMAIL PROTECTED] wrote: Being an experienced BSD user who on a daily basis gives support to other people using BSD, wether FreeBSD, OpenBSD or NetBSD, I hardly think this has to do with FreeBSD. This rather sounds like a typical MS whiner, who hasn't really got around to actually understand what he is doing. In some situations there are hardware complications, which again hasn't got anything to do with FreeBSD but rather is based upon hardware vendores keeping others than MS from using their hardware. Long story short, stop whining and just go back to MS Windows. Nobody cares! Part of the FreeBSD experience is the comunity and you're not helping. It's about helping people who want and need help, not people who whine! I care, most probably someone else cares. Well, go ahead then, care all you want! But please do so somewhere else! Not on this list! Please don't talk for the comunity by stating nobody cares. I do talk for the comunity by stating nobody cares. This list is about helping. Not venting! Nobody from the comunity cares about that! Please don't speak for me. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Frustration
Rico Secada wrote: I do talk for the comunity by stating nobody cares. This list is about helping. Not venting! Nobody from the comunity cares about that! No you don't. You do not talk for me. Until I give you my proxy, neither you nor anyone else talks for me. If others want to let you speak for them then that is their decision. Nothing personal, just a plain statement of fact. -- Gerard Seibert [EMAIL PROTECTED] O'Toole's Commentary on Murphy's Law: Murphy was an optimist. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Frustration
I am writing to you because I need to vent. I have tried installing version 5.3 of FreeBSD on a Pentium III machine. I thought I succeeded in doing it so, but when I tried to build xOrg I realized that I did not have all the ports installed and that some other dependencies were also missing. I realized then that the installation had not been as successful as I first thought. So, I tried to re-install the ports from the CD, since I didn't have an Internet connection to that machine. Well, I kept getting more and more hardware/software errors. I then tried to upgrade FreeBSD to version 6.1. And that was what I did; I tried. Well, I kept getting more errors, as usual. The more I tried to install/reinstall/upgrade/fix FreeBSD, the more I was realizing that anything that had to do with FreeBSD that could go wrond would go wrong, be it the software installation or hardware behavior. The amount of work and headache that I have been experiencing to move a single 'inch' towards a working Unix environment has been enourmously frustating. The worst part of it all is that I have not accomplished anything tangible at all. I think now it is time for this boy to abandon the 'Unix' bandwagon for good and move back to MS Windows. At least I will be able to concentrate on doing real productive work, instead of dealing with temperamental hardware and software every time I touch the PC. Good luck to those heroic individuals who stick with the configuration fight to the end. I failed to see the 'Power to Serve'. Bye, Fernando ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Frustration
[Format recovered--see http://www.lemis.com/email/email-format.html] Single line paragraphs. On Thursday, 29 June 2006 at 22:51:00 -0400, Fernando Pinguelo wrote: I am writing to you because I need to vent. I have tried installing version 5.3 of FreeBSD on a Pentium III machine. I thought I succeeded in doing it so, but when I tried to build xOrg I realized that I did not have all the ports installed and that some other dependencies were also missing. I realized then that the installation had not been as successful as I first thought. So, I tried to re-install the ports from the CD, since I didn't have an Internet connection to that machine. Well, I kept getting more and more hardware/software errors. I then tried to upgrade FreeBSD to version 6.1. And that was what I did; I tried. If you have hardware problems, you'll run into trouble installing anything. Well, I kept getting more errors, as usual. The more I tried to install/reinstall/upgrade/fix FreeBSD, the more I was realizing that anything that had to do with FreeBSD that could go wrond would go wrong, be it the software installation or hardware behavior. The amount of work and headache that I have been experiencing to move a single 'inch' towards a working Unix environment has been enourmously frustating. The worst part of it all is that I have not accomplished anything tangible at all. I think now it is time for this boy to abandon the 'Unix' bandwagon for good and move back to MS Windows. At least I will be able to concentrate on doing real productive work, instead of dealing with temperamental hardware and software every time I touch the PC. You really can't blame FreeBSD for temperamental hardware. And if you're used to Microosft, of course it will seem a little strange at first. But this mailing list isn't for venting your spleen, it's for getting help. Go and read The Complete FreeBSD (http://grog.evilcode.net/book.pdf.gz), then if you still have problems, report them here with details of what went wrong. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers. pgpm9HFluPp4C.pgp Description: PGP signature
Re: Frustration
On 6/29/06, Fernando Pinguelo [EMAIL PROTECTED] wrote: I am writing to you because I need to vent. I have tried installing version 5.3 of FreeBSD on a Pentium III machine. I thought I succeeded in doing it so, but when I tried to build xOrg I realized that I did not have all the ports installed and that some other dependencies were also missing. I realized then that the installation had not been as successful as I first thought. So, I tried to re-install the ports from the CD, since I didn't have an Internet connection to that machine. Well, I kept getting more and more hardware/software errors. I then tried to upgrade FreeBSD to version 6.1. And that was what I did; I tried. Well, I kept getting more errors, as usual. The more I tried to install/reinstall/upgrade/fix FreeBSD, the more I was realizing that anything that had to do with FreeBSD that could go wrond would go wrong, be it the software installation or hardware behavior. The amount of work and headache that I have been experiencing to move a single 'inch' towards a working Unix environment has been enourmously frustating. The worst part of it all is that I have not accomplished anything tangible at all. I think now it is time for this boy to abandon the 'Unix' bandwagon for good and move back to MS Windows. At least I will be able to concentrate on doing real productive work, instead of dealing with temperamental hardware and software every time I touch the PC. Good luck to those heroic individuals who stick with the configuration fight to the end. I failed to see the 'Power to Serve'. How come you never asked for help?: http://groups.google.com/groups/search?ie=UTF-8oe=UTF-8q=%22Fernando+pinguelo%22qt_s=Search You do realize that's what this list is for, correct? anyways... good bye and good luck. -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
[OT] X+mga frustration
Sorry for the littering but I am so frustrated trying to make a Matrox G550 work with DVI output. The G550 has dual head capability and both the VGA and the DVI output works from the console, but only VGA from X. Tried 4.11, 6.0-RC1 with both Xfree86-4 and xorg. If there is anyone out there who successfully configured this card to use DVI only output under X please, please, how did you do it? Thanks, ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [OT] X+mga frustration
On Sun, 16 Oct 2005 15:39:03 +0200 Per olof Ljungmark [EMAIL PROTECTED] wrote: If there is anyone out there who successfully configured this card to use DVI only output under X please, please, how did you do it? Port: mga_hal-4.1 Path: /usr/ports/x11-servers/mga_hal Info: Module for additional features with X.Org/XFree86 Matrox driver You need this for DVI, DualHead and such things installed and loaded. Works fine with my G450-DVI and Xorg. Joerg ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [OT] X+mga frustration
You need this for DVI, DualHead and such things installed and loaded. Works fine with my G450-DVI and Xorg. fixed it. Thanks a lot! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Shell script frustration
At 11:14 PM +0100 7/27/05, [EMAIL PROTECTED] wrote:
echo ldapdelete -W -D $binddn \cn=$1, $group_base\
ldapdelete -W -D $binddn \cn=$1, $group_base\
when run ('./rmgroup users') it outputs -
ldapdelete -W -D cn=Manager,dc=orbweavers,dc=co,dc=uk cn=users,
ou=groups,dc=orbweavers,dc=co,dc=uk
Enter LDAP Password:
ldap_bind: Invalid DN syntax (34)
additional info: invalid DN
However, if I copy and paste the echod statement (the first line
of the output) straight to the shell, it run fine.
What I do in this cases is create a script called list_args.sh:
#!/bin/sh
printf \nlist_args.sh at `date +%H:%M:%S` with \$# = $#\n
# Process all parameters.
N=0
while test $# != 0 ; do
N=$(($N+1))
printf \$$N = [%3d] '$1'\n ${#1}
shift
done
Then in your script, replace the ldapdelete command with
list_args.sh. That way you'll see *exactly* what ldapdelete
is seeing for parameters, and that might help.
I tried that one, with an echo $* - though I assume the printf prints it
out 'more precise'? I've come up with a work around - in my slapd.conf I
have quotes around the rootdn, if I take them off it works fine (I did try
it without the quotes around the variable, but that didn't work either,
much confusion)
I'd love to know what was causing the problem, but enough time is spend on
it. I will update the script to strip off quotes when found, which should
sort it out.
I now have the LDAP tools I discussed earlier written. Very rough and
ready, but they do the job I want, so they are 'complete' in that respect!
We have:
adduser - adds a user, and a group if it does not already exist
rmuser - removes a user
rmgroup - removes a group
users - prints a list of users found, or details if a username is
passed
groups - prints a list of groups found, or details if a groupname is
passed
passwd - change a user password
They are certainly not ready for an end user, but if anyone wants to make
use of them or polish them up a bit, let me know and I will send them to
you. I will put them up on my site at some point over the week.
Cheers,
Martin
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Shell script frustration
At 10:10 AM +0100 7/28/05, [EMAIL PROTECTED] wrote:
Garance wrote:
What I do in this cases is create a script called list_args.sh:
#!/bin/sh
printf \nlist_args.sh at `date +%H:%M:%S` with \$# = $#\n
# Process all parameters.
N=0
while test $# != 0 ; do
N=$(($N+1))
printf \$$N = [%3d] '$1'\n ${#1}
shift
done
Then in your script, replace the ldapdelete command with
list_args.sh. That way you'll see *exactly* what ldapdelete
is seeing for parameters, and that might help.
I tried that one, with an echo $* - though I assume the printf
prints it out 'more precise'?
Well, I also have versions that use an echo instead of printf.
The printf just makes it easier to have a pretty output.
The problem with using a plain 'echo *' is that there are
several different inputs which will produce the same output.
Compare:
echo a b
and echo a b
or echo a b
and echo a b
The outputs from `echo' will look the same, but the arguments to
the program are very different. That's why my script lists out
the exact arguments, with their lengths. I did that because
sometimes those details matter. I have solved problems similar
to the one which is frustrating you by using this kind of script.
--
Garance Alistair Drosehn = [EMAIL PROTECTED]
Senior Systems Programmer or [EMAIL PROTECTED]
Rensselaer Polytechnic Institute; Troy, NY; USA
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Shell script frustration
Hi,
I am making big progress in writing the ldap tools I mentioned earlier,
but I have come across a completly frustrating problem I can't crack.
Most likely it is something simple to do with the shell scripting, but
I can't figure it out at all - script is
binddn=`awk '/rootdn/ {print $2}' /usr/local/etc/openldap/slapd.conf`
group_base=`awk '/nss_base_group/ {print $2}' /etc/ldap.conf | cut -f1 -d?`
echo ldapdelete -W -D $binddn \cn=$1, $group_base\
ldapdelete -W -D $binddn \cn=$1, $group_base\
It grabs the rootdn from the slapd.conf file, then the base ou for the
groups from the ldap.conf file, and construct the delete statement from
that.
when run ('./rmgroup users') it outputs -
ldapdelete -W -D cn=Manager,dc=orbweavers,dc=co,dc=uk cn=users,
ou=groups,dc=orbweavers,dc=co,dc=uk
Enter LDAP Password:
ldap_bind: Invalid DN syntax (34)
additional info: invalid DN
However, if I copy and paste the echod statement (the first line of the
output) straight to the shell, it run fine. I've tried every which way of
quoting I can think of, but nothing gives. Please tell me I am missing
something really obvious and I can retrieve my sanity!
cheers,
Martin
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Shell script frustration
At 11:14 PM +0100 7/27/05, [EMAIL PROTECTED] wrote:
echo ldapdelete -W -D $binddn \cn=$1, $group_base\
ldapdelete -W -D $binddn \cn=$1, $group_base\
when run ('./rmgroup users') it outputs -
ldapdelete -W -D cn=Manager,dc=orbweavers,dc=co,dc=uk cn=users,
ou=groups,dc=orbweavers,dc=co,dc=uk
Enter LDAP Password:
ldap_bind: Invalid DN syntax (34)
additional info: invalid DN
However, if I copy and paste the echod statement (the first line
of the output) straight to the shell, it run fine.
What I do in this cases is create a script called list_args.sh:
#!/bin/sh
printf \nlist_args.sh at `date +%H:%M:%S` with \$# = $#\n
# Process all parameters.
N=0
while test $# != 0 ; do
N=$(($N+1))
printf \$$N = [%3d] '$1'\n ${#1}
shift
done
Then in your script, replace the ldapdelete command with
list_args.sh. That way you'll see *exactly* what ldapdelete
is seeing for parameters, and that might help.
--
Garance Alistair Drosehn= [EMAIL PROTECTED]
Senior Systems Programmer or [EMAIL PROTECTED]
Rensselaer Polytechnic Instituteor [EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Frustration
I've done a successful 4.9 standard install of FreeBSD aand it is performing as a file server for my mac. I've never been able to install xfree86 wich is no problem, but whenever I've tried to do installs of daapd and its dependencies, I've had a variety of failures, Recently i tried installing cvsup and now I'm getting the following. cd /usr/ports/net/cvsup-without-gui # make install clean cvsup-snap-16.1h.tar.gz doesn't seem to exist in /usr/ports/distfiles/. Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/snapshots/. fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/snapshots/cvsup- snap-16.1h.tar.gz: Host not found I'm hoping this something real simple that I'm overlooking. thanks, Paul ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Frustration
On 2004-11-13 12:24, Paul A. Sprague [EMAIL PROTECTED] wrote: I've done a successful 4.9 standard install of FreeBSD aand it is performing as a file server for my mac. I've never been able to install xfree86 wich is no problem, but whenever I've tried to do installs of daapd and its dependencies, I've had a variety of failures, Recently i tried installing cvsup and now I'm getting the following. cd /usr/ports/net/cvsup-without-gui # make install clean cvsup-snap-16.1h.tar.gz doesn't seem to exist in /usr/ports/distfiles/. Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/snapshots/. fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/snapshots/cvsup-snap-16.1h.tar.gz: Host not found I'm hoping this something real simple that I'm overlooking. Your DNS setup seems broken -- ftp.freebsd.org resolves fine here: gothmog:/home/giorgos$ host ftp.FreeBSD.org ftp.FreeBSD.org has address 62.243.72.50 ftp.FreeBSD.org has IPv6 address 2001:4f8:0:2::e gothmog:/home/giorgos$ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Frustration: the only thing mounting with NFS client :-)
Hi, I don't know what the problem in your case is, but just a few thoughts: - make sure your linux box isn't providing NFSv4, as FreeBSD does only support for v2 and 3, - to test and whether the nfs server is receiving you use showmount -e lg, it's quicker - yes, you need a portmapper running on the client too and apparently you have, its that sunrpc thingy - read mount_nfs(8) ;) I hope that helps a bit.. Alex. lost gweilo wrote: Hi there, I am trying to access an NFS server (Debian Linux, host name lg) from my FreeBSD 4.10-STABLE system (host name gw) on my LAN. My basic system info: gw# uname -mnprs FreeBSD gw 4.10-STABLE i386 i386 It doesn't seem to work: gw# mount -v -t nfs lg:/mnt/tt/music /root/uu lg:/mnt/tt/music: NFSPROC_NULL: RPC: Timed out ^C It works when I try on the server though... (Hopefully this also shows that basic networking is OK between the two boxes...) gw# ssh lg Password: [EMAIL PROTECTED]:~# pwd pwd /root [EMAIL PROTECTED]:~# mkdir uu mkdir uu [EMAIL PROTECTED]:~# mount -v -t nfs lg:/mnt/tt/music /root/uu mount -v -t nfs lg:/mnt/tt/music /root/uu lg:/mnt/tt/music on /root/uu type nfs (rw,addr=127.0.0.1) [EMAIL PROTECTED]:~# exit exit logout Connection to lg closed. RPC calls seem OK either with TCP or UDP: gw# rpcinfo -u lg nfs program 13 version 2 ready and waiting program 13 version 3 ready and waiting gw# rpcinfo -t lg nfs program 13 version 2 ready and waiting program 13 version 3 ready and waiting I read in Managing NFS and NIS by Hal Stern, in Chapter 10 p. 231 that that rpcinfo -u is supposed to call the null procedure of the RPC server... The error message I get from mount seems related... But I have no clue, it just does the same thing all the time: gw# mount -v -t nfs lg:/mnt/tt/music /root/uu lg:/mnt/tt/music: NFSPROC_NULL: RPC: Timed out ^C I also noticed that portmap doesn't run on my client. It won't start. Is it needed, for an NFS client? gw# portmap -d portmap[36419]: cannot bind udp: Address already in use gw# tail /var/log/messages Sep 17 05:00:00 gw newsyslog[90252]: logfile turned over due to size100K Sep 17 16:50:41 gw dhclient: New Network Number: 192.168.1.0 Sep 17 16:50:41 gw dhclient: New Broadcast Address: 192.168.1.255 Sep 17 23:14:55 gw portmap[9379]: cannot bind udp: Address already in use Sep 17 23:15:12 gw portmap[9472]: cannot bind udp: Address already in use Sep 18 00:23:26 gw portmap[36419]: cannot bind udp: Address already in use Naive attempt to investigate the portmap error message: gw# netstat -a -f inet Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp4 0 0 192.168.1.100.4294 lg.ssh ESTABLISHED tcp4 0 0 *.smtp *.* LISTEN tcp4 0 0 *.ssh *.* LISTEN tcp4 0 0 *.telnet *.* LISTEN tcp4 0 0 *.sunrpc *.* LISTEN udp4 0 0 *.**.* udp4 0 0 *.sunrpc *.* udp4 0 0 *.syslog *.* udp4 0 0 *.bootpc *.* Basically I have no clue what is going on. I hope you can suggest things to look at. Regards. Lostgweilo _ Linguaphone : Learning English? Get Japanese lessons for FREE http://go.msnserver.com/HK/46165.asp ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Frustration: the only thing mounting with NFS client :-)
Hi there, I am trying to access an NFS server (Debian Linux, host name lg) from my FreeBSD 4.10-STABLE system (host name gw) on my LAN. My basic system info: gw# uname -mnprs FreeBSD gw 4.10-STABLE i386 i386 It doesn't seem to work: gw# mount -v -t nfs lg:/mnt/tt/music /root/uu lg:/mnt/tt/music: NFSPROC_NULL: RPC: Timed out ^C It works when I try on the server though... (Hopefully this also shows that basic networking is OK between the two boxes...) gw# ssh lg Password: [EMAIL PROTECTED]:~# pwd pwd /root [EMAIL PROTECTED]:~# mkdir uu mkdir uu [EMAIL PROTECTED]:~# mount -v -t nfs lg:/mnt/tt/music /root/uu mount -v -t nfs lg:/mnt/tt/music /root/uu lg:/mnt/tt/music on /root/uu type nfs (rw,addr=127.0.0.1) [EMAIL PROTECTED]:~# exit exit logout Connection to lg closed. RPC calls seem OK either with TCP or UDP: gw# rpcinfo -u lg nfs program 13 version 2 ready and waiting program 13 version 3 ready and waiting gw# rpcinfo -t lg nfs program 13 version 2 ready and waiting program 13 version 3 ready and waiting I read in Managing NFS and NIS by Hal Stern, in Chapter 10 p. 231 that that rpcinfo -u is supposed to call the null procedure of the RPC server... The error message I get from mount seems related... But I have no clue, it just does the same thing all the time: gw# mount -v -t nfs lg:/mnt/tt/music /root/uu lg:/mnt/tt/music: NFSPROC_NULL: RPC: Timed out ^C I also noticed that portmap doesn't run on my client. It won't start. Is it needed, for an NFS client? gw# portmap -d portmap[36419]: cannot bind udp: Address already in use gw# tail /var/log/messages Sep 17 05:00:00 gw newsyslog[90252]: logfile turned over due to size100K Sep 17 16:50:41 gw dhclient: New Network Number: 192.168.1.0 Sep 17 16:50:41 gw dhclient: New Broadcast Address: 192.168.1.255 Sep 17 23:14:55 gw portmap[9379]: cannot bind udp: Address already in use Sep 17 23:15:12 gw portmap[9472]: cannot bind udp: Address already in use Sep 18 00:23:26 gw portmap[36419]: cannot bind udp: Address already in use Naive attempt to investigate the portmap error message: gw# netstat -a -f inet Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address(state) tcp4 0 0 192.168.1.100.4294 lg.ssh ESTABLISHED tcp4 0 0 *.smtp *.*LISTEN tcp4 0 0 *.ssh *.*LISTEN tcp4 0 0 *.telnet *.*LISTEN tcp4 0 0 *.sunrpc *.*LISTEN udp4 0 0 *.**.* udp4 0 0 *.sunrpc *.* udp4 0 0 *.syslog *.* udp4 0 0 *.bootpc *.* Basically I have no clue what is going on. I hope you can suggest things to look at. Regards. Lostgweilo _ Linguaphone : Learning English? Get Japanese lessons for FREE http://go.msnserver.com/HK/46165.asp ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
PPP, LAN and Newbie Frustration.
hi i was wondering if u could help me. When i type ipconfig/release [adapter] in msprompt it says dhcp not enabled for that adapter. it is a ppp adapter. I have managed to enble dhcp for my lan but not my internet connection. Can u help me out? Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: frustration (freeBSD ports system)
On Tuesday 16 December 2003 05:52 pm, richard michael bagstad wrote: i find this frustrating. on your website (page http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports- using.html) the following tells me that 'from cd' and 'from internet' are exactly the same... it does not tell me the directory of (ie.) lsof. it simply tells me to 'make install'. please help a poor green newbie. --- Hello from one FreeBSD newbie to another -- In FreeBSD, the ports are basically information and instructions for various system utility programs (like the program make), in order to automate, to some extent, the installation of programs that the FreeBSD user would like to install. All of the ports reside in the directory: /usr/ports which is to say that inside the /usr directory, which is one of the top level directories (immediately under the root directory), there is a directory called ports, and inside that directory are quite a few directories which are categories of related programs, such as audio, editors, finance, databases etc. In each of those subdirectories there are directories for many different programs, each in its own subdirectory, like: /usr/ports/editors/nedit nedit is a text editor whose information and instructions reside in the directory nedit that is inside the directory editors which is itself inside the ports directory in the directory usr It is important to remember that the program itself is not inside its associated directory (nedit, the program or its source files, are not inside the /usr/ports/editors/nedit directory). Instead, the information and instructions contained within the nedit directory tell the system to look for and get the files it needs to build nedit. The usual place these files are stored (after they are placed there by the user or a program) is in /usr/ports/distfiles. If the files are not already in /usr/ports/distfiles, then they will be fetched via the Internet (you must be connected to the Internet at the time, of course) and placed in the /usr/ports/distfiles directory. If, on the other hand, you happen to have a CD that has those distfiles already on it, you can copy those files, yourself, from the CD into the directory /usr/ports/distfiles. Then when you enter one of the ports directories like: cd /usr/ports/editors/nedit and issue the following command: make the file(s) will be found in the /usr/ports/distfiles directory (because you placed them there yourself, by copying them from a CD), instead of the system having to get them from the Internet. I hope this makes sense. Best wishes, Steve D -- You grow up on the day you have your first real laugh at yourself. -Ethel Barrymore ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: frustration
On Tue, 16 Dec 2003, richard michael bagstad wrote: i find this frustrating. on your website (page http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports- using.html) the following tells me that 'from cd' and 'from internet' are exactly the same... it does not tell me the directory of (ie.) lsof. it simply tells me to 'make install'. please help a poor green newbie. The difference they are talking about is after you've given the 'make install' command in /usr/ports/sysutils/lsof. The ports system looks for the distfile in /usr/ports/distfiles. If you've already copied the distfile in there manually (from a CD or someplace else), it proceeds to build the port. The internet version is where it doesn't find the distfile in /usr/ports/distfiles. Then it uses your net connection to find one and download it. -Warren Block * Rapid City, South Dakota USA ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: frustration
richard michael bagstad wrote: i find this frustrating. on your website (page http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports- using.html) the following tells me that 'from cd' and 'from internet' are exactly the same... it does not tell me the directory of (ie.) lsof. it simply tells me to 'make install'. please help a poor green newbie. 4.5.2.1 Installing Ports from a CD-ROM The FreeBSD Project's official CD-ROM images no longer include distfiles. They take up a lot of room that is better used for precompiled packages. CD-ROM products such as the FreeBSD PowerPak do include distfiles, and you can order these sets from a vendor such as the FreeBSD Mall . This section assumes you have such a FreeBSD CD-ROM set. Place your FreeBSD CD-ROM in the drive. Mount it on /cdrom . (If you use a different mount point, the install will not work.) To begin, change to the directory for the port you want to install: #cd /usr/ports/sysutils/lsof Once inside the lsof directory, you will see the port skeleton. The next step is to compile, or ``build'', the port. This is done by simply typing make at the prompt. Once you have done so, you should see something like this: #make lsof_4.57D.freebsd.tar.gz doesn't seem to exist in /usr/ports/distfiles/. Attempting to fetch from file:/cdrom/ports/distfiles/. === Extracting for lsof-4.57 ... [extraction output snipped] ... Checksum OK for lsof_4.57D.freebsd.tar.gz. === Patching for lsof-4.57 === Applying FreeBSD patches for lsof-4.57 === Configuring for lsof-4.57 ... [configure output snipped] ... === Building for lsof-4.57 ... [compilation output snipped] ... # Notice that once the compile is complete you are returned to your prompt. The next step is to install the port. In order to install it, you simply need to tack one word onto the make command, and that word is install : #make install === Installing for lsof-4.57 ... [installation output snipped] ... === Generating temporary packing list === Compressing manual pages for lsof-4.57 === Registering installation for lsof-4.57 === SECURITY NOTE: This port has installed the following binaries which execute with increased privileges. # Once you are returned to your prompt, you should be able to run the application you just installed. Since lsof is a program that runs with increased privileges, a security warning is shown. During the building and installation of ports, you should take heed of any other warnings that may appear. Note: You can save an extra step by just running make install instead of make and make install as two separate steps. Note: Some shells keep a cache of the commands that are available in the directories listed in the PATH environment variable, to speed up lookup operations for the executable file of these commands. If you are using one of these shells, you might have to use the rehash command after installing a port, before the newly installed commands can be used. This is true for both shells that are part of the base-system (such as tcsh ) and shells that are available as ports (for instance, shells/zsh ). Note: Please be aware that the licenses of a few ports do not allow for inclusion on the CD-ROM. This could be because a registration form needs to be filled out before downloading or redistribution is not allowed, or for another reason. If you wish to install a port not included on the CD-ROM, you will need to be online in order to do so (see the next section ). 4.5.2.2 Installing Ports from the Internet As with the last section, this section makes an assumption that you have a working Internet connection. If you do not, you will need to perform the CD-ROM installation , or put a copy of the distfile into /usr/ports/distfiles manually. Installing a port from the Internet is done exactly the same way as it would be if you were installing from a CD-ROM. The only difference between the two is that the distfile is downloaded from the Internet instead of read from the CD-ROM. The steps involved are identical: #make install lsof_4.57D.freebsd.tar.gz doesn't seem to exist in /usr/ports/distfiles/. Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/. Receiving lsof_4.57D.freebsd.tar.gz (439860 bytes): 100% 439860 bytes transferred in 18.0 seconds (23.90 kBps) === Extracting for lsof-4.57 ... [extraction output snipped] ... Checksum OK for lsof_4.57D.freebsd.tar.gz. === Patching for lsof-4.57 === Applying FreeBSD patches for lsof-4.57 === Configuring for lsof-4.57 ... [configure output snipped] ... === Building for lsof-4.57 ... [compilation output snipped] ... === Installing for lsof-4.57 ... [installation output snipped] ... === Generating temporary packing list === Compressing manual pages for lsof-4.57 === Registering installation for lsof-4.57 === SECURITY NOTE: This port has installed the following binaries which
PPP, LAN and Newbie Frustration.
Hello! This is my third month with FreeBSD, and while so far everything worked mostly fine, I think I now hit a wall. Hard. Please note that I lack Unix and networking background, so expect me to sound embarrassingly amateurish. The current situation: Over the past few weeks I used a network consisting of two machines. Machine A is a Window XP Pro system with a dial-up connection to my ISP. Machine B is a FreeBSD 4.8 system that shares XP's internet connection when available. This was easy enough to set up: I used the idiot-proof set up a network wizard in XP and enabled Internet Connection Sharing, and in FreeBSD I let Sysinstall DHCP-configure the Ethernet card. This works flawlessly. However, this isn't what I really want. It makes little sense for the FreeBSD box to run local IMAP and NTTP servers, connect through the XP box to the net, and then serves mail and news to the very same XP machine. It's just not pretty or efficient, since it requires me to have the workstation running 24/7, too. The goal: I'd like the FreeBSD to connect to the 'net, using a PPP dial-up connection, and the XP box to share the (dial-up) Internet connection of the FreeBSD machine. So, yesterday I plugged an old, external ISDN modem into the FreeBSD machine. It took me a while to get PPP working (with the help of a kind freebsd-questions soul), but it eventually did work. It connects to the ISP, and it will also use this connection, but ONLY if the XP machine is also there (even if not connected). If the XP machine is turned off or the LAN interrupted, the FreeBSD box will not use its own Internet connection. (I suspect it has to do with resolv.conf listing the XP machine's internal IP address as nameserver? If I remove this, FreeBSD still can't resolve addresses, even though ppp.conf has enable dns.) Roughly, what I'd like is this: Have the FreeBSD box connect to the Internet via PPP (dial-up) whenever an application on either the FreeBSD box *or* the Windows box requires a connection to the Internet, and disconnect when it's been idle for a while (I know how to set *this* in ppp.conf, but that's pretty much all I know). I'd like the FreeBSD system to internally use 192.168.0.1 and the XP box 192.168.0.2. Some of the problems: - I get a dynamic IP address whenever I connect to the ISP and I don't know this address before I connect. - I do not have a local DNS/nameserver. I understand that I can set one up locally, but that I would need my ISPs nameserver IP for this. Also, how would this help me if the host configuration is done before a PPP connection is established? Ideally, in addition, I'd like to use different ISPs. - I am uncertain if it is all right that the host names of these two machines are fictive. With the old setup, both use system.mshome.net (something Windows assigns, I didn't choose this.) Is it acceptable to use something made up? (Let's say I own example.org and name the boxes freebsd.example.org and xp.example.org, would this be all right even though the machines have 192.x.x.x IP addresses and don't really exist as far as the outside world is concerned?) - I noticed that after setting up PPP, FreeBSD will automatically establish a PPP connection at boot time. It will only use the papchap configuration, and fail if I rename this entry. The problem is that the only change I made to anything but /etc/ppp/ppp.conf is that I added ppp_enable=YES to /etc/rc.conf. Where does it get the idea from to use the papchap entry in ppp.conf? - I am in the dark when it comes to configuring the XP side. This is off-topic here, but if anyone has an idea, I'd be grateful for the assistance. The wizard allows for two modes: XP being the machine connecting to the 'net, and XP using another machine's connection. It doesn't actually ask for any IP addresses, or lets me assign any IP addresses (it picks 169.x.x.x for itself when I make it a client). How does one configure this manually? (I never thought I'd see the day where I actually *want* textual configuration files -- but three months with FreeBSD changed this fundamentally.) - To make matters worse, I don't really understand what netstat tells me, or how to draw any conclusions from the information it provides. I did read the man pages for netstat, PPP and so on, but frankly, it's over my head. I know, I must sound pathetically helpless here. Rest assured, I feel exactly this way, too! :) What am I looking for? Ideally, for easy-to-understand, step-by-step instructions! Seriously though, I've tried the entire morning and afternoon to figure this out, but it's clearly out of my scope. It is a pitiful experience to read documentation and not understand it. I don't know which files to edit (on the FreeBSD side), and how to set up everything to work as outlined above. The future: If/when I get this to work, I'll add a second 80GB disk to the XP machine and put FreeBSD on it, and then dual-boot. The current FreeBSD box would continue to connect to the
Re: PPP, LAN and Newbie Frustration.
On Tuesday 02 September 2003 07:37, Michael Vondung wrote: Hello! Morning :) - I get a dynamic IP address whenever I connect to the ISP and I don't know this address before I connect. This is fine, unless of course you were planning on running a mailserver/webserver/someserver for the outside world to see and then you can either play with some of the dynamic DNS services available or your S.O.L. - I do not have a local DNS/nameserver. I understand that I can set one up locally, but that I would need my ISPs nameserver IP for this. Yes, you can setone up and you don't need the ISP nameservers since your DNS server will query down to the root level for you, but it is more polite to ask your ISP nameservers first for info. For starters, since you're running only 2 machines I would just use your ISP nameservers on both boxes and not run a DNS server locally. Also, how would this help me if the host configuration is done before a PPP connection is established? Ideally, in addition, I'd like to use different ISPs. Different ISPs all the time or just switching now and again? - I am uncertain if it is all right that the host names of these two machines are fictive. With the old setup, both use system.mshome.net (something Windows assigns, I didn't choose this.) Is it acceptable to use something made up? (Let's say I own example.org and name the boxes freebsd.example.org and xp.example.org, would this be all right even though the machines have 192.x.x.x IP addresses and don't really exist as far as the outside world is concerned?) I prefer setting up something like: boxname.int.domain.com (int = internal) and yes, you can name them anything you like since you aren't broadcasting to the world and are in private space. The 2 machines should have different names however. Another issue, unless you are running an internal DNS server or add the info to the hosts file (yes, XP has a hosts file as well..just a well hidden one) you won't be able to actually use the names to get from one box to another. IPs only. - I noticed that after setting up PPP, FreeBSD will automatically establish a PPP connection at boot time. It will only use the papchap configuration, and fail if I rename this entry. The problem is that the only change I made to anything but /etc/ppp/ppp.conf is that I added ppp_enable=YES to /etc/rc.conf. Where does it get the idea from to use the papchap entry in ppp.conf? My PPP is really rusty..sorry. Check the ppp man page and/or the ppp.conf man page. or look in /etc/defaults/rc.conf for any default settings related to ppp.conf - I am in the dark when it comes to configuring the XP side. This is off-topic here, but if anyone has an idea, I'd be grateful for the assistance. The wizard allows for two modes: XP being the machine connecting to the 'net, and XP using another machine's connection. It doesn't actually ask for any IP addresses, or lets me assign any IP addresses (it picks 169.x.x.x for itself when I make it a client). How does one configure this manually? (I never thought I'd see the day where I actually *want* textual configuration files -- but three months with FreeBSD changed this fundamentally.) Don't use the wizard :) Right-Click on Network Neihborhood and select Properties (or go through to Network via the Control Panel) and then click around in there. I don't use Windows and don't have access to an XP box at all, so I'm a little fuzzy. I would assign IPs manually at first. Not a lot of detailed help..sorry...I haven't setup a PPP connection in a LONG time. Henrik -- Henrik Hudson [EMAIL PROTECTED] `If there's anything more important than my ego around, I want it caught and shot now.' --Hitchhikers Guide to the Galaxy ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: PPP, LAN and Newbie Frustration.
Henrik wrote: Not a lot of detailed help..sorry...I haven't setup a PPP connection in a LONG time. The good news is that in a year I'll relocate to an area where ADSL is available. Until then I'm stuck in a beautiful but telecommunication-wise terribly medieval area. I received an e-mail from another list member, and with both his and your thoughts I had enough pointers to read up more on the relevant topics. The most important resource was the FreeBSD Unleashed book that came with a very nice for dummies type of chapter about networking. ;) Here's a short summary in case someone else has a similar problem and suffers the same lack of knowledge as I did: - Learned that ppp_enable=YES in rc.conf results in FreeBSD establishing a PPP connection at boot time. Unless otherwise configured in rc.conf, it'll be in auto mode (connection on demand). If not specified, it will use the papchap profile. ppp_profile= will cause it to use the profile. It also uses the -nat option by default. - Went to sysinstall and configured my ethernet card manually this time. Managed to fill in the right values, amazingly enough. - Got ahold of my ISPs name servers and put the IP addresses in the resolv.conf. - Figured out how to configure the LAN manually in XP, without the wizard (right-click on the connection icon, properties, highlight tcp-ip, properties button). Put in the appropriate IP addresses, and that was that. I also had to change the Internet settings to prevent that XP uses the local ISDN adapter to establish a dial-up connection. - The last step was the biggest obstacle. While the two machines could ping each other, FreeBSD wouldn't forward the packets for outside systems. After some digging around I learned that this is disabled by default. Adding gateway_enable=YES to rc.conf fixed this. A small thing, but took the most time to solve. In short, it works as desired. Broke through the wall, and quite happy with myself. ;) Cheers, Michael ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
