Intel 2200bg issue on freebsd 7.2
I have included all the modules if_iwi.ko, iwi_ibss.ko,iwi_bss.ko and iwi_monitor.ko. No errors during post boot and I have set all the necessary options in /boot/loader.conf for the modules and for the liscence to no avail. ifconfig iwi0 scan == hangs ifconfig iwi0 list scan == returns 0 ap's ifconfig iwi0 list sta == ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 00:0e:35:58:61:db0 1 1M 0.0 300 0 0 A and since cloning doesnt work except in freebsd 8.0. How can i go on with scanning my networks on freebsd 7.2? Is there a workaround? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
adapting src.conf to nanobsd CONF build options
Hello all, I'd like to implement the following src.conf for nanobsd. Goal is to have these subset neither being built, nor installed. cat /etc/src.conf WITHOUT_BLUETOOTH WITHOUT_CALENDAR WITHOUT_CPP WITHOUT_CTM WITHOUT_CVS WITHOUT_CXX WITHOUT_DICT WITHOUT_EXAMPLES WITHOUT_FLOPPY WITHOUT_GAMES WITHOUT_GCOV WITHOUT_IPFILTER WITHOUT_INFO WITHOUT_INSTALLLIB WITHOUT_IPFW WITHOUT_IPX WITHOUT_LPR WITHOUT_MAKE WITHOUT_GROFF WITHOUT_NCP WITHOUT_NIS WITHOUT_FREEBSD_UPDATE WITHOUT_RCS WITHOUT_SHAREDOCS As far as I have read, what I need to do is put these into CONF_BUILD section to prevent buildworld compiling them Do I need to put them also into CONF_INSTALL and CONF_WORLD to prevent them from being propagated into the image or just having them into CONF_BUILD will suffice? Thanks, Dimitar ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
xorg and jails
How do I start Xorg from within a jail so that it will output to a xephyr session? Tell me which files I will need to configure and I will post them here for you to look at. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
How long do you go without upgrading FreeBSD to a newer release?
Hello folks Just a thought/question that has recently come to my mind: How long do you usually wait until upgrading to a newer release of FreeBSD? I am sure there are lots of people who upgrade straight away, but what about the opposite? What's your oldest currently running installation, do you have any issues and are you planning on an upgrade or do you intend to leave it running as is until some critical piece of hardware breaks down, requiring a replacement? The reason I am asking is: I have a 8.0 installation that I am VERY happy with. It runs like clockwork. eveything is properly configured and highly locked down, all services accessible to the outside world are running inside ezjail-managed jails on top of ZFS, meaning it's also very trivial to restore jails via snapshots, should the need ever arise. I don't really see myself NEEDING to upgrade for many years. even long after security updates stop being made for 8.0, since I can see myself being able to at least work my way around arising security issues with my configuration and to break into the real host OS and cause real damage would mean you have to be either really really dedicated, have a gun and know where I live or serve me with a warrant. Do you liva by the If it's not broken, don't fix it mantra or do you religiously keep your OS installations up to date? - Sincerely, Dan Naumov ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How long do you go without upgrading FreeBSD to a newer release?
then stay with what you have if its working, no need to upgrade, unless theres new feature you can use, after you are confident its runs the same or better in pre-production with all the apps you use, ive still got a 4.10 box On Sun, May 16, 2010 at 11:42 AM, Dan Naumov dan.nau...@gmail.com wrote: Hello folks Just a thought/question that has recently come to my mind: How long do you usually wait until upgrading to a newer release of FreeBSD? I am sure there are lots of people who upgrade straight away, but what about the opposite? What's your oldest currently running installation, do you have any issues and are you planning on an upgrade or do you intend to leave it running as is until some critical piece of hardware breaks down, requiring a replacement? The reason I am asking is: I have a 8.0 installation that I am VERY happy with. It runs like clockwork. eveything is properly configured and highly locked down, all services accessible to the outside world are running inside ezjail-managed jails on top of ZFS, meaning it's also very trivial to restore jails via snapshots, should the need ever arise. I don't really see myself NEEDING to upgrade for many years. even long after security updates stop being made for 8.0, since I can see myself being able to at least work my way around arising security issues with my configuration and to break into the real host OS and cause real damage would mean you have to be either really really dedicated, have a gun and know where I live or serve me with a warrant. Do you liva by the If it's not broken, don't fix it mantra or do you religiously keep your OS installations up to date? - Sincerely, Dan Naumov ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How long do you go without upgrading FreeBSD to a newer release?
On Sun, 16 May 2010 18:42:44 +0300, Dan Naumov dan.nau...@gmail.com wrote: Just a thought/question that has recently come to my mind: How long do you usually wait until upgrading to a newer release of FreeBSD? A quite generic answer: Only as long as needed. :-) Upgrading often is determined by certain considerations, such as the ability to maintain system security (again depending on the setting and the purpose of the installation), or the require- ment for some functionality that explicitely requires upgrading. What's your oldest currently running installation, do you have any issues and are you planning on an upgrade or do you intend to leave it running as is until some critical piece of hardware breaks down, requiring a replacement? FreeBSD 5.4-p14 on a P2/300, 128 MB RAM, office workstation, last update both in system and applications in 2006. Upgrade planning: no. Leave it running as long as possible: yes. Reason: System runs perfectly (it's not on WAN or acting as a server, so no major security considerations). It runs better than my FreeBSD 7 home system which awaits upgrading to 8 soon. :-) Oldest: 4.1 on a 486 laptop, I'm sure it still works, but it's not in regular use. :-) The reason I am asking is: I have a 8.0 installation that I am VERY happy with. It runs like clockwork. eveything is properly configured and highly locked down, all services accessible to the outside world are running inside ezjail-managed jails on top of ZFS, meaning it's also very trivial to restore jails via snapshots, should the need ever arise. I don't really see myself NEEDING to upgrade for many years. even long after security updates stop being made for 8.0, since I can see myself being able to at least work my way around arising security issues with my configuration and to break into the real host OS and cause real damage would mean you have to be either really really dedicated, have a gun and know where I live or serve me with a warrant. If you're running services available to the outside world, keep in mind *their* security updates also. If those require a system update, do it, but usually they don't - you usually just upgrade the ports in question. For servers, you should follow -p as long as possible. If there are no further security updates for a certain release, it MAY be a valid idea to upgrade to the new release (e. g. 8.0 to 8.2, or what's the current release when 8.0-p doesn't continue). Do you liva by the If it's not broken, don't fix it mantra or do you religiously keep your OS installations up to date? Maybe you'll laugh, but I go with both ways. :-) I've got an experimental system that I try bleeding edge software on, just to see how well it works. Servers and workstations that I need to RELY ON go with not broken, not fix. I'm sure you'll get more answers that suggest you to really think about what you want to do, and that determines your way, maybe both ways, if that fits your requirements. Both ways have their advantages and disadvantages, and it's up to you how you handle it. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How long do you go without upgrading FreeBSD to a newer release?
On 16 May 2010 17:05, Polytropon free...@edvax.de wrote: On Sun, 16 May 2010 18:42:44 +0300, Dan Naumov dan.nau...@gmail.com wrote: Just a thought/question that has recently come to my mind: How long do you usually wait until upgrading to a newer release of FreeBSD? A quite generic answer: Only as long as needed. :-) Upgrading often is determined by certain considerations, such as the ability to maintain system security (again depending on the setting and the purpose of the installation), or the require- ment for some functionality that explicitely requires upgrading. What's your oldest currently running installation, do you have any issues and are you planning on an upgrade or do you intend to leave it running as is until some critical piece of hardware breaks down, requiring a replacement? FreeBSD 5.4-p14 on a P2/300, 128 MB RAM, office workstation, last update both in system and applications in 2006. Upgrade planning: no. Leave it running as long as possible: yes. Reason: System runs perfectly (it's not on WAN or acting as a server, so no major security considerations). It runs better than my FreeBSD 7 home system which awaits upgrading to 8 soon. :-) Oldest: 4.1 on a 486 laptop, I'm sure it still works, but it's not in regular use. :-) The reason I am asking is: I have a 8.0 installation that I am VERY happy with. It runs like clockwork. eveything is properly configured and highly locked down, all services accessible to the outside world are running inside ezjail-managed jails on top of ZFS, meaning it's also very trivial to restore jails via snapshots, should the need ever arise. I don't really see myself NEEDING to upgrade for many years. even long after security updates stop being made for 8.0, since I can see myself being able to at least work my way around arising security issues with my configuration and to break into the real host OS and cause real damage would mean you have to be either really really dedicated, have a gun and know where I live or serve me with a warrant. If you're running services available to the outside world, keep in mind *their* security updates also. If those require a system update, do it, but usually they don't - you usually just upgrade the ports in question. For servers, you should follow -p as long as possible. If there are no further security updates for a certain release, it MAY be a valid idea to upgrade to the new release (e. g. 8.0 to 8.2, or what's the current release when 8.0-p doesn't continue). Do you liva by the If it's not broken, don't fix it mantra or do you religiously keep your OS installations up to date? Maybe you'll laugh, but I go with both ways. :-) I've got an experimental system that I try bleeding edge software on, just to see how well it works. Servers and workstations that I need to RELY ON go with not broken, not fix. I'm sure you'll get more answers that suggest you to really think about what you want to do, and that determines your way, maybe both ways, if that fits your requirements. Both ways have their advantages and disadvantages, and it's up to you how you handle it. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org we have some production dns caches at work running bsd 4.3, that have been there for nearly a decade. We keep the dns software on them upto date and they are locked down with a firewall. However they will be going some time this year, but thats more down to consolidation than anything else. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
bindtextdomain
Sorry guys, didn't notice if this has come up yet... did a big portupgrade (-af) and now I'm having issues with quite a few programs failing to run. In time tracker I always get: AttributeError: 'module' object has no attribute '*bindtextdomain*' A few of the built in games... like chess and sudoku: File /usr/local/lib/python2.6/site-packages/glchess/defaults.py, line 46, in module locale.bind_textdomain_codeset(DOMAIN, UTF-8) # See Bug 608425 AttributeError: 'module' object has no attribute '*bind_textdomain_codeset*' === I was also wondering if someone could explain packagekit... I read that it's a work in progress... but every time I boot I see two updates show up... I then try to upgrade using the upgrade now button, and receive a few errors. The first error states that packages for these items can not be found, the second error stats that upgrade-packages can not be found (sorry, going from memory), but basically it can't find the actual program or script required to do the upgrade. Is Packagekit broken at the moment or am I missing something? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Intel 2200bg issue on freebsd 7.2
I also am unable to get that device to work on 8.0. If I try to set it up it will momentary hang the system, then cause a restart. Did some searching and found there are many looking for help with this device. I have found no solutions. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How long do you go without upgrading FreeBSD to a newer release?
On Sun 16 May 2010 at 08:42:44 PDT Dan Naumov wrote: Just a thought/question that has recently come to my mind: How long do you usually wait until upgrading to a newer release of FreeBSD? My machines are all for personal use only, and it wouldn't be a disaster if any of them went down for an extended period. So I don't hesitate to upgrade to new releases as soon as they appear. I'm currently running 8.0-STABLE and update it every week or so. The portstree is updated daily. If my income depended on these machines, I'd probably be more cautious. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Quantum SuperLoader 3 under Bacula on FreeBSD 8
On Fri, May 14, 2010 at 4:29 AM, Paul Mather p...@gromit.dlib.vt.edu wrote: I am currently assembling a quote for an LTO-4 tape backup system. So far, I am looking at using a 16-slot Quantum SuperLoader 3 with LTO-4HH drive as the tape unit. Married to this will be a server to act as the backup server that will drive the tape unit using Bacula to manage backups. The server will be a quad core X3440 system with 4 GB of RAM and four 1 TB SATA 7200 rpm hard drives in a case that has room for eight hot-swap drives. I plan on using FreeBSD 8 on the system, using ZFS to raidz the drives together to provide spool space for Bacula. I will be using an Areca ARC-1300-4X PCIe SAS card to interface with the tape drive. My main question is this: is the Quantum SuperLoader 3 LTO-4 tape drive supported by Bacula 5 on FreeBSD? In particular, is the autoloader supported? The Bacula documentation indicates the SuperLoader works fully under Bacula, though not explicitly whether under FreeBSD. The backup server will serve a network cluster of perhaps a dozen machines with over 6 TB of storage, most of which is on the cluster's NFS server. Does anyone have good advice on sizing the spool/holding/disk pool for a Bacula server? Is it imperative to have enough disk space to hold a full backup, or is it sufficient to have enough space to maintain streaming to tape? (I don't have much experience of Bacula, having used it only to back up to disk.) In other words, do I need more 1 TB drives in my backup server? Finally, is 4 GB of RAM sufficient for good performance with ZFS? Will ZFS on FreeBSD be able to maintain full streaming speeds to tape, given the various reports of I/O stalls under ZFS reported recently? Thanks in advance for any advice or information. Hello Paul, we are using successfully a Quantum Scalar 50 with an expansion box and two F/C FH LTO-4 drives on FreeBSD 7-STABLE and Bacula 5.0.x. FreeBSD 7-STABLE or 8-STABLE is recommended if you have a QLogiq F/C card. Having Bacula's spooling area in a fast disk partition (e.g. a RAID0 volume) would be a good idea too. Regards, Panagiotis ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Stop in /usr/ports/x11-toolkits/gtk20
Hi, x11-toolkits/gtk20 stops. Thanks in advance! Winston Weinert /usr/local/bin/g-ir-scanner --add-include-path=../gdk-pixbuf --namespace=Gdk --nsversion=2.0 --libtool=/bin/sh /usr/ports/x11-toolkits/gtk20/work/gnome-libtool --library=libgdk-x11-2.0.la --include=Gio-2.0 --include=GdkPixbuf-2.0 --include=Pango-1.0 --strip-prefix=Gdk --add-include-path=../gdk-pixbuf -DG_LOG_DOMAIN=\Gdk\ -DGDK_COMPILATION -I.. -I../gdk -I../gdk-pixbuf -DG_DISABLE_CAST_CHECKS -D_REENTRANT -D_THREAD_SAFE -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/pango-1.0 -I/usr/local/include/cairo -I/usr/local/include/pixman-1 -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/local/include/gio-unix-2.0/ ./gdk.h /gdkapplaunchcontext.h ./gdkcairo.h ./gdkcolor.h ./gdkcursor.h /gdkdisplay.h ./gdkdisplaymanager.h ./gdkdnd.h ./gdkdrawable.h /gdkevents.h ./gdkfont.h ./gdkgc.h ./gdki18n.h ./gdkimage.h /gdkinput.h ./gdkkeys.h ./gdkkeysyms.h ./gdkpango.h ./gdkpixbuf.h /gdkpixmap.h ./gdkprivate.h ./gdkproperty.h ./gdkregion.h ./gdkrgb.h /gdkscreen.h ./gdkselection.h ./gdkspawn.h ./gdktestutils.h /gdktypes.h ./gdkvisual.h ./gdkwindow.h ./gdk.c ./gdkapplaunchcontext.c /gdkcairo.c ./gdkcolor.c ./gdkcursor.c ./gdkdisplay.c /gdkdisplaymanager.c ./gdkdnd.c ./gdkdraw.c ./gdkevents.c ./gdkfont.c /gdkgc.c ./gdkglobals.c ./gdkimage.c ./gdkkeys.c ./gdkkeyuni.c /gdkoffscreenwindow.c ./gdkpango.c ./gdkpixbuf-drawable.c /gdkpixbuf-render.c ./gdkpixmap.c ./gdkpolyreg-generic.c /gdkrectangle.c ./gdkregion-generic.c ./gdkrgb.c ./gdkscreen.c /gdkselection.c ./gdkvisual.c ./gdkwindow.c ./gdkwindowimpl.c /gdkenumtypes.c ./gdkenumtypes.h ././x11/*.c --output Gdk-2.0.gir Couldn't find include 'Pango-1.0.gir' (search path: ['../gdk-pixbuf', '../gdk-pixbuf', '/usr/local/share/gir-1.0', '/usr/share/gir-1.0', '/usr/local/share/gir-1.0']) gmake[4]: *** [Gdk-2.0.gir] Error 1 gmake[4]: Leaving directory `/usr/ports/x11-toolkits/gtk20/work/gtk+-2.20.1/gdk' gmake[3]: *** [all-recursive] Error 1 gmake[3]: Leaving directory `/usr/ports/x11-toolkits/gtk20/work/gtk+-2.20.1/gdk' gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/usr/ports/x11-toolkits/gtk20/work/gtk+-2.20.1/gdk' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/x11-toolkits/gtk20/work/gtk+-2.20.1' gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/ports/x11-toolkits/gtk20. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Seamonkey 2.0.4: crash crash crash post-update
Greetings... uname -a: FreeBSD whisperer.chthonixia.net 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #0: Sat May 15 11:47:55 EDT 2010 r...@whisperer.chthonixia.net:/usr/obj/usr/src/sys/WHISPERER amd64 This is a fresh build of world and updated ports. I have also deinstalled and reinstalled Seamonkey, thinking I had to do with it what I had to do to work around the X bug(s)[1] for the Radeon driver following the X upgrade I performed on May 14. That manifested as an inability to load both radeon_drv.la and radeon_drv.so. Unfortunately, the make reinstall of Seamonkey has not remedied whatever its problem is. Here is all I know; see footnote: Seamonkey just blinks off. It's random; it does not appear to be associated with any particular website nor plugin. It leaves no core. It does restore my tabs. I should be explicit: this has never happened on this installation until after the May 14th-15th update. I've seen no bug reports filed recently; but is anyone else seeing this and waiting to see if it's fixed silently? I do see this in the Xorg.log: record: RECORD extension enabled at configure time. record: This extension is known to be broken, disabling extension now.. record: http://bugs.freedesktop.org/show_bug.cgi?id=20500 The referenced bug report has this (final?) entry: == Peter Hutterer 2010-04-15 23:40:39 PDT I'm going to pretend this is all fixed now - at least how the bug claims it is. If there are any leftovers they're probably real bugs and should be filed as separate bugreports. Thanks for everyone's help. === Thanks for any help, and best regards, Joe [1] Which bug(s) now appear to be manifesting as loss of attachment to the X display when using ctrl-alt-f1 to look at the console; meaning: I cannot reliably use ctrl-alt-f9 to go back to the X display. Which, in turn, required a complete reboot to regain the ability to use X (I logged in from a different machine and tried to kill off X to regain the console; no joy.) The ultimate result: I can no longer post the sole error message I had on the console regarding the Seamonkey issue. It had something to do with a bad picture, IIRC. Sigh. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Seamonkey 2.0.4: crash crash crash post-update
Following up to myself: I ran Seamonkey from a terminal; it took a few minutes under two hours to crash again; this time, I have the error: The program 'seamonkey-bin' received an X Window System error. This probably reflects a bug in the program. The error was 'RenderBadPicture (invalid Picture parameter)'. (Details: serial 1692977 error_code 157 request_code 147 minor_code 7) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Maybe this will help. There is still no seamonkey.core in ~; nothing in messages; nothing in the Xorg.log. Seamonkey just blinks off. On Sun, May 16, 2010 at 08:02:34PM -0400, J. Altman wrote: Greetings... uname -a: FreeBSD whisperer.chthonixia.net 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #0: Sat May 15 11:47:55 EDT 2010 r...@whisperer.chthonixia.net:/usr/obj/usr/src/sys/WHISPERER amd64 This is a fresh build of world and updated ports. I have also deinstalled and reinstalled Seamonkey, thinking I had to do with it what I had to do to work around the X bug(s)[1] for the Radeon driver following the X upgrade I performed on May 14. That manifested as an inability to load both radeon_drv.la and radeon_drv.so. Unfortunately, the make reinstall of Seamonkey has not remedied whatever its problem is. Here is all I know; see footnote: Seamonkey just blinks off. It's random; it does not appear to be associated with any particular website nor plugin. It leaves no core. It does restore my tabs. I should be explicit: this has never happened on this installation until after the May 14th-15th update. I've seen no bug reports filed recently; but is anyone else seeing this and waiting to see if it's fixed silently? I do see this in the Xorg.log: record: RECORD extension enabled at configure time. record: This extension is known to be broken, disabling extension now.. record: http://bugs.freedesktop.org/show_bug.cgi?id=20500 The referenced bug report has this (final?) entry: == Peter Hutterer 2010-04-15 23:40:39 PDT I'm going to pretend this is all fixed now - at least how the bug claims it is. If there are any leftovers they're probably real bugs and should be filed as separate bugreports. Thanks for everyone's help. === Thanks for any help, and best regards, Joe [1] Which bug(s) now appear to be manifesting as loss of attachment to the X display when using ctrl-alt-f1 to look at the console; meaning: I cannot reliably use ctrl-alt-f9 to go back to the X display. Which, in turn, required a complete reboot to regain the ability to use X (I logged in from a different machine and tried to kill off X to regain the console; no joy.) The ultimate result: I can no longer post the sole error message I had on the console regarding the Seamonkey issue. It had something to do with a bad picture, IIRC. Sigh. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
