Portupgrading ports with individual settings.
Very neophyte'ish question again, but: I currently have Qt installed and now downloaded the distfile for a new version. I'd like to compile this new version with the WITHOUT_OPENGL option, which isn't the default. If I have portupgrade -ra do this, it will use the default settings, I believe. How would I go about this? Should I make deinstall the currently installed Qt version and then make WITHOUT_OPENGL=yes install the whole thing? (and then update the rest of the software with portupgrade -ra) This seems a bit awkward, especially in regard to future versions. Is there a better way? Thanks for bearing with my fairly basic questions! M. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: ports on a CD
Sounds like a business opportunity. Make and sell CD sets with the 'missing' ports. Every couple of months, a new snapshot of the entire ports tree with all of the legally-CD-able distfiles; for people who don't have the (cheap) bandwidth to stay up to date with cvsup... I believe that is what Tadimeti originally meant. If you get the seven Debian CDs, you can install and use a wide variety of different software, even if you have no or a slow/expensive connection to the 'net. With FreeBSD you get some packages, but if you want or need more than the minimum software, you depend on an online connection. If the same person also has a slow machine, then FreeBSD is not really suited for them. This has actually been one of my problems. I'm stuck in an area where the fastest connection speed is ISDN, and I pay for that by the minute (an average of fifty cents an hour, for one channel). Setting up a workstation with a decent selection of software, was more costly for me than if I had done the same with Debian. To me, this was a perfectly acceptable investment, but I can see why it would turn people off who haven't yet decided to go with FreeBSD and instead shop for an OS (it makes little difference if you purchase two or seven CDs if you get them for one or two dollars a piece). M. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Simple Make question.
This is one of those questions that label me as a complete neophyte, but, how does one specify a paramter for the Make tool? When trying to make install the port of the Qt version of licq (net/licq-qt-gui), a message said that I could compile this port with KDE support by defining WITH_KDE. I've tried this with make WITH_KDE install, make -WITH_KDE install and make -WITH_KDE=yes install, but none of these worked. How can I achieve this? Thanks! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
XFree86 -- Gamma Correction
Hello, all, I successfully managed to install the FreeBSD nVidia video drivers, but ran into a problem that is apparently X related: How does one tune the gamma correction? man XFree86 suggests the command line option -gamma value, where value is a number between 0.1 and 10.0, 1.0 being the default. I tried to start X with startx -gamma 2.0, but right after displaying the nVidia logo, X drops back to the command line. The error message says, /usr/X11R6/bin/xterm: bad command line option '-gamma'. The XFree86 version is 4.3.0 (compiled from ports). What am I doing wrong, and where would I look for more information? Also, if a working option can be found, is there a place where I can put this so that it is automatically used and I don't have to type it in manually every time X is started? (At this point I actually miss the nice GUI-interface to tweak the card that comes with nVidia's XP drivers. :) Thanks! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Partitioning advice (/usr and /home)
I'm trying to figure out a decent partitioning layout for a workstation. The system has an ~80GB disk. After /, /var, /tmp and swap, I have 70GB left. I'm wondering how to split these between /usr and /home. Ironically, it is more space than I seem to need. The box has only one user (me), I do not have a fast enough connection to download large amounts audio or video files. I plan to run the KDE3 desktop environment with most of its applications (this is still well under 1.5GB), assorted other software, Wine, two or three Windows apps if they'll run. I'm torn between various options here, and would appreciate your input: 35GB for each, /usr and /home 25GB for /home and 45GB for /home 70GB for both together (no /home partition) Or something completely different? I'd like this to be spacey enough so that I won't run out of room at some point in the future, but 35GB for /usr seems unrealistically much (there won't be mail on this system, it's fed by an IMAP server on a different machine). Then again, 35GB for /home seems just as unrealistically much. Backup matters aside, is there a significant advantage of having a separate /home partition at all? If not, just skipping /home and using 70GB for /usr (including /usr/home) might be the most practical and flexible approach? Thanks. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Easy boot between FBSD and WinXP
Hi, Denis, This sounds pretty much like my set-up. All I had to do was to let Sysinstall write a BootMgr on *both* disks. In /stand/sysinstall, just go in the Fdisk section, select your first drive, don't do anything else here, and immediately leave with Q. It will ask you if you want to write the BootMgr, a standard MBR or do nothing. Select BootMgr. You'll need to do this for each of the disks. Then leave sysinstall. When you boot, you'll see something like this (assuming XP is on the first disk (disk 0) and you have two NTFS partitions): F1 ??? F2 ??? F5 Disk 1 F1 will boot XP. Hit F5 to boot from the second disk and you'll see: F1 FreeBSD F5 Disk 0 F1 here will boot you into FreeBSD, and F5 get you back to the first selection. Note: I'm a newbie myself, but the above worked for me and doesn't require additional software. The ??? isn't pretty, but it works. Just be careful that you don't slice the disk that has XP on it. M. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Denis Sent: Thursday, September 11, 2003 18:00 To: [EMAIL PROTECTED] Subject: Easy boot between FBSD and WinXP Hi All!!! I use two hard disk. In first I have FreeBSD. In Second - WinXP. Does anybody know some easy way to boot between FBSD hard and WinXP hard? Now, I change priority of hard disks in my BIOS options it's very uncomfortable: -- Best regards, Denis [EMAIL PROTECTED] ___ [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]
Planning a FreeBSD desktop, basic questions.
Hello! My apologies for the length of this post. Summary: 4.x or 5.x for a desktop machine, disk partitioning for a workstation, miscellaneous installation questions. Okay, the details! Now that I have my local FreeBSD server (mail/news, router, firewall) successfully running, I'm ready to tackle my workstation. This is currently a system with a P4-2.6Ghz, 512MB RAM, an 80GB EIDE disk, and the usual devices (CDR, CD/DVD player, network adapter and so on). At this time it is running Windows XP, and I plan to keep it where it is. To avoid having two operating systems on the same disk, I've purchased an identical HD (WD800BB) where FreeBSD will live on. Since I don't download movies or obscene amounts of MP3s, this is all a bit spacey. The XP disk only uses 35 of 80GB and I doubt the FreeBSD one will even be this full. How times change. :) 4.8 or 5.1? My personal server happily runs 4.8R and will be updated to 4.9 when -stable becomes a bit more stable. It consists of older hardware and I don't plan to upgrade it to 5.x any time soon, if ever. But what do you recommend for the workstation? It doesn't have dual-processors and all of its hardware seems to be supported by 4.x. This machine, though, will eventually get 5.x. I'm wondering if it makes sense to put 4.8 on it now or if it would be a better choice to just go with 5.1R. My primary concern here is ease of upgrading. Will it be difficult to go from 4.9 to 5.2, somewhere down the road? Mergemaster is a rather scary looking critter. Differently put, will there be tools provided to allow this without too much fiddling? Partitions If anything brings out the perfectionist in me, it is figuring out how to partition a disk. What I have in mind for the 80GB FreeBSD disk for the workstation is this: / = 512MB (too spacey, but that should be plenty for future releases) swap = 3GB (see notes below) /var = 1GB (probably too much, but the room's there) /tmp = 1GB (256MB would probably be enough, but why not?) /usr = the rest (essentially 74GB) The machine currently has 512MB of RAM, but since I won't have the financial means or desire to get a new complete system in the next two to four years, it's possible that I'll upgrade the memory first to 1GB and later to 1.5GB if needed or wanted. 3GB would then be an acceptable amount of swap space, but I certainly won't need this much right now, and I might never. Am I overdoing it, or doesn't it really matter since I don't seem to lack storage room anyway? Then there's this huge /usr partition. 74GB. I thought about splitting this between /home and /usr, but I have honestly no idea (and experience) how much space I'll end up using where. It probably wouldn't matter since I won't need more 30 or 40GB of that space. There's also the possibility that I might end up using the second disk (another 80GB one that currently belongs to XP) for FreeBSD also. That would then be for /home, if for some unexpected reason I should need more space. In other words, I would like to keep this option open. This workstation won't hold critical data, so I do not plan on backing up entire partitions. If all of this is inefficient and I'm missing the obvious, please let me know. Keep in mind that I -am- new to the FreeBSD and Unix world. I'm open for suggestions here. Miscellaneous - FreeBSD will be on the second disk. Is Sysinstall, if FreeBSD is installed on the slave, going to ask if I'd like to put the BootMgr on the first drive? - In case I decide to make the second disk (with FreeBSD) the master drive some time in the not-so-near future, will it be fairly simple to accomplish this? Only jumper rearrangement, MBR and fstab editing? - Anything else I need to pay particular attention to? Besides backing up important files on the XP disk in case something goes wrong. Thanks! Cheers, Michael ___ [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.
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.
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]
PPP and the backslash-containing AT command in ppp.conf
I am fairly to FreeBSD (and any kind of Unix), so please be easy on me in case I'm overlooking the obvious. :) I've been trying to connect to my ISP with an external Elsa Microlink ISDN/TL pro modem. The init string that the modem requires is ATF\N9. I modified the following line in /etc/ppp/ppp.conf: set dial ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \ \\ AT OK-AT-OK ATF\\N9 OK ATE1Q0 OK \\dATDT\\T TIMEOUT 40 CONNECT The man page for chat (http://www.freebsd.org/cgi/man.cgi?query=chatsektion=8) says that \\ sends a backlash character, so I figured that ATF\\N9 would be sent as ATF\N9. However, it doesn't seem to send a backslash. Here's the relevant bit from /var/log/ppp.log: Sep 1 15:01:36 catbox ppp[372]: tun1: Chat: deflink: Dial attempt 1 of 1 Sep 1 15:01:36 catbox ppp[372]: tun1: Chat: Send: AT^M Sep 1 15:01:36 catbox ppp[372]: tun1: Chat: Expect(5): OK Sep 1 15:01:37 catbox ppp[372]: tun1: Chat: Received: AT^M^M Sep 1 15:01:37 catbox ppp[372]: tun1: Chat: Received: OK^M Sep 1 15:01:37 catbox ppp[372]: tun1: Chat: Send: ATFN9^M Sep 1 15:01:37 catbox ppp[372]: tun1: Chat: Expect(5): OK Sep 1 15:01:37 catbox ppp[372]: tun1: Chat: Received: ATFN9^M^M Sep 1 15:01:37 catbox ppp[372]: tun1: Chat: Received: ERROR^M Sep 1 15:01:42 catbox ppp[372]: tun1: Chat: Expect timeout Sep 1 15:01:42 catbox ppp[372]: tun1: Warning: Chat script failed I have also tried this with ATF\N9, ATF\\\N9 and ATF^\N9. I'm unsure why the script expects timeout and not CONNECT. If I leave out ATF\\N9 OK before ATE1Q0, the modem will dial (the LNE LED indicates that an ISDN connection is being established), but won't get a carrier. In this case the log looks like this: Sep 1 14:58:43 catbox ppp[359]: tun1: Chat: deflink: Dial attempt 1 of 1 Sep 1 14:58:43 catbox ppp[359]: tun1: Chat: Send: AT^M Sep 1 14:58:43 catbox ppp[359]: tun1: Chat: Expect(5): OK Sep 1 14:58:43 catbox ppp[359]: tun1: Chat: Received: AT^M^M Sep 1 14:58:43 catbox ppp[359]: tun1: Chat: Received: OK^M Sep 1 14:58:43 catbox ppp[359]: tun1: Chat: Send: ATF^M Sep 1 14:58:43 catbox ppp[359]: tun1: Chat: Expect(5): OK Sep 1 14:58:43 catbox ppp[359]: tun1: Chat: Received: ATF^M^M Sep 1 14:58:43 catbox ppp[359]: tun1: Chat: Received: OK^M Sep 1 14:58:43 catbox ppp[359]: tun1: Chat: Send: ATDT019102345^M Sep 1 14:58:45 catbox ppp[359]: tun1: Chat: Expect(40): CONNECT Sep 1 14:58:45 catbox ppp[359]: tun1: Chat: Received: ATDT019102345^M^M Sep 1 14:58:45 catbox ppp[359]: tun1: Chat: Received: NO CARRIER^M Sep 1 14:58:45 catbox ppp[359]: tun1: Warning: Chat script failed Any help is greatly appreciated. Thanks! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: PPP and the backslash-containing AT command in ppp.conf
Malcolm wrote: Sould work if you use '', that is: ATFN9 which the first interpretation reduces to: ATF\\N9 Thank you! This worked indeed. After an hour of frustrating fiddling I also figured out that the string I needed for this particular ISP was ATF\N10 rather than ATF\N9 -- and yet another hour later I managed to figure out that my user name needed to be in a different format (very cryptic and well hidden on the ISP's pages) than the one used in the ISP's dialer software for Windows. (User PPP is almost too verbose.) So, PPP now connects just fine. The only problem is that FreeBSD doesn't recognise this connection as its primary connection to the Internet. Up until this point, the FreeBSD box used the shared Internet connection of a Windows XP system (a situation I'm attempting to reverse). Even when the PPP connection is established, ping, traceroute, etcetera go via the LAN to the XP box ... and time out because the XP machine doesn't have an active connection to the Internet. Probably off topic under this subject line, but would you know where I should start looking? Thanks! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
