Re: How Write To Win Drive?
Roland Smith [EMAIL PROTECTED] wrote:Try /usr/ports/sysutils/fusefs-ntfs instead. It's newer and is supposed to support writing. Hmm. Well, there's no such port in FBSD. There is such a port, however, available from Absolute FBSD. So I d/l'd it and all the required to build products. I checked to see if libtool15 was built on my system. It was, so I didn't bother with that. I built out fusefs-libs, then fusefs-kmod, all successfully. However, when I tried to compile fusefs-ntfs, I got an error and was referred to the d/l page http://freeports.org/sysutils/fusefs-ntfs for information...which only seems to tell me I need to build the other products (which I just built) first. Perhaps this doesn't work on FBSD? TIA, Stan - 8:00? 8:25? 8:40? Find a flick in no time with theYahoo! Search movie showtime shortcut. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Time changed back to old daylight savings
I'm not sure when this happened, but I noticed today that my server reverted back to the old daylight savings time (1 hour off) When I run ntpdate and have it update it even then it shows the wrong time. I haven't done anything to replace the /etc/localtime file, even tried running tzsetup again, but that still didn't help. My system is FreeBSD 6.1-stable, the only thing that has changed since I last noticed the system had the _right_ time was I built a new kernel. I tried installing the port 'zoneinfo', but it's broken, it can't find the appropriate file to download and install (seems to be missing or updated). At the moment I've addressed the issue with a date -v +1H. Any reason this would happen? How do I fix it? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Time changed back to old daylight savings
On Wed, Mar 28, 2007 at 12:45:11AM -0700, Don O'Neil wrote: I'm not sure when this happened, but I noticed today that my server reverted back to the old daylight savings time (1 hour off) When I run ntpdate and have it update it even then it shows the wrong time. This tends to indicate the your /etc/localtime file is wrong. The timeservers all return UTC; the display for the date consults /etc/localtime to display UTC time in local time. I haven't done anything to replace the /etc/localtime file, even tried running tzsetup again, but that still didn't help. This indicates that your zoneinfo files have not been updated correctly. [...] At the moment I've addressed the issue with a date -v +1H. Which definitely isn't the correct fix. Any reason this would happen? How do I fix it? What does md5 /usr/src/share/zoneinfo/northamerica return? (I'm assuming that you're in North America). On my 6-STABLE machine it's: MD5 (/usr/src/share/zoneinfo/northamerica) = 3e582e371f445a18b065eed8f775fb20 Any other result means that your should re-cvsup, and rebuild your system again. If it is the same, make sure your zoneinfo files have been rebuilt (check the file timestamps). Cheers. -- Jonathan Chen [EMAIL PROTECTED]Once is dumb luck. Twice is coincidence. Three times and Somebody Is Trying To Tell You Something. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Time changed back to old daylight savings
On Wed, Mar 28, 2007 at 12:45:11AM -0700, Don O'Neil wrote: I'm not sure when this happened, but I noticed today that my server reverted back to the old daylight savings time (1 hour off) When I run ntpdate and have it update it even then it shows the wrong time. I haven't done anything to replace the /etc/localtime file, even tried running tzsetup again, but that still didn't help. My system is FreeBSD 6.1-stable, the only thing that has changed since I last noticed the system had the _right_ time was I built a new kernel. There is no such thing as 6.1-stable any more, so what do you really mean? Kris I tried installing the port 'zoneinfo', but it's broken, it can't find the appropriate file to download and install (seems to be missing or updated). At the moment I've addressed the issue with a date -v +1H. Any reason this would happen? How do I fix it? ___ 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: the art of pkgdb -F
On Tue, 27 Mar 2007 21:17:13 -0400 Michael P. Soulier [EMAIL PROTECTED] wrote: I'm looking at http://www.freebsddiary.org/pkgdb.php while I run it myself. I'm finding wonderful questions like Stale dependency: p5-Authen-SASL-2.09 - p5-GSSAPI-0.24 (security/p5-GSSAPI): p5-Geography-Countries-1.4 (score:26%) ? ([y]es/[n]o/[a]ll) [no] I must ask. How the hell am I supposed to know?? I build that as a dependency of something that I built months ago. There's a good chance that I'll be simply guessing at all of the answers. Is it really useful to run this if you can't remember? And why am I remembering anyway? That's what a packaging system is for, isn't it? You can run: portmanager -u -p -l That will rebuild all broken and or missing dependencies for all of your ports. If you just want to correct a single port, try this: portmanager /port/name-of-port -p -l HTH -- Gerard Horner's Five Thumb Postulate: Experience varies directly with equipment ruined. signature.asc Description: PGP signature
Re: FreeBSD on IBM Blade HS21
Hi, Nejc Škoberne wrote: Hello, today I tried to migrate a FreeBSD 6.1 installation from an ordinary PC machine to an IBM Blade HS21 server. The server is a brand new machine with two Dual Core Xeon 5130 processors, two 72GB SAS drives. i installed FreeBSD 6.1-Beta2 on an IBM HS20 Blade. Take a look here: http://wiki.bsdgroup.de/FreeBSD_on_IBM_Blade Hth. Axel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New to FreeBSD
On 2007-03-26 23:09, Ivan Zenzerovi? [EMAIL PROTECTED] wrote: Hi to all. My name is Ivan and I'm new to FreeBSD and Unix, I worked a little in Linux, but it was a long time ago. I downloaded the 5.5 release and I plan installing it. I downloaded also all availible docs. I wondered if it is ok to start with this. And, also, I have an integrated GPU, it works well on FreeBSD? This question was posted to the comp.unix.bsd.freebsd.misc newsgroup too. 'jpd' took the time to write a fairly informative reply there: % Date: 27 Mar 2007 03:36:37 GMT % From: jpd [EMAIL PROTECTED] % Subject: Re: New to FreeBSD % Newsgroups: comp.unix.bsd.freebsd.misc % Message-ID: [EMAIL PROTECTED] % % Begin [EMAIL PROTECTED] % On 2007-03-27, Walter Vaughan [EMAIL PROTECTED] wrote: % [...] I'm new to FreeBSD and Unix, I worked a little in Linux, but % it was a long time ago. I downloaded the 5.5 release and I plan % installing it. I downloaded also all availible docs. I wondered if it % is ok to start with this. % % That is quite a lot of documentation. The handbook covers quite a lot % of topics and is a recommended read. The installation, release, and % hardware notes you'll also want to read at least once. % % The other handbooks and articles are useful if you're interested in % their particular topics, of course. % % There are also one or two complete books, previously in print, now % online, that you might want to look at. If they're not linked to on % the FreeBSD site, they've certainly been mentioned in this group. % % And, also, I have an integrated GPU, it works well on FreeBSD? % % FreeBSD itself does very little on that front. The graphics are usually % provided through the Xorg X Window System (previously the XFree86 one), % and that works well for 2d and accelerated 2d graphics. More details % in the Xorg documentation. Accelerated OpenGL 3d support is a sore % point with the free software world, as most vendors won't share the % programming specs, and if they provide binary drivers at all it is often % only for linux. % % So, for really snazzy 3d graphics out of the box you'll have to look at % other solutions. A commercial X server might help. Have you actually *read* the reply of jpd to the group? Did you find it useful? Did you find it confusing, in any way? If it was unclear, what was it exactly that you didn't understand in his reply? - Giorgos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New to FreeBSD
On 2007-03-27 23:36, Ivan Zenzerovi? [EMAIL PROTECTED] wrote: Hi guys, i managed to install it, and, in fact I'm working on it right now. It's great, just tell me, I should compile my kernel at this point? And a question: I don't like this xorg, and I have installed KDE but how do I run KDE? Right after your first FreeBSD installation, you are certainly *not* expected to rush into rebuilding a kernel, for any reason. In fact, this could be a dangerous exercise. It's far too easy to build a kernel which lacks critical components, and render your system unbootable (at least unbootable without manual intervention). Since you are new to the FreeBSD system, my suggestion would be to forget about rebuilding kernels, optimizing compiler flags, and tweaking knobs here and there. Now that you have a working FreeBSD installation you should *read* about the system you have just installed. There is a wealth of information about FreeBSD both in the CD-ROM set which you used to install it, and online. You should, at least, check the following: * The README.TXT file at the toplevel directory of your installation CD-ROM. * The web pages at http://www.FreeBSD.org/docs.html * The FreeBSD FAQ book, at http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/ The FAQ contains a lagre list of frequently asked questions about FreeBSD. You will find answers there about a very diverse range of topics, including such obscure things as ``I managed to trash by boot loader, what should I do now?''. * The FreeBSD Handbook, at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ The FreeBSD Handbook is the largest book written by the FreeBSD documentation team. It is both a guide for the beginning user, and a common reference for administrators setting up services with FreeBSD. Your answer about KDE vs. X11 is already answered in the Handbook. Note that a copy of the Handbook and all the articles, books and other reference material related to the FreeBSD release you have just installed, are also conveniently available in the CD-ROM you used to install FreeBSD. You can install them locally too, by logging in as root and running ``sysinstall'': # sysintall Follow the menus to add the ``doc'' distribution, and then you will have a copy of all the documentation articles and books at: /usr/share/doc Welcome to FreeBSD, and if you have other questions regarding its every day use and operation, feel free to email this list again :-) - Giorgos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How Write To Win Drive?
Stan Cooper wrote: Roland Smith [EMAIL PROTECTED] wrote:Try /usr/ports/sysutils/fusefs-ntfs instead. It's newer and is supposed to support writing. Hmm. Well, there's no such port in FBSD. Are you certain? [EMAIL PROTECTED]/usr/ports] uname -s FreeBSD [EMAIL PROTECTED]/usr/ports] ll IN*6 -rw-r--r-- 1 root wheel 9888013 Feb 6 09:33 INDEX-6 [EMAIL PROTECTED]/usr/ports] ll sysutils/fusefs-ntfs total 1 -rw-r--r-- 1 root wheel 1075 Feb 20 21:25 Makefile -rw-r--r-- 1 root wheel 214 Feb 20 21:25 distinfo drwxr-xr-x 2 root wheel 512 Jan 21 02:09 files/ -rw-r--r-- 1 root wheel 354 Dec 5 16:56 pkg-descr -rw-r--r-- 1 root wheel 840 Dec 5 16:15 pkg-plist And that's well over a month old. According to freshports.org, this port was added on December 6th. There is such a port, however, available from Absolute FBSD. AFAIK, this is a book, not an operating system. Perhaps Michael mentioned how to compile this from scratch in his book? So I d/l'd it and all the required to build products. I checked to see if libtool15 was built on my system. It was, so I didn't bother with that. I built out fusefs-libs, then fusefs-kmod, all successfully. However, when I tried to compile fusefs-ntfs, I got an error and was referred to the d/l page http://freeports.org/sysutils/fusefs-ntfs for information... which only seems to tell me I need to build the other products (which I just built) first. Perhaps this doesn't work on FBSD? I wouldn't know; but I'd try the port, because if it failed I might get some support from this community. KDK -- A few hours grace before the madness begins again. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
stty -echo
Hi, I have been using the command stty -echo which is supposed to turn of displaying characters. But it is not turning off the echoing of typed chars. Example: $ stty -echo $ echo hi hi $ Here echo hi should not have been printed. Is this a bug or have I not interpreted the man pages? Thanks in advance, Apeksha Godiyal ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: stty -echo
On 28/03/07, Apeksha Godiyal [EMAIL PROTECTED] wrote: Hi, I have been using the command stty -echo which is supposed to turn of displaying characters. But it is not turning off the echoing of typed chars. Example: $ stty -echo $ echo hi hi $ Here echo hi should not have been printed. Is this a bug or have I not interpreted the man pages? AFAIK it doesn't work in an interactive shell. But it works in a script, just try something like: #!/bin/sh stty -echo read Thanks in advance, Apeksha Godiyal HTH Christian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How Write To Win Drive?
Kevin Kinsey [EMAIL PROTECTED] wrote: Stan Cooper wrote: Roland Smith wrote:Try /usr/ports/sysutils/fusefs-ntfs instead. It's newer and is supposed to support writing. Hmm. Well, there's no such port in FBSD. Are you certain? [EMAIL PROTECTED]/usr/ports] uname -s FreeBSD [EMAIL PROTECTED]/usr/ports] ll IN*6 -rw-r--r-- 1 root wheel 9888013 Feb 6 09:33 INDEX-6 [EMAIL PROTECTED]/usr/ports] ll sysutils/fusefs-ntfs total 1 -rw-r--r-- 1 root wheel 1075 Feb 20 21:25 Makefile -rw-r--r-- 1 root wheel 214 Feb 20 21:25 distinfo drwxr-xr-x 2 root wheel 512 Jan 21 02:09 files/ -rw-r--r-- 1 root wheel 354 Dec 5 16:56 pkg-descr -rw-r--r-- 1 root wheel 840 Dec 5 16:15 pkg-plist Geez, well I just copied your commands directly and, naturally, the first two went without a hitch, but the last one gave me No such file or directory, and yes, I did that from /usr/ports And that's well over a month old. According to freshports.org, this port was added on December 6th. I built this system this year. So you'd think it'd be there, right? I wouldn't know; but I'd try the port, because if it failed I might get some support from this community. Well, let's hope some help's forthcoming ;) TIA, Stan - Sucker-punch spam with award-winning protection. Try the free Yahoo! Mail Beta. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New to FreeBSD
hello again. I made a mistake during post install config. I put a name that I don't want for my computer, and when I logon as root it's written in the comand line. How di I change it? Ivan On 3/28/07, Giorgos Keramidas [EMAIL PROTECTED] wrote: On 2007-03-27 23:36, Ivan Zenzerovi? [EMAIL PROTECTED] wrote: Hi guys, i managed to install it, and, in fact I'm working on it right now. It's great, just tell me, I should compile my kernel at this point? And a question: I don't like this xorg, and I have installed KDE but how do I run KDE? Right after your first FreeBSD installation, you are certainly *not* expected to rush into rebuilding a kernel, for any reason. In fact, this could be a dangerous exercise. It's far too easy to build a kernel which lacks critical components, and render your system unbootable (at least unbootable without manual intervention). Since you are new to the FreeBSD system, my suggestion would be to forget about rebuilding kernels, optimizing compiler flags, and tweaking knobs here and there. Now that you have a working FreeBSD installation you should *read* about the system you have just installed. There is a wealth of information about FreeBSD both in the CD-ROM set which you used to install it, and online. You should, at least, check the following: * The README.TXT file at the toplevel directory of your installation CD-ROM. * The web pages at http://www.FreeBSD.org/docs.html * The FreeBSD FAQ book, at http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/ The FAQ contains a lagre list of frequently asked questions about FreeBSD. You will find answers there about a very diverse range of topics, including such obscure things as ``I managed to trash by boot loader, what should I do now?''. * The FreeBSD Handbook, at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ The FreeBSD Handbook is the largest book written by the FreeBSD documentation team. It is both a guide for the beginning user, and a common reference for administrators setting up services with FreeBSD. Your answer about KDE vs. X11 is already answered in the Handbook. Note that a copy of the Handbook and all the articles, books and other reference material related to the FreeBSD release you have just installed, are also conveniently available in the CD-ROM you used to install FreeBSD. You can install them locally too, by logging in as root and running ``sysinstall'': # sysintall Follow the menus to add the ``doc'' distribution, and then you will have a copy of all the documentation articles and books at: /usr/share/doc Welcome to FreeBSD, and if you have other questions regarding its every day use and operation, feel free to email this list again :-) - Giorgos -- --- Correr, competir, eu levo isso no sangue, é parte da minha vida. - Ayrton Senna ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New to FreeBSD
On Wednesday 28 March 2007 09:08:30 am Ivan Zenzerović wrote: hello again. I made a mistake during post install config. I put a name that I don't want for my computer, and when I logon as root it's written in the comand line. How di I change it? Ivan Edit /etc/rc.conf .. find the line hostname=wrong name and change it to the name you prefer. -- Q: How many pre-med's does it take to change a lightbulb? A: Five: One to change the bulb and four to pull the ladder out from under him. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hi
On Tue, Mar 27, 2007 at 09:39:10PM -0400, Drew White wrote: Hi Jerry, installed the system. Now getting a terrible message video input 'out of range' on both my monitors... one showsup partially distorted and the other not at all . It worked find on the friends monitor who installed it for me, so i guess its a difference in the monitor and nothe computer . Can you tell me how to get 'in range'? This is weird! Both normal monitors, out of the box! Please do not post questions back to me personally. It is considered to be very bad Email list etiquette. Post them to the questions list. That is the proper way. The second reason, besides etiquette is that the single person may well not know the answer and you are cutting yourself short by not posting to the list. I believe this has been mentioned to you at least once already. In this case, I don't know much of anything about setting up the graphics of Xorg. I manage to get it going enough to get by and leave it alone.So, ask someone who knows. jerry Thanks,, DRew :) On 3/21/07, Jerry McAllister [EMAIL PROTECTED] wrote: On Tue, Mar 20, 2007 at 09:25:34PM -0400, Daniel Molina Wegener wrote: On Tuesday 20 March 2007 20:33, Drew White wrote: Hi NOOB question... Hi... I installed a second hard drive on the computer to put FreeBSD on, with windows xp on the other drive. Can I dl the software and install it on the other hard drive without burning it to cds or using floppy discs? Wondering if I can do it from the other drive/operating system. Yes, you can. But you need to install the boot loader on the first disc. Try using shell from install disc. The problem is, he seems to be asking about doing it without making an install disc. Once he has made the install CD, then he might as well go ahead and do the install with it and not bother with the MS monkey business. jerry Thanks, please advise. Drew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Regards, -- .O. | Daniel Molina Wegener | C/C++ Developer ..O | dmw [at] unete [dot] cl | FOSS Coding Adict OOO | BSD Linux User| Standards Rocks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Drew White [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: New to FreeBSD
On Wed, Mar 28, 2007 at 04:08:30PM +0200, Ivan Zenzerovi? wrote: hello again. I made a mistake during post install config. I put a name that I don't want for my computer, and when I logon as root it's written in the comand line. How di I change it? Presuming by that that you mean your hostname, then that is set in /etc/rc.conf -- look for the hostname command and edit it. It is best if it has the fully qualified hostname including domain, not just the first (left-most) element of it. If you are using this machine on the net, then that hostname has to be registered with who-ever is providing DNS for you. So, whatever you set it to needs to be what is registered and matches the IP address you have for the machine. In addition, the domain name needs to be correct in /etc/resolv.conf jerry Ivan On 3/28/07, Giorgos Keramidas [EMAIL PROTECTED] wrote: On 2007-03-27 23:36, Ivan Zenzerovi? [EMAIL PROTECTED] wrote: Hi guys, i managed to install it, and, in fact I'm working on it right now. It's great, just tell me, I should compile my kernel at this point? And a question: I don't like this xorg, and I have installed KDE but how do I run KDE? Right after your first FreeBSD installation, you are certainly *not* expected to rush into rebuilding a kernel, for any reason. In fact, this could be a dangerous exercise. It's far too easy to build a kernel which lacks critical components, and render your system unbootable (at least unbootable without manual intervention). Since you are new to the FreeBSD system, my suggestion would be to forget about rebuilding kernels, optimizing compiler flags, and tweaking knobs here and there. Now that you have a working FreeBSD installation you should *read* about the system you have just installed. There is a wealth of information about FreeBSD both in the CD-ROM set which you used to install it, and online. You should, at least, check the following: * The README.TXT file at the toplevel directory of your installation CD-ROM. * The web pages at http://www.FreeBSD.org/docs.html * The FreeBSD FAQ book, at http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/ The FAQ contains a lagre list of frequently asked questions about FreeBSD. You will find answers there about a very diverse range of topics, including such obscure things as ``I managed to trash by boot loader, what should I do now?''. * The FreeBSD Handbook, at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ The FreeBSD Handbook is the largest book written by the FreeBSD documentation team. It is both a guide for the beginning user, and a common reference for administrators setting up services with FreeBSD. Your answer about KDE vs. X11 is already answered in the Handbook. Note that a copy of the Handbook and all the articles, books and other reference material related to the FreeBSD release you have just installed, are also conveniently available in the CD-ROM you used to install FreeBSD. You can install them locally too, by logging in as root and running ``sysinstall'': # sysintall Follow the menus to add the ``doc'' distribution, and then you will have a copy of all the documentation articles and books at: /usr/share/doc Welcome to FreeBSD, and if you have other questions regarding its every day use and operation, feel free to email this list again :-) - Giorgos -- --- Correr, competir, eu levo isso no sangue, é parte da minha vida. - Ayrton Senna ___ 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: Problems with SMP on 6.1-STABLE-200608
Don O'Neil [EMAIL PROTECTED] writes: I've been having problems with my server freezing up, having the #2 CPU 'shut down', kernel panics, and all sorts of nastyness Originally I thought it was exim, or possibly bind, or bad hardware (mb, cpu or memory)... I've swapped out the motherboard CPU's memory from an old server that was running 4.11 ROCK SOLID for years... At first I thought the problem was solved, but now it's popping up again... The 2nd CPU gets 'shut down', or kernel panics, esentially taking the system offline. There are lots of things this could be, and I certainly wouldn't rule out hardware problems (power supply?). Figuring out the problems directly would certainly involve looking at more details than you're listing here. If I install a single CPU (non-smp) kernel, then the system works fine... (I did this on the old motherboard before I swapped it out, and it worked fine too).. So I'm wondering if there is an SMP bug or problem I'm running into. I'm running 6.1-STABLE-200608, an ISO image I downloaded from the archives when I built the box (NOT 6.1-RELEASE). The whole point of making releases is that it's much easier to support a small number of known reference software configurations. I'm runining an Intel Serverworks motherboard with 2 1.4 GHz PIII's... The problem only seems to show up under high load. I don't think I've heard of anything similar. I think there are a bunch of these boards out there. I'm wondering what I should do here... I'm concerned about doing a binary upgrade to 6.2 won't fix the problem, and I've tried using freebsd-update, but it complains about the version not being compatible. If I do a binary upgrade from CD, will it also update the kernel sources so I can build a new one? Will it complain about it not being compatible? It can give you the sources; that's a menu option during the install. That should work fine. Is there a way to 'force' the ID of the system to be 6.1-RELEASE so that freebsd-update will work? Well, yes, but there's a reason for the check, you know... Will doing the 6.1-6.2 binary upgrade as posted by Colin also update the kernel sources? I don't know what procedure he described, so I don't know. But if you update to 6.2-RELEASE, then it will be easy to get the right sources afterwards. Again, that is the advantage of having releases. Would my best option really be to start over with a fresh install rather than upgrade? (this would be painful) If it's that painful, you'd probably be well served to have a spare system to stage changes on. In addition to being good risk management, it saves you time, which is worth something too. I'm going to try to test out 6.2 on the old MB/CPU combo to see if I can re-create it under 6.2 as well before I do anything. As well as try doing an upgrade on the bench from CD from 6.1-STABLE-200608 to 6.2-RELEASE... Since this is a production server (and for months it was burned in with no apparent issues) I only have 1 shot at this to do it right. Any help/recomendation would be appreciated. Good luck. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sound on an amilo pro notebook
Ghirai [EMAIL PROTECTED] writes: I'm trying to get the sound working on a Fujitsu Siemens Amilo Pro v3205 notebook. The datasheet says i have a Conexant AMOM soundcard. I've tried all drivers, but /dev/sndstat doesn't report anything being installed. I'm running 6.2 x86. How do you know you tried all drivers? Did you load snd_driver? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New to FreeBSD
David J Brooks skrev: On Wednesday 28 March 2007 09:08:30 am Ivan Zenzerović wrote: hello again. I made a mistake during post install config. I put a name that I don't want for my computer, and when I logon as root it's written in the comand line. How di I change it? Ivan Edit /etc/rc.conf .. find the line hostname=wrong name and change it to the name you prefer. Maybe also edit /etc/hosts ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with SMP on 6.1-STABLE-200608
On Wed, 28 Mar 2007, Lowell Gilbert wrote: Don O'Neil [EMAIL PROTECTED] writes: I've been having problems with my server freezing up, having the #2 CPU 'shut down', kernel panics, and all sorts of nastyness Originally I thought it was exim, or possibly bind, or bad hardware (mb, cpu or memory)... I've swapped out the motherboard CPU's memory from an old server that was running 4.11 ROCK SOLID for years... At first I thought the problem was solved, but now it's popping up again... The 2nd CPU gets 'shut down', or kernel panics, esentially taking the system offline. There are lots of things this could be, and I certainly wouldn't rule out hardware problems (power supply?). Figuring out the problems directly would certainly involve looking at more details than you're listing here. If I install a single CPU (non-smp) kernel, then the system works fine... (I did this on the old motherboard before I swapped it out, and it worked fine too).. So I'm wondering if there is an SMP bug or problem I'm running into. I'm running 6.1-STABLE-200608, an ISO image I downloaded from the archives when I built the box (NOT 6.1-RELEASE). The whole point of making releases is that it's much easier to support a small number of known reference software configurations. I'm runining an Intel Serverworks motherboard with 2 1.4 GHz PIII's... The problem only seems to show up under high load. I don't think I've heard of anything similar. I think there are a bunch of these boards out there. I'm wondering what I should do here... I'm concerned about doing a binary upgrade to 6.2 won't fix the problem, and I've tried using freebsd-update, but it complains about the version not being compatible. If I do a binary upgrade from CD, will it also update the kernel sources so I can build a new one? Will it complain about it not being compatible? It can give you the sources; that's a menu option during the install. That should work fine. Is there a way to 'force' the ID of the system to be 6.1-RELEASE so that freebsd-update will work? Well, yes, but there's a reason for the check, you know... Will doing the 6.1-6.2 binary upgrade as posted by Colin also update the kernel sources? I don't know what procedure he described, so I don't know. But if you update to 6.2-RELEASE, then it will be easy to get the right sources afterwards. Again, that is the advantage of having releases. Would my best option really be to start over with a fresh install rather than upgrade? (this would be painful) If it's that painful, you'd probably be well served to have a spare system to stage changes on. In addition to being good risk management, it saves you time, which is worth something too. I'm going to try to test out 6.2 on the old MB/CPU combo to see if I can re-create it under 6.2 as well before I do anything. As well as try doing an upgrade on the bench from CD from 6.1-STABLE-200608 to 6.2-RELEASE... Since this is a production server (and for months it was burned in with no apparent issues) I only have 1 shot at this to do it right. Any help/recomendation would be appreciated. Good luck. Honestly I would probe around your motherboard a bit checking voltages (power supply) and/or heat dissipation, because those are the most likely cases if it _only_ fails under high load. Next thing to check would be RAM integrity. -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How Write To Win Drive?
Stan Cooper wrote: Kevin Kinsey [EMAIL PROTECTED] wrote: Stan Cooper wrote: Roland Smith wrote:Try /usr/ports/sysutils/fusefs-ntfs instead. It's newer and is supposed to support writing. Hmm. Well, there's no such port in FBSD. Are you certain? [EMAIL PROTECTED]/usr/ports] uname -s FreeBSD [EMAIL PROTECTED]/usr/ports] ll IN*6 -rw-r--r-- 1 root wheel 9888013 Feb 6 09:33 INDEX-6 [EMAIL PROTECTED]/usr/ports] ll sysutils/fusefs-ntfs total 1 -rw-r--r-- 1 root wheel 1075 Feb 20 21:25 Makefile -rw-r--r-- 1 root wheel 214 Feb 20 21:25 distinfo drwxr-xr-x 2 root wheel 512 Jan 21 02:09 files/ -rw-r--r-- 1 root wheel 354 Dec 5 16:56 pkg-descr -rw-r--r-- 1 root wheel 840 Dec 5 16:15 pkg-plist Geez, well I just copied your commands directly and, naturally, the first two went without a hitch, but the last one gave me No such file or directory, and yes, I did that from /usr/ports Well, hmm What was the date of the INDEX file? Where did your ports tree come from, and when was it last updated? I'd be willing to stick my neck out and boldly guess that it was prior to 6 Dec last year ;-) I built this system this year. So you'd think it'd be there, right? Built it how? With what installation media? What does uname -a say? The date of the build doesn't logically prove much. To play devil's advocate, if I built a 4.10 system from CD-ROM _yesterday_ and installed the ports collection from its CD, I'd not expect to find a port added 4 months ago. The certainty of the port's existence depends on other factors, and until we know more about your system/situation, we can't play Carnac the Magnificent. :-) I wouldn't know; but I'd try the port, because if it failed I might get some support from this community. Well, let's hope some help's forthcoming ;) Touche. I'm thinking that you may already be familiar with the Handbook's Chapter 4 --- I'd look also at Chapter 22 (The Cutting Edge) with the realization (and this might be a shortcoming of the book, but I've not done enough recent reading to say) that the process of updating your system (base system, that is, FreeBSD) shares a good many similarities with keeping the Ports Collection updated. If you have cvsup installed, take a look at the ports-supfile in /usr/share/examples/cvsup --- it shouldn't be too difficult to get a ports collection that contains this port. What may happen after that, I can't say --- YMMV, #include disclaimer.h and all that. Finally, here's a couple of classics from my Bookmark collection that deal with keeping ports up-to-date. AFAIK, they are still pretty applicable today, with the exception of the fact that portupgrade isn't the only way to do this anymore --- I think the first one (Dru Lavigne's article) has all the procedure in gory detail: http://www.onlamp.com/pub/a/bsd/2003/08/28/FreeBSD_Basics.html http://www.onlamp.com/pub/a/bsd/2001/11/29/Big_Scary_Daemons.html Hopefully this is at least a start at community support. :-) Best of luck, Kevin Kinsey -- If a man is not a liberal at 25, he has no heart. If he's not a conservative by 45, he has no brain. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hi
Jerry McAllister wrote: On Tue, Mar 27, 2007 at 09:39:10PM -0400, Drew White wrote: Hi Jerry, installed the system. Now getting a terrible message video input 'out of range' on both my monitors... one showsup partially distorted and the other not at all . It worked find on the friends monitor who installed it for me, so i guess its a difference in the monitor and nothe computer . Can you tell me how to get 'in range'? This is weird! Both normal monitors, out of the box! There is no such thing as a normal monitor. There are just monitors. Unless the two are the same make/model, you can't expect the configuration set up for Monitor A to work on Monitor B; which is why you have this problem. Ok, well, technically you could expect it to, but I'd predict disappointment about 50% of the time See the Handbook, Chapter 5, and specifically 5.4, X11 Configuration. If you can't use a X-enabled browser to do this, drop to console and try lynx (/usr/ports/www/lynx) from the command line. HTH, Kevin Kinsey -- We're happy little Vegemites, As bright as bright can be. We all enjoy our Vegemite For breakfast, lunch and tea. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How Write To Win Drive?
Kevin Kinsey wrote: Finally, here's a couple of classics from my Bookmark collection that deal with keeping ports up-to-date. AFAIK, they are still pretty applicable today, with the exception of the fact that portupgrade isn't the only way to do this anymore --- I think the first one (Dru Lavigne's article) has all the procedure in gory detail: http://www.onlamp.com/pub/a/bsd/2003/08/28/FreeBSD_Basics.html http://www.onlamp.com/pub/a/bsd/2001/11/29/Big_Scary_Daemons.html Hopefully this is at least a start at community support. :-) Best of luck, Kevin Kinsey use portsnap if you havent already updated your ports. its built in and very simple to use man portsnap to get started Eric ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Time changed back to old daylight savings
I mean 6.1-stable Uname shows: FreeBSD 6.1-STABLE-200608 #0 It was installed from a snapshot ISO last summer. -Original Message- From: Kris Kennaway [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 28, 2007 1:05 AM To: Don O'Neil Cc: freebsd-questions@freebsd.org Subject: Re: Time changed back to old daylight savings On Wed, Mar 28, 2007 at 12:45:11AM -0700, Don O'Neil wrote: I'm not sure when this happened, but I noticed today that my server reverted back to the old daylight savings time (1 hour off) When I run ntpdate and have it update it even then it shows the wrong time. I haven't done anything to replace the /etc/localtime file, even tried running tzsetup again, but that still didn't help. My system is FreeBSD 6.1-stable, the only thing that has changed since I last noticed the system had the _right_ time was I built a new kernel. There is no such thing as 6.1-stable any more, so what do you really mean? Kris I tried installing the port 'zoneinfo', but it's broken, it can't find the appropriate file to download and install (seems to be missing or updated). At the moment I've addressed the issue with a date -v +1H. Any reason this would happen? How do I fix it? ___ 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: Time changed back to old daylight savings
Well, since I didn't install it from source, but a snapshot, I don't have the northamerica source to get an MD5 # on. Isn't there some other way to update the zone info files to fix this? -Original Message- From: Jonathan Chen [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 28, 2007 1:03 AM To: Don O'Neil Cc: freebsd-questions@freebsd.org Subject: Re: Time changed back to old daylight savings On Wed, Mar 28, 2007 at 12:45:11AM -0700, Don O'Neil wrote: I'm not sure when this happened, but I noticed today that my server reverted back to the old daylight savings time (1 hour off) When I run ntpdate and have it update it even then it shows the wrong time. This tends to indicate the your /etc/localtime file is wrong. The timeservers all return UTC; the display for the date consults /etc/localtime to display UTC time in local time. I haven't done anything to replace the /etc/localtime file, even tried running tzsetup again, but that still didn't help. This indicates that your zoneinfo files have not been updated correctly. [...] At the moment I've addressed the issue with a date -v +1H. Which definitely isn't the correct fix. Any reason this would happen? How do I fix it? What does md5 /usr/src/share/zoneinfo/northamerica return? (I'm assuming that you're in North America). On my 6-STABLE machine it's: MD5 (/usr/src/share/zoneinfo/northamerica) = 3e582e371f445a18b065eed8f775fb20 Any other result means that your should re-cvsup, and rebuild your system again. If it is the same, make sure your zoneinfo files have been rebuilt (check the file timestamps). Cheers. -- Jonathan Chen [EMAIL PROTECTED]Once is dumb luck. Twice is coincidence. Three times and Somebody Is Trying To Tell You Something. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: the art of pkgdb -F
Jeffrey Goldberg wrote:
On Mar 27, 2007, at 8:34 PM, Josh Carroll wrote:
Stale dependency: p5-Authen-SASL-2.09 - p5-GSSAPI-0.24
(security/p5-GSSAPI):
p5-Geography-Countries-1.4 (score:26%) ? ([y]es/[n]o/[a]ll) [no]
Well this one is pretty obvious. Look at what the stale dependency is,
and what it's suggesting? :)
To me it is entirely unclear. First of all, I don't know what stale
dependency is supposed to mean. Second, I don't know what score
means, and finally, I don't know what the question is that I'm to answer
yes, no or all to.
I could attempt, but it's easier to type See below.
So I've just taken to running with -Fa and hope for the best (and so far
everything has worked).
This makes you pretty normal, I expect.
If the answers to these questions are in the man page for pkgdb, I
apologize, but I haven't found them there.
Here is a time-honored and rather canonical diatribe on The Art of
Pkgdb -F (a great thread title, BTW). Note also that it is nearly
six years old, and that additional package-management tools have been
proposed, created, and released to the public, and some may have already
been EOL'ed and buried, but the rest of them aren't considered standard
by any means, and currently the FreeBSD world is in a pseudo-Biblical
every man did as he saw fit state these days[1].
http://www.onlamp.com/pub/a/bsd/2001/11/29/Big_Scary_Daemons.html
Of course, (and here's a rather large can of worms), there weren't {m?}any
alternatives back in the day, the the tools that are 'officially' documented
became standard more or less by default. (and, come to think of it, are
they at all, if so, where, etc., etc.)
HTH, `cat flames /dev/null 21`,
Kevin Kinsey
[1] Since the punishment for these transgressions is basically just
a temporal make deinstall under /usr/ports followed by 2-4 days of
rebuilding, (more if KDE/GNOME is installed, but not much as opposed
to eternal flame/torment), I suppose it's OK to let everybody fend
for themselves with whatever tool they like best. One thing you'll
notice about the BSDs is that since they are traditional Unix-like
systems, a lot of folks stick to traditions pretty closely.
--
You need no longer worry about the future.
This time tomorrow you'll be dead.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Time changed back to old daylight savings
Don O'Neil wrote: Well, since I didn't install it from source, but a snapshot, I don't have the northamerica source to get an MD5 # on. Isn't there some other way to update the zone info files to fix this? The failed download is because the source file changed at the external source. You might hack the Makefile to read c instead of b (or whatnot) on that file and have the port work, although you might then have verification problems. The other way was discussed recently on the list. Search the archives, late February, early March. Good luck, Kevin Kinsey -- The devil can cite Scripture for his purpose. -- William Shakespeare, The Merchant of Venice ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Time changed back to old daylight savings
Don O'Neil wrote: Well, since I didn't install it from source, but a snapshot, I don't have the northamerica source to get an MD5 # on. Sorry, you could also update your ports tree and install the port. KDK -- The devil can cite Scripture for his purpose. -- William Shakespeare, The Merchant of Venice ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
iwi-firmware port
Hey all, I installed the iwi-firmware and iwi-firmware-kmod ports and I am now trying to load specific firmware on the iwi adapter but it keeps failing. The port installs fine and puts the firmware to /boot/firmware. The docs for iwicontrol state to load firmware for a specific function issue a: iwicontrol -i iwi0 -d /boot/firmware -m bss Every time I issue that command I get an error saying it cannot load firmware: Invalid argument. The system is FreeBSD 6.2 with an Intel PRO Wireless 2200BG adapter. I have the most up to date stable source and ports tree. I also tried the ipw-firmware port but that did not pick up my adapter when I loaded the kernel module. Any ideas? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hi
On 28/03/07, Jerry McAllister [EMAIL PROTECTED] wrote: On Tue, Mar 27, 2007 at 09:39:10PM -0400, Drew White wrote: Hi Jerry, installed the system. Now getting a terrible message video input 'out of range' on both my monitors... one showsup partially distorted and the other not at all . It worked find on the friends monitor who installed it for me, so i guess its a difference in the monitor and nothe computer . Can you tell me how to get 'in range'? This is weird! Both normal monitors, out of the box! Please do not post questions back to me personally. It is considered to be very bad Email list etiquette. Post them to the questions list. That is the proper way. The second reason, besides etiquette is that the single person may well not know the answer and you are cutting yourself short by not posting to the list. The thrydde reason being that should someone wish to search for answers through the archive, the whole conversation will be there, failures, followups, (likely) correct answers, and all. As for the monitor, you can try hand editing your /etc/X11/xorg.conf (or whichever you may be using) and changing the sync ranges to match yours. A fair database can be found at: http://monitorworld.com/monitors_home.html -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New to FreeBSD
Thanks, i managed to fix this by running the post install configuration with sysinstall. But I have another problem. Every time i start the system my soundcard won't work. I must tipe kldload snd_driver and then logoff and again logon in kde to get my soundcard working. How can i fix this? Ivan On 3/28/07, Jerry McAllister [EMAIL PROTECTED] wrote: On Wed, Mar 28, 2007 at 04:08:30PM +0200, Ivan Zenzerovi? wrote: hello again. I made a mistake during post install config. I put a name that I don't want for my computer, and when I logon as root it's written in the comand line. How di I change it? Presuming by that that you mean your hostname, then that is set in /etc/rc.conf -- look for the hostname command and edit it. It is best if it has the fully qualified hostname including domain, not just the first (left-most) element of it. If you are using this machine on the net, then that hostname has to be registered with who-ever is providing DNS for you. So, whatever you set it to needs to be what is registered and matches the IP address you have for the machine. In addition, the domain name needs to be correct in /etc/resolv.conf jerry Ivan On 3/28/07, Giorgos Keramidas [EMAIL PROTECTED] wrote: On 2007-03-27 23:36, Ivan Zenzerovi? [EMAIL PROTECTED] wrote: Hi guys, i managed to install it, and, in fact I'm working on it right now. It's great, just tell me, I should compile my kernel at this point? And a question: I don't like this xorg, and I have installed KDE but how do I run KDE? Right after your first FreeBSD installation, you are certainly *not* expected to rush into rebuilding a kernel, for any reason. In fact, this could be a dangerous exercise. It's far too easy to build a kernel which lacks critical components, and render your system unbootable (at least unbootable without manual intervention). Since you are new to the FreeBSD system, my suggestion would be to forget about rebuilding kernels, optimizing compiler flags, and tweaking knobs here and there. Now that you have a working FreeBSD installation you should *read* about the system you have just installed. There is a wealth of information about FreeBSD both in the CD-ROM set which you used to install it, and online. You should, at least, check the following: * The README.TXT file at the toplevel directory of your installation CD-ROM. * The web pages at http://www.FreeBSD.org/docs.html * The FreeBSD FAQ book, at http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/ The FAQ contains a lagre list of frequently asked questions about FreeBSD. You will find answers there about a very diverse range of topics, including such obscure things as ``I managed to trash by boot loader, what should I do now?''. * The FreeBSD Handbook, at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ The FreeBSD Handbook is the largest book written by the FreeBSD documentation team. It is both a guide for the beginning user, and a common reference for administrators setting up services with FreeBSD. Your answer about KDE vs. X11 is already answered in the Handbook. Note that a copy of the Handbook and all the articles, books and other reference material related to the FreeBSD release you have just installed, are also conveniently available in the CD-ROM you used to install FreeBSD. You can install them locally too, by logging in as root and running ``sysinstall'': # sysintall Follow the menus to add the ``doc'' distribution, and then you will have a copy of all the documentation articles and books at: /usr/share/doc Welcome to FreeBSD, and if you have other questions regarding its every day use and operation, feel free to email this list again :-) - Giorgos -- --- Correr, competir, eu levo isso no sangue, é parte da minha vida. - Ayrton Senna ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- --- Correr, competir, eu levo isso no sangue, é parte da minha vida. - Ayrton Senna ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Time changed back to old daylight savings
Ok, Thanks to Paul who sent me the previous tzdata file I was able to download the port and install it... However that didn't solve the problem! Here's my output from the make/make install: make install === Installing for zoneinfo-2007.c === Generating temporary packing list === Checking if misc/zoneinfo already installed /bin/mkdir -p /usr/share/zoneinfo /bin/cp -R -p /home/don/zoneinfo/work/zoneinfo/ /usr/share/zoneinfo install -o root -g wheel -m 444 /home/don/zoneinfo/work/zone.tab /usr/share/zon einfo Now run tzsetup(8) again to install the right file to /etc/localtime. === Registering installation for zoneinfo-2007.c kermit# date Wed Mar 28 09:37:23 PDT 2007 kermit# /usr/sbin/ntpdate -v -b 0.us.pool.ntp.org 28 Mar 09:37:27 ntpdate[52308]: ntpdate 4.2.0-a Mon Aug 7 17:44:27 UTC 2006 (1) 28 Mar 09:37:29 ntpdate[52308]: step time server 204.186.233.118 offset 3583.019 I ran tzsetup and then ran ntpdate. It was 10:37 when I ran ntpdate Not 9:37. This is strange... Any more ideas? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Time changed back to old daylight savings
On Wed, Mar 28, 2007 at 09:11:27AM -0700, Don O'Neil wrote: I mean 6.1-stable Uname shows: FreeBSD 6.1-STABLE-200608 #0 It was installed from a snapshot ISO last summer. OK, so you're running an 8 month stale snapshot and you wonder why you don't have the recent timezone updates? What is wrong with this picture? :-) Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Time changed back to old daylight savings
PDT, as it shows. _ From: Paul Khavkine [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 28, 2007 10:51 AM To: Don O'Neil Cc: freebsd-questions@freebsd.org Subject: Re: Time changed back to old daylight savings Hi Don. What timezone are you supposed to be in ? Paul On 3/28/07, Don O'Neil mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Ok, Thanks to Paul who sent me the previous tzdata file I was able to download the port and install it... However that didn't solve the problem! Here's my output from the make/make install: make install === Installing for zoneinfo-2007.c === Generating temporary packing list === Checking if misc/zoneinfo already installed /bin/mkdir -p /usr/share/zoneinfo /bin/cp -R -p /home/don/zoneinfo/work/zoneinfo/ /usr/share/zoneinfo install -o root -g wheel -m 444 /home/don/zoneinfo/work/zone.tab /usr/share/zon einfo Now run tzsetup(8) again to install the right file to /etc/localtime. === Registering installation for zoneinfo-2007.c kermit# date Wed Mar 28 09:37:23 PDT 2007 kermit# /usr/sbin/ntpdate -v -b 0.us.pool.ntp.org 28 Mar 09:37:27 ntpdate[52308]: ntpdate 4.2.0-a Mon Aug 7 17:44:27 UTC 2006 (1) 28 Mar 09:37:29 ntpdate[52308]: step time server 204.186.233.118 offset 3583.019 I ran tzsetup and then ran ntpdate. It was 10:37 when I ran ntpdate Not 9:37. This is strange... Any more ideas? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions 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: Time changed back to old daylight savings
Well... If you read about the original timezone issue it was fixed in 6.1-release, so any snapshot AFTER that shouldn't have the problem... And I'll re-itterate that it WAS working fine until I recently re-built the kernel. Even with the timezone port update installed it is still wrong. -Original Message- From: Kris Kennaway [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 28, 2007 10:49 AM To: Don O'Neil Cc: 'Kris Kennaway'; freebsd-questions@freebsd.org Subject: Re: Time changed back to old daylight savings On Wed, Mar 28, 2007 at 09:11:27AM -0700, Don O'Neil wrote: I mean 6.1-stable Uname shows: FreeBSD 6.1-STABLE-200608 #0 It was installed from a snapshot ISO last summer. OK, so you're running an 8 month stale snapshot and you wonder why you don't have the recent timezone updates? What is wrong with this picture? :-) Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Time changed back to old daylight savings
It was installed from a snapshot ISO last summer. OK, so you're running an 8 month stale snapshot and you wonder why you don't have the recent timezone updates? What is wrong with this picture? :-) Kris Not to be a smartass, but the energy conservation act was passed in 2005, so one would think an 8 month old snapshot would include a fix that has been known about for 2 years ;) Jeff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Time changed back to old daylight savings
Hi Don. What timezone are you supposed to be in ? Paul On 3/28/07, Don O'Neil [EMAIL PROTECTED] wrote: Ok, Thanks to Paul who sent me the previous tzdata file I was able to download the port and install it... However that didn't solve the problem! Here's my output from the make/make install: make install === Installing for zoneinfo-2007.c === Generating temporary packing list === Checking if misc/zoneinfo already installed /bin/mkdir -p /usr/share/zoneinfo /bin/cp -R -p /home/don/zoneinfo/work/zoneinfo/ /usr/share/zoneinfo install -o root -g wheel -m 444 /home/don/zoneinfo/work/zone.tab /usr/share/zon einfo Now run tzsetup(8) again to install the right file to /etc/localtime. === Registering installation for zoneinfo-2007.c kermit# date Wed Mar 28 09:37:23 PDT 2007 kermit# /usr/sbin/ntpdate -v -b 0.us.pool.ntp.org 28 Mar 09:37:27 ntpdate[52308]: ntpdate 4.2.0-a Mon Aug 7 17:44:27 UTC 2006 (1) 28 Mar 09:37:29 ntpdate[52308]: step time server 204.186.233.118 offset 3583.019 I ran tzsetup and then ran ntpdate. It was 10:37 when I ran ntpdate Not 9:37. This is strange... Any more ideas? ___ 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: Time changed back to old daylight savings
On Wed, Mar 28, 2007 at 02:12:42PM -0400, Jeff Palmer wrote: It was installed from a snapshot ISO last summer. OK, so you're running an 8 month stale snapshot and you wonder why you don't have the recent timezone updates? What is wrong with this picture? :-) Kris Not to be a smartass, but the energy conservation act was passed in 2005, so one would think an 8 month old snapshot would include a fix that has been known about for 2 years ;) One might hope or guess that, but it would be in contradiction to the facts, and the published advisories. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Help
Hi! I want to play FreeBSD image with my VM player how can i do it? Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New to FreeBSD
Ivan Zenzerović wrote: Thanks, i managed to fix this by running the post install configuration with sysinstall. But I have another problem. Every time i start the system my soundcard won't work. I must tipe kldload snd_driver and then logoff and again logon in kde to get my soundcard working. How can i fix this? In short, add: snd_driver_load=YES to /boot/loader.conf. However, it'd be better to figure out which of the umpty-leven drivers is really being used, and only load it. See snd(4) for more details. Kevin Kinsey -- Don't knock President Fillmore. He kept us out of Vietnam. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Time changed back to old daylight savings
On Wed, Mar 28, 2007 at 11:02:33AM -0700, Don O'Neil wrote: Well... If you read about the original timezone issue it was fixed in 6.1-release Um, no. Where did you read that? Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Time changed back to old daylight savings
To see if you zonefile is correct you can do the following: %zdump -v /etc/localtime | grep 2007 /etc/localtime Sun Mar 11 06:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 EST isdst=0 gmtoff=-18000 /etc/localtime Sun Mar 11 07:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 EDT isdst=1 gmtoff=-14400 /etc/localtime Sun Nov 4 05:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 EDT isdst=1 gmtoff=-14400 /etc/localtime Sun Nov 4 06:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 EST isdst=0 gmtoff=-18000 On 3/28/07, Jeff Palmer [EMAIL PROTECTED] wrote: It was installed from a snapshot ISO last summer. OK, so you're running an 8 month stale snapshot and you wonder why you don't have the recent timezone updates? What is wrong with this picture? :-) Kris Not to be a smartass, but the energy conservation act was passed in 2005, so one would think an 8 month old snapshot would include a fix that has been known about for 2 years ;) Jeff ___ 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: New to FreeBSD
On 2007-03-28 19:43, Ivan Zenzerovi? [EMAIL PROTECTED] wrote: Thanks, i managed to fix this by running the post install configuration with sysinstall. But I have another problem. Every time i start the system my soundcard won't work. I must tipe kldload snd_driver and then logoff and again logon in kde to get my soundcard working. How can i fix this? Add the line: snd_driver_load=YES in your /boot/loader.conf file. This way the kernel will preload the sound driver modules when it boots, and you won't have to load them manually. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Time changed back to old daylight savings
Don O'Neil [EMAIL PROTECTED] writes: Ok, Thanks to Paul who sent me the previous tzdata file I was able to download the port and install it... However that didn't solve the problem! Here's my output from the make/make install: make install === Installing for zoneinfo-2007.c === Generating temporary packing list === Checking if misc/zoneinfo already installed /bin/mkdir -p /usr/share/zoneinfo /bin/cp -R -p /home/don/zoneinfo/work/zoneinfo/ /usr/share/zoneinfo install -o root -g wheel -m 444 /home/don/zoneinfo/work/zone.tab /usr/share/zon einfo Now run tzsetup(8) again to install the right file to /etc/localtime. === Registering installation for zoneinfo-2007.c kermit# date Wed Mar 28 09:37:23 PDT 2007 kermit# /usr/sbin/ntpdate -v -b 0.us.pool.ntp.org 28 Mar 09:37:27 ntpdate[52308]: ntpdate 4.2.0-a Mon Aug 7 17:44:27 UTC 2006 (1) 28 Mar 09:37:29 ntpdate[52308]: step time server 204.186.233.118 offset 3583.019 I ran tzsetup and then ran ntpdate. It was 10:37 when I ran ntpdate Not 9:37. This is strange... Any more ideas? You didn't update your ports tree before installing the port, I'll bet. That was an essential part of the advice that Kevin Kinsey gave you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
How to get watchdogd from biting me!?
Hi, I'm starting it with : watchdogd -s 15 -t 120 -e logger I'm gonna hurl And sometimes within a few minutes it reboots, and other times its hours... But at no time was the system inactive (I've been on it 3 of 4 reboots) and its never logged that for me either. What am I doing wrong?? Thanks, Tuc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
fsck fails on 6T system
I am trying to fsck a 6T filesystem on a server that crashed. I'm running FreeBSD 6.2-p3. # fsck -t ufs -y /dev/da0 fsck_ufs: cannot alloc 1993797728 bytes for inoinfo I also tried: # fsck -t ufs -f -p /dev/da0 /dev/da0: UNKNOWN FILE TYPE I=11895232 /dev/da0: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. I built a custom kernel with MAXDSIZ and DFLDSIZ just under 3G, and got the same results. It was at about 430M in use when it crashed, so the total would be 2332 M which is less that the size allowed (reported by limits). I found an old bug report from 2004 that is still open, but nothing has been done. I also found an old article about someone (thinking about) rewriting fsck to use disk instead of memory, but no follow-up. Has anyone found a solution to this? Any suggestions? HELP! Thanks, Dan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Time changed back to old daylight savings
http://www.freebsd.org/releng/dst_info.html FreeBSD-6.1 has correct zoneinfo files for time zones in the United States of America -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kris Kennaway Sent: Wednesday, March 28, 2007 11:06 AM To: Don O'Neil Cc: freebsd-questions@freebsd.org; 'Kris Kennaway' Subject: Re: Time changed back to old daylight savings On Wed, Mar 28, 2007 at 11:02:33AM -0700, Don O'Neil wrote: Well... If you read about the original timezone issue it was fixed in 6.1-release Um, no. Where did you read that? Kris ___ 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]
Can iostat(8) report on gmirror devices?
Hello, I've grown quite fond of iostat(8) for monitoring various i386 6.x servers and have several boxes using gmirror(8). It appears that iostat will not accept things like gm0 as a drive argument. Is that a feature or am I missing something. -- Regards, Doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Time changed back to old daylight savings
I don't have the port tree installed, so you are correct that I did not update them first... I installed JUST the zoneinfo port, which according to: http://www.freebsd.org/releng/dst_info.html the misc/zoneinfo port can be installed to update the /usr/share/zoneinfo files, followed by running tzsetup(8) to update /etc/localtime So why wouldn't installing this port fix the problem like advertised? I shouldn't even have the problem to begin with... When the time change happened a few weeks ago my system updated correctly, but since then I've built a new kernel (the only thing I've done) and now it's not right. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lowell Gilbert Sent: Wednesday, March 28, 2007 11:08 AM To: Don O'Neil Cc: freebsd-questions@freebsd.org Subject: Re: Time changed back to old daylight savings Don O'Neil [EMAIL PROTECTED] writes: Ok, Thanks to Paul who sent me the previous tzdata file I was able to download the port and install it... However that didn't solve the problem! Here's my output from the make/make install: make install === Installing for zoneinfo-2007.c === Generating temporary packing list === Checking if misc/zoneinfo already installed /bin/mkdir -p /usr/share/zoneinfo /bin/cp -R -p /home/don/zoneinfo/work/zoneinfo/ /usr/share/zoneinfo install -o root -g wheel -m 444 /home/don/zoneinfo/work/zone.tab /usr/share/zon einfo Now run tzsetup(8) again to install the right file to /etc/localtime. === Registering installation for zoneinfo-2007.c kermit# date Wed Mar 28 09:37:23 PDT 2007 kermit# /usr/sbin/ntpdate -v -b 0.us.pool.ntp.org 28 Mar 09:37:27 ntpdate[52308]: ntpdate 4.2.0-a Mon Aug 7 17:44:27 UTC 2006 (1) 28 Mar 09:37:29 ntpdate[52308]: step time server 204.186.233.118 offset 3583.019 I ran tzsetup and then ran ntpdate. It was 10:37 when I ran ntpdate Not 9:37. This is strange... Any more ideas? You didn't update your ports tree before installing the port, I'll bet. That was an essential part of the advice that Kevin Kinsey gave you. ___ 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: Time changed back to old daylight savings
Yup... thats what I get: %zdump -v /etc/localtime | grep 2007 /etc/localtime Sun Mar 11 09:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 PST isdst=0 gmtoff=-28800 /etc/localtime Sun Mar 11 10:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 PDT isdst=1 gmtoff=-25200 /etc/localtime Sun Nov 4 08:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 PDT isdst=1 gmtoff=-25200 /etc/localtime Sun Nov 4 09:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 PST isdst=0 gmtoff=-28800 So it looks like my zone info files are correct... could the ntp pool be off for some reason, or does ntpdate need to be updated? 28 Mar 10:53:51 ntpdate[90706]: ntpdate 4.2.0-a Mon Aug 7 17:44:27 UTC 2006 (1) _ From: Paul Khavkine [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 28, 2007 11:31 AM To: Jeff Palmer Cc: Kris Kennaway; Don O'Neil; freebsd-questions@freebsd.org Subject: Re: Time changed back to old daylight savings To see if you zonefile is correct you can do the following: %zdump -v /etc/localtime | grep 2007 /etc/localtime Sun Mar 11 06:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 EST isdst=0 gmtoff=-18000 /etc/localtime Sun Mar 11 07:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 EDT isdst=1 gmtoff=-14400 /etc/localtime Sun Nov 4 05:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 EDT isdst=1 gmtoff=-14400 /etc/localtime Sun Nov 4 06:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 EST isdst=0 gmtoff=-18000 On 3/28/07, Jeff Palmer [EMAIL PROTECTED] wrote: It was installed from a snapshot ISO last summer. OK, so you're running an 8 month stale snapshot and you wonder why you don't have the recent timezone updates? What is wrong with this picture? :-) Kris Not to be a smartass, but the energy conservation act was passed in 2005, so one would think an 8 month old snapshot would include a fix that has been known about for 2 years ;) Jeff ___ 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: Time changed back to old daylight savings
Pacific, which is what my date output shows: Wed Mar 28 10:55:26 PDT 2007 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Khavkine Sent: Wednesday, March 28, 2007 10:51 AM To: Don O'Neil Cc: freebsd-questions@freebsd.org Subject: Re: Time changed back to old daylight savings Hi Don. What timezone are you supposed to be in ? Paul On 3/28/07, Don O'Neil [EMAIL PROTECTED] wrote: Ok, Thanks to Paul who sent me the previous tzdata file I was able to download the port and install it... However that didn't solve the problem! Here's my output from the make/make install: make install === Installing for zoneinfo-2007.c === Generating temporary packing list === Checking if misc/zoneinfo already installed /bin/mkdir -p /usr/share/zoneinfo /bin/cp -R -p /home/don/zoneinfo/work/zoneinfo/ /usr/share/zoneinfo install -o root -g wheel -m 444 /home/don/zoneinfo/work/zone.tab /usr/share/zon einfo Now run tzsetup(8) again to install the right file to /etc/localtime. === Registering installation for zoneinfo-2007.c kermit# date Wed Mar 28 09:37:23 PDT 2007 kermit# /usr/sbin/ntpdate -v -b 0.us.pool.ntp.org 28 Mar 09:37:27 ntpdate[52308]: ntpdate 4.2.0-a Mon Aug 7 17:44:27 UTC 2006 (1) 28 Mar 09:37:29 ntpdate[52308]: step time server 204.186.233.118 offset 3583.019 I ran tzsetup and then ran ntpdate. It was 10:37 when I ran ntpdate Not 9:37. This is strange... Any more ideas? ___ 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] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Time changed back to old daylight savings
Well AFAIK, the recent changes only affect EST/EDT and not the PDT timezone. Paul On 3/28/07, Don O'Neil [EMAIL PROTECTED] wrote: PDT, as it shows. -- *From:* Paul Khavkine [mailto:[EMAIL PROTECTED] *Sent:* Wednesday, March 28, 2007 10:51 AM *To:* Don O'Neil *Cc:* freebsd-questions@freebsd.org *Subject:* Re: Time changed back to old daylight savings Hi Don. What timezone are you supposed to be in ? Paul On 3/28/07, Don O'Neil [EMAIL PROTECTED] wrote: Ok, Thanks to Paul who sent me the previous tzdata file I was able to download the port and install it... However that didn't solve the problem! Here's my output from the make/make install: make install === Installing for zoneinfo-2007.c === Generating temporary packing list === Checking if misc/zoneinfo already installed /bin/mkdir -p /usr/share/zoneinfo /bin/cp -R -p /home/don/zoneinfo/work/zoneinfo/ /usr/share/zoneinfo install -o root -g wheel -m 444 /home/don/zoneinfo/work/zone.tab /usr/share/zon einfo Now run tzsetup(8) again to install the right file to /etc/localtime. === Registering installation for zoneinfo-2007.c kermit# date Wed Mar 28 09:37:23 PDT 2007 kermit# /usr/sbin/ntpdate -v -b 0.us.pool.ntp.org 28 Mar 09:37:27 ntpdate[52308]: ntpdate 4.2.0-a Mon Aug 7 17:44:27 UTC 2006 (1) 28 Mar 09:37:29 ntpdate[52308]: step time server 204.186.233.118 offset 3583.019 I ran tzsetup and then ran ntpdate. It was 10:37 when I ran ntpdate Not 9:37. This is strange... Any more ideas? ___ 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: Time changed back to old daylight savings
On Wed, Mar 28, 2007 at 11:47:39AM -0700, Don O'Neil wrote: http://www.freebsd.org/releng/dst_info.html FreeBSD-6.1 has correct zoneinfo files for time zones in the United States of America OK, yes you are right. I was confused by your statement that 6.1 shipped with fixed timezone files, since it did not [unless you only care about the U.S.] :) Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New to FreeBSD
Ivan Zenzerović [EMAIL PROTECTED] writes: Thanks, i managed to fix this by running the post install configuration with sysinstall. But I have another problem. Every time i start the system my soundcard won't work. I must tipe kldload snd_driver and then logoff and again logon in kde to get my soundcard working. How can i fix this? Use loader.conf(5). This is covered in the handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/sound-setup.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Time changed back to old daylight savings
On Mar 28, 2007, at 11:53 AM, Don O'Neil wrote: So it looks like my zone info files are correct... could the ntp pool be off for some reason, or does ntpdate need to be updated? 28 Mar 10:53:51 ntpdate[90706]: ntpdate 4.2.0-a Mon Aug 7 17:44:27 UTC 2006 (1) Nope, the NTP protocol uses GMT (or UTC, if you prefer that name) exclusively. However, once you've updated the timezone files, you either need to restart all of the processes which have cached the old TZ file info, or simply reboot. You might find running ntpdate -b to reset your clock once before starting ntpd will help correctly sync if your local clock is one hour off (depends on whether your BIOS is trying to keep local time or GMT time)...see man adjkerntz. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help with port that uses scons
On Wed, 28 Mar 2007, Alejandro Pulver wrote: Hello. I am updating a port that now uses scons to build. It reads the environment variables correctly, but passes CCFLAGS as a single argument to the compiler, resulting in an error. The port (the install part isn't done yet) is available here: http://people.freebsd.org/~alepulver/boswars.shar Any help would be appreciated. Thanks and Best Regards, Ale If the last line is your problem with SCONS_ARGS, stuff isn't passed in quoted, and IIRC CPPFLAGS should be CXXFLAGS for all applications (I could be wrong about scons though..). -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help with port that uses scons
On Wed, 28 Mar 2007 [EMAIL PROTECTED] wrote: On Wed, 28 Mar 2007, Alejandro Pulver wrote: Hello. I am updating a port that now uses scons to build. It reads the environment variables correctly, but passes CCFLAGS as a single argument to the compiler, resulting in an error. The port (the install part isn't done yet) is available here: http://people.freebsd.org/~alepulver/boswars.shar Any help would be appreciated. Thanks and Best Regards, Ale If the last line is your problem with SCONS_ARGS, stuff isn't passed in quoted, and IIRC CPPFLAGS should be CXXFLAGS for all applications (I could be wrong about scons though..). -Garrett That's what I get for answering questions on multiple lists on 5 hours sleep. Reduced response time . -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: the art of pkgdb -F
On Wed, 28 Mar 2007 00:19:47 -0500 [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Obviously, as I am not about to batter you about the neck and head with the beam projecting from my eye (hold still, you've got a . . .), I can only suggest a decent cringepray manouver (as I execute from time to time), and a stout attempt to wean oneself off, albeit % portupgrade -fr blorf* is quite seductive, nearly doubly so when blorf* is actually gettext.arg.bah. ports-mgmt/portmaster disposes with the hairy databases and leering dependancies at the cost of being slightly less . . . err, come to think of it, after a bit of man page perusal I cannot think of anything that I use portupgrade for that portmaster seems to be missing. YMMV as usual. The gettext upgrade is actually a good example of what portupgrade offers. With portupgrade the -rf option is advisable, but not essential, with portmaster, it's essential that the -r option is used, If it's not, or the upgrade fails to complete, you can end-up with not much more than the base-system working. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Why is 'disklabel'ng a new drive so difficult?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Just bought a new WD SATA drive: WDC WD5000YS-01MPB1 09.02E09 Tried to disklabel it, and it gives me all kinds of warnings when I look at it after running the disklabel: ganymede# bsdlabel -w ad4s1 auto ganymede# bsdlabel ad4s1c # /dev/ad4s1c: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 976767986 79unused0 0 c: 976768002 63unused0 0 # raw part, don't edit partition a: partition extends past end of unit partition c: partition extends past end of unit bsdlabel: partition c doesn't start at 0! bsdlabel: An incorrect partition c may cause problems for standard system utilities Even if I try to use /stand/sysinstall to do the fdisk, the end result has 'issues' ... So, what is the generally accepted method of label'ng a new drive? :( - Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFGCs+Q4QvfyHIvDvMRAmTBAJwMJeMPTiJEDHWzA3ffe/YnVvRdgwCfVkBt YsPlRNHb6p3WJSIqMXA1K78= =n8pH -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why is 'disklabel'ng a new drive so difficult?
On Wed, Mar 28, 2007 at 05:26:49PM -0300, Marc G. Fournier wrote: Just bought a new WD SATA drive: WDC WD5000YS-01MPB1 09.02E09 Tried to disklabel it, and it gives me all kinds of warnings when I look at it after running the disklabel: ganymede# bsdlabel -w ad4s1 auto ganymede# bsdlabel ad4s1c # /dev/ad4s1c: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 976767986 79unused0 0 c: 976768002 63unused0 0 # raw part, don't edit partition a: partition extends past end of unit partition c: partition extends past end of unit bsdlabel: partition c doesn't start at 0! bsdlabel: An incorrect partition c may cause problems for standard system utilities Even if I try to use /stand/sysinstall to do the fdisk, the end result has 'issues' ... So, what is the generally accepted method of label'ng a new drive? :( I learned a useful trick the other day: you can use abbreviations like 1g, also '*' to mean automatically calculate. See the manpage. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why is 'disklabel'ng a new drive so difficult?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - --On Wednesday, March 28, 2007 16:41:28 -0400 Kris Kennaway [EMAIL PROTECTED] wrote: On Wed, Mar 28, 2007 at 05:26:49PM -0300, Marc G. Fournier wrote: Just bought a new WD SATA drive: WDC WD5000YS-01MPB1 09.02E09 Tried to disklabel it, and it gives me all kinds of warnings when I look at it after running the disklabel: ganymede# bsdlabel -w ad4s1 auto ganymede# bsdlabel ad4s1c # /dev/ad4s1c: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 976767986 79unused0 0 c: 976768002 63unused0 0 # raw part, don't edit partition a: partition extends past end of unit partition c: partition extends past end of unit bsdlabel: partition c doesn't start at 0! bsdlabel: An incorrect partition c may cause problems for standard system utilities Even if I try to use /stand/sysinstall to do the fdisk, the end result has 'issues' ... So, what is the generally accepted method of label'ng a new drive? :( I learned a useful trick the other day: you can use abbreviations like 1g, also '*' to mean automatically calculate. See the manpage. Neat, that seems to do it ... but, shouldn't that be disklabel's default behaviour be for the initial -w operation? Thanks though, seems to have worked great ... - Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFGCtSQ4QvfyHIvDvMRAtCwAJ9JxiON1i8EvHjJcB4On3usQ5YGbwCbBpKv JI8xirWGrOpDdDqdytuc5pU= =MU77 -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why is 'disklabel'ng a new drive so difficult?
On 28/03/07, Marc G. Fournier [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Just bought a new WD SATA drive: WDC WD5000YS-01MPB1 09.02E09 Tried to disklabel it, and it gives me all kinds of warnings when I look at it after running the disklabel: ganymede# bsdlabel -w ad4s1 auto ganymede# bsdlabel ad4s1c # /dev/ad4s1c: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 976767986 79unused0 0 c: 976768002 63unused0 0 # raw part, don't edit partition a: partition extends past end of unit partition c: partition extends past end of unit bsdlabel: partition c doesn't start at 0! bsdlabel: An incorrect partition c may cause problems for standard system utilities Even if I try to use /stand/sysinstall to do the fdisk, the end result has 'issues' ... So, what is the generally accepted method of label'ng a new drive? :( I think you have it correct (or right as they say). When I: % bsdlabel [da|ad]NsNc those very error messages are horked up on _some_ drives. To me % bsdlabel [da|ad]NsN has always been the correct method. The drives which DO return the errors have partitions newfs-ed with a non-default blocksize (-b 8192). What effect (or impact if you learnt English in a Zeppelin over Italy in 1916) that may have is beyond me. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why is 'disklabel'ng a new drive so difficult?
On Wed, Mar 28, 2007 at 05:26:49PM -0300, Marc G. Fournier wrote: Just bought a new WD SATA drive: WDC WD5000YS-01MPB1 09.02E09 Tried to disklabel it, and it gives me all kinds of warnings when I look at it after running the disklabel: ganymede# bsdlabel -w ad4s1 auto ganymede# bsdlabel ad4s1c # /dev/ad4s1c: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 976767986 79unused0 0 c: 976768002 63unused0 0 # raw part, don't edit partition a: partition extends past end of unit partition c: partition extends past end of unit bsdlabel: partition c doesn't start at 0! bsdlabel: An incorrect partition c may cause problems for standard system utilities Even if I try to use /stand/sysinstall to do the fdisk, the end result has 'issues' ... So, what is the generally accepted method of label'ng a new drive? :( I see you must have run fdisk on it and created a slice. That's good. Also, although you keep saying disklabel, I see you are using the bsdlabel command, so that is good. Then, the only thing wrong is that your offsets should start at 0. They mean within the slice, not raw disk sector 0. I don't know the actual size of the slice, but if it is 9 7676 8002 then starting at sector 63 and going for that size will make it go beyond the disk slice. If you did a 'bsdlabel -e ad4s1'(no 'c' on it) it should put you in an edit session and plug in the correct offset (0 in this case) and size for the slice in the c: line. You appear to want to use all the slice for one partition, so just dup that c: line and make the copy be a: Then change the fstype from 'unused' to '4.2BSD' and the [fsize bsize bps/cpg] fields be 2048 16384 28552 or doubled or just let it pick those fields. You can also put '*' in the offset and size fields for the a: line and it will create one partition that takes up the whole slice. If you make more than one partition, still make the offset be '*', but you can name the sizes in blocks or by size such as 10g, 512m, etc and then put '*' in for the size of the last partition and it will make the sizes you specify and then make that last partition take all that remains. Don't forget to newfs the partition[s]. jerry - Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFGCs+Q4QvfyHIvDvMRAmTBAJwMJeMPTiJEDHWzA3ffe/YnVvRdgwCfVkBt YsPlRNHb6p3WJSIqMXA1K78= =n8pH -END PGP SIGNATURE- ___ 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: Why is 'disklabel'ng a new drive so difficult?
On Wed, Mar 28, 2007 at 04:04:49PM -0500, [EMAIL PROTECTED] wrote: On 28/03/07, Marc G. Fournier [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Just bought a new WD SATA drive: WDC WD5000YS-01MPB1 09.02E09 Tried to disklabel it, and it gives me all kinds of warnings when I look at it after running the disklabel: ganymede# bsdlabel -w ad4s1 auto ganymede# bsdlabel ad4s1c # /dev/ad4s1c: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 976767986 79unused0 0 c: 976768002 63unused0 0 # raw part, don't edit partition a: partition extends past end of unit partition c: partition extends past end of unit bsdlabel: partition c doesn't start at 0! bsdlabel: An incorrect partition c may cause problems for standard system utilities Even if I try to use /stand/sysinstall to do the fdisk, the end result has 'issues' ... So, what is the generally accepted method of label'ng a new drive? :( I think you have it correct (or right as they say). When I: % bsdlabel [da|ad]NsNc those very error messages are horked up on _some_ drives. To me % bsdlabel [da|ad]NsN has always been the correct method. Yes, do not use the 'c' on the bsdlabel command. Just make is da0s1 or ad0s1 (or whichever drive and slice it really is). If you do a 'baslabel -e [da|ad]NsN' it will give you a nice edit session with an appropriate value for the 'c:' line and you can easily go from there. jerry -- -- ___ 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: Why is 'disklabel'ng a new drive so difficult?
On Wed, Mar 28, 2007 at 05:23:22PM -0400, Jerry McAllister wrote: On Wed, Mar 28, 2007 at 04:04:49PM -0500, [EMAIL PROTECTED] wrote: On 28/03/07, Marc G. Fournier [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Just bought a new WD SATA drive: WDC WD5000YS-01MPB1 09.02E09 Tried to disklabel it, and it gives me all kinds of warnings when I look at it after running the disklabel: ganymede# bsdlabel -w ad4s1 auto ganymede# bsdlabel ad4s1c # /dev/ad4s1c: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 976767986 79unused0 0 c: 976768002 63unused0 0 # raw part, don't edit partition a: partition extends past end of unit partition c: partition extends past end of unit bsdlabel: partition c doesn't start at 0! bsdlabel: An incorrect partition c may cause problems for standard system utilities Even if I try to use /stand/sysinstall to do the fdisk, the end result has 'issues' ... So, what is the generally accepted method of label'ng a new drive? :( I think you have it correct (or right as they say). When I: % bsdlabel [da|ad]NsNc those very error messages are horked up on _some_ drives. To me % bsdlabel [da|ad]NsN has always been the correct method. Yes, do not use the 'c' on the bsdlabel command. Just make is da0s1 or ad0s1 (or whichever drive and slice it really is). If you do a 'baslabel -e [da|ad]NsN' it will give you a nice Oops, that should be 'bsdlabel -e [da|ad]NsN' as I hope is obvious. edit session with an appropriate value for the 'c:' line and you can easily go from there. jerry -- -- ___ 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] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why is 'disklabel'ng a new drive so difficult?
On Wed, 28 Mar 2007 17:19:12 -0400 Jerry McAllister [EMAIL PROTECTED] wrote: Then, the only thing wrong is that your offsets should start at 0. They mean within the slice, not raw disk sector 0. I was just looking at the bsdlable manpage, and it says: For partition `c', * will be interpreted as an offset of 0. The first partition should start at offset 16, because the first 16 sectors are reserved for metadata. I normally use sysintall for new slices, but a few days ago I edited an old slice to turn the old root, swap, /tmp and /var partitions into a single partition d for a squid cache, and I ended-up with this: $ bsdlabel /dev/ad0s2 # /dev/ad0s2: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] c: 1418539500unused0 0 # ... d: 524288004.2BSD 2048 16384 28552 f: 16777216 52428804.2BSD0 0 0 g: 119833854 220200964.2BSD0 0 0 I'm wondering if I should put in an offset of 16 for the d partition ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
LD_LIBRARY_PATH
New to FreeBSD. How can I update my LD_LIBRARY_PATH? In Linux I modify my /etc/ld.so.conf file and run ldconfig. Is there an equivalent here? A pointer to docs would be fine. thanks. -- Charles Farinella Appropriate Solutions, Inc. (www.AppropriateSolutions.com) [EMAIL PROTECTED] voice: 603.924.6079 fax: 603.924.8668 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why is 'disklabel'ng a new drive so difficult?
On Wed, Mar 28, 2007 at 10:49:15PM +0100, RW wrote: On Wed, 28 Mar 2007 17:19:12 -0400 Jerry McAllister [EMAIL PROTECTED] wrote: Then, the only thing wrong is that your offsets should start at 0. They mean within the slice, not raw disk sector 0. I was just looking at the bsdlable manpage, and it says: For partition `c', * will be interpreted as an offset of 0. The first partition should start at offset 16, because the first 16 sectors are reserved for metadata. I normally use sysintall for new slices, but a few days ago I edited an old slice to turn the old root, swap, /tmp and /var partitions into a single partition d for a squid cache, and I ended-up with this: $ bsdlabel /dev/ad0s2 # /dev/ad0s2: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] c: 1418539500unused0 0 # ... d: 524288004.2BSD 2048 16384 28552 f: 16777216 52428804.2BSD0 0 0 g: 119833854 220200964.2BSD0 0 0 I'm wondering if I should put in an offset of 16 for the d partition I think that is only true for some old stuff in old systems. I believe I saw somewhere that it only is meaningful it the -A option is used. It might also be meaningful for the so-called 'dangerously dedicated' disk where you don't use a slice, but the raw drive. But, I never start it at an offset of 16 - always 0 if my partition is within a slice. jerry ___ 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: LD_LIBRARY_PATH
New to FreeBSD. How can I update my LD_LIBRARY_PATH? In Linux I modify my /etc/ld.so.conf file and run ldconfig. Is there an equivalent here? A pointer to docs would be fine. There are a couple of ways. First, you can look at /etc/defaults/rc.conf for the default value of ldconfig_paths. On this 6.2-RELEASE system, it's set to: ldconfig_paths=/usr/lib/compat /usr/X11R6/lib /usr/local/lib /usr/local/lib/compat/pkg So you can edit /etc/rc.conf and append to that list. E.g. if you wanted to add /usr/local/my_libs, you'd put the following in /etc/rc.conf: ldconfig_paths=/usr/lib/compat /usr/X11R6/lib /usr/local/lib /usr/local/lib/compat/pkg /usr/local/my_libs Another possibility, based on a cursory read of /etc/rc.d/ldconfig, would be to add the path to /etc/ld-elf.so.conf (which probably doesn't exist by default). Either way, once you've added your path, you'd run: /etc/rc.d/ldconfig start Which should add the libraries from the added path. Regards, Josh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
HP OfficeJet OJ5610
Hello list members! The last time I bought a new printer I had to right away as the old one kicked the bucket and I had work related printed material I just had to print out, so I picked up a cheap Lexmark from Canadian Tire which was on sale. To this day the Lexmark is working great! Except since purchasing it, I haven't been able to print directly to it from my FreeBSD machine because it just isn't (or at least wasn't) supported. Today I see Staples has a HP OfficeJet OJ5610 Colour 4-in-1 printer on at a reasonable price. It's all I need. Since I am soon due to replace both of my print cartridges in the Lexmark, I figure I could just as easily buy the HP printer instead, but I thought I would run this model by the list members to see if it's compatible with FreeBSD, likely through CUPS? Anybody know off hand? Thanks! -gerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iwi-firmware port
On Wed, 28 Mar 2007 12:12:28 -0400
Timothy Radigan [EMAIL PROTECTED] wrote:
Hey all,
I installed the iwi-firmware and iwi-firmware-kmod ports and I am now
trying to load specific firmware on the iwi adapter but it keeps failing.
The port installs fine and puts the firmware to /boot/firmware. The docs
for iwicontrol state to load firmware for a specific function issue a:
iwicontrol -i iwi0 -d /boot/firmware -m bss
Every time I issue that command I get an error saying it cannot load
firmware: Invalid argument.
The system is FreeBSD 6.2 with an Intel PRO Wireless 2200BG adapter. I
have the most up to date stable source and ports tree.
I also tried the ipw-firmware port but that did not pick up my adapter
when I loaded the kernel module.
Any ideas?
here are some examples from my laptop, an IBM T42, with the same wireless
adapter as yours.
in /etc/rc.conf:
ifconfig_iwi0=DHCP WPA
iwi_enable=YES
iwi_interfaces=iwi0
iwi_mod_iwi0=bss
in /etc/wpa_supplicant.conf:
network={
ssid=network
psk=wpa-passwd
}
and in /boot/loader.conf:
# Wireless Network - Intel BG2200
if_iwi_load=YES
wlan_acl_load=YES
wlan_wep_load=YES
wlan_ccmp_load=YES
wlan_tkip_load=YES
wlan_xauth_load=YES
and finally, the port:
[EMAIL PROTECTED] ~]$ pkg_info |grep iwi
iwi-firmware-kmod-3.0_2 Intel PRO/Wireless 2200 Firmware Kernel Module
hope this helps,
jonathan
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: regular portsdb maintanence
On 27/03/07 David J Brooks said: Have you looked at 'man pkgdb'? Yes. I'm looking for how it works, not how to use it. Mike -- Michael P. Soulier [EMAIL PROTECTED] Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction. --Albert Einstein pgp0riZwcEdRk.pgp Description: PGP signature
Re: Install with modified kernel?
On Mar 27, 2007, at 8:53 PM, Garrett Cooper wrote: jekillen wrote: On Mar 27, 2007, at 4:35 PM, [EMAIL PROTECTED] wrote: On Tue, 27 Mar 2007, jekillen wrote: Hello: Is it possible to install FreeBSD ( in this case v6.2 GENERIC RELEASE) with a modified kernel? I am having some network problems with an installation on ASUS N2M32 WS pro (AMD64) mb. I want to try installing without fire wire emulation support, which means I have to modify the kernel to eliminate it. But if I install and then modify the Kernel, it will have made its mark. Please forgive me it this seems like a stupid question. It probably is but I just want to be certain. Thanks in advance. Jeff K Jeff, Of course you can! Please read this chapter in the handbook, which describes the process in great detail: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ kernelconfig.html. As for the network problems, what exactly are you experiencing? -Garrett Hehe.. fun... it appears that I probably got myself into a real mess with the hardware I just purchased (ATI card, Soundblaster X-Fi card, Asus motherboard full of nForce stuff :(..). Oh well, I've learned my lesson I suppose *sign*. You should probably tell what you told me to the questions@ list though. I'm not the only one in the freebsd community, ya know ;)? -Garrett There's more, as a matter of fact, I should write an FYI. It involves much more than just the interface problem. Here goes: I made the mistake of thinking I could use a 64 bit PCIx SCSI adapter in PCIe slots. Now I have one MSI motherboard, AMD64 socket 939 processor and 1Gb of DDR ram I can't use the SCSI card with. So I found this ASUS ($309+) board, It has PCIx slots, two of them. I also had to get another AMD64 processor for it with AM2 slot. I also had to get another Gb of DDR2 RAM. I started assembling the thing and had trouble with the cdrom (ata) drive. It turns out that this board is picky about what ata connector it is plugged into. It is not the one that is usually right next to the power connector (20 pin). it is one further down the board and faces not up from the board but toward the front of the case. It has 3 black SATA bus connectors and 6 orange SATA connectors. I thought the black connectors where for internal drives, It turns out that they are for external drives and I should have plugged in the SATA drive I am using to boot the system into one of the orange connectors. The SCSI stuff works fine; 15k rpm with backplane adapters from 80 pin to 68 pin, I have been through this obstacle coarse before so I was already prepared. Ok, Now it was time to discover the networking problem. First was that the onboard lan is not supported directly by FreeBSD. All I got in the way of interfaces to configure by sysinstall was fwe0 (firewire ethernet emulation). I went looking for inet cards that would work in PCIe slots. The motherboard only has on standard PCI slot and I have a video card installed in it. I find the Intel cards that are made to work in PCIe lane one slots. I go to install them and one of the lane one slots is blocked physically by a copper heat sink assembly on a nearby component. I cannot use that lane one slot. I ended up putting the two Intel cards in the PCIe lane 16 slots. Now I get the system installed and go to the Apache site and get a v1.3.37 tarball and to the php site and get a v5.2.1 tarball, I go get Openssl and mod_ssl and the php gd module and a binary distribution of MySQL (first one specifically for FreeBSD that I had seen). So configure, build and install went fine accept for a few dumb mistakes on my part with Apache, but I got it together. I got all the stuff built and installed to be used with php , mcrypt, gd with freetype and all that. It went well. Then I go to build and install php. Now the next problem: Php goes all the way through the configure, make and make install without complaint. It is being built as a DSO for use with Apache, which means that a file called libphp5.so is supposed to be created and placed in Apache's libexec dir. NO FILE BY THAT NAME SHOWED UP ANY WHERE. I tried it again, same thing, I went and got a tarball I had around of php 5.1.2 and tried that, Same thing; no llibphp5.so and am talking find / -name libphp5.so -print; nothing. I have posted these problems. But the first time I mentioned on this list that I had bypassed ports to install from source I was told that if I do that do not come to this list with problem. I can really understand that and I have had specific and impatient reason from bypassing ports. But, common now, why would php configure, make and install without errors and not produce a critical file for its operation.? As a matter of fact the last few posts about this (networking) have been ignored, Actually your response has been the first on this subject (networking problem). Um... I take that back, I did get
Re: the art of pkgdb -F
On 28/03/07 Kevin Kinsey said: Here is a time-honored and rather canonical diatribe on The Art of Pkgdb -F (a great thread title, BTW). Note also that it is nearly six years old, and that additional package-management tools have been proposed, created, and released to the public, and some may have already been EOL'ed and buried, but the rest of them aren't considered standard by any means, and currently the FreeBSD world is in a pseudo-Biblical every man did as he saw fit state these days[1]. http://www.onlamp.com/pub/a/bsd/2001/11/29/Big_Scary_Daemons.html I suppose I'm curious as to how my ports got into this state in the first place, since I would have expected a package managements system to have prevented it. Now, I've been upgrading ports via portupgrade -R port as suggested in the handbook. As -R upgrades only those packages that require those supplied, and not those that it requires, would that cause it? I'm wondering how my port dependencies became broken in the first place. Mike -- Michael P. Soulier [EMAIL PROTECTED] Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction. --Albert Einstein pgpEjniW1tlh0.pgp Description: PGP signature
Re: using nut-ups with apc UPS on USB
I still have one server running 5.X release. 5.X also should automatically generate the devs. Do you have support for usb in your kernel? If you do have usb compiled in your kernel, check your dmesg that the usb devices are properly being identified. -Derek At 07:27 PM 3/27/2007, Michael P. Soulier wrote: On 27/03/07 Derek Ragona said: Which FreeBSD version are you running? In 6.X the devs are created automatically on bootup. In earlier versions you may need to make it. Look at the Makefile in /dev for the correct make option. I'm running 5-STABLE. I don't see a Makefile in /dev. Mike -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: the art of pkgdb -F
On 28/03/07 RW said: The gettext upgrade is actually a good example of what portupgrade offers. With portupgrade the -rf option is advisable, but not essential, with portmaster, it's essential that the -r option is used, If it's not, or the upgrade fails to complete, you can end-up with not much more than the base-system working. Wow. You would think that such tools would prevent you from getting into that situation. Mike -- Michael P. Soulier [EMAIL PROTECTED] Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction. --Albert Einstein pgpGNniQrLuol.pgp Description: PGP signature
Re: the art of pkgdb -F
On 28/03/07 Gerard Seibert said: You can run: portmanager -u -p -l That will rebuild all broken and or missing dependencies for all of your ports. How does it know what ports are installed? Originally, I thought that the pkgdb was that source of information, so if it was gone, how could it be rebuilt? Obviously there is installed package metadata elsewhere. Just not sure where. If you just want to correct a single port, try this: portmanager /port/name-of-port -p -l Thanks. Mike -- Michael P. Soulier [EMAIL PROTECTED] Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction. --Albert Einstein pgpNiY0kiBlC7.pgp Description: PGP signature
Re: using nut-ups with apc UPS on USB
On 28/03/07 Derek Ragona said: I still have one server running 5.X release. 5.X also should automatically generate the devs. Do you have support for usb in your kernel? If you do have usb compiled in your kernel, check your dmesg that the usb devices are properly being identified. It's there. ugen0: APC Back-UPS ES 500 FW:824.B1.D USB FW:B1, rev 1.10/1.06, addr 2 [EMAIL PROTECTED] ~]# usbdevs addr 1: OHCI root hub, SiS addr 2: Back-UPS ES 500 FW:824.B1.D USB FW:B1, APC addr 1: OHCI root hub, SiS Hmm, seems that I have it now. [EMAIL PROTECTED] ~]# ls -l /dev/usb* crw-rw 1 root operator 240, 255 Mar 24 11:07 /dev/usb crw-rw 1 root operator 240, 0 Mar 24 11:07 /dev/usb0 crw-rw 1 root operator 240, 1 Mar 24 11:07 /dev/usb1 Mike pgp9dBRRXH3H3.pgp Description: PGP signature
Re: HP OfficeJet OJ5610
On Wed, Mar 28, 2007 at 07:17:20PM -0400, Gerry Freymann wrote: Hello list members! The last time I bought a new printer I had to right away as the old one kicked the bucket and I had work related printed material I just had to print out, so I picked up a cheap Lexmark from Canadian Tire which was on sale. To this day the Lexmark is working great! Except since purchasing it, I haven't been able to print directly to it from my FreeBSD machine because it just isn't (or at least wasn't) supported. Today I see Staples has a HP OfficeJet OJ5610 Colour 4-in-1 printer on at a reasonable price. It's all I need. Since I am soon due to replace both of my print cartridges in the Lexmark, I figure I could just as easily buy the HP printer instead, but I thought I would run this model by the list members to see if it's compatible with FreeBSD, likely through CUPS? Anybody know off hand? Thanks! -gerry Try this site: http://openprinting.org/printer_list.cgi Just type in your printer info. and see how compatible it is. This is how I make my choice on the HP photosmart 7660 -- Alexander FreeBSD 6.0 i386 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HP OfficeJet OJ5610
On Wed, 28 Mar 2007 18:19:47 -0500 ajm [EMAIL PROTECTED] wrote: Today I see Staples has a HP OfficeJet OJ5610 Colour 4-in-1 printer on at a reasonable price. It's all I need. Since I am soon due to replace both of my print cartridges in the Lexmark, I figure I could just as easily buy the HP printer instead, but I thought I would run this model by the list members to see if it's compatible with FreeBSD, likely through CUPS? Anybody know off hand? Thanks! -gerry Try this site: http://openprinting.org/printer_list.cgi Just type in your printer info. and see how compatible it is. This is how I make my choice on the HP photosmart 7660 Amazing! Exactly what I was looking for. This printer will work just fine then, using the HPIJS driver. Awesome! Thanks! -gerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck fails on 6T system
Dan D Niles wrote: I am trying to fsck a 6T filesystem on a server that crashed. I'm running FreeBSD 6.2-p3. # fsck -t ufs -y /dev/da0 fsck_ufs: cannot alloc 1993797728 bytes for inoinfo I also tried: # fsck -t ufs -f -p /dev/da0 /dev/da0: UNKNOWN FILE TYPE I=11895232 /dev/da0: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. I built a custom kernel with MAXDSIZ and DFLDSIZ just under 3G, and got the same results. It was at about 430M in use when it crashed, so the total would be 2332 M which is less that the size allowed (reported by limits). I found an old bug report from 2004 that is still open, but nothing has been done. I also found an old article about someone (thinking about) rewriting fsck to use disk instead of memory, but no follow-up. Has anyone found a solution to this? Any suggestions? HELP! Thanks, Dan RAM...lots and lots of RAM. Start with about 8 gigs and give it a try. Thanks, Josh Paetzel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Updating php5-interbase
While updating my ports, I've run into a problem. portversion shows php5-interbase needs updating, but when I ran 'portupgrade php5-interbase' I got the message: '== Please do not build firebird as 'root' because this may cause conflicts with SysV semaphores of running services' ... 'Stop in /usr/ports/databases/firebird2-client'. When I try to build it as another user, I'm told I don't have permissions. I've tried searching Google, including the special BSD search page, with no luck. I couldn't find anything in the firebird documentation. What should I try next? Actually, I didn't even know I had Firebird installed, so I presume it's been pulled in as a dependency for another port. I don't object to having it, because it looks like an excellent RDBMS, but I'd like to either update it or deinstall it. -- Roger ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: the art of pkgdb -F
Hi, On Wed, 28 Mar 2007 20:34:00 -0400, Michael P. Soulier wrote: Now, I've been upgrading ports via portupgrade -R port as suggested in the handbook. As -R upgrades only those packages that require those supplied, and not those that it requires, would that cause it? Be careful with your syntax: '-R' isn't consistent between pkg_info and portupgrade: Running 'pkg_info -R' will downward recurse, or show dependencies of the port in question, but 'portupgrade -R' will upward recurse and upgrade every port on which it depends - which often causes a _lot_ of ports to be rebuilt and is, in fact, the opposite of your description above. I've been caught by this before... regards -- Joel Hatton -- Infrastructure Manager | Hotline: +61 7 3365 4417 AusCERT - Australia's national CERT | Fax: +61 7 3365 7031 The University of Queensland| WWW: www.auscert.org.au Qld 4072 Australia | Email: [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
skype replacement
Hi all, Since skype requires some i386 binary, it doesn't build on amd64. Could you advise me on what is available as a replacement? What program do you use to implement p2p voice connection on amd64 machine? Thank you in advance. Andriy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck fails on 6T system
On Wed, 2007-03-28 at 20:21 -0500, Josh Paetzel wrote: Dan D Niles wrote: I am trying to fsck a 6T filesystem on a server that crashed. I'm running FreeBSD 6.2-p3. # fsck -t ufs -y /dev/da0 fsck_ufs: cannot alloc 1993797728 bytes for inoinfo I also tried: # fsck -t ufs -f -p /dev/da0 /dev/da0: UNKNOWN FILE TYPE I=11895232 /dev/da0: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. I built a custom kernel with MAXDSIZ and DFLDSIZ just under 3G, and got the same results. It was at about 430M in use when it crashed, so the total would be 2332 M which is less that the size allowed (reported by limits). [clip] RAM...lots and lots of RAM. Start with about 8 gigs and give it a try. The machine has 3G of RAM. But as I said, it should only be using 2.3G when it stops. It has 3G of space so adding more RAM wouldn't help. It does not appear that it will go past 2G even though I increased the process limits to near 3G. BTW, if MAXDSIZ plus MAXSSIZ is greater than the size of real memory the machine won't boot. I tried it. Also, the max memory FreeBSD can use is about 3.5G unless you use the experimental PAE kernel. Any other ideas on how to get fsck to work on a 6T filesystem? Thanks, Dan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Can cvs-sup Safely Upgrade a 5.3 System to 6.2?
The system is on, but not in production so I would like to upgrade it before we use it. Many thanks. Martin McCormick WB5AGZ Stillwater, OK Systems Engineer OSU Information Technology Department Network Operations Group ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Can cvs-sup Upgrade a 5.3 system to 6.2?
The system is up and running, but presently not in production. Thank you. Martin McCormick WB5AGZ Stillwater, OK Systems Engineer OSU Information Technology Department Network Operations Group ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: regular portsdb maintanence
On 27/03/07, Michael P. Soulier [EMAIL PROTECTED] wrote: Hello, I just upgraded portupgrade, and it recommended that I run pkgdb -L to look for lost dependencies. This raised the question to me of what I should regularly run in cron jobs to maintain the db. Is it wise to put say, pkgdb -L into a weekly cron? Anything else? I am not sure you would want to do that, as if it were to overlap with a normal portupgrade the results may be interesting. The machine's day to day running depends not at all on the pkgdb. I would suggest that if you sense that you need to keep atop these things you run pkgdb -L about as often as you run portupgrade -fr something. If you do not have to recursively rebuild (say for leaf packages) pkgdb -L is redundant at best. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can cvs-sup Safely Upgrade a 5.3 System to 6.2?
On Wed, 28 Mar 2007, Martin McCormick wrote: The system is on, but not in production so I would like to upgrade it before we use it. Keep strictly to the canonical way to update your system http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html Else - as far as I remember - you might run into problems with some pseudo user account which is needed for 6.x Good Luck, Uli. Many thanks. Martin McCormick WB5AGZ Stillwater, OK Systems Engineer OSU Information Technology Department Network Operations Group ___ 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: the art of pkgdb -F
On 28/03/07, Joel Hatton [EMAIL PROTECTED] wrote: Hi, On Wed, 28 Mar 2007 20:34:00 -0400, Michael P. Soulier wrote: Now, I've been upgrading ports via portupgrade -R port as suggested in the handbook. As -R upgrades only those packages that require those supplied, and not those that it requires, would that cause it? Be careful with your syntax: '-R' isn't consistent between pkg_info and portupgrade: Running 'pkg_info -R' will downward recurse, or show dependencies of the port in question, but 'portupgrade -R' will upward recurse and upgrade every port on which it depends - which often causes a _lot_ of ports to be rebuilt and is, in fact, the opposite of your description above. I've been caught by this before... In fact, as frequently the build looks for a binary, and portupgrade checks /var/db/pkg there can be some quite exciting results from a portupgrade -R if you have alternate dependancies. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Can't work out which disk we are booting from
Hi, When i install freebsd ,a problem occurred: Can't work out which disk we are booting from. Guessed BIOS device 0x not found by probes defaulting to disk0: What should i do? Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: the art of pkgdb -F
Michael P. Soulier wrote:
On 28/03/07 Kevin Kinsey said:
Here is a time-honored and rather canonical diatribe on The Art of
Pkgdb -F (a great thread title, BTW). Note also that it is nearly
six years old, and that additional package-management tools have been
proposed, created, and released to the public, and some may have already
been EOL'ed and buried, but the rest of them aren't considered standard
by any means, and currently the FreeBSD world is in a pseudo-Biblical
every man did as he saw fit state these days[1].
http://www.onlamp.com/pub/a/bsd/2001/11/29/Big_Scary_Daemons.html
I suppose I'm curious as to how my ports got into this state in the first
place, since I would have expected a package managements system to have
prevented it.
Good point, perhaps --- if I understand the problem (and there is no
guarantee that I do), it would seem, upon a first, furtive, tentative
and cursory examination that the fact you might need to run pkgdb -F
violates the POLA. Maybe you should qualify and say I would have
expected a *perfect* package management system to
However, ports get moved, dropped, re-named, re-categorized and so on
(somewhat) frequently --- perhaps no *one* port, but taken as a whole
(what, +15K ports now?) the tree is rather a moving target. In the
case of a moved or deleted port, I see no particular way that you
would miss out on at least a missing origin warning from the pkgtools
after obtaining an updated tree.
Otherwise, I suppose that, canonically, if one does the right thing
every time, you might come close. But I bet I'm not the only one who,
once upon a time, happened to try portupgrade -arR or equivalent
after forgetting to read UPDATING and ended up with more to do than I
originally thought.
And, of course, this is the point where the various disciples/proponents
(and possibly even the maintainers/authors) of the increasing variety of
package management tools come forth to sing the praises of their
favorite software.
So far we've heard from portupgrade, portmanager, and portmaster.
Any portscout, managepkg, or porteasy advocates wanna speak up?
[What did I miss, and, no, sorry, I didn't read every pkg-descr]
As I mentioned earlier, it's no secret that:
1. The Ports Collection is large, dynamic, and somewhat complex.
2. Different tools exist for ports management (in fact, there are now
so many that a new ports category was recently created to store all of them).
3. One set of tools existed for a long time before the others pretty much
by itself, and became the accepted (or at least the documented) way to
upgrade 3rd-party software. It wasn't perfect, but it continues to be
improved, as do the newer management programs.
4. The future of package management remains to be seen, but the various
and occasional pitfalls of the system have given rise to varied paths
to package nirvana (I, for one, haven't yet decided which to take).
This is actually a Good Thing for BSD, insofar as it continues to
exemplify another UNIX principle, tools, not policy.
I might expect, given this philosophy, that development on several
programs for the management of installed 3rd-party software will
continue, and that, unless one shows itself to be very superior to
the others, a variety of programs will continue in general use, much
to the chagrin of the FDP people, who will have to decide if the
current approach should be changed, and, if so, how. Doesn't sound
like as much fun as, say, beachcombing on Fiji or strolling through
downtown {$nice_city} in spring, though.
Full circle, Kinda back to every man for himself ---
Kevin Kinsey
--
The things that interest people most are usually none of their business.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can cvs-sup Safely Upgrade a 5.3 System to 6.2?
Martin McCormick wrote: The system is on, but not in production so I would like to upgrade it before we use it. Many thanks. Martin McCormick WB5AGZ Stillwater, OK Systems Engineer OSU Information Technology Department Network Operations Group ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] it should work, but you may want to take it to the latest 5.x branch and then to 6.2 If you need a nice walkthrough, i have one on my site at http://mikestammer.com under the FreeBSD section Eric ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Re: Install with modified kernel?
Hello again: It is only fair to post this addenda to the message thread with this subject: From various suggestions from list responses, UUASC and I seem to remember one from this list also, that the problem could be consecutive addresses on the same subnet is what is causing the problem. I was asked by message from UUASC (Unix Users Association Of Southern California) to try changing the address. So I change it to (just for the sake of difference) 172.1.1.1 with netmask of 225.225.225.0 and I WAS able to ping the inter face successfully. was nfe0 192.168.1.16 (could ping) nfe1 192.168.1.17 (could not ping) nfe1 changed to 172.1.1.1 (now returns ping request) so that does seem to make a difference. I do not know why. But it looks like I will be able to go ahead and assign it the public ip address and it should work. Thanks Jeff K ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck fails on 6T system
On woensdag 28 maart 2007, Dan D Niles wrote: I am trying to fsck a 6T filesystem on a server that crashed. I'm running FreeBSD 6.2-p3. # fsck -t ufs -y /dev/da0 fsck_ufs: cannot alloc 1993797728 bytes for inoinfo Could you run 'limits' here? I suspect 'datasize' is too low. Regards, Pieter de Goeje ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: the art of pkgdb -F
Kevin Kinsey writes: But I bet I'm not the only one who, once upon a time, happened to try portupgrade -arR or equivalent after forgetting to read UPDATING and ended up with more to do than I originally thought. Might as well paint PLEASE KICK ME! and an arrow pointing down on your back 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: skype replacement
On 3/28/07, Andriy Babiy [EMAIL PROTECTED] wrote: Since skype requires some i386 binary, it doesn't build on amd64. Could you advise me on what is available as a replacement? What program do you use to implement p2p voice connection on amd64 machine? Thank you in advance. hihi. You may want to have a look at [1][2]Ekiga. It's a really nice SIP and H.323 soft phone for GNOME. HTH! 1. http://www.freshports.org/net/ekiga/ 2. http://www.gnomemeeting.org/ -- James. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Sierra Wireless AirCard 555 drivers (?), and NDIS...
Hi, This might be a slightly offtopic question - I have a bunch of Sierra Wireless AirCard 555 driver/firmware files, and I am unable to figure out which is the correct .inf file, or which are the remaining firmware files. I could only recognize the driver, which had a .sys extension. These files are: Air555.sys, mdmac555.cat, mfac555.cat, netac555.inf, MFAC555.INF, mdmac555.inf, netac555.cat. None of the .inf files give a clue as to which one really belongs to the .sys file. Hence, I tried building the ko, using ndisgen utility, by specifying .sys as the driver, and netac555.inf as the corresponding .inf files. Then I specified all the remaining files as additional firmware files. ndisgen happily built the kernel object, and I was able to insert it too... ...butno device appeared, no nothing in the syslog too! This leaves me wondering if I specified the incorrect files... Does anyone have an idea as to which will be the correct .inf file, and which are the firmware files? I'd appreciate help here, I can also send these file offlist for inspection. Thanks in advance! Best, Amarendra ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can cvs-sup Upgrade a 5.3 system to 6.2?
On 3/28/07, Martin McCormick [EMAIL PROTECTED] wrote: The system is up and running, but presently not in production. cvsup (or csup, available from ports) can update /usr/src from any version to any version. If you try to update it to 6.2 on a 5.3 system - then, yes, you'll succeed in rebuilding world and kernel, and installing them. Please refer to the last parts of /usr/src/UPDATING and/or Handbook for further info. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
