Re: Newbie questions (updating, ports, etc.)
Thanks to all for your detailed and informative replies to my questions. I have many new things to try out. I can't speak for anyone else, but long posts don't bother me. I hope we've clarified things for you. Welcome to FreeBSD! Thanks. Its good to be here! -Richard ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Newbie questions (updating, ports, etc.)
On Thu, Dec 3, 2009 at 3:13 AM, Richard Mace mac...@telkomsa.net wrote: I recently installed FreeBSD 8.0-RELEASE on my home desktop and am considering making the switch from Debian GNU/Linux. I have a few questions which I am hoping the list can clarify for me. 1.) Keeping installed ports/packages up to date. As far as I can tell from the docs, perhaps the most convenient method is to use something like: # portsnap fetch update # pkgdb -F # portupgrade --batch -aP (do I need an R here?) which should first try to find a package from the repositories and failing that will fall back to a port. What is the current wisdom here? Is it safe to use the --batch switch? As far as I understand, this will use the configuration defaults and not prompt the user whenever a port requires some user (options) configuration. Is this interpretation correct? Otherwise, is there a way to get portupgrade to use the defaults non-interactively, to automate the process. Related to the above, are the default options that appear in the ncurses dialogues the same as those used in the building of packages? You method should work fine except you don't need the pkgdb -F step. Normally i use portmaster -dga to do this which will basically ask on new config entries and allow you to preset them before compiling starts. It's much quicker IME than portupgrade. portupgrade also has a preconfigure flag but I don't remember it offhand. portupgrade also is slower due to it's db backend and ruby parsing but it's still a great utility and I use it when something breaks portmaster. 2.) Evolution of ports (and packages) versus evolution of the base system. Reading the docs makes it clear that FreeBSD maintains is a rigorous distinction between the base system and add-on packages (ports). This is very appealing. However, as far as I can tell so far, even though my base system is 8.0 -RELEASE (and remains fixed between releases?), the ports continuously evolve (are updated). Is my understanding correct that by tracking a RELEASE system I can have bleeding edge (or close) versions of ports? Or, do I need to track STABLE of CURRENT for that? Yes, your understanding is correct. that's what portsnap fetch update will do for you. 3.) Upgrading ports seems to take considerable time (at least with my experiments on a 5 year old Pentium IV). I am keen to adopt FreeBSD as my desktop for work (Physics Professor, Research and teaching). Is it feasible in a work environment to upgrade ports without getting bogged down in a compile-a-thon, leaving one with a useless workstation. (My target machine will be an 8-core HP z600 (Xeon) which leads me to believe that I could do the upgrading in the background while I continue to work uninterrupted. I'd like to hear others experiences here.) If you're going to run with ports, you'll be spending more time than simply packages alone. There are things to make it easier though. First and foremost is make a backup of packages you create in case something goes wrong. Then you have a choice of frequent updates of ports tree or intermittent style. If you update all installed ports say on a weekly basis, each update run is generally not too intensive. If you take 10 minutes out you're day to preconfig, read UPDATING, and start the compile you should generally be done. However sometimes things break either during the compile or later in use. Sometimes resolving those eat up time and backup package can be of help there. If you update less frequently eg monthly, be prepared for longer upgrade times, more problems at once and with a longer stable time in between. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Newbie questions (updating, ports, etc.)
On Thu, 3 Dec 2009, Richard Mace wrote: I recently installed FreeBSD 8.0-RELEASE on my home desktop and am considering making the switch from Debian GNU/Linux. I have a few questions which I am hoping the list can clarify for me. 1.) Keeping installed ports/packages up to date. As far as I can tell from the docs, perhaps the most convenient method is to use something like: # portsnap fetch update # pkgdb -F Really should check /usr/ports/UPDATING at this step. There are upgrades which will bite you otherwise. # portupgrade --batch -aP (do I need an R here?) which should first try to find a package from the repositories and failing that will fall back to a port. What is the current wisdom here? Packages are quick to install but can't be customized. Building from source takes longer but lets you set CPUTYPE for compiler optimization and build with the specific options you want. On slow machines or for getting going quickly, packages are great. As far as batch or even -a, I update the ports tree often and prefer to manually upgrade ports as needed, usually with portupgrade -r. A lot of people seem to like -R; maybe I have the dependencies backwards. But I rarely have trouble, either. I use csup, then portsdb -Fu, then portversion -vL= to show what needs updating. 2.) Evolution of ports (and packages) versus evolution of the base system. Reading the docs makes it clear that FreeBSD maintains is a rigorous distinction between the base system and add-on packages (ports). This is very appealing. However, as far as I can tell so far, even though my base system is 8.0 -RELEASE (and remains fixed between releases?), the ports continuously evolve (are updated). Is my understanding correct that by tracking a RELEASE system I can have bleeding edge (or close) versions of ports? Or, do I need to track STABLE of CURRENT for that? Since ports are in a separate tree than the FreeBSD operating system source, you can keep ports current regardless of which version of the operating system. So stick with 8.0 or go to 8-STABLE and it's no problem. 9-CURRENT is bleeding edge, where things can break with no warning. And you'd need to rebuild all of your ports if you switched to it, since they were built on 8. But you could still get the newest ports. 3.) Upgrading ports seems to take considerable time (at least with my experiments on a 5 year old Pentium IV). I am keen to adopt FreeBSD as my desktop for work (Physics Professor, Research and teaching). Is it feasible in a work environment to upgrade ports without getting bogged down in a compile-a-thon, leaving one with a useless workstation. (My target machine will be an 8-core HP z600 (Xeon) which leads me to believe that I could do the upgrading in the background while I continue to work uninterrupted. I'd like to hear others experiences here.) I'd think background ports building on that kind of system would be no problem at all. The only thing that really slows down this Core 2 Duo system is building something big (openoffice), and that seems to be more due to swapping or disk contention than CPU time. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Newbie questions (updating, ports, etc.)
2009/12/3 Richard Mace mac...@telkomsa.net: 1.) Keeping installed ports/packages up to date. As far as I can tell from the docs, perhaps the most convenient method is to use something like: # portsnap fetch update # pkgdb -F # portupgrade --batch -aP (do I need an R here?) I don't see any reason to upgrade all installed ports on daily or weekly basis. In most cases you'll get nothing as the result of updating some port version 2.16.134 to new version 2.16.135 but lost time. which should first try to find a package from the repositories and failing that will fall back to a port. What is the current wisdom here? Yes, it's right. Is it safe to use the --batch switch? As far as I understand, this will use the configuration defaults and not prompt the user whenever a port requires some user (options) configuration. Is this interpretation correct? If the package is in use, there will no prompt. While building a port, configuration in which this port was built last time is used. If there is no such configuration, then port builds with default options. Related to the above, are the default options that appear in the ncurses dialogues the same as those used in the building of packages? It's really intresting. 3.) Upgrading ports seems to take considerable time (at least with my experiments on a 5 year old Pentium IV). I am keen to adopt FreeBSD as my desktop for work (Physics Professor, Research and teaching). Is it feasible in a work environment to upgrade ports without getting bogged down in a compile-a-thon, leaving one with a useless workstation. (My target machine will be an 8-core HP z600 (Xeon) which leads me to believe that I could do the upgrading in the background while I continue to work uninterrupted. I'd like to hear others experiences here.) Try to use something like nice portupgrade -a. Read man nice. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Newbie questions (updating, ports, etc.)
S4mmael wrote: 2009/12/3 Richard Mace mac...@telkomsa.net: 1.) Keeping installed ports/packages up to date. As far as I can tell from the docs, perhaps the most convenient method is to use something like: # portsnap fetch update # pkgdb -F # portupgrade --batch -aP (do I need an R here?) I don't see any reason to upgrade all installed ports on daily or weekly basis. In most cases you'll get nothing as the result of updating some port version 2.16.134 to new version 2.16.135 but lost time. There are probably as many approaches to this as there are users. I update very regularly. I find it worse to have a long list of updates required that to dedicate a little time every day or so to updating. And I use... cd /usr/ports make update portmaster -aD portmaster --clean-distfiles which should first try to find a package from the repositories and failing that will fall back to a port. What is the current wisdom here? Yes, it's right. Given the machine you are targeting initially packages will probably be fine. I use ports because I have a non-typical processor. Is it safe to use the --batch switch? As far as I understand, this will use the configuration defaults and not prompt the user whenever a port requires some user (options) configuration. Is this interpretation correct? If the package is in use, there will no prompt. While building a port, configuration in which this port was built last time is used. If there is no such configuration, then port builds with default options. I don't use --batch. I want to use the last configuration unless there are new options, then I want to be asked. I do use the -D option so that it does not ask me what to do with the dist files after each new update. Then I clean the distfiles at the end. Related to the above, are the default options that appear in the ncurses dialogues the same as those used in the building of packages? It's really intresting. 3.) Upgrading ports seems to take considerable time (at least with my experiments on a 5 year old Pentium IV). I am keen to adopt FreeBSD as my desktop for work (Physics Professor, Research and teaching). Is it feasible in a work environment to upgrade ports without getting bogged down in a compile-a-thon, leaving one with a useless workstation. (My target machine will be an 8-core HP z600 (Xeon) which leads me to believe that I could do the upgrading in the background while I continue to work uninterrupted. I'd like to hear others experiences here.) Try to use something like nice portupgrade -a. Read man nice. nice is probably the right answer here. Although given what you have said about your current machine I am not sure you will want/need to be bleeding edge. It may be best in that case to get it configured and leave it unless there is a security concern. When you get your new machine it will not be a factor so I would go with checking for fresh ports everyday or week. Also you will probably be able to take full advantage of the new target hardware by compiling from source. Colin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Newbie questions (updating, ports, etc.)
On Thu 03 Dec 2009 at 01:13:39 PST Richard Mace wrote: I recently installed FreeBSD 8.0-RELEASE on my home desktop and am considering making the switch from Debian GNU/Linux. I have a few questions which I am hoping the list can clarify for me. 1.) Keeping installed ports/packages up to date. As far as I can tell from the docs, perhaps the most convenient method is to use something like: # portsnap fetch update # pkgdb -F # portupgrade --batch -aP (do I need an R here?) which should first try to find a package from the repositories and failing that will fall back to a port. What is the current wisdom here? As others have said, there are almost as many approaches to this as there are users. The approach I've been using is: portsnap fetch update followed by portversion -vL= to see which of my installed ports needs updating. If there are many of them, I'll use portupgrade -ar to update them all in one fell swoop. But if there are just or two, or if I know that some of them (like OpenOffice or KDE) are going to take a long time to build, I'll specify the individual ports I want updated: portupgrade -r port1 port2 port3 ... I don't usually install packages, because I want to optimize the builds a little. On an i386-class machine, the compiler defaults to using the lowest common denominator instruction set, i.e., it doesn't use instructions introduced by later versions of the microprocessor. My machine is an old Pentium3, and I'm trying to squeeze as much performance out of it as possible. So I have the following in /etc/make.conf and always compile ports from source: CPUTYPE?=pentium3 Lately I've been looking at portmaster as a replacement for portupgrade, because it's so often recommended on this list. Is it safe to use the --batch switch? As far as I understand, this will use the configuration defaults and not prompt the user whenever a port requires some user (options) configuration. Is this interpretation correct? Otherwise, is there a way to get portupgrade to use the defaults non-interactively, to automate the process. I recently asked about this myself, while planning to do a complete reinstall of all my ports following an upgrade to FreeBSD 8.0. The --batch switch is quite safe, and your understanding is correct. But you might find that your needs are better met by doing a preconfigure, that is, by answering the config dialogs for all of the updating ports before proceeding to the actual build of any of them. portmaster does this by default, and portupgrade has the --config switch. Related to the above, are the default options that appear in the ncurses dialogues the same as those used in the building of packages? I would assume so, yes. 2.) Evolution of ports (and packages) versus evolution of the base system. Reading the docs makes it clear that FreeBSD maintains is a rigorous distinction between the base system and add-on packages (ports). This is very appealing. However, as far as I can tell so far, even though my base system is 8.0 -RELEASE (and remains fixed between releases?), the ports continuously evolve (are updated). Is my understanding correct that by tracking a RELEASE system I can have bleeding edge (or close) versions of ports? Or, do I need to track STABLE of CURRENT for that? The correct answer is Any of the above. The base system and the ports system are independent of each other, and evolve separately. This means you can combine any version of the portstree with any version of the base system -- within reason, of course. The base system guarantees that its APIs will not be changed except when its major version changes; this is why, for example, all ports need to be recompiled when going from FreeBSD 7.x to 8.0. Otherwise, changes in the base system do no affect the ports, and you can track RELEASE, STABLE or CURRENT as you prefer, while updating ports as ofen as you like. 3.) Upgrading ports seems to take considerable time (at least with my experiments on a 5 year old Pentium IV). I am keen to adopt FreeBSD as my desktop for work (Physics Professor, Research and teaching). Is it feasible in a work environment to upgrade ports without getting bogged down in a compile-a-thon, leaving one with a useless workstation. (My target machine will be an 8-core HP z600 (Xeon) which leads me to believe that I could do the upgrading in the background while I continue to work uninterrupted. I'd like to hear others experiences here.) As you can see above, my machine is an even older Pentium3. ;-) Compiling is what it is, and unless you're willing to accept the shortcomings of packages, is a price that has to be paid. I've found that the best way to avoid a compile-a-thon is to spread the work out, by updating my ports on a daily basis. (As someone else pointed out, you do NOT need to recompile each and every port every time! Just the ones that are out of date.) But I should also point out that FreeBSD, like most Unix
Re: Newbie questions (updating, ports, etc.)
On Thu 03 Dec 2009 at 07:32:33 PST Warren Block wrote: As far as batch or even -a, I update the ports tree often and prefer to manually upgrade ports as needed, usually with portupgrade -r. A lot of people seem to like -R; maybe I have the dependencies backwards. Since this is a newbie thread, perhaps we should clarify this point. portupgrade -r portA upgrades portA and any other installed ports which depend on it. For example, if portA installs a shared library that portB uses, both portA and portB will be upgrade by this command. portupgrade -R portA upgrades portA and any other ports on which portA depends. For example, if portA uses gtk+, this command will compile both portA and gtk+, along with all the other libraries and whatnot that underpin gtk+. In other words, it rebuilds portA from the ground up -- starting from the absolute bare ground. If the changes in portA did not introduce any binary incompatibilities, portupgrade -r is probably unnecessary. The problem is knowing ahead of time whether there are any such incompatibilities. So many people habitually use -r as a precautionary measure. As far as I can see, the only reason to use -R is when you're having some problem with portA and you suspect that the underlying libraries and whatnot have gotten out of sync. Rebuilding the whole chain from scratch is sometimes the only way to restore sanity to the system. (Or maybe it's just that you have nothing else to do on a rainy weekend.) -- Charlie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Newbie questions about updating
Hi, let me give some very basic answers. cothrige wrote: ports system is completely separate from the OS itself, and that these Applications have nothing to do with the operating system. In theory at least. Practically it is more limited. can be upgraded or updated separately. From what I can see this seems Yes, as long as the port tree still supports the OS. A strange example: FreeBSD 1.0 is not supported anymore with the current port tree. to most often involve CVSup, and I have been operating under the Yes. assumption that one must run two cvsup operations with two separate supfiles to update both the core OS and the ports. Am I understanding this correctly? It seems for me to be the best choice. Assuming I am, my main confusion concerns just how these two systems actually interact and relate to each other, and whether there are any They do not interact. The operating system provides the base for the applications. As long as base and application fit together, it all simply works. requirements connecting updating each of them together? For instance, There is no requirement. Upgrading the operating system should be done if there are bug fixes provides or if you want to switch to a newer version. I have downloaded the FreeBSD 6.2 install discs and have finished the Just stick with 6.2 for the moment. basic installation and setup. Now at some point if I wish to update the ports does that mean I have to update the OS to a particular No problem. level? If I don't want to run stable and use tag=RELENG_6_2 will I be required to keep the ports as they have installed from the disc? Is there any connection between how current the ports are and how current the OS is? Wait, you do not install ports from the disc, you install packages from the disc. This is a small difference. Ports are source based, packages are binaries. One of the things which caused me to wonder about this was that some time back I tried FreeBSD out for a while and ran into some oddities concerning the ports system. When I first finished setting things up I could install packages using pkg_add -r, but noticed that after updating the ports I could no longer do that. That struck me as odd, Updating the ports tree means actually switching to ports but you still can use packages via portupgrade. and because of it I always had a suspicion that I had broken the system with my out of whack updates (I did not move up to stable at that time) but I just never could really find out if that were so. Never forget, the ports tree is a live object. It can happen that you upgrade now and find a ruined system, then upgrade a minute later and the system is fine again. One last newb question is concerning cvsup itself. In reference to ports is there a difference, in the end, between this and portsnap? There should be no difference at the final end. Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie questions about updating
On Friday 07 September 2007, Lars Eighner wrote: 2. Install cvsup from a package or the ports, but do not install any other ports. Isn't csup, a functional and faster equivalent to cvsup part of the base system now? -- Dave ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie questions about updating
Predrag Punosevac wrote: I am not sure. I know that portsnap is the part of base package. dgmm wrote: On Friday 07 September 2007, Lars Eighner wrote: 2. Install cvsup from a package or the ports, but do not install any other ports. Isn't csup, a functional and faster equivalent to cvsup part of the base system now? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] It is actually. No need whatsoever to install cvsup now, just use csup ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie questions about updating
Lars Eighner writes: assumption that one must run two cvsup operations with two separate supfiles to update both the core OS and the ports. Am I understanding this correctly? [deletia] Many people do it it two operations because they really are two different things. Another reason is to (theoretically) limit possible damage is things Go Horribly Wrong and make the post-mortem easier. I have a cron job that updates the base OS, the docs (a separate entity), and the ports every night at midnight. Once it connects, the update take less than five minutes. (Except for rare occasions.) Aside from bugs introduced by my attempts to improve the script, this has run without porblem for years. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie questions about updating
Hi, I can't answer all your questions, but will take a shot at a couple. You should check out the handbook at: http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/ports.html and http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/porters-handbook/ For more complete information. On Fri, Sep 07, 2007 at 12:35:39AM -0500, cothrige wrote: I know this is going to be a very dumb question, but I just can't seem to get my mind around exactly what is involved and what I should do regarding this issue. I understand from reading the handbook that the ports system is completely separate from the OS itself, and that these can be upgraded or updated separately. From what I can see this seems to most often involve CVSup, and I have been operating under the assumption that one must run two cvsup operations with two separate supfiles to update both the core OS and the ports. Am I understanding this correctly? No, not quite. They are two separate things, but can be run from the same supfile in the same csup run.By the way, cvsup has been replaced by csup which is now in the base system from about 6.2 on. or maybe it was 6.1. Here is the relevant part of my supfile: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- # *default host=cvsup.FreeBSD.org *default base=/var/db *default prefix=/usr *default tag=RELENG_6_2 *default release=cvs *default delete use-rel-suffix *default compress ## Main Source Tree. # The easiest way to get the main source tree is to use the src-all # mega-collection. It includes all of the individual src-* collections. src-all ports-all tag=. doc-all tag=. -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- This gets 6.2 OS and the latest ports and docs. You could put tag=RELENG_6 and get the latest OS updates for 6.xx (but not the latest over all) included. Assuming I am, my main confusion concerns just how these two systems actually interact and relate to each other, and whether there are any requirements connecting updating each of them together? For instance, I have downloaded the FreeBSD 6.2 install discs and have finished the basic installation and setup. Now at some point if I wish to update the ports does that mean I have to update the OS to a particular level? If I don't want to run stable and use tag=RELENG_6_2 will I be required to keep the ports as they have installed from the disc? Is there any connection between how current the ports are and how current the OS is? They do interact and there can be problems. The OS has versions. The ports tree does not. It is just the latest that has been supplied by the port maintainer. As the OS gets older, it becomes more likely that a giver port is too new for it and may not build or run on it. It can happen the other way around too - the OS is too new for the present condition of the port. But, there is an attempt to keep this from happening. When the head of an OS branch is getting to the point of making a new RELEASE, then a freeze is put on code in the OS thus making a temporary non-moving target to build all the system plus the ports against. It is generally up to the port maintainers to make sure their port[s] can build to that frozen image. When all seems to build, run and test together then a RELEASE is made. Then the branch is unfrozen and changes start coming in again - both to the base OS and to the ports. In general, the OS versions are managed so that anything that will run in one version of a main branch will run in another. eg, if it will run in 6.1, it should run in 6.2 and 6.3. But it may well not work in 7.xx because os some non-compatible change introduced in the new major branch level. That is the main part of the decision to create a new main branch and what usually determines whether some change will be introduced in a lower branch or reserved for a higher branch. But, again, the ports are not limited to a version so in some cases, especially when signiicant time has elapsed, a port may not build or run on some version. You may need to go back and get a legacy version of the port to make it run, or note the changes and tinker. In practice, though, it usually works well to keep your OS and ports up to date. Developers and maintainers try to make things work and to keep them compatible as far as possible. jerry One of the things which caused me to wonder about this was that some time back I tried FreeBSD out for a while and ran into some oddities concerning the ports system. When I first finished setting things up I could install packages using pkg_add -r, but noticed that after updating the ports I could no longer do that. That struck me as odd, and because of it I always had a suspicion that I had broken the system with my out of whack updates (I did not move up to stable at that time) but I just never could really find out if that were so. One
Re: Newbie questions about updating
On 9/7/07, Lars Eighner [EMAIL PROTECTED] wrote: On Fri, 7 Sep 2007, cothrige wrote: assumption that one must run two cvsup operations with two separate supfiles to update both the core OS and the ports. Am I understanding this correctly? No. It is not must. You can update your source and your ports tree with one supfile. You can add the line [snip] Many people do it it two operations because they really are two different things. Okay, that seems to confirm my basic understanding then. I must readily admit that the overall application is a bit above me at this point (it is certainly more complicated than the aptitude update and aptitude upgrade that I am used to.). At least though I appear to be on the right track about how the two are different entities in some manner. There is no necessary, hard and fast, connection between the two. If your ports tree gets very, very stale, it will largely cease to work because many (some) of the source files will disappear or their dependencies will disappear or change. Okay, this makes sense to me. General, upgrading the OS is a good idea about six months after the second release of a major version number (i.e. when 7.2 or 7.3 is a release and is about six-months old). So, you would say that there is no pressing need to update the OS yet? If I don't want to run stable and use tag=RELENG_6_2 will I be required to keep the ports as they have installed from the disc? No. In fact you shouldn't. (But as mentioned above, never use any tag with ports except ..) Of course there are two different things here that you might be confusing. The ports tree, which is a skeleton for building applications from scratch, and packages, which are pre-built binaries for applications. Yes, I think I am probably confusing them at least to a degree. Probably that is because it just seems logical that the packages would match what is in the ports tree and it is hard for me to imagine it may not be the case. If my ports tree has a particular version of an app in it, say mplayer-1.0.7 wouldn't the package available be the same? I also wonder about this because portupgrade, which is obviously for ports, does have the option for using packages. It does make me wonder, how does pkg_add or portupgrade know which versions of which packages to retrieve, as opposed to using the port to know which version of the port to install? Does that make sense? I feel like I am being very awkward in my wording, and I apologize for not being more clear in it. Here's the best way to install 6.2 starting with the CD release (assuming you have internet connectivity which I guess you do since you mailed to this list). 1. Install 6.2 including source, but do not install Xorg. [snip] 6. Install Xorg (and other applications you may want) from the ports tree. Very good to know. Unfortunately, I did not use this way to get started, but next time I will certainly follow your suggestions as even now I can see how they would help. Installing X from the disc was not the best choice, but being used to Linux installers it seemed logical at the time. As did installing the ports tree. [snip] The main object is to keep the ports in synch with other ports. There are just a few ports that do things (like build loadable kernel modules) which just won't work if they are too out of synch with the operating system, but these are few and far between. I think I understand. So, I can update the ports x number of times per a given period of time, but I don't have to update the OS as often. They are not so intimately connected that I have to keep them in sync somehow with one another, and therefore updating them at different rates will not cause breakage, am I right? When I first finished setting things up I could install packages using pkg_add -r, but noticed that after updating the ports I could no longer do that More than likely the packages were broken. Often the available packages are way out of date or do not exist (because of licensing restrictions or no one got around to building them). Packages depend to much greater extent on the OS release. Very interesting. But, could that really explain a 100% failure rate? In my previous experience with FreeBSD I became convinced that I had broken things badly since after updating I was unable to use even one package. I mean, no big deal in itself, and if the system had no package options I would have no real complaint. But, it just seemed broken as it was, and so I was convinced that I had done something wrong. Portsnap is a different system from cvsup. They should get approximately the same tree (not exactly the same because the ports tree changes so rapidly). Portsnap is usually run automatically (as a cron job) every few days, or oftener if you are really complusive. It is said to save bandwidth if used this way, so if you are administering a large system, it probably pays off. If this
Re: Newbie questions about updating
That is the correct but I prefer to use portsnap for ports and keep cvsup just for core OS! Robert Huff wrote: Lars Eighner writes: assumption that one must run two cvsup operations with two separate supfiles to update both the core OS and the ports. Am I understanding this correctly? [deletia] Many people do it it two operations because they really are two different things. Another reason is to (theoretically) limit possible damage is things Go Horribly Wrong and make the post-mortem easier. I have a cron job that updates the base OS, the docs (a separate entity), and the ports every night at midnight. Once it connects, the update take less than five minutes. (Except for rare occasions.) Aside from bugs introduced by my attempts to improve the script, this has run without porblem for years. Robert Huff ___ 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: Newbie questions about updating
cothrige [EMAIL PROTECTED] writes: Sorry. What I really had in mind was the ports tree itself, which I had an option during install to add. BTW, I answered yes to this and so had that which was on the 6.2 install disc. Based on the other responses, it is looking like perhaps that is not the best method, and maybe I should have skipped that and then added the ports after the install using cvsup or such. This is certainly a good thing to know for the future, though as of right now I am dealing with the disc install method. That works fine, but to save yourself a bit of annoyance later, see the cvsup FAQ for how to adopt that ports tree before trying to update it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie questions about updating
On Fri, 7 Sep 2007 12:16:32 -0400 Jerry McAllister [EMAIL PROTECTED] wrote: In general, the OS versions are managed so that anything that will run in one version of a main branch will run in another. eg, if it will run in 6.1, it should run in 6.2 and 6.3. But it may well not work in 7.xx because os some non-compatible change introduced in the new major branch level. Generally packages built on an older version of the OS will run on a newer version. When one upgrades to 7x there will be a compat6x port to supply the missing libraries. It's normally not essential to upgrade ports after an OS upgrade, but it is advisable on a major upgrade. Problems are more likely to occur the other way around, there are currently 6-stable packages the wont run on 6.2 because new libraries have been ported into 6-stable. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie questions about updating
I am not sure. I know that portsnap is the part of base package. dgmm wrote: On Friday 07 September 2007, Lars Eighner wrote: 2. Install cvsup from a package or the ports, but do not install any other ports. Isn't csup, a functional and faster equivalent to cvsup part of the base system now? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie questions about updating
On Fri, 7 Sep 2007, cothrige wrote: assumption that one must run two cvsup operations with two separate supfiles to update both the core OS and the ports. Am I understanding this correctly? No. It is not must. You can update your source and your ports tree with one supfile. You can add the line ports-all tag=. to either the standard or the stable supfile. The tag=. part is vitally important, because otherwise the tag from the system update will fall through (being right now either RELENG_6 (for stable) or RELENG_6_2 (for standard) and your whole ports tree will be deleted (because ports do not have a tag and so there are not any that match either of the other tags). If you do this once, you will forever be prejudiced against doing it in one operation. Many people do it it two operations because they really are two different things. Assuming I am, my main confusion concerns just how these two systems actually interact and relate to each other, and whether there are any requirements connecting updating each of them together? There is no necessary, hard and fast, connection between the two. If your ports tree gets very, very stale, it will largely cease to work because many (some) of the source files will disappear or their dependencies will disappear or change. Many of the applications in the ports were not written to work specifically on FreeBSD by FreeBSD developers, but were written variously to work on any generally sort-of-Unix-like system, any system with a C++ compiler and so forth. Theoretically ports in a very old tree should build (FreeBSD keeps many old distribution files as a last resort), but as a practical matter, many won't. Occasionally there is a change in the operating system that breaks some old ports, often because the person who wrote the port was sloppy and took things for granted, but those things changed. For instance, I have downloaded the FreeBSD 6.2 install discs and have finished the basic installation and setup. Now at some point if I wish to update the ports does that mean I have to update the OS to a particular level? No. There certainly is no fixed point at which ports will become useless. But someday 6,2 will no longer be supported (like years from now). 6.2 will still run on the machine you have got, and the ports you have installed will still run on it, but much of the then current port tree will deal with hardware you don't have and so forth. When the Donovan's Brain Interface is invented 6.2 won't support it and you will want it because it is easier to think than to find your mouse (although I can think of an operating system that is designed for people who have it the other way around). General, upgrading the OS is a good idea about six months after the second release of a major version number (i.e. when 7.2 or 7.3 is a release and is about six-months old). If I don't want to run stable and use tag=RELENG_6_2 will I be required to keep the ports as they have installed from the disc? No. In fact you shouldn't. (But as mentioned above, never use any tag with ports except ..) Of course there are two different things here that you might be confusing. The ports tree, which is a skeleton for building applications from scratch, and packages, which are pre-built binaries for applications. Here's the best way to install 6.2 starting with the CD release (assuming you have internet connectivity which I guess you do since you mailed to this list). 1. Install 6.2 including source, but do not install Xorg. 2. Install cvsup from a package or the ports, but do not install any other ports. 3. Use cvsup to update the release source (use the standard supfile). 4. Build and install world and the kernel according to instructions at the end of the UPDATING file in /usr/src 5. Cvsup the ports tree using the ports-supfile. 6. Install Xorg (and other applications you may want) from the ports tree. Well, 5a is install ports management software from the ports-mgmt section of the ports tree. I use portupgrade because it is the way I have always done things, but I hear some of the others may be better. You can use the -N switch with it when you are installing fresh ports instead of just upgrading. 6.2 is now fairly static (but it isn't STABLE) so you will only rarely see anything happening when you cvsup with the standard supfile. If anything does happen it is usually error-correction/diasater-avoidance related, so you probably should rebuild the system (or at least read the UPDATING file to see if the changes really affect something that is important to you). The ports tree, on the other hand, will usually have dozens of updates every day. After the usually flurry of basic applications you install at first, you probably should update the ports tree, read the ports UPDATING file and upgrade all your ports (like portupgrade -a) before you install any major application. The main object is to keep the ports in synch with other ports. There
Re: Newbie questions about updating
On 9/7/07, Jerry McAllister [EMAIL PROTECTED] wrote: On Fri, Sep 07, 2007 at 10:53:09AM -0500, cothrige wrote: Sorry. What I really had in mind was the ports tree itself, which I had an option during install to add. BTW, I answered yes to this and so had that which was on the 6.2 install disc. Based on the other responses, it is looking like perhaps that is not the best method, and maybe I should have skipped that and then added the ports after the install using cvsup or such. This is certainly a good thing to know for the future, though as of right now I am dealing with the disc install method. No. You were right to choose yes. That just installs the ports tree skeleton. It does not install any actual ports. Then when you do a csup tag=. for the ports tree, then it updates that tree. But you would still have to update the ports from the tree that you have chosen to install. What exactly is the best method for the new install when it comes to ports? I should say yes to installing the ports tree, but then how should I go forward at that point? For instance, should I immediately run csup when booting into the new system before actually installing anything from ports? Will that speed things up in the end, or make for greater stability? The ports tree from one version of the OS to the next is not particularly different. It is just instructions on how to get the source and build the port (including dependant ports). It gets a little out of date now and then as the list of files that need to be downloaded or build procedured change, so it need a csup update now and then. But what that csup does is update the skeleton, not the actual ports. That is a subsequent step. Cool, that makes sense. I suppose right now it is a matter of figuring out just getting used to how to handle the system and know that I am carrying out the correct steps, or at least the most reliable steps, in the most beneficial order. Thanks, Patrick ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie questions about updating
On Fri, Sep 07, 2007 at 10:53:09AM -0500, cothrige wrote: On 9/7/07, Erich Dollansky [EMAIL PROTECTED] wrote: Hi, Howdy, and thanks for the help. [snip] I have downloaded the FreeBSD 6.2 install discs and have finished the Just stick with 6.2 for the moment. Wait, you do not install ports from the disc, you install packages from the disc. This is a small difference. Ports are source based, packages are binaries. Sorry. What I really had in mind was the ports tree itself, which I had an option during install to add. BTW, I answered yes to this and so had that which was on the 6.2 install disc. Based on the other responses, it is looking like perhaps that is not the best method, and maybe I should have skipped that and then added the ports after the install using cvsup or such. This is certainly a good thing to know for the future, though as of right now I am dealing with the disc install method. No. You were right to choose yes. That just installs the ports tree skeleton. It does not install any actual ports. Then when you do a csup tag=. for the ports tree, then it updates that tree. But you would still have to update the ports from the tree that you have chosen to install. The ports tree from one version of the OS to the next is not particularly different. It is just instructions on how to get the source and build the port (including dependant ports). It gets a little out of date now and then as the list of files that need to be downloaded or build procedured change, so it need a csup update now and then. But what that csup does is update the skeleton, not the actual ports. That is a subsequent step. One of the things which caused me to wonder about this was that some time back I tried FreeBSD out for a while and ran into some oddities concerning the ports system. When I first finished setting things up I could install packages using pkg_add -r, but noticed that after updating the ports I could no longer do that. That struck me as odd, Updating the ports tree means actually switching to ports but you still can use packages via portupgrade. What has happened to me before is that after the fresh install if I typed pkg_add -r foo it would say something like fetching http://...freebsd-6.[x]/foo.1.0.0.tbz...; and then install it. But, after I would update the ports if I typed the same command, pkg_add -r foo, it would fail saying something like fetching http://...freebsd-6.[x]/foo.1.0.1.tbz...; and then say something about no such package. At the time it was happening I had looked at the address being used and of course in the one for freebsd-6.whatever (or whichever directory my OS was trying to fetch from) there was only the foo.1.0.0 file and not the new one. The ports upgrade seemed to make my system stop searching for foo.1.0.0 and begin looking for 1.0.1, but it did not change where the pkg_add program looked and so it would always fail. Most of the time this would be no big deal, and I don't run KDE, Gnome or such, but it is more time consuming (especially on some of my old stuff like this laptop) and more importantly it just always made me think it was broken. It really just doesn't seem like the intended behaviour with it looking for nonexistent packages. When things seem to misbehave like that I always have a sneaking suspicion that not too long in the future it will come crashing down as I have some fundamental setting flawed and with every install or change I am compounding the problem. Never forget, the ports tree is a live object. It can happen that you upgrade now and find a ruined system, then upgrade a minute later and the system is fine again. Yes, I can see how that would be the case, and in a broken port I think that likely this may be so. Also, if the package system does not operate after updating ports then I could also rest easy that things are operating as they should. However, my reading of the handbook, and other documents, implies that one should in theory be able to use packages even with an updated ports tree, as portupgrade -P would seem to suggest. But, in the past that would always fail as the package does not exist in the place being searched and then a port would be built. Again, building is usually fine, and I may even prefer it most of the time, but since portupgrade seems to exist to work with updated ports trees, and it has options to use packages, my experiences with these in the past have given me the distinct impression that I have been doing something wrong. One last newb question is concerning cvsup itself. In reference to ports is there a difference, in the end, between this and portsnap? There should be no difference at the final end. Good to know. Erich Thanks Erich. Patrick ___ freebsd-questions@freebsd.org mailing list
Re: Newbie questions about updating
On 9/7/07, Erich Dollansky [EMAIL PROTECTED] wrote: Hi, Howdy, and thanks for the help. [snip] I have downloaded the FreeBSD 6.2 install discs and have finished the Just stick with 6.2 for the moment. I had thought this might be the best method, and so figured I would for some time anyway. I am also running FreeBSD on an ancient laptop just for a learning experience, and because so far FreeBSD has been the only system which seems able to run on it :-). For this reason I am tending to keep things fairly small and am trying not to make huge updates unless I have to. level? If I don't want to run stable and use tag=RELENG_6_2 will I be required to keep the ports as they have installed from the disc? Is there any connection between how current the ports are and how current the OS is? Wait, you do not install ports from the disc, you install packages from the disc. This is a small difference. Ports are source based, packages are binaries. Sorry. What I really had in mind was the ports tree itself, which I had an option during install to add. BTW, I answered yes to this and so had that which was on the 6.2 install disc. Based on the other responses, it is looking like perhaps that is not the best method, and maybe I should have skipped that and then added the ports after the install using cvsup or such. This is certainly a good thing to know for the future, though as of right now I am dealing with the disc install method. One of the things which caused me to wonder about this was that some time back I tried FreeBSD out for a while and ran into some oddities concerning the ports system. When I first finished setting things up I could install packages using pkg_add -r, but noticed that after updating the ports I could no longer do that. That struck me as odd, Updating the ports tree means actually switching to ports but you still can use packages via portupgrade. What has happened to me before is that after the fresh install if I typed pkg_add -r foo it would say something like fetching http://...freebsd-6.[x]/foo.1.0.0.tbz...; and then install it. But, after I would update the ports if I typed the same command, pkg_add -r foo, it would fail saying something like fetching http://...freebsd-6.[x]/foo.1.0.1.tbz...; and then say something about no such package. At the time it was happening I had looked at the address being used and of course in the one for freebsd-6.whatever (or whichever directory my OS was trying to fetch from) there was only the foo.1.0.0 file and not the new one. The ports upgrade seemed to make my system stop searching for foo.1.0.0 and begin looking for 1.0.1, but it did not change where the pkg_add program looked and so it would always fail. Most of the time this would be no big deal, and I don't run KDE, Gnome or such, but it is more time consuming (especially on some of my old stuff like this laptop) and more importantly it just always made me think it was broken. It really just doesn't seem like the intended behaviour with it looking for nonexistent packages. When things seem to misbehave like that I always have a sneaking suspicion that not too long in the future it will come crashing down as I have some fundamental setting flawed and with every install or change I am compounding the problem. Never forget, the ports tree is a live object. It can happen that you upgrade now and find a ruined system, then upgrade a minute later and the system is fine again. Yes, I can see how that would be the case, and in a broken port I think that likely this may be so. Also, if the package system does not operate after updating ports then I could also rest easy that things are operating as they should. However, my reading of the handbook, and other documents, implies that one should in theory be able to use packages even with an updated ports tree, as portupgrade -P would seem to suggest. But, in the past that would always fail as the package does not exist in the place being searched and then a port would be built. Again, building is usually fine, and I may even prefer it most of the time, but since portupgrade seems to exist to work with updated ports trees, and it has options to use packages, my experiences with these in the past have given me the distinct impression that I have been doing something wrong. One last newb question is concerning cvsup itself. In reference to ports is there a difference, in the end, between this and portsnap? There should be no difference at the final end. Good to know. Erich Thanks Erich. Patrick ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie questions about updating
On Fri, Sep 07, 2007 at 12:26:40PM -0500, cothrige wrote: On 9/7/07, Jerry McAllister [EMAIL PROTECTED] wrote: On Fri, Sep 07, 2007 at 10:53:09AM -0500, cothrige wrote: Sorry. What I really had in mind was the ports tree itself, which I had an option during install to add. BTW, I answered yes to this and so had that which was on the 6.2 install disc. Based on the other responses, it is looking like perhaps that is not the best method, and maybe I should have skipped that and then added the ports after the install using cvsup or such. This is certainly a good thing to know for the future, though as of right now I am dealing with the disc install method. No. You were right to choose yes. That just installs the ports tree skeleton. It does not install any actual ports. Then when you do a csup tag=. for the ports tree, then it updates that tree. But you would still have to update the ports from the tree that you have chosen to install. What exactly is the best method for the new install when it comes to ports? I should say yes to installing the ports tree, but then how should I go forward at that point? For instance, should I immediately run csup when booting into the new system before actually installing anything from ports? Will that speed things up in the end, or make for greater stability? That is what I do. Actually, I csup the OS because it may have updates on it that are needed - security fixes mostly and also ports and even doc right then before doing any other installing. Some people don't even install Xorg until doing the csup. I haven't been quite that hard core, but it isn't a bad idea. The ports tree from one version of the OS to the next is not particularly different. It is just instructions on how to get the source and build the port (including dependant ports). It gets a little out of date now and then as the list of files that need to be downloaded or build procedured change, so it need a csup update now and then. But what that csup does is update the skeleton, not the actual ports. That is a subsequent step. Cool, that makes sense. I suppose right now it is a matter of figuring out just getting used to how to handle the system and know that I am carrying out the correct steps, or at least the most reliable steps, in the most beneficial order. Yup. jerry Thanks, Patrick ___ 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: Newbie questions
On Wednesday 23 August 2006 12:37 am, E. Gad wrote: Hello First I was directed to post the here because I posted to the stable mailing list before re-reading what it's purpose is- I apologise-. I am playing with freebsd 6 on a testing box. I Upgraded l from 6.0 to 6.1 because it looked like popular opinion is that it's got a number of improvements After a few false starts and finally figuring what I did wrong it went basicly ok. I went to use sysinstall to install a few usefull looking items however I got a error message: Release 6.1-p3 not found on server What is puzling is if I do essentially the samething: run pkg_add -f from the command line I seem to get some of the packages I wanted-to install. Is this normal? or did I do something wrong? I am not entirely sure how fix this and any assistance is apreciated. (The free-bsd etiquite note statements says I should mention what I have done so far) I have started by using google to see if anyone else has this problem. I haven't found the problem on bulitin boards or the like (not yet anyway-i'll look again in the morning) -thanks - Do you Yahoo!? Get on board. You're invited to try the new Yahoo! Mail. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Go to the the Options menu in sysinstall and change the entry for 6.1-RELEASE-P3 to 6.1-RELEASE FreeBSD tries to exactly match what you have as a system and the p3 means patch level #3, You will have to do this each time you try to use sysinstall to add binaries. You can also use the ports system which is more up to date typically than the binaries. However, installing via the ports means compiling from source which works but takes time. One port that you may want to install is: /usr/ports/sysutils/desktopbsd-tools go to it and type make clean make make install make clean This is a system to help you find programs and install them from source or binaries. It allows you to have the most up to date programs available. Checkout www.desktopbsd.net for their version of BSD or if you want a distribution that is very user friendly try www.PCBSD.org. Both are excellent. DesktopBSD is based on FreeBSD 5.5 while PCBSD is based on FreeBSD 6.1. If you want to stick with FreeBSD, you might want to buy FreeBSD 6 Unleashed by Brian Tiemann and Michael Urban the 2006 edition ISBN 0-672-32875-5 It is the most complete book out there. Have fun Ralph Ellis ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie questions
Hello, Welcome to the world of FreeBSD. First of all, why are you trying to install binaries? I would say it is wiser to use the port system yourself. However remember to cvsup your ports tree before you start using it to get the required software. Refer to the handbook for understanding how ports work. Thanks and Best Regards Subhro On 8/23/06, E. Gad [EMAIL PROTECTED] wrote: Hello First I was directed to post the here because I posted to the stable mailing list before re-reading what it's purpose is- I apologise-. I am playing with freebsd 6 on a testing box. I Upgraded l from 6.0 to 6.1 because it looked like popular opinion is that it's got a number of improvements After a few false starts and finally figuring what I did wrong it went basicly ok. I went to use sysinstall to install a few usefull looking items however I got a error message: Release 6.1-p3 not found on server What is puzling is if I do essentially the samething: run pkg_add -f from the command line I seem to get some of the packages I wanted-to install. Is this normal? or did I do something wrong? I am not entirely sure how fix this and any assistance is apreciated. (The free-bsd etiquite note statements says I should mention what I have done so far) I have started by using google to see if anyone else has this problem. I haven't found the problem on bulitin boards or the like (not yet anyway-i'll look again in the morning) -thanks - Do you Yahoo!? Get on board. You're invited to try the new Yahoo! Mail. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Subhro Kar Security Engineer iViZ Techno Solutions Pvt. Ltd. Dhanshree Bldg, 1st Floor Plot XI-16, Sector V Salt Lake City 700091 India ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie questions
Subhro wrote: yourself. However remember to cvsup your ports tree before you start using it to get the required software. Refer to the handbook for understanding how ports work. For most people portsnap would be a better way of updating one's ports tree. Firstly, it's in the base system and thus doesn't require any third party software. Secondly, most newbies find it easier to use. Svein Halvor signature.asc Description: OpenPGP digital signature
Re: Newbie questions: 2 of a few.
On 3/8/06, Bruce M. Axtens [EMAIL PROTECTED] wrote: I've been trying to get FreeBSD 5.4 going on a friend's Celeron and have been doing okay ... until now. Question 1: How do I get automounting of cdroms working? Is it possible in KDE or GNOME, when you put in a cd that the icon just appears on the desktop (like it does in another OS I could name)? Question 2: How do I get FreeBSD to automount a USB drive? I have a Kingston DataTraveller 128MB usb drive. The Auto Mounter Daemon will do the job.. Start here: http://www.freebsd.org/cgi/man.cgi?query=amd Then go on here: http://www.nber.org/amd.html Thanks in advance. Hope this helps. Regards, Bruce. -- Pietro Cerutti [EMAIL PROTECTED] Non lasciar calpestare i TUOI diritti! Don't let 'em take YOUR rights! NO al Trusted Computing! Say NO to Trusted Computing! www.no1984.org www.againsttcpa.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie Questions
On Fri, 2005-10-07 at 20:00 -0500, Kevin Kinsey wrote: makisupa wrote: Been using Linux awhile...recently migrated a laptop to FreeBSD. Its a bit old and BSD runs nicely on the deprecated hardware. I am using 6.0-BETA 5 despite warning to the contrary because my atheros based wifi card works well -- i had all kinds of trouble in 5.4. Running gnome 2.12. My newbie questions: 1. I am pretty sure that FAM is not running. The newest version of the package is installed. I followed the directions from the gnome FAQ and the pkg_message. 'killall -HUP inetd' gives me 'no matching processes were found.' What does `ps -aux | grep inetd` tell you? Inetd doesn't run unless enabled in /etc/rc.conf... and IIRC (I've switched to xfce4 from Gnome2), fam runs from inetd, so that could be a root (no pun intended) cause of these issues, perhaps? IANAE OK...after a reading up a bit more i did a 'make deinstall' and 'make reinstall' of the /devel/fam port. Before this the output of 'ps -aux | grep inetd' as user was: makisupa 3330 0.0 0.1 512 392 p0 R+8:45PM 0:00.00 grep inetd There was no output as root. Now there is no output as user and as root the output is: root 1895 0.0 0.0 348 228 p0 L+1:04PM 0:00.00 grep inetd Still getting FAM errors and same weirdness...starting to drive me nuts! Thanks everyone for your help... mak ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie Questions
makisupa wrote: Been using Linux awhile...recently migrated a laptop to FreeBSD. Its a bit old and BSD runs nicely on the deprecated hardware. I am using 6.0-BETA 5 despite warning to the contrary because my atheros based wifi card works well -- i had all kinds of trouble in 5.4. Running gnome 2.12. My newbie questions: 1. I am pretty sure that FAM is not running. The newest version of the package is installed. I followed the directions from the gnome FAQ and the pkg_message. 'killall -HUP inetd' gives me 'no matching processes were found.' What does `ps -aux | grep inetd` tell you? Inetd doesn't run unless enabled in /etc/rc.conf... and IIRC (I've switched to xfce4 from Gnome2), fam runs from inetd, so that could be a root (no pun intended) cause of these issues, perhaps? IANAE When i launch something like gnome-menu-editor i get a 'failed to connect to the FAM server' message in the terminal. Similiarly, whenever i gedit a file su'd as root i get a 'gnomeUI-WARNING **: While connecting to the session manage: authentication rejected, reason: None of the authentication protocols specified are supported and host based authentication failed.' Please help...its very annoying as the gnome does not update worth a damn as you move, add, and delete files. I realize the instructions were for gnome 2.10 and i probably missed something obvious. 2. Is there a way to turn DMA on for a certain device or devices and not every ATAPI drive? I got permissions and whatnot straight to allow a users to mount CD/DVD drives -- my CD drive does not work correctly in DMA mode. BUT, i will need DMA in order to play DVDs correctly (see below). I passed the hw.ata.atapi_dma=1 option in my /boot/loader.conf file. is there a option i can pass that only enables DMA on my acd1 (dvd) and ad0 (hd) but NOT acd0 (CD)? Hrm, I'm not much good from here out. I note that there are two sysctl's hw.ata.ata.dma and hw.ata.atapi.dma, dunno if that'd help. Maybe see ata(4) for a little more detail. Being as the DVD and CD are on the same bus, I'd say it's not too likely, but, again, IANAE 3. DVD playback. Just trying to use the totem default in my gnome install. I get a 'failed to retrieve capabilities of device /dev/acd1: inappropriate ioctl for device'. I've googled the hell out of this and came up with little helpful info. Any ideas? Thanks for your help. I think i'm doing fairly well for only running BSD for a couple of days...but if i could get these minor things straightened out i'd be set (and have a rockin' little laptop). FreeBSD definately seems more intuitive than most of the linux distros i've used... Thanks, Mak. Best o' luck, Kevin Kinsey ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie Questions
Added inetd_enable=YES to rc.conf and made sure the rest of the steps from the pkg-message where followed. 'killall -HUP inetd' does not give an error. the output of 'ps -aux | grep inetd' (as user, no output as root): makisupa 3330 0.0 0.1 512 392 p0 R+8:45PM 0:00.00 grep inetd So i missed something real obvious, inetd not running, but its still not working...same behavior as before (after a reboot). Thanks for your help (it is truly appreciated), Mak On Fri, 2005-10-07 at 20:00 -0500, Kevin Kinsey wrote: makisupa wrote: Been using Linux awhile...recently migrated a laptop to FreeBSD. Its a bit old and BSD runs nicely on the deprecated hardware. I am using 6.0-BETA 5 despite warning to the contrary because my atheros based wifi card works well -- i had all kinds of trouble in 5.4. Running gnome 2.12. My newbie questions: 1. I am pretty sure that FAM is not running. The newest version of the package is installed. I followed the directions from the gnome FAQ and the pkg_message. 'killall -HUP inetd' gives me 'no matching processes were found.' What does `ps -aux | grep inetd` tell you? Inetd doesn't run unless enabled in /etc/rc.conf... and IIRC (I've switched to xfce4 from Gnome2), fam runs from inetd, so that could be a root (no pun intended) cause of these issues, perhaps? IANAE When i launch something like gnome-menu-editor i get a 'failed to connect to the FAM server' message in the terminal. Similiarly, whenever i gedit a file su'd as root i get a 'gnomeUI-WARNING **: While connecting to the session manage: authentication rejected, reason: None of the authentication protocols specified are supported and host based authentication failed.' Please help...its very annoying as the gnome does not update worth a damn as you move, add, and delete files. I realize the instructions were for gnome 2.10 and i probably missed something obvious. 2. Is there a way to turn DMA on for a certain device or devices and not every ATAPI drive? I got permissions and whatnot straight to allow a users to mount CD/DVD drives -- my CD drive does not work correctly in DMA mode. BUT, i will need DMA in order to play DVDs correctly (see below). I passed the hw.ata.atapi_dma=1 option in my /boot/loader.conf file. is there a option i can pass that only enables DMA on my acd1 (dvd) and ad0 (hd) but NOT acd0 (CD)? Hrm, I'm not much good from here out. I note that there are two sysctl's hw.ata.ata.dma and hw.ata.atapi.dma, dunno if that'd help. Maybe see ata(4) for a little more detail. Being as the DVD and CD are on the same bus, I'd say it's not too likely, but, again, IANAE 3. DVD playback. Just trying to use the totem default in my gnome install. I get a 'failed to retrieve capabilities of device /dev/acd1: inappropriate ioctl for device'. I've googled the hell out of this and came up with little helpful info. Any ideas? Thanks for your help. I think i'm doing fairly well for only running BSD for a couple of days...but if i could get these minor things straightened out i'd be set (and have a rockin' little laptop). FreeBSD definately seems more intuitive than most of the linux distros i've used... Thanks, Mak. Best o' luck, Kevin Kinsey ___ 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: Newbie Questions
Joseph Borg wrote: Hi, I've got a couple of questions I was hoping someone could help me with: [snip] - Finally, I've just installed gnome and when it starts up, I get the following error: No volume control elements and/or devices found. The A8V Motherboard on which the system is installed has an inbuilt 8.0 sound card. Is there any way I can test this is working under Freebsd. Provided this is the case, how can I eliminate the error in gnome? Can't answer your first couple of questions, but I know from solving this for myself over the weekend that this one should just require getting the correct kernel module loaded for your sound card. See http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/sound-setup.html For me, it was as simple as running the sound driver meta loader kldload snd_driver to see if my card would fly at all, and then looking at dmesg to see that the meta loader was finding device pcm0 and from there figuring out which sound module I needed to load from /boot/loader.conf with my_modname_load=YES (can't remember the actual module name I used) Then boot, and Gnome starts up happy (just like me every time I boot FreeBSD ;-). -- Greg Barniskis, Computer Systems Integrator South Central Library System (SCLS) Library Interchange Network (LINK) gregb at scls.lib.wi.us, (608) 266-6348 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie Questions
On Tue, May 17, 2005 at 09:58:51PM +0200, Joseph Borg wrote: Hi, I've got a couple of questions I was hoping someone could help me with: - I've got an (extremely old) HP Scanjet 4c Scanner hooked up via an Adaptec SCSI card to my system. Freebsd seems to recognize this scanner at boot: May 17 20:48:36 cronus kernel: pass0 at ahc0 bus 0 target 2 lun 0 May 17 20:48:36 cronus kernel: pass0: HP C2520A 3503 Fixed Processor SCSI-2 device May 17 20:48:36 cronus kernel: pass0: 3.300MB/s transfers Would you know of any software (preferably under gnome/X that I can use to operate this scanner)? The 'xsane' port works fine. Also needs the 'sane-backends' port. - Secondly, I've also got a NEC IDE DVD-RW drive hooked up which the system recognizes fine. What software can I use to burn DVDs? All I'm looking for is some software (preferably also under X/gnome) that would allow me to make backup DVD's of files I have on the drive (i.e. Data DVDs). For dvds: 'growisofs' (port), for CD's burncd (part of the distribution) or 'cdrecord' (port). These are command-line programs. cdrecord requires the use of following devices in the kernel: 'atapicam', 'scbus' 'cd' and 'pass'. More info on my FreeBSD page: http://www.xs4all.nl/~rsmith/freebsd/ There are several GUIs for cdrecord, e.g. k3b (KDE) and gcombust (GTK). Nautilus can also burn CDs with the nautilus-cd-burner port. Try searching freshmeat.net. - Finally, I've just installed gnome and when it starts up, I get the following error: No volume control elements and/or devices found. The A8V Motherboard on which the system is installed has an inbuilt 8.0 sound card. Is there any way I can test this is working under Freebsd. Provided this is the case, how can I eliminate the error in gnome? If you issue the 'mixer' command in a terminal, what kind of output do you get? It should look something like: $ mixer Mixer vol is currently set to 75:75 Mixer pcm is currently set to 58:58 Mixer speaker is currently set to 75:75 Mixer line is currently set to 75:75 Mixer mic is currently set to 0:0 Mixer cd is currently set to 75:75 Mixer rec is currently set to 0:0 Mixer ogainis currently set to 50:50 Mixer line1is currently set to 75:75 Mixer phin is currently set to 0:0 Mixer phoutis currently set to 0:0 Recording source: mic If not, there are several things that could be wrong, and it depends on the error you get. Check that you have sufficient permissions on /dev/mixer (should be crw-rw-rw-) HTH, Roland -- R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt pgpdNdVfJuSCt.pgp Description: PGP signature
RE: Newbie Questions
Hi Ron, Thanks for your tips. The sound card and mixer look ok now. I've also installed xsane and I'm now figuring out how to use it. As for the DVD, I've search my ports for growisofs however, I cannot find it. Can I download it off anywhere? Thanks, Joe ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie Questions
On Wed, May 18, 2005 at 12:01:23AM +0200, Joseph Borg wrote: As for the DVD, I've search my ports for growisofs however, I cannot find it. Can I download it off anywhere? The program is called growisofs, but it's packaged as dvd+rw-tools (in /usr/ports/sysutils). Roland -- R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt pgp57tNHMbWET.pgp Description: PGP signature
Re: newbie questions
On Fri, 9 Apr 2004 11:18:34 +0300 (EEST) Radu MOLNAR [EMAIL PROTECTED] wrote: I hope this is the right place to post this.Sorry if it isn't Just some stupid newbie questions: 1) I have an alias made in my .profile alias vi='/usr/local/bin/vim' but the alias is not made when i log in X. If a log in console or using ssh from a remote host the alias is made but when i log in x it is not. Anybody know why? As shell i use bash. Its definitely the right place to ask questions. I can only comment on the first question. Its more of a question of how your shell is being invoked in your window manager. It sounds as if the window manager is invoking the shell as a non-login shell. You can test this by using xterm -ls and see if your alias settings are being read. This causes the xterm to act as a login shell and bash will act accordingly. Take a look at man page for bash in the section INVOCATION for a complete description of how bash behaves depending on whether or not its a login or non-login shell. There are several different ways to address it. You could simply duplicate your alias settings in a ~/.bashrc file which bash will read when invoked in a non-login shell. I personally don't like having more than one place for any configuration. It would probably be easier to change the way your window manager invokes a shell. I use xterms and blackbox so it was easy to change the menu configuration from xterm to xterm -ls. If you are using a different type of terminal window in XFree86, then look in its documentation for a way to make it behave as a login. If you're using some other terminal type, check its documentation for similar things and change your window manager menus accordingly. HTH, Randy -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie Questions Regarding SU Command Running Periodic Updating
On Sun, Feb 15, 2004 at 10:20:12AM -0500, [EMAIL PROTECTED] wrote: Question # 1: When I type 'su' and subsequently type in my password, I am taken to the root. However, certain programs; i.e., 'portupgrade' will not run. If I then subsequently type 'su' I a, presented with a new prompt although no password is requested. I can now run programs like 'portupgrade' without incident. I am unable to find any documentation that states I should be running the 'su' command twice. Can someone explain to me what is happening here? Is this normal. Exactly how many levels are there? I thought that there were only two: the log in level and root level. Is there a third level or is this some sort of fluke. Yes. You're right that there are only the two privilege levels -- root vs ordinary users. What you're seeing is due to a different effect. The first time you su(1) you become root, but your shell environment is not set up the way you expect. Specifically you don't have /usr/local/sbin on your $PATH, so when you type 'portupgrade' at the prompt, the shell can't find the executable. You should be able to type '/usr/local/sbin/portupgrade' and have things work as expected. The second time you type su(1), it takes effect without asking for a password, since the super user can become any other user without giving one. However, changing from root to root normally isn't usually very productive. Usually when you su(1), the shell environment is left the same except for the USER, HOME and SHELL environment variables, which are reset appropriately for the new userid. However, settings in the target login's .cshrc or .profile or .bashrc or whatever will take effect exactly as for starting up any new shell. There are some flags to su(1) to modify that behaviour: '-l' (or just '-') says simulate a full login by the target user, and '-m' does the opposite -- leaving the original environment unmodified. My guess is that the behaviour you are seeing is because either the su(1) command is aliased to add in some other options, or that you have something in root's shell initialization files which is causing the effect. On general principles, I'd recommend you to install and use sudo(8) instead of su(1) -- it has much finer grained access controls, you don't need to give out the root password in order to let people run commands with root privilege and it logs everything done with it. Question # 2: Second, while typing in search terms in Google, I came across this web site - http://andrsn.stanford.edu/FreeBSD/newuser.html You will notice the entry about updating the database for the 'whereis' and 'locate' commands. I have read the manual on 'locate' and tried running the files mentioned manually, but alias all I receive is an error message that the command does not exist. Again, I have no idea what I am doing incorrectly. Any assistance would be appreciated. The database update will happen automatically, overnight, in the wee small hours of Saturday morning. So long as you leave you machine running, that is. You can manually update the 'locate' database by running (as root): # /etc/periodic/weekly/310.locate and similarly for whereis: # /etc/periodic/weekly/320.whatis Those should run without errors -- if you still have problems, please feel free to e-mail here again, including the exact output of running those commands. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
Re: newbie questions (2) 5.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 20 August 2003 10:39 am, [EMAIL PROTECTED] wrote: hello again, first, i can't seem to get my modem to do anything, i think it's an irq conflict, but don't really want to mess around with the config files too much if i don't have to. in 5.1 sysinstall(8) there seems to be no option to change or confirm the info probed and sysinstall skips the kernel, not sure if that is the right expression, and sysinstall starts with the automatic defaults. i have attached the dmesg file. help, i am new to FreeBSD so i may need to be walked through the steps. The modem is recognized: [From dmesg.txt] sio4: U.S. Robotics Sportster 33600 FAX/Voice Int at port 0x2f8-0x2ff irq 3 on isa0 sio4: type 16550A What is it you are trying to do with the modem and how? - -Mark -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE/Q7nVF/yyV91po54RAjDmAKDDycxz9A4VadkbUl2vxkt2hjcblQCgqqL+ ag2VtlDkpN37bnlcn/+Z3Qw=/zal -END PGP SIGNATURE- i saw that, but what does the sio1 message port not recognized mean, and what is sio1? i'm trying to use modem for dial-up, and haven't heard a peep from it. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: newbie questions (2) 5.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 20 August 2003 11:22 am, [EMAIL PROTECTED] wrote: On Wednesday 20 August 2003 10:39 am, [EMAIL PROTECTED] wrote: hello again, first, i can't seem to get my modem to do anything, i think it's an irq conflict, but don't really want to mess around with the config files too much if i don't have to. in 5.1 sysinstall(8) there seems to be no option to change or confirm the info probed and sysinstall skips the kernel, not sure if that is the right expression, and sysinstall starts with the automatic defaults. i have attached the dmesg file. help, i am new to FreeBSD so i may need to be walked through the steps. The modem is recognized: [From dmesg.txt] sio4: U.S. Robotics Sportster 33600 FAX/Voice Int at port 0x2f8-0x2ff irq 3 on isa0 sio4: type 16550A What is it you are trying to do with the modem and how? - -Mark i saw that, but what does the sio1 message port not recognized mean, and what is sio1? i'm trying to use modem for dial-up, and haven't heard a peep from it. Those messages mean that the kernel thinks it is detecting a serial port (com port), but that the irq isn't what it's expecting. You can usually safely ignore those. The important bit for you is that it detects your modem at sio4, so you'll want use sio4 (or cuaa4) in whatever document you are using to get dial-up working. How are trying to get dial-up working? ppp? You'll probably want to have a look at the handbook (if you aren't already). http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/userppp.html - -Mark -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE/Q8bXF/yyV91po54RApFLAJ4+wxGTVjm63oB2Bg+OT4GXYbx61gCZAZMB 1xPb4Bai8BzyY2rQ9d212lI= =ZCHr -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
solved : Re: newbie questions about pppoe and netgraph
2 problems 1 cable modem needed 10baset connection. changed rc.conf= ifconfig_dc0=inet xxx.xxx.xxx.xxx mask 255.255.255.0 media 10baseT/UTP fixed that problem 2 didn't need pppoe after all! after changing media, was able to ping external router btw, this is charter pipeline (vermont) service (768) using 3com 3cr29223 home connect external usb/ether (NOT adsl dual connect). tech support was friendly but basically clueless (i don't know anything about free-bee-ess-dee ppp over ethernet? what's that?). anyway, thanks for all of your helpi learned more about pppoe than i ever wanted. all you guys are terrific! stephen On Sat, 11 Jan 2003, Stephen D. Kingrea wrote: this is the latest, unchanged from this am. i should say that using different parameters from the several different tutorial sources has resulted in pretty much the same result: flaking out at lpc (if that is what is really happening) additionally, the set ifaddr line seems superfluous, since i have an assigned ip address and established route default: set device PPPoE:fxp0 set speed mru 1492 set speed mtu 1492 set ctsrts off enable lqr set lqrperiod 5 set cd 5 set log All set log local phase chat lcp ccp tun command add default HISADDR enable dns set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255 0.0.0.0 set authname * set authkey * set login set dial set timeout 0 open stephen On Sat, 11 Jan 2003, Matthew Emmerton wrote: What does your ppp.conf look like? For PPPoE, it you should have a line like this: [ dang email client ] set device PPPoE:ed1 where ed1 is the network card that is hooked up to your DSL modem. -- Matt www# /usr/sbin/ppp Working in interactive mode Using interface: tun0 tun0: Command: default: add default HISADDR tun0: Command: default: enable DNS tun0: Command: default: set ifaddr 10.0.0.1/0 10.0.0.0/2 255.255.255 0.0.0.0 tun0: Command: default: set authname ** tun0: Command: default: set authkey ** tun0: Command: default: set login tun0: Command: default: set dial tun0: Command: default: set timeout 0 tun0: Command: default: open tun0: Phase: bundle: Establish tun0: Phase: closed - opening tun0: Phase: PPP started (interactive) tun0: Phase: deflink: Connected! tun0: Phase: deflink: opening - dial tun0: Chat: deflink: Dial attempt 1 of 1 tun0: Phase: deflink: dial - carrier ppp ON www tun0: Phase: deflink: Disconnected! tun0: Phase: deflink: carrier - hangup tun0: Phase: deflink: Connect time: 5 secs: 0 octets in, 0 octets out tun0: Phase: total 0 bytes/sec, peak 0 bytes/sec on Sat Jan 11 tun0: Phase: deflink hangup - closed tun0: Phase: bundle: Dead i imagine that some of this is unnecessary, but it appears that i am not even getting to authentication before disconnecting. thank you stephen On Sat, 11 Jan 2003, Matthew Emmerton wrote: attempting to run pppoe on freebsd 4.7 over cable/dsl connection. manual says kernel recompilation unnecessary for this release in order to run pppoe. however, netgraph does not seem to be loading at boot time. additionally, pppoe seems unable to get past lcp when connecting. how can i tell if netgraph is active after boot? if not, can netgraph modules be loaded at boot by adding necessary lines into loader.conf? or is recompiling kernel a preferred method? If netgraph and pppoe support are not present in your kernel (or not loaded from modules automatically), the ppp program will complain loudly. Can you post part of your ppp log file so that we can determine if the lack of pppoe is your problem or if it's something else? -- Matt Emmerton To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: newbie questions about pppoe and netgraph
ok here is what i get www# /usr/sbin/ppp Working in interactive mode Using interface: tun0 tun0: Command: default: add default HISADDR tun0: Command: default: enable DNS tun0: Command: default: set ifaddr 10.0.0.1/0 10.0.0.0/2 255.255.255 0.0.0.0 tun0: Command: default: set authname ** tun0: Command: default: set authkey ** tun0: Command: default: set login tun0: Command: default: set dial tun0: Command: default: set timeout 0 tun0: Command: default: open tun0: Phase: bundle: Establish tun0: Phase: closed - opening tun0: Phase: PPP started (interactive) tun0: Phase: deflink: Connected! tun0: Phase: deflink: opening - dial tun0: Chat: deflink: Dial attempt 1 of 1 tun0: Phase: deflink: dial - carrier ppp ON www tun0: Phase: deflink: Disconnected! tun0: Phase: deflink: carrier - hangup tun0: Phase: deflink: Connect time: 5 secs: 0 octets in, 0 octets out tun0: Phase: total 0 bytes/sec, peak 0 bytes/sec on Sat Jan 11 tun0: Phase: deflink hangup - closed tun0: Phase: bundle: Dead i imagine that some of this is unnecessary, but it appears that i am not even getting to authentication before disconnecting. thank you stephen On Sat, 11 Jan 2003, Matthew Emmerton wrote: attempting to run pppoe on freebsd 4.7 over cable/dsl connection. manual says kernel recompilation unnecessary for this release in order to run pppoe. however, netgraph does not seem to be loading at boot time. additionally, pppoe seems unable to get past lcp when connecting. how can i tell if netgraph is active after boot? if not, can netgraph modules be loaded at boot by adding necessary lines into loader.conf? or is recompiling kernel a preferred method? If netgraph and pppoe support are not present in your kernel (or not loaded from modules automatically), the ppp program will complain loudly. Can you post part of your ppp log file so that we can determine if the lack of pppoe is your problem or if it's something else? -- Matt Emmerton To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: newbie questions about pppoe and netgraph
attempting to run pppoe on freebsd 4.7 over cable/dsl connection. manual says kernel recompilation unnecessary for this release in order to run pppoe. however, netgraph does not seem to be loading at boot time. additionally, pppoe seems unable to get past lcp when connecting. how can i tell if netgraph is active after boot? if not, can netgraph modules be loaded at boot by adding necessary lines into loader.conf? or is recompiling kernel a preferred method? If netgraph and pppoe support are not present in your kernel (or not loaded from modules automatically), the ppp program will complain loudly. Can you post part of your ppp log file so that we can determine if the lack of pppoe is your problem or if it's something else? -- Matt Emmerton To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: newbie questions about pppoe and netgraph
What does your ppp.conf look like? For PPPoE, it you should have a line like this: [ dang email client ] set device PPPoE:ed1 where ed1 is the network card that is hooked up to your DSL modem. -- Matt www# /usr/sbin/ppp Working in interactive mode Using interface: tun0 tun0: Command: default: add default HISADDR tun0: Command: default: enable DNS tun0: Command: default: set ifaddr 10.0.0.1/0 10.0.0.0/2 255.255.255 0.0.0.0 tun0: Command: default: set authname ** tun0: Command: default: set authkey ** tun0: Command: default: set login tun0: Command: default: set dial tun0: Command: default: set timeout 0 tun0: Command: default: open tun0: Phase: bundle: Establish tun0: Phase: closed - opening tun0: Phase: PPP started (interactive) tun0: Phase: deflink: Connected! tun0: Phase: deflink: opening - dial tun0: Chat: deflink: Dial attempt 1 of 1 tun0: Phase: deflink: dial - carrier ppp ON www tun0: Phase: deflink: Disconnected! tun0: Phase: deflink: carrier - hangup tun0: Phase: deflink: Connect time: 5 secs: 0 octets in, 0 octets out tun0: Phase: total 0 bytes/sec, peak 0 bytes/sec on Sat Jan 11 tun0: Phase: deflink hangup - closed tun0: Phase: bundle: Dead i imagine that some of this is unnecessary, but it appears that i am not even getting to authentication before disconnecting. thank you stephen On Sat, 11 Jan 2003, Matthew Emmerton wrote: attempting to run pppoe on freebsd 4.7 over cable/dsl connection. manual says kernel recompilation unnecessary for this release in order to run pppoe. however, netgraph does not seem to be loading at boot time. additionally, pppoe seems unable to get past lcp when connecting. how can i tell if netgraph is active after boot? if not, can netgraph modules be loaded at boot by adding necessary lines into loader.conf? or is recompiling kernel a preferred method? If netgraph and pppoe support are not present in your kernel (or not loaded from modules automatically), the ppp program will complain loudly. Can you post part of your ppp log file so that we can determine if the lack of pppoe is your problem or if it's something else? -- Matt Emmerton To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
