authdaemond issues / breakage after upgrade to 8.0
I recently upgraded from FreeBSD 7.2 to 8.0. This resulted in a strange error with authdaemond (part of the Courier imap package, used to authenticate users) when used in conjunction with postfix; I've rebuilt all of the packages, but the config they're using has worked since the 6.0 days. I attempt to send a message using SASL and get the following in my logs (passwords and hashes have been consistently redacted; nothing else has been altered): Dec 1 14:49:06 alcatraz authdaemond: Authenticated: sysusername=, sysuserid=1008, sysgroupid=1008, homedir=/usr/local/virtual/, address=...@sequestered.net, fullname=Jay Chandler, maildir=sequestered.net/j...@sequestered.net/, quota=102400S, options= Dec 1 14:49:06 alcatraz authdaemond: Authenticated: clearpasswd=omgponies, passwd=$1$6dICANHAZPONIEZ?$Z1ySHXcliB8vx0jqwZ9Bp1 Dec 1 14:49:06 alcatraz imapd-ssl: LOGIN, user=...@sequestered.net, ip=[166.191.99.147], port=[52341], protocol=IMAP Dec 1 14:49:07 alcatraz imapd-ssl: LOGOUT, user=...@sequestered.net, ip=[166.191.99.147], headers=0, body=0, rcvd=25, sent=699, time=1, starttls=1 Dec 1 14:49:08 alcatraz imapd-ssl: LOGIN, user=...@sequestered.net, ip=[166.191.99.147], port=[52342], protocol=IMAP Dec 1 14:49:08 alcatraz authdaemond: Authenticated: sysusername=, sysuserid=1008, sysgroupid=1008, homedir=/usr/local/virtual/, address=...@sequestered.net, fullname=Jay Chandler, maildir=sequestered.net/j...@sequestered.net/, quota=102400S, options= Dec 1 14:49:08 alcatraz authdaemond: Authenticated: clearpasswd=omgponies, passwd=$1$6dICANHAZPONIEZ?$Z1ySHXcliB8vx0jqwZ9Bp1 Dec 1 14:49:11 alcatraz imapd-ssl: LOGIN, user=...@sequestered.net, ip=[166.191.99.147], port=[52343], protocol=IMAP Dec 1 14:49:11 alcatraz authdaemond: Authenticated: sysusername=, sysuserid=1008, sysgroupid=1008, homedir=/usr/local/virtual/, address=...@sequestered.net, fullname=Jay Chandler, maildir=sequestered.net/j...@sequestered.net/, quota=102400S, options= Dec 1 14:49:11 alcatraz authdaemond: Authenticated: clearpasswd=omgponies, passwd=$1$6dICANHAZPONIEZ?$Z1ySHXcliB8vx0jqwZ9Bp1 It appears I'm authing correctly; in fact, authtest shows: alcatraz# authtest j...@sequestered.net omgponies Authentication succeeded. Authenticated: j...@sequestered.net (uid 1008, gid 1008) Home Directory: /usr/local/virtual/ Maildir: sequestered.net/j...@sequestered.net/ Quota: 102400S Encrypted Password: $1$6dICANHAZPONIEZ?$Z1ySHXcliB8vx0jqwZ9Bp Cleartext Password: omgponies Options: wbnodsn=1 At this point I'm at a loss as to what else I can try. I've included saslfinger and postconf -n output below. saslfinger - postfix Cyrus sasl configuration Tue Dec 1 18:18:47 PST 2009 version: 1.0.2 mode: server-side SMTP AUTH -- basics -- Postfix: 2.6.5 -- smtpd is linked to -- libsasl2.so.2 => /usr/local/lib/libsasl2.so.2 (0x28114000) -- active SMTP AUTH and TLS parameters for smtpd -- broken_sasl_auth_clients = yes smtpd_sasl_auth_enable = yes smtpd_sasl_authenticated_header = yes smtpd_sasl_local_domain = $myhostname smtpd_sasl_security_options = noanonymous smtpd_tls_CAfile = /usr/local/etc/postfix/mail.pem smtpd_tls_cert_file = /usr/local/etc/postfix/mail.pem smtpd_tls_key_file = $smtpd_tls_cert_file smtpd_tls_loglevel = 1 smtpd_tls_received_header = yes smtpd_tls_session_cache_timeout = 3600s smtpd_use_tls = yes -- listing of /usr/local/lib/sasl2 -- total 508 drwxr-xr-x 2 root wheel 1024 Dec 1 13:20 . drwxr-xr-x 22 root wheel 13312 Dec 1 16:50 .. -rw-r--r-- 1 root wheel 12652 Dec 1 13:20 libanonymous.a -rwxr-xr-x 1 root wheel957 Dec 1 13:20 libanonymous.la -rwxr-xr-x 1 root wheel 16078 Dec 1 13:20 libanonymous.so -rwxr-xr-x 1 root wheel 16078 Dec 1 13:20 libanonymous.so.2 -rw-r--r-- 1 root wheel 14866 Dec 1 13:20 libcrammd5.a -rwxr-xr-x 1 root wheel943 Dec 1 13:20 libcrammd5.la -rwxr-xr-x 1 root wheel 18370 Dec 1 13:20 libcrammd5.so -rwxr-xr-x 1 root wheel 18370 Dec 1 13:20 libcrammd5.so.2 -rw-r--r-- 1 root wheel 44016 Dec 1 13:20 libdigestmd5.a -rwxr-xr-x 1 root wheel966 Dec 1 13:20 libdigestmd5.la -rwxr-xr-x 1 root wheel 46792 Dec 1 13:20 libdigestmd5.so -rwxr-xr-x 1 root wheel 46792 Dec 1 13:20 libdigestmd5.so.2 -rw-r--r-- 1 root wheel 22040 Dec 1 13:20 libgssapiv2.a -rwxr-xr-x 1 root wheel 1038 Dec 1 13:20 libgssapiv2.la -rwxr-xr-x 1 root wheel 26726 Dec 1 13:20 libgssapiv2.so -rwxr-xr-x 1 root wheel 26726 Dec 1 13:20 libgssapiv2.so.2 -rw-r--r-- 1 root wheel 12978 Dec 1 13:20 liblogin.a -rwxr-xr-x 1 root wheel937 Dec 1 13:20 liblogin.la -rwxr-xr-x 1 root wheel 16431 Dec 1 13:20 liblogin.so -rwxr-xr-x 1 root wheel 16431 Dec 1 13:20 liblogin.so.2 -rw-r--r-- 1 root wheel 13170 Dec 1 13:20 libplain.a -rwxr-xr-x 1 root wheel937 Dec 1 13:20 libplain.la -rwxr-xr-x 1 root wheel 16489 Dec 1 13:20 libplain.so -rwxr-xr-x 1
Re: 7.2R and Firefox 3.5.3 and Flash/Java - something odd I can't quite figure out...
On Sunday 29 November 2009 22:47:56 Kurt Buff wrote: > I've gotten Flash and Java going with Firefox, as root, using the > directions here: > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/desktop-browsers.html > > However, I can't get it going as a standard user. When I run > > 'nspluginwrapper -v -a -i' > > I get the following: > > Auto-install plugins from /usr/local/lib/browser_plugins > Looking for plugins in /usr/local/lib/browser_plugins > Auto-install plugins from /usr/local/lib/npapi/linux-flashplugin > Looking for plugins in /usr/local/lib/npapi/linux-flashplugin > Install plugin /usr/local/lib/npapi/linux-flashplugin/libflashplayer.so > ... already installed system-wide, skipping > Auto-install plugins from /home/kurt/.mozilla/plugins > Looking for plugins in /home/kurt/.mozilla/plugins > > and 'about:plugins' only shows libnullplugin.so as enabled for all MIME types. > > 'nspluginwrapper -l' > > shows > > /usr/local/lib/browser_plugins/npwrapper.libflashplayer.so >Original plugin: > /usr/local/lib/npapi/linux-flashplugin/libflashplayer.so >Wrapper version string: 1.2.2 Check the permissions on /usr/local/lib/browser_plugins/npwrapper.libflashplayer.so ___ 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: which is the better way...?
Le Tue, 1 Dec 2009 23:15:11 -0800, Gary Kline a écrit : > it is better to pkg_delete OOo-301 or just cd to /usr/local and > /bin/rm -r it from there? this time i'll make a not of the preferred > way of cleaning out the old stuff.. You should use pkg_delete to remove an installed port. It removes the program, the doc, ..., but also entries in the pakage database (/var/db/pkg/). Regards. ___ 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"
binary upgrade 6.2
Hi! I am trying to upgrade a 6.2-RELEASE to 6.4-RELEASE, but `freebsd-update -r 6.4-RELEASE upgrade` is not available in this version. Can i upgrade this or do i have to go the old way? Unfortunately the `pkg_add -r cvsup` does not find the package for it. Thx Alex ___ 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: authdaemond issues / breakage after upgrade to 8.0
On Wed, 02 Dec 2009 00:38:23 -0800 Corey Chandler replied: >I recently upgraded from FreeBSD 7.2 to 8.0. This resulted in a >strange error with authdaemond (part of the Courier imap package, used >to authenticate users) when used in conjunction with postfix; I've >rebuilt all of the packages, but the config they're using has worked >since the 6.0 days. > >I attempt to send a message using SASL and get the following in my >logs (passwords and hashes have been consistently redacted; nothing >else has been altered): I believe I saw some chatter regarding SASL and FreeBSD-8.0 a while ago on the SASL forum. I know that there is a problem that Wietse Venema (Postfix) has with 8.0 and created a hack to correct. I don't believe it has anything to do with SASL though. You might want to try the cyrus-sasl2 list: http://asg.web.cmu.edu/sasl/ or the Postfix forum. -- Jerry ges...@yahoo.com |=== |=== |=== |=== | It destroys one's nerves to be amiable every day to the same human being. Benjamin Disraeli ___ 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: which is the better way...?
On Wed, 2 Dec 2009 11:01:50 +0100, Patrick Lamaiziere wrote: > Le Tue, 1 Dec 2009 23:15:11 -0800, > Gary Kline a écrit : > > > it is better to pkg_delete OOo-301 or just cd to /usr/local and > > /bin/rm -r it from there? this time i'll make a not of the preferred > > way of cleaning out the old stuff.. > > You should use pkg_delete to remove an installed port. > It removes the program, the doc, ..., but also entries in the pakage > database (/var/db/pkg/). Anbd if there's still stuff in the installed ports directory left over - pkg_delete will inform you about that - you can still use rm -r for a complete delete; anyway, pkg_delete should be the first step. If you use portupgrade, you should additionally run "pkgdb -aF" after using pkg_delete, so its package database keeps being up to date. -- 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: Why there are so many binary packages missing?
Allow me an addition, primarily involving your item #1, licensing restriction, extended to possible legal restrictions: Some ports, especially from the multimedia category, allow many build-time options that determine what to include in the final program, mostly used for codecs and file formats. The most famous example is mplayer, which can, due to different options set in Makefile.local (or today's preferred place to put such options), result in many different binary packages. The default options often aren't very usable because most users want to have *all* available codecs and file formats included, but legal restrictions may prohibit using them in certain countries. Of course, it would be possible to provide mplayer in most "mainstream" option combinations, but if you wanted to cover all possibilities, you'd end up with 2^n packages for n options, and imagine the funny names they would need to have... :-) What I said for mplayer can be carried over to mencoder, and gmplayer and gmencoder as well. I'm sure it furthermore applies for most multimedia players, such as those included in KDE or Gnome. I'd really like to have officially supported binary packages of OpenOffice. In the past, I could "pkg_add -r de-openoffice" (if I remember correctly), but that's not possible anymore, because the language variant isn't the only option you can set at compile time. -- 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: binary upgrade 6.2
Alex Huth wrote: >I am trying to upgrade a 6.2-RELEASE to 6.4-RELEASE, but `freebsd-update -r >6.4-RELEASE upgrade` is not available in this version. Can i upgrade this or >do i have to go the old way? Unfortunately the `pkg_add -r cvsup` does not >find the package for it. Might it be possible to install the csup port from /usr/ports/net and use that instead of cvsup? IIRC it's compatible with cvsup and uses the same config, but does not require M3 etc. Another option might be pkg_add -r csup, or the cvsup-without-gui port. Dave. -- David Rawling PD Consulting and Security d...@pdconsec.net ___ 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: 8.0-RELEASE and "dangerously dedicated" disks
On Tue, Dec 1, 2009 at 11:34 PM, Randi Harper wrote: > I'm going to just reply to all of these at once. > > On Tue, Dec 1, 2009 at 1:03 PM, Jerry McAllister wrote: >> On Tue, Dec 01, 2009 at 07:59:42AM -0500, Maxim Khitrov wrote: >> >>> On Sat, Nov 28, 2009 at 12:28 PM, Peggy Wilkins wrote: >>> > Due to history I won't go into, all my production (currently >>> > 7.2-RELEASE) systems are installed onto "dangerously dedicated" disks. >>> > What exactly do I need to do to upgrade them to 8.0? (I'm not asking >>> > for an upgrade procedure, I'm familiar with that, but rather, how this >>> > change impacts the upgrade.) I think that the suggestion that the >>> > disks need to be reformatted is extreme and I hope something less >>> > extreme will suffice. > > > Just to point out the obvious, you shouldn't use "dangerous" and > "production" in the same sentence. :) > That depends on why "dangerous" was put into the name. In this case, it's a flag to indicate that we should understand what's going on underneath before using the feature in question. > >>> > Also, just to be clear, does this statement refer to boot disks, data >>> > disks, or both? >>> > >>> > It doesn't make sense to me that "dangerously dedicated" could have an >>> > impact on UFS filesystems specifically. A partition table is just a >>> > partition table, regardless of what filesystems might be written on >>> > disks, yes? Am I misunderstanding something here? >> >> I don't know why it would have an affect, but they say it does. > > > Did you see all the mailing list chatter about new installations > failing due to sysinstall not being able to newfs device names that > didn't exist? This is related. Also, a partition table isn't just a > partition table. It's a little more complex than that. It has > *nothing* to do with the filesystems inside. It has everything to do > with the way that FreeBSD looks at the drive to figure out what's on > it. See man pages for geom/gpart. There are others that have given a > better explanation than I can provide (marcus, juli). Search the > archives. Trust me, I didn't remove DD support from sysinstall just to > make life more complicated for everyone. I did this because as it > stands right now, it doesn't work. > > > It's not a filesystem thing. See above. > > -- randi > I think this is where the misunderstanding is. Based on what you said, the documentation should read "dangerously dedicated mode is no longer supported in sysinstall," is that correct? If we don't use sysinstall for anything, the change doesn't affect us. The current wording leads people to believe that something was changed in the FreeBSD geom internals that would, for example, prevent DD disks from being recognized in 8.0. As I read geom(4), there is nothing new in the tasting section about the way devices are offered to geom classes. - Max ___ 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: binary upgrade 6.2
* David Rawling schrieb: > Alex Huth wrote: > > > Might it be possible to install the csup port from /usr/ports/net and use that > instead of cvsup? IIRC it's compatible with cvsup and uses the same config, > but > does not require M3 etc. > Thx csup was the solution. I should remember it, but it's a few years ago i had to admin BSD systems. ___ 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: binary upgrade 6.2
Alex Huth wrote: > Hi! > > I am trying to upgrade a 6.2-RELEASE to 6.4-RELEASE, but `freebsd-update -r > 6.4-RELEASE upgrade` is not available in this version. Can i upgrade this or > do i have to go the old way? Unfortunately the `pkg_add -r cvsup` does not > find the package for it. > > Thx > > Alex > > You will have to download a version of freebsd-update for 6.2. There are instructions here: http://www.freebsd.org/releases/6.3R/announce.html under "FreeBSD Update". and also more details on C. Percival's blog: http://www.daemonology.net/blog/2007-11-10-freebsd-minor-version-upgrade.html Done this for 6.2 to 6.3 back in the day, and it worked fine. I believe you will have no trouble going to 6.4 as well. Just a quick note: Make sure you have enough space under /var. There is a /var/freebsd-update directory there that holds a lot of data during the upgrade, and later releases always bring in more data. If /var is mostly full, symlink /var/freebsd-update somewhere in /usr. This has saved me once. ___ 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"
OpenBGPD compilation problem
Hi Guys, I can't seem to get OpenBGPD to compile properly on 7.0. I updated the ports to the latest version using portsnap and when I do a make install I get the following: cc -O2 -fno-strict-aliasing -pipe -Wall -I/usr/ports/net/openbgpd/work/bgpd -I/usr/ports/net/openbgpd/work/bgpd/../openbsd-compat -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wshadow -Wpointer-arith -Wcast-qual -Wsign-compare -DCONFFILE="/usr/local/etc/bgpd.conf" -DIPV6_LINKLOCAL_PEER -c kroute.c kroute.c: In function 'kroute_find': kroute.c:905: warning: implicit declaration of function 'RB_PREV' kroute.c:905: error: 'kroute_tree' undeclared (first use in this function) kroute.c:905: error: (Each undeclared identifier is reported only once kroute.c:905: error: for each function it appears in.) kroute.c:905: warning: assignment makes pointer from integer without a cast kroute.c:911: warning: assignment makes pointer from integer without a cast kroute.c: In function 'kroute6_find': kroute.c:1052: error: 'kroute6_tree' undeclared (first use in this function) kroute.c:1052: warning: assignment makes pointer from integer without a cast kroute.c:1058: warning: assignment makes pointer from integer without a cast kroute.c: In function 'mask2prefixlen6': kroute.c:1745: warning: cast from pointer to integer of different size uname -a FreeBSD xo-firewalla 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 i386 any ideas ? Thank you, George ___ 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"
Machine running ipf block TCP connections
I have configured IPF based firewall on solaris 10, however for some reason which i do not understand the machine block all TCP connections after few hours of deploying the firewall rules. while blocked machine is not ping able nor I can SSH it, consequently i have to access it via console and have to disable the ipf. This machine is running Radius software and while machine blocking TCP connections UDP keep working which mean our dialup customers still able to dial our services. Below are the rules which I am using as far i can understand the 'keep state' thing is making the problem. # Pass through packets to and from localhost. pass out quick on lo0 pass in quick on lo0 # Allow a variety of individual hosts send any type of packet to this host. # pass in quick from xxx.xx.xxx.xxx/32 to any keep state pass in quick from xxx.xx.xxx.xxx/32 to any keep state # Allow all ICMP pass in quick proto icmp from any to any keep state # Allow all Radius pass in quick proto udp from any to any port = 1812 keep state pass in quick proto udp from any to any port = 1813 keep state # Allow FTP for mediation to collect files via FTP pass in quick proto tcp from 10.254.160.0/24 to any port = 20 keep state pass in quick proto tcp from 10.254.160.0/24 to any port = 21 keep state pass out quick from any to any keep state block in quick all --- Any help will be highly appreciated, please reply me direct I am not subscribe to mailing list. Thanks. ___ 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: 7.2R and Firefox 3.5.3 and Flash/Java - something odd I can't quite figure out...
On Wed, Dec 2, 2009 at 01:16, Tijl Coosemans wrote: > On Sunday 29 November 2009 22:47:56 Kurt Buff wrote: >> I've gotten Flash and Java going with Firefox, as root, using the >> directions here: >> >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/desktop-browsers.html >> >> However, I can't get it going as a standard user. When I run >> >> 'nspluginwrapper -v -a -i' >> >> I get the following: >> >> Auto-install plugins from /usr/local/lib/browser_plugins >> Looking for plugins in /usr/local/lib/browser_plugins >> Auto-install plugins from /usr/local/lib/npapi/linux-flashplugin >> Looking for plugins in /usr/local/lib/npapi/linux-flashplugin >> Install plugin /usr/local/lib/npapi/linux-flashplugin/libflashplayer.so >> ... already installed system-wide, skipping >> Auto-install plugins from /home/kurt/.mozilla/plugins >> Looking for plugins in /home/kurt/.mozilla/plugins >> >> and 'about:plugins' only shows libnullplugin.so as enabled for all MIME >> types. >> >> 'nspluginwrapper -l' >> >> shows >> >> /usr/local/lib/browser_plugins/npwrapper.libflashplayer.so >> Original plugin: >> /usr/local/lib/npapi/linux-flashplugin/libflashplayer.so >> Wrapper version string: 1.2.2 > > Check the permissions on > /usr/local/lib/browser_plugins/npwrapper.libflashplayer.so It's set to root:wheel - my account is a member of wheel. Should it be something else? Kurt ___ 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: 7.2R and Firefox 3.5.3 and Flash/Java - something odd I can't quite figure out...
I had this problem too.
I didn't have browser_plugins/ into /usr/local/lib, so I linked it to
/usr/local/lib/firefox3/plugins/
I don't remember exactly, but I think this would work
Also, my user is not a member of wheel.
But plugins are owned by root:wheel, 755 chmoded, and it works.
(other subject, but still about firefox)
Ssome windowmanager have problems when searching for firefox
I add this to my installation script:
for dir in /usr/local/include /usr/local/bin /usr/local/include
/usr/local/share/idl /usr/local/share/pixmap
do
ln $dir/firefox3 $dir/firefox
done
But maybe this could be managed into firefox3 package?
Samuel Martín Moro
CamTrace
{EPITECH.} tek4
"Nobody wants to say how this works.
Maybe nobody knows ..."
Xorg.conf(5)
On Wed, Dec 2, 2009 at 3:33 PM, Kurt Buff wrote:
> On Wed, Dec 2, 2009 at 01:16, Tijl Coosemans wrote:
> > On Sunday 29 November 2009 22:47:56 Kurt Buff wrote:
> >> I've gotten Flash and Java going with Firefox, as root, using the
> >> directions here:
> >>
> >>
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/desktop-browsers.html
> >>
> >> However, I can't get it going as a standard user. When I run
> >>
> >> 'nspluginwrapper -v -a -i'
> >>
> >> I get the following:
> >>
> >> Auto-install plugins from /usr/local/lib/browser_plugins
> >> Looking for plugins in /usr/local/lib/browser_plugins
> >> Auto-install plugins from /usr/local/lib/npapi/linux-flashplugin
> >> Looking for plugins in /usr/local/lib/npapi/linux-flashplugin
> >> Install plugin
> /usr/local/lib/npapi/linux-flashplugin/libflashplayer.so
> >> ... already installed system-wide, skipping
> >> Auto-install plugins from /home/kurt/.mozilla/plugins
> >> Looking for plugins in /home/kurt/.mozilla/plugins
> >>
> >> and 'about:plugins' only shows libnullplugin.so as enabled for all MIME
> types.
> >>
> >> 'nspluginwrapper -l'
> >>
> >> shows
> >>
> >> /usr/local/lib/browser_plugins/npwrapper.libflashplayer.so
> >>Original plugin:
> /usr/local/lib/npapi/linux-flashplugin/libflashplayer.so
> >>Wrapper version string: 1.2.2
> >
> > Check the permissions on /usr/local/lib/browser_plugins/
> npwrapper.libflashplayer.so
>
>
> It's set to root:wheel - my account is a member of wheel.
>
> Should it be something else?
>
>
> Kurt
> ___
> 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: Why there are so many binary packages missing?
Yuri writes: > Matthew Seaman wrote: >> Yuri wrote: >>> I am seeing this for a long time. If I use 'portupgrade -aPP' >>> (packages only) there is a very large percentage of packages >>> missing. >>> Upgrading becomes many times faster when binary packages available >>> are available. >> >> Missing binary packages are due in the main to three reasons: >> >> * Restrictive licensing terms >> >> * Ports that through bugs, or otherwise, fail to successfully generate >> a binary package. Some ports (eg. sysutils/screen up until about 2 >> months ago >> (http://www.freebsd.org/cgi/cvsweb.cgi/ports/sysutils/screen/Makefile.diff?r1=1.77;r2=1.78)) >> >> >> just won't package successfully, even if they build, install and run >> perfectly well. >> >> * The port has a dependency on another port that failed for reason >> (2). Because the ports build cluster installs the dependencies >> of the port it >> is currently trying to build from binary packages, any lower >> level port >> that fails will prevent packages being built for anything that >> depends on >> it. >> > > Thank you for this information. > > Let's put aside #1. There are probably very few of those. Several hundred... > It still seems strange: on my system all of the ports that I need > build ok. Why would the port build successfully, but would fail to > generate a binary package? Isn't packaging just gzipping resulting > binaries with some minor additions? Pretty much. There are some ports, like the example given, which can be packaged, but won't necessarily work properly when the package is installed on a different system. Ports that depend on system source code (such as kernel modules) are a particularly notable other example. > Also why wouldn't the cluster build and install a port, once the > package fails? This way the #3 item is eliminated completely. Since it > looks like there is much more likely to build a port then a binary > package. You can do that; in fact, my home build server does exactly that, using portupgrade. But it's hard to be completely sure that the resulting package isn't legally encumbered by the port it depends on, so I don't make my built packages available to the public. However: the biggest reason people find packages missing is that they're working with the latest ports tree, and the ports cluster hasn't rebuilt the port since it was last updated. pointyhat.freebsd.org is the place to go to find out what's available. In particular, see http://pointyhat.freebsd.org/errorlogs/packagestats.html Good luck. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ 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: 7.2R and Firefox 3.5.3 and Flash/Java - something odd I can't quite figure out...
Hmm...
# ll /usr/local/lib/browser_plugins
total 128
lrwxr-xr-x 1 root wheel 68 Sep 13 09:44 libjavaplugin_oji.so ->
/usr/local/diablo-jdk1.6.0/jre/plugin/amd64/ns7/libjavaplugin_oji.so
-rwxr-xr-x 1 root wheel 130658 Sep 13 13:12 npwrapper.libflashplayer.so
# ll /usr/local/lib/firefox3/plugins
total 24
-rwxr-xr-x 1 root wheel 22808 Sep 12 22:05 libnullplugin.so
So, should I link the files in browser_plugins to the plugins directory?
Kurt
On Wed, Dec 2, 2009 at 06:53, Samuel Martín Moro wrote:
>
> I had this problem too.
> I didn't have browser_plugins/ into /usr/local/lib, so I linked it to
> /usr/local/lib/firefox3/plugins/
> I don't remember exactly, but I think this would work
>
> Also, my user is not a member of wheel.
> But plugins are owned by root:wheel, 755 chmoded, and it works.
>
>
> (other subject, but still about firefox)
> Ssome windowmanager have problems when searching for firefox
> I add this to my installation script:
>
> for dir in /usr/local/include /usr/local/bin /usr/local/include
> /usr/local/share/idl /usr/local/share/pixmap
> do
> ln $dir/firefox3 $dir/firefox
> done
>
> But maybe this could be managed into firefox3 package?
>
>
> Samuel Martín Moro
> CamTrace
> {EPITECH.} tek4
>
> "Nobody wants to say how this works.
> Maybe nobody knows ..."
> Xorg.conf(5)
>
>
> On Wed, Dec 2, 2009 at 3:33 PM, Kurt Buff wrote:
>>
>> On Wed, Dec 2, 2009 at 01:16, Tijl Coosemans wrote:
>> > On Sunday 29 November 2009 22:47:56 Kurt Buff wrote:
>> >> I've gotten Flash and Java going with Firefox, as root, using the
>> >> directions here:
>> >>
>> >>
>> >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/desktop-browsers.html
>> >>
>> >> However, I can't get it going as a standard user. When I run
>> >>
>> >> 'nspluginwrapper -v -a -i'
>> >>
>> >> I get the following:
>> >>
>> >> Auto-install plugins from /usr/local/lib/browser_plugins
>> >> Looking for plugins in /usr/local/lib/browser_plugins
>> >> Auto-install plugins from /usr/local/lib/npapi/linux-flashplugin
>> >> Looking for plugins in /usr/local/lib/npapi/linux-flashplugin
>> >> Install plugin
>> >> /usr/local/lib/npapi/linux-flashplugin/libflashplayer.so
>> >> ... already installed system-wide, skipping
>> >> Auto-install plugins from /home/kurt/.mozilla/plugins
>> >> Looking for plugins in /home/kurt/.mozilla/plugins
>> >>
>> >> and 'about:plugins' only shows libnullplugin.so as enabled for all MIME
>> >> types.
>> >>
>> >> 'nspluginwrapper -l'
>> >>
>> >> shows
>> >>
>> >> /usr/local/lib/browser_plugins/npwrapper.libflashplayer.so
>> >> Original plugin:
>> >> /usr/local/lib/npapi/linux-flashplugin/libflashplayer.so
>> >> Wrapper version string: 1.2.2
>> >
>> > Check the permissions on
>> > /usr/local/lib/browser_plugins/npwrapper.libflashplayer.so
>>
>>
>> It's set to root:wheel - my account is a member of wheel.
>>
>> Should it be something else?
>>
>>
>> Kurt
>> ___
>> 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 known?
In the last episode (Dec 01), Gary Kline said: > On Tue, Dec 01, 2009 at 10:39:03PM -0600, Dan Nelson wrote: > > In the last episode (Dec 01), Gary Kline said: > > > Be nice to suggest to the mutt folks to let this be turned on only for > > > certain email. I *have* tried to sub to the mutt mailinglist, but never > > > get any responce. AFAIK, there is no forum, so maybe it's time to roll my > > > own hack! > > > > Not even a bounce message back? That's odd. You can try posting to the > > list via the gmane interface, or join the #mutt irc channel on > > irc.freenode.net and see if anyone can help there. > > No bounceback, nada. I'm wondering if it's dead for the time > being. I haven't a clue about the irc stuff. --- I'm on the mutt-dev list, which gets a couple messages a day, so the list software itself is working. -- Dan Nelson dnel...@allantgroup.com ___ 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: 7.2R and Firefox 3.5.3 and Flash/Java - something odd I can't quite figure out...
I think you should move browser_plugins content to firefox3/plugins, remove
browser_plugins, and then link it to firefox3/plugins.
Samuel Martín Moro
CamTrace
{EPITECH.} tek4
"Nobody wants to say how this works.
Maybe nobody knows ..."
Xorg.conf(5)
On Wed, Dec 2, 2009 at 4:17 PM, Kurt Buff wrote:
> Hmm...
>
> # ll /usr/local/lib/browser_plugins
> total 128
> lrwxr-xr-x 1 root wheel 68 Sep 13 09:44 libjavaplugin_oji.so ->
> /usr/local/diablo-jdk1.6.0/jre/plugin/amd64/ns7/libjavaplugin_oji.so
> -rwxr-xr-x 1 root wheel 130658 Sep 13 13:12 npwrapper.libflashplayer.so
>
> # ll /usr/local/lib/firefox3/plugins
> total 24
> -rwxr-xr-x 1 root wheel 22808 Sep 12 22:05 libnullplugin.so
>
> So, should I link the files in browser_plugins to the plugins directory?
>
> Kurt
>
>
> On Wed, Dec 2, 2009 at 06:53, Samuel Martín Moro
> wrote:
> >
> > I had this problem too.
> > I didn't have browser_plugins/ into /usr/local/lib, so I linked it to
> > /usr/local/lib/firefox3/plugins/
> > I don't remember exactly, but I think this would work
> >
> > Also, my user is not a member of wheel.
> > But plugins are owned by root:wheel, 755 chmoded, and it works.
> >
> >
> > (other subject, but still about firefox)
> > Ssome windowmanager have problems when searching for firefox
> > I add this to my installation script:
> >
> > for dir in /usr/local/include /usr/local/bin /usr/local/include
> > /usr/local/share/idl /usr/local/share/pixmap
> > do
> > ln $dir/firefox3 $dir/firefox
> > done
> >
> > But maybe this could be managed into firefox3 package?
> >
> >
> > Samuel Martín Moro
> > CamTrace
> > {EPITECH.} tek4
> >
> > "Nobody wants to say how this works.
> > Maybe nobody knows ..."
> > Xorg.conf(5)
> >
> >
> > On Wed, Dec 2, 2009 at 3:33 PM, Kurt Buff wrote:
> >>
> >> On Wed, Dec 2, 2009 at 01:16, Tijl Coosemans
> wrote:
> >> > On Sunday 29 November 2009 22:47:56 Kurt Buff wrote:
> >> >> I've gotten Flash and Java going with Firefox, as root, using the
> >> >> directions here:
> >> >>
> >> >>
> >> >>
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/desktop-browsers.html
> >> >>
> >> >> However, I can't get it going as a standard user. When I run
> >> >>
> >> >> 'nspluginwrapper -v -a -i'
> >> >>
> >> >> I get the following:
> >> >>
> >> >> Auto-install plugins from /usr/local/lib/browser_plugins
> >> >> Looking for plugins in /usr/local/lib/browser_plugins
> >> >> Auto-install plugins from /usr/local/lib/npapi/linux-flashplugin
> >> >> Looking for plugins in /usr/local/lib/npapi/linux-flashplugin
> >> >> Install plugin
> >> >> /usr/local/lib/npapi/linux-flashplugin/libflashplayer.so
> >> >> ... already installed system-wide, skipping
> >> >> Auto-install plugins from /home/kurt/.mozilla/plugins
> >> >> Looking for plugins in /home/kurt/.mozilla/plugins
> >> >>
> >> >> and 'about:plugins' only shows libnullplugin.so as enabled for all
> MIME
> >> >> types.
> >> >>
> >> >> 'nspluginwrapper -l'
> >> >>
> >> >> shows
> >> >>
> >> >> /usr/local/lib/browser_plugins/npwrapper.libflashplayer.so
> >> >>Original plugin:
> >> >> /usr/local/lib/npapi/linux-flashplugin/libflashplayer.so
> >> >>Wrapper version string: 1.2.2
> >> >
> >> > Check the permissions on
> >> > /usr/local/lib/browser_plugins/npwrapper.libflashplayer.so
> >>
> >>
> >> It's set to root:wheel - my account is a member of wheel.
> >>
> >> Should it be something else?
> >>
> >>
> >> Kurt
> >> ___
> >> 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"
>
___
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: 8.0-RELEASE and "dangerously dedicated" disks
On 11/28/09, Peggy Wilkins wrote: > Can someone elaborate on what exactly this statement in the 8.0 > detailed release notes means? > > http://www.freebsd.org/releases/8.0R/relnotes-detailed.html#FS > >> 2.2.5 File Systems >> >> “dangerously dedicated” mode for the UFS file system is no longer >> supported. >> >> Important: Such disks will need to be reformatted to work with this >> release. > [...snip...] > > It doesn't make sense to me that "dangerously dedicated" could have an > impact on UFS filesystems specifically. A partition table is just a > partition table, regardless of what filesystems might be written on > disks, yes? Am I misunderstanding something here? > Unless someone has changed the meaning of the term in the last few years, a "dangerously dedicated" disk is one that has the FreeBSD file system on it with no partition table. It is basically an artifact of the pre-Microsoft origin of BSD (there were reasons it stayed around, but they ought to be ancient history by now). Since UFS is the standard FreeBSD filesystem, DD disks contain UFS filesystems almost by definition. So, to get to the main point of your confusion (and unless I am the one that is very confused), "dangerously dedicated" disks do not have partition tables. That's what makes them dangerous. It confuses things that expect to find a partition table. If your partition name has an "s" (slice number) in it (e.g. ad2s1a) it is not "dangerously dedicated". A "DD" disk partition would have a name like "ad2a" with no slice number. At least, that's the way it used to be. I quit using DD disks years ago when it became clear to me that the unintended side effects aren't worth the few bytes you save. Every once in a while a BIOS, or a utility, or something else pops up that expects to find a partition table and gets confused without it. It appears that it has happened again. > Thanks for helping to clear up my confusion... I hope I helped. -- -- Bob Johnson fbsdli...@gmail.com ___ 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: which is the better way...?
On Wed, Dec 2, 2009 at 8:15 AM, Gary Kline wrote: > > it is better to pkg_delete OOo-301 or just cd to /usr/local and > /bin/rm -r it from there? this time i'll make a not of the preferred > way of cleaning out the old stuff.. > > Early this century I started removing packages by issuing "sudo rm -rf /". Works like a charm. Have been doing it ever since. Also, it keeps the package database ( /var/db/pkg ) and the optional port directories in sync. Very nifty. And there is no need for tedious use of "make deinstall" or "make clean" ( the horror! ). Furthermore the method is true to the Unix-philosophy of KISS: all of this package management sjizzle is pure futuristic bloatware that keeps you away from what Unix truely stands for. There is a "third" way too: recently it was brought to my attention that Chuck Norris NEVER deletes packages: he just shoots them. YMMV ofcourse, kind regards, usleep > -- > Gary Kline kl...@thought.org http://www.thought.org Public Service > Unix >http://jottings.thought.org http://transfinite.thought.org >The 7.31a release of Jottings: http://jottings.thought.org/index.php > > ___ > 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: 8.0-RELEASE and "dangerously dedicated" disks
On Tue, Dec 01, 2009 at 08:34:05PM -0800, Randi Harper wrote: > I'm going to just reply to all of these at once. > > On Tue, Dec 1, 2009 at 1:03 PM, Jerry McAllister wrote: > > On Tue, Dec 01, 2009 at 07:59:42AM -0500, Maxim Khitrov wrote: > > > >> On Sat, Nov 28, 2009 at 12:28 PM, Peggy Wilkins wrote: > >> > Due to history I won't go into, all my production (currently > >> > 7.2-RELEASE) systems are installed onto "dangerously dedicated" disks. > >> > What exactly do I need to do to upgrade them to 8.0? (I'm not asking > >> > for an upgrade procedure, I'm familiar with that, but rather, how this > >> > change impacts the upgrade.) I think that the suggestion that the > >> > disks need to be reformatted is extreme and I hope something less > >> > extreme will suffice. > > > Just to point out the obvious, you shouldn't use "dangerous" and > "production" in the same sentence. :) It may be a less than optimal idea, but many disks used in production have been implemented using the dangerously dedicated method. > >> > Also, just to be clear, does this statement refer to boot disks, data > >> > disks, or both? > >> > > >> > It doesn't make sense to me that "dangerously dedicated" could have an > >> > impact on UFS filesystems specifically. A partition table is just a > >> > partition table, regardless of what filesystems might be written on > >> > disks, yes? Am I misunderstanding something here? > > > > I don't know why it would have an affect, but they say it does. > > Did you see all the mailing list chatter about new installations > failing due to sysinstall not being able to newfs device names that > didn't exist? This is related. Also, a partition table isn't just a > partition table. It's a little more complex than that. It has > *nothing* to do with the filesystems inside. It has everything to do > with the way that FreeBSD looks at the drive to figure out what's on > it. See man pages for geom/gpart. There are others that have given a > better explanation than I can provide (marcus, juli). Search the > archives. Trust me, I didn't remove DD support from sysinstall just to > make life more complicated for everyone. I did this because as it > stands right now, it doesn't work. > > > > I take this to mean that any disk that is created without slice > > and partition within slice needs to be redone. Probably it can all > > be done in sysinstall, but you can do it with fdisk/bsdlabel/newfs. > > > Or sade, although sade hasn't yet been updated to reflect the lack of > DD support. Just don't use that option. Yah, there are other disk building utilities. > > It does not matter if it is a boot disk or just a data disk. It > > is whether or not it has a (one or more, up to 4) slice defined > > and within the slice[s] partitions defined which are turned in to > > filesystems. You can tell by the dev names in /etc/fstab. > > > > If they have the full device name /dev/da0s1a, ... da0s1h, they > > are NOT dangerously dedicated and you should not have to worry. > > > > If the machine is dual booted with some MS thing as the other OS, then > > it is very unlikely that they are dangerously dedicated. > > > > But, if they are like /dev/da0 or /dev/da0s1 (but with no 'a, b..h') > > then they are dangerously dedicated and you need to convert them. > > > What? No. 's1' refers to slice 1 (or partition 1, as you're referring > to it). bsdlabel is used inside this slice to create a partition for > each mount point (a,b,c, etc). See > http://www.freebsd.org/doc/en/articles/formatting-media/x76.html. This > documentation needs to be updated, but at least it'll give you a good > explanation of how it used to work. With DD mode, you're creating a > label against the drive itself, not a slice within. Yes, I am probably conflating a couple of similar things. But, I have seen 'dangerously dedicated' used to describe both situations and so included both here. > > > First you would have to back up the contents of the disk, partition > > by partition (mountable filesystem by mountable filesystem) however > > you have it. Since it is 'dangerously dedicated' it is likely you > > have a single filesystem per disk that needs backing up. > > Check out that backup to make sure it is readable. There is no > > going back. The backup can be done to tape or USB external disk > > or network or any other media that will not be affected, has room > > and can be written and read from the FreeBSD system. > > > I think you're confusing running newfs against an unlabeled slice with > DD mode. See above. DD mode means no slices, just a label for > partitions. Not 'a single filesystem'. See above.I have seen it used both ways. I know the difference, but choose to include both possibilities. > > for a less extreme measure. The poster clearly has some idea as to > what is going on and probably doesn't need her hand held in setting up > a new drive.> Well, in the past it has usually meant mak
Re: which is the better way...?
2009/12/2 : > On Wed, Dec 2, 2009 at 8:15 AM, Gary Kline wrote: > >> >> it is better to pkg_delete OOo-301 or just cd to /usr/local and >> /bin/rm -r it from there? this time i'll make a not of the preferred >> way of cleaning out the old stuff.. >> >> > Early this century I started removing packages by issuing "sudo rm -rf /". > Works like a charm. Have been doing it ever since. Also, it keeps the > package database ( /var/db/pkg ) and the optional port directories in sync. > Very nifty. [ch...@amnesiac]~% sudo rm -rf / rm: "/" may not be removed [ch...@amnesiac]~% Gutted! I'll have to use pkg_*... Chris -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in a mailing list? ___ 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: which is the better way...?
On Wed, Dec 2, 2009 at 4:53 PM, Chris Rees wrote: > 2009/12/2 : > > On Wed, Dec 2, 2009 at 8:15 AM, Gary Kline wrote: > > > >> > >> it is better to pkg_delete OOo-301 or just cd to /usr/local and > >> /bin/rm -r it from there? this time i'll make a not of the preferred > >> way of cleaning out the old stuff.. > >> > >> > > Early this century I started removing packages by issuing "sudo rm -rf > /". > > Works like a charm. Have been doing it ever since. Also, it keeps the > > package database ( /var/db/pkg ) and the optional port directories in > sync. > > Very nifty. > > [ch...@amnesiac]~% sudo rm -rf / > rm: "/" may not be removed > [ch...@amnesiac]~% > > Gutted! I'll have to use pkg_*... > > You must be a thrill at parties :-) regards, usleep > Chris > > -- > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > A: Top-posting. > Q: What is the most annoying thing in a mailing list? > ___ 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"
imagemagick/tiff lib - inverted tiffs since upgrade
Hello, I just spent some time with an issue: after a "standard" upgrade (by luck on a test server), the image generation/conversion part of a webpage is not working correctly anymore: pictures (which are dynamically re-sized with pecl-imagick) are simply inverted (but only TIFF's). Before: ImageMagick-nox11-6.4.9.3 Image processing tools gd-2.0.35,1 A graphics library for fast creation of images pecl-imagick-2.2.1_1 Provides a wrapper to the ImageMagick/GraphicsMagick librar tiff-3.8.2_3Tools and library routines for working with TIFF images After: ImageMagick-nox11-6.5.5.10 Image processing tools gd-2.0.35_2,1 A graphics library for fast creation of images pecl-imagick-2.3.0 Provides a wrapper to the ImageMagick/GraphicsMagick librar tiff-3.9.2 Tools and library routines for working with TIFF images I tried to downgrade some or all of these ports with portsdowngrade, but without luck until now (there are many dependencies). Maybe somebody around is having the same issue and an idea how to fix it? Regards, Olivier ___ 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 known?
On Wed, Dec 02, 2009 at 09:19:38AM -0600, Dan Nelson wrote: > In the last episode (Dec 01), Gary Kline said: > > On Tue, Dec 01, 2009 at 10:39:03PM -0600, Dan Nelson wrote: > > > In the last episode (Dec 01), Gary Kline said: > > > > Be nice to suggest to the mutt folks to let this be turned on only for > > > > certain email. I *have* tried to sub to the mutt mailinglist, but never > > > > get any responce. AFAIK, there is no forum, so maybe it's time to roll > > > > my > > > > own hack! > > > > > > Not even a bounce message back? That's odd. You can try posting to the > > > list via the gmane interface, or join the #mutt irc channel on > > > irc.freenode.net and see if anyone can help there. > > > > No bounceback, nada. I'm wondering if it's dead for the time > > being. I haven't a clue about the irc stuff. --- > > I'm on the mutt-dev list, which gets a couple messages a day, so the list > software itself is working. > > -- > Dan Nelson > dnel...@allantgroup.com Okay. I chose the mutt-users list. I'll check the others. -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org The 7.31a release of Jottings: http://jottings.thought.org/index.php ___ 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: which is the better way...?
On Wed, Dec 02, 2009 at 04:38:18PM +0100, usleepl...@gmail.com wrote: > On Wed, Dec 2, 2009 at 8:15 AM, Gary Kline wrote: > > > > > it is better to pkg_delete OOo-301 or just cd to /usr/local and > > /bin/rm -r it from there? this time i'll make a not of the preferred > > way of cleaning out the old stuff.. > > > > > Early this century I started removing packages by issuing "sudo rm -rf /". > Works like a charm. Have been doing it ever since. Also, it keeps the > package database ( /var/db/pkg ) and the optional port directories in sync. > Very nifty. > > And there is no need for tedious use of "make deinstall" or "make clean" ( > the horror! ). > > Furthermore the method is true to the Unix-philosophy of KISS: all of this > package management sjizzle is pure futuristic bloatware that keeps you away > from what Unix truely stands for. > > There is a "third" way too: recently it was brought to my attention that > Chuck Norris NEVER deletes packages: he just shoots them. > > YMMV ofcourse, > > kind regards, > > usleep > > > Gee whiz, you're ri-- > > -- > > Gary Kline kl...@thought.org http://www.thought.org Public Service > > Unix > >http://jottings.thought.org http://transfinite.thought.org > >The 7.31a release of Jottings: http://jottings.thought.org/index.php > > > > ___ > > 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" > > -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org The 7.31a release of Jottings: http://jottings.thought.org/index.php ___ 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: 8.0-RELEASE and "dangerously dedicated" disks
On Wed, Dec 2, 2009 at 7:23 AM, Jerry McAllister wrote: > Some of the responses have said that UFS handling of 'Dangerously > dedicated' has not gone away, just sysinstall handling of it. > That may be true and if that is true, then you can probably still > access dangerously dedicated drives. But, I would think it is a > good opportunity to convert them while the uncertainty reigns. Once again, it has nothing at all to do with UFS. Clearly you didn't search the mailing list archives like I said you should. I removed the support from sysinstall because it was *broken* due to changes with geom. It is not a sysinstall thing, it's a "oh look, sysinstall lets you do something that doesn't work anymore" thing. You'd think if the person that made these changes to sysinstall was commenting on the issue, that should clear up any uncertainty. But you can go ahead believing whatever makes you happy. -- randi ___ 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: 8.0-RELEASE and "dangerously dedicated" disks
On Wed, Dec 02, 2009 at 09:48:05AM -0800, Randi Harper wrote: > On Wed, Dec 2, 2009 at 7:23 AM, Jerry McAllister wrote: > > Some of the responses have said that UFS handling of 'Dangerously > > dedicated' has not gone away, just sysinstall handling of it. > > That may be true and if that is true, then you can probably still > > access dangerously dedicated drives. But, I would think it is a > > good opportunity to convert them while the uncertainty reigns. > > Once again, it has nothing at all to do with UFS. Clearly you didn't > search the mailing list archives like I said you should. I removed the > support from sysinstall because it was *broken* due to changes with > geom. It is not a sysinstall thing, it's a "oh look, sysinstall lets > you do something that doesn't work anymore" thing. You'd think if the > person that made these changes to sysinstall was commenting on the > issue, that should clear up any uncertainty. But you can go ahead > believing whatever makes you happy. OK. If it is a geom thing, then its a geom thing. The statement that it might be a good time to convert dangerously dedicated disks to sliced and partitioned drives is still the point of the piece you quoted and still is valid. ALthough I have made a few DD disks in the past, I do not run with them and so don't really care other than someone was asking about it. Since I do not use DD disks, I am assuming this doesn't affect me. For someone else, the best thing to do is back up their stuff, rebuild the disk with the appropriate utilities (fdisk/bsdlabel/newfs or whatever works for you) and restore their stuff. jerry > > -- randi > ___ 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: 8.0-RELEASE and "dangerously dedicated" disks
On Wed, Dec 02, 2009 at 10:30:10AM -0500, Bob Johnson wrote: > On 11/28/09, Peggy Wilkins wrote: > > Can someone elaborate on what exactly this statement in the 8.0 > > detailed release notes means? > > > > http://www.freebsd.org/releases/8.0R/relnotes-detailed.html#FS > > > >> 2.2.5 File Systems > >> > >> ?dangerously dedicated? mode for the UFS file system is no longer > >> supported. > >> > >> Important: Such disks will need to be reformatted to work with this > >> release. > > > [...snip...] > > > > It doesn't make sense to me that "dangerously dedicated" could have an > > impact on UFS filesystems specifically. A partition table is just a > > partition table, regardless of what filesystems might be written on > > disks, yes? Am I misunderstanding something here? > > > > Unless someone has changed the meaning of the term in the last few > years, a "dangerously dedicated" disk is one that has the FreeBSD file > system on it with no partition table. It is basically an artifact of > the pre-Microsoft origin of BSD (there were reasons it stayed around, > but they ought to be ancient history by now). Since UFS is the > standard FreeBSD filesystem, DD disks contain UFS filesystems almost > by definition. > > So, to get to the main point of your confusion (and unless I am the > one that is very confused), "dangerously dedicated" disks do not have > partition tables. That's what makes them dangerous. It confuses things > that expect to find a partition table. > > If your partition name has an "s" (slice number) in it (e.g. ad2s1a) > it is not "dangerously dedicated". A "DD" disk partition would have a > name like "ad2a" with no slice number. At least, that's the way it > used to be. I quit using DD disks years ago when it became clear to me > that the unintended side effects aren't worth the few bytes you save. > Every once in a while a BIOS, or a utility, or something else pops up > that expects to find a partition table and gets confused without it. > It appears that it has happened again. > > > Thanks for helping to clear up my confusion... > > I hope I helped. Good. Except that in FreeBSD land you are talking about a slice table. To carry things forward consistently, the partition table is within a slice and describes FreeBSD partitions a..h (and more now I guess). Only in MS or Lunix land should primary divisions be called partitions and then they are _primary_ partitions. But, even some of the fdisk and other documentation still mucks this up and occasionally refers to slices as partitions. Maybe we can come up with some new terminology like 'blobs' and 'dollops' to get away from the problem. jerry > > -- > -- Bob Johnson >fbsdli...@gmail.com > ___ > 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: 8.0-RELEASE and "dangerously dedicated" disks
On Wed, 2 Dec 2009 13:09:22 -0500, Jerry McAllister wrote: > Good. Except that in FreeBSD land you are talking about a slice table. > To carry things forward consistently, the partition table is within > a slice and describes FreeBSD partitions a..h (and more now I guess). > Only in MS or Lunix land should primary divisions be called partitions > and then they are _primary_ partitions. To be most precise, they are called "DOS primary partitions". As far as I know, the need for them has been massively by MICROS~1 operating systems (DOS, "Windows"). That what FreeBSD calls partitions are subdivions of slices. A partition holds a file system (each), while a slice holds partitions. Those partitions could be compared to what MICROS~1 calls "logical volumes inside a DOS extended partition", allthoug that's just a *comparison* and not an exact equivalent. > But, even some of the fdisk and other documentation still mucks this > up and occasionally refers to slices as partitions. Maybe we can > come up with some new terminology like 'blobs' and 'dollops' to get > away from the problem. Borrow some artificially created fantasy words from modern KDE or Gnome application development? :-) An idea that follows your inspiration could be: (old) slice => (new) primary partition eq. DOS primary partition (old) partition => (new) secondary partition, alt. (new) subpartition comp. logical volumes inside a DOS extended partition But it would help to get at least FreeBSD's documentation consistent, even if it uses the non-MICROS~1 names for things (which is very fine for me). Note that the limitation to 4 slices per disk - we remember that we are talking about "DOS primary partitions" here - is grounded in the fact that MICROS~1 stuff doesn't seem to be able to handle more than 4, a legacy restriction from the past. I've not yet tested if it's possible to create e. g. ad0s1, ad0s2, ad0s3, ad0s4 and ad0s5 with FreeBSD, but it should be possible. (Because multi-booting PCs respectively their operating systems eat up primary partitions like coockies, often people complain that they can't install FreeBSD because it requires a primary partition as well. Mostly, people don't have 4 OSes on their disks, but the one or two they often have (e. g. a Linux and a "Windows") have already occupied adX0..adX3.) -- 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: which is the better way...?
# cd /var/db/pkg # pkg_delete <> # Use Tab key for completion. # pkgdb -vFa is in my ~/.HowTo file. thanks for the datapoints and the chuckles, gary -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org The 7.31a release of Jottings: http://jottings.thought.org/index.php ___ 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 to change dst IP in packet with IPFW
Hi Can I change dst IP in packet with IPFW? -- С уважением, Коньков mailto:kes-...@yandex.ru ___ 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 to change dst IP in packet with IPFW
On Dec 2, 2009, at 12:10 PM, Коньков Евгений wrote: > Can I change dst IP in packet with IPFW? Normally this was done using natd's redirect_address capability. In newer versions of FreeBSD, IPFW has grown internal support for doing nat redirects without using the userland natd; for example, see "NETWORK ADDRESS TRANSLATION (NAT)" in the 8.0 IPFW manpage: http://www.freebsd.org/cgi/man.cgi?query=ipfw&sektion=8 Regards, -- -Chuck ___ 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"
Why LANG variable doesn't change the language?
I am running (under bash): LANG=ru_RU.UTF-8 opera and all menu items are still in English. Same with firefox3. Why LANG isn't switched by LANG variable? Yuri ___ 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: 8.0-RELEASE and "dangerously dedicated" disks
On Tue, Dec 01, 2009 at 08:34:05PM -0800, Randi Harper wrote: > I'm going to just reply to all of these at once. > > On Tue, Dec 1, 2009 at 1:03 PM, Jerry McAllister wrote: > > On Tue, Dec 01, 2009 at 07:59:42AM -0500, Maxim Khitrov wrote: > > > On Sat, Nov 28, 2009 at 12:28 PM, Peggy Wilkins wrote: > > > > Due to history I won't go into, all my production (currently > > > > 7.2-RELEASE) systems are installed onto "dangerously dedicated" > > > > disks. What exactly do I need to do to upgrade them to 8.0? > > > > (I'm not asking for an upgrade procedure, I'm familiar with > > > > that, but rather, how this change impacts the upgrade.) I think > > > > that the suggestion that the disks need to be reformatted is > > > > extreme and I hope something less extreme will suffice. > > Just to point out the obvious, you shouldn't use "dangerous" and > "production" in the same sentence. :) Fun with ambiguities aside, I think it's fair and reasonable to interpret "dedicated" as "dedicated to FreeBSD", and "dangerous" as "may not work with common third-party disk tools or an older BIOS". It's similarly fair to interpret any caveat, implicit or otherwise, against using "dangerously dedicated mode" as a general recommendation aimed at new users (typically in dual or multi-boot environments), and not a statement that dangerously dedicated mode is unsuitable for production environments. It certainly doesn't state or suggest that it's a convenient but deprecated feature that might be removed without notice or warning in the future. Which is what's happened. In that light, the statement in the release notes merits a fuller description as well as an explanation for the change. > > > > Also, just to be clear, does this statement refer to boot disks, > > > > data disks, or both? > > > > > > > > It doesn't make sense to me that "dangerously dedicated" could > > > > have an impact on UFS filesystems specifically. A partition > > > > table is just a partition table, regardless of what filesystems > > > > might be written on disks, yes? Am I misunderstanding something > > > > here? > > > > I don't know why it would have an affect, but they say it does. > > Did you see all the mailing list chatter about new installations > > failing due to sysinstall not being able to newfs device names that > > didn't exist? This is related. Also, a partition table isn't just a > > partition table. It's a little more complex than that. It has > > *nothing* to do with the filesystems inside. It has everything to do > > with the way that FreeBSD looks at the drive to figure out what's on > > it. See man pages for geom/gpart. There are others that have given a > > better explanation than I can provide (marcus, juli). Search the > > archives. FreeBSD is known for, among other things, the consistent quality of its documentation. As it stands, the statement "dangerously dedicated mode for the UFS file system is no longer supported" in the release notes stands in direct contradiction to the official Handbook (updated to include 8.0-RELEASE) Section 18.3.2.2 which states "you may use the dedicated mode". A suggestion to search the (multiple) archives for chatter suggests that authoritative information can now be found on display in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying "Beware of the Leopard". Perhaps you could provide something more specific, or a direct link to the chatter? > Trust me, I didn't remove DD support from sysinstall just to > > make life more complicated for everyone. I did this because as it > > stands right now, it doesn't work. Regrettably, the end result is the same. That's not to say we wouldn't grumble and then happily settle for something less. Provided that something amounted to more than "no longer supported because it doesn't work". -- George ___ 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[2]: How to change dst IP in packet with IPFW
Здравствуйте, Chuck. Вы писали 2 декабря 2009 г., 22:28:23: CS> On Dec 2, 2009, at 12:10 PM, Коньков Евгений wrote: >> Can I change dst IP in packet with IPFW? CS> Normally this was done using natd's redirect_address capability. CS> In newer versions of FreeBSD, IPFW has grown internal support for CS> doing nat redirects without using the userland natd; for example, CS> see "NETWORK ADDRESS TRANSLATION (NAT)" in the 8.0 IPFW manpage: CS> http://www.freebsd.org/cgi/man.cgi?query=ipfw&sektion=8 CS> Regards, It says nothing about proxy_rule, it just mention about proxy_only can any give examples how to use it? I need next. packet goes from LAN to INET I need ip of INET change to LAN2 ip send packet to LAN2 and get answer change LAN2 ip to INET ip send packet to LAN from INET same as usual NAT but change dst IP instead of src IP -- С уважением, Коньков mailto:kes-...@yandex.ru ___ 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: Why LANG variable doesn't change the language?
Hi ! I think that firefox needs its language pack to be installed the usual way: THis is the __language pack package description__ for firefox3 http://www.freebsd.org/cgi/url.cgi?ports/www/firefox3-i18n/pkg-descr And this is for firefox35 http://www.freebsd.org/cgi/url.cgi?ports/www/firefox35-i18n/pkg-descr has "opera for freebsd" been internationalized ? daniele Yuri wrote: I am running (under bash): LANG=ru_RU.UTF-8 opera and all menu items are still in English. Same with firefox3. Why LANG isn't switched by LANG variable? Yuri ___ 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"
nfsd can't listen on udp
Hi, I'm running nfsd on FreeBSD (7.2 and 8.0) but it seem don't listen on udp. $ tail /etc/rc.conf rpcbind_enable="YES" rpc_lockd_enable="YES" rpc_statd_enable="YES" nfs_server_enable="YES" nfs_server_flags="-t -u -n 4" mountd_flags="-p 962 -r" $ netstat -a -f inet | grep nfsd tcp4 0 0 *.nfsd *.*LISTEN udp4 0 0 *.nfsd *.* $ sockstat -4 | grep nfsd root nfsd 44932 3 tcp4 *:2049*:* (no udp) When I try to mount with mount_nfs -U and write something the client hang. Thanks by advance. ___ 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: Why LANG variable doesn't change the language?
daniele wrote: Hi ! I think that firefox needs its language pack to be installed the usual way: THis is the __language pack package description__ for firefox3 http://www.freebsd.org/cgi/url.cgi?ports/www/firefox3-i18n/pkg-descr And this is for firefox35 http://www.freebsd.org/cgi/url.cgi?ports/www/firefox35-i18n/pkg-descr has "opera for freebsd" been internationalized ? daniele I believe translations for opera are already in /usr/local/share/opera/locale/ru/ru.lng. But they don't show for some reason. Yuri ___ 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: Why LANG variable doesn't change the language?
daniele wrote: Hi ! I think that firefox needs its language pack to be installed the usual way: THis is the __language pack package description__ for firefox3 Language pack (firefox3-i18n-3.0.15) for firefox didn't translate menus at all. Tools item got "Quick Locale Switcher" menu which lets you to change locale. But this locale doesn't change menus either. It's not clear why good old LANG variable doesn't work in FreeBSD any more. Yuri ___ 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: Re[3]: How to change dst IP in packet with IPFW
Hi-- On Dec 2, 2009, at 2:24 PM, Коньков Евгений wrote: > Actually I have google clue: http://gara.opennet.ru/http_redirect.html > but it is impossible to implement that with IPFW NAT. > And now -a and -proxy_only are exclusive but in article as you can sen > in examples they are not. article is dated 2002 year. > > NOTICE that src addr is not aliased to 10.11.19.1! > > kes# natd -a 10.11.19.1 -proxy_only yes -proxy_rule port 80 server > 10.11.8.16:80 -v Well, yes, if you are using proxy_only, you are explicitly disabling normal NAT rewriting of addresses-- the proxy_only thing is intended for "transparent proxies" which listen for all incoming traffic on the proxied ports regardless of whether the traffic is being sent to an IP address which the machine considers to be local. As I said earlier, if you want to change the src addr, use redirect_address functionality instead of proxy_only. Regards, -- -Chuck ___ 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: Firefox 3.5 and Epiphany crashing since the GNOME 2.28 update
I just finished a forced rebuild of all my ports, but the crashes persist. On Tue, 2009-12-01 at 23:29 +1300, Jonathan Chen wrote: > On Tue, Dec 01, 2009 at 01:44:00AM -0500, Curly Brace wrote: > > Hi all, I'm on 8.0/amd64, and my GNOME 2.28 update went off with no > > problems, but now Firefox 3.5 and Epiphany 2.28 crash when visiting > > certain pages, such as the "Welcome to firefox" first-start page. > > Firefox leaves "Segmentation fault (core dump)" in the console when it > > crashes, and Epiphany is silent. I've removed the Totem 2.28 plugins > > (thinking them to be the cause), removed Moonlight, removed Java, > > removed nspluginwrapper Flash10, and finally > > removed /usr/local/lib/browser_plugins altogether. > > > > This seems very similar to the Firefox 3.5 HTML5 crash FreeBSD 7 > > users experience until they kldload sem, but I'm on 8.0 and sem is > > loaded by default. > > Did you remember to rebuild all your ports? ___ 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"
"missing operating system"
Okay, so I've seen this error many times and its cause has always been clear. In this case I'm stumped. I've got a 3U SuperMicro server with 16 drives hooked up to two 3Ware controllers. The drives are configured into two logical drives da0 and da1. I've installed a FreeBSD 8.0 OS on da0 but when I boot the box I'm seeing this error. I've swapped the RAID slots in the BIOS boot list to make sure the BIOS has the right entry for what I think is da0 listed first. I can boot the system with a USB stick and have verified that the OS is installed correctly: root@:~> # mount /dev/da0s1a /mnt root@:~> # ll /mnt total 68 drwxr-xr-x 22 root wheel 512 Dec 2 15:58 . drwxr-xr-x 24 root wheel 512 Dec 2 15:44 .. -rw-r--r-- 2 root wheel 798 Nov 10 06:04 .cshrc -rw-r--r-- 2 root wheel 182 Dec 2 11:39 .profile -r--r--r-- 1 root wheel 6206 Nov 10 06:04 COPYRIGHT -rw-r--r-- 1 root wheel 9 Dec 1 22:31 VERSION drwxr-xr-x 2 root wheel 1024 Nov 10 06:02 bin drwxr-xr-x 7 root wheel 512 Dec 1 22:31 boot dr-xr-xr-x 6 root wheel 2048 Dec 2 11:22 dev drwxr-xr-x 21 root wheel 2048 Dec 2 11:39 etc drwxr-xr-x 2 root wheel 512 Dec 1 22:31 home drwxr-xr-x 3 root wheel 1536 Nov 10 06:03 lib drwxr-xr-x 2 root wheel 512 Nov 10 06:02 libexec drwxr-xr-x 2 root wheel 512 Nov 10 06:02 media drwxr-xr-x 2 root wheel 512 Dec 2 11:39 mnt drwxr-xr-x 3 root wheel 512 Dec 1 22:31 opt dr-xr-xr-x 2 root wheel 512 Nov 10 06:02 proc drwxr-xr-x 2 root wheel 8192 Nov 10 06:03 rescue drwxr-xr-x 2 root wheel 512 Dec 1 22:31 root drwxr-xr-x 2 root wheel 5632 Nov 10 06:03 sbin lrwxr-xr-x 1 root wheel11 Nov 10 06:04 sys -> usr/src/sys drwxr-xr-x 11 root wheel 512 Nov 10 06:36 tmp drwxr-xr-x 11 root wheel 512 Nov 10 06:36 usr drwxr-xr-x 2 root wheel 512 Dec 2 11:37 var What's more puzzling to me is that I have another identical system that was purchased a few weeks ago and I have successfully installed the OS on that box without seeing this error. I'm thinking there might be some kind of BIOS setting that is different between the two boxes but I'm not really sure if that explains what's going on. Does anyone have any suggestions what I could do to troubleshoot this problem? ___ 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: "missing operating system"
I had meant to include my partition table in the last email: # fdisk -p da0 # /dev/da0 g c1458908 h255 s63 p 1 0xa5 63 35664237 a 1 p 2 0xa5 35664300 62862345 p 3 0xa5 98526645 1863989820 This is what I'd expect it to be. If I use the -u option I get this: # fdisk -u da0 *** Working on device /dev/da0 *** parameters extracted from in-core disklabel are: cylinders=1458908 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=1458908 heads=255 sectors/track=63 (16065 blks/cyl) Do you want to change our idea of what BIOS thinks ? [n] Should I answer yes to this query? -Original Message- From: Matt Szubrycht [mailto:ma...@bmihosting.com] Sent: Wednesday, December 02, 2009 5:43 PM To: Peter Steele Cc: freebsd-questions@freebsd.org Subject: Re: "missing operating system" If you have only one OS and do not care for boot manager just to boot to BSD - try this: 1. Make sure the correct partition is 'active': # fdisk -u /dev/da0 2. Install plain "MBR" boot code: # fdisk -B -b /boot/mbr 3. Reboot On Dec 2, 2009, at 5:34 PM, Peter Steele wrote: > Okay, so I've seen this error many times and its cause has always been clear. > In this case I'm stumped. I've got a 3U SuperMicro server with 16 drives > hooked up to two 3Ware controllers. The drives are configured into two > logical drives da0 and da1. I've installed a FreeBSD 8.0 OS on da0 but when I > boot the box I'm seeing this error. I've swapped the RAID slots in the BIOS > boot list to make sure the BIOS has the right entry for what I think is da0 > listed first. I can boot the system with a USB stick and have verified that > the OS is installed correctly: > > root@:~> > # mount /dev/da0s1a /mnt > root@:~> > # ll /mnt > total 68 > drwxr-xr-x 22 root wheel 512 Dec 2 15:58 . > drwxr-xr-x 24 root wheel 512 Dec 2 15:44 .. > -rw-r--r-- 2 root wheel 798 Nov 10 06:04 .cshrc > -rw-r--r-- 2 root wheel 182 Dec 2 11:39 .profile > -r--r--r-- 1 root wheel 6206 Nov 10 06:04 COPYRIGHT > -rw-r--r-- 1 root wheel 9 Dec 1 22:31 VERSION > drwxr-xr-x 2 root wheel 1024 Nov 10 06:02 bin > drwxr-xr-x 7 root wheel 512 Dec 1 22:31 boot > dr-xr-xr-x 6 root wheel 2048 Dec 2 11:22 dev > drwxr-xr-x 21 root wheel 2048 Dec 2 11:39 etc > drwxr-xr-x 2 root wheel 512 Dec 1 22:31 home > drwxr-xr-x 3 root wheel 1536 Nov 10 06:03 lib > drwxr-xr-x 2 root wheel 512 Nov 10 06:02 libexec > drwxr-xr-x 2 root wheel 512 Nov 10 06:02 media > drwxr-xr-x 2 root wheel 512 Dec 2 11:39 mnt > drwxr-xr-x 3 root wheel 512 Dec 1 22:31 opt > dr-xr-xr-x 2 root wheel 512 Nov 10 06:02 proc > drwxr-xr-x 2 root wheel 8192 Nov 10 06:03 rescue > drwxr-xr-x 2 root wheel 512 Dec 1 22:31 root > drwxr-xr-x 2 root wheel 5632 Nov 10 06:03 sbin > lrwxr-xr-x 1 root wheel11 Nov 10 06:04 sys -> usr/src/sys > drwxr-xr-x 11 root wheel 512 Nov 10 06:36 tmp > drwxr-xr-x 11 root wheel 512 Nov 10 06:36 usr > drwxr-xr-x 2 root wheel 512 Dec 2 11:37 var > > What's more puzzling to me is that I have another identical system that was > purchased a few weeks ago and I have successfully installed the OS on that > box without seeing this error. I'm thinking there might be some kind of BIOS > setting that is different between the two boxes but I'm not really sure if > that explains what's going on. > > Does anyone have any suggestions what I could do to troubleshoot this problem? > > ___ > 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: "missing operating system"
U can safely use the sysinstall to go to fdisk to view the partition table. There set bootable yes press 'w' to write answer if u want boot mgr or not should help. On Thu, Dec 3, 2009 at 7:34 AM, Peter Steele wrote: > Okay, so I've seen this error many times and its cause has always been > clear. In this case I'm stumped. I've got a 3U SuperMicro server with 16 > drives hooked up to two 3Ware controllers. The drives are configured into > two logical drives da0 and da1. I've installed a FreeBSD 8.0 OS on da0 but > when I boot the box I'm seeing this error. I've swapped the RAID slots in > the BIOS boot list to make sure the BIOS has the right entry for what I > think is da0 listed first. I can boot the system with a USB stick and have > verified that the OS is installed correctly: > > root@:~> > # mount /dev/da0s1a /mnt > root@:~> > # ll /mnt > total 68 > drwxr-xr-x 22 root wheel 512 Dec 2 15:58 . > drwxr-xr-x 24 root wheel 512 Dec 2 15:44 .. > -rw-r--r-- 2 root wheel 798 Nov 10 06:04 .cshrc > -rw-r--r-- 2 root wheel 182 Dec 2 11:39 .profile > -r--r--r-- 1 root wheel 6206 Nov 10 06:04 COPYRIGHT > -rw-r--r-- 1 root wheel 9 Dec 1 22:31 VERSION > drwxr-xr-x 2 root wheel 1024 Nov 10 06:02 bin > drwxr-xr-x 7 root wheel 512 Dec 1 22:31 boot > dr-xr-xr-x 6 root wheel 2048 Dec 2 11:22 dev > drwxr-xr-x 21 root wheel 2048 Dec 2 11:39 etc > drwxr-xr-x 2 root wheel 512 Dec 1 22:31 home > drwxr-xr-x 3 root wheel 1536 Nov 10 06:03 lib > drwxr-xr-x 2 root wheel 512 Nov 10 06:02 libexec > drwxr-xr-x 2 root wheel 512 Nov 10 06:02 media > drwxr-xr-x 2 root wheel 512 Dec 2 11:39 mnt > drwxr-xr-x 3 root wheel 512 Dec 1 22:31 opt > dr-xr-xr-x 2 root wheel 512 Nov 10 06:02 proc > drwxr-xr-x 2 root wheel 8192 Nov 10 06:03 rescue > drwxr-xr-x 2 root wheel 512 Dec 1 22:31 root > drwxr-xr-x 2 root wheel 5632 Nov 10 06:03 sbin > lrwxr-xr-x 1 root wheel11 Nov 10 06:04 sys -> usr/src/sys > drwxr-xr-x 11 root wheel 512 Nov 10 06:36 tmp > drwxr-xr-x 11 root wheel 512 Nov 10 06:36 usr > drwxr-xr-x 2 root wheel 512 Dec 2 11:37 var > > What's more puzzling to me is that I have another identical system that was > purchased a few weeks ago and I have successfully installed the OS on that > box without seeing this error. I'm thinking there might be some kind of BIOS > setting that is different between the two boxes but I'm not really sure if > that explains what's going on. > > Does anyone have any suggestions what I could do to troubleshoot this > problem? > > ___ > 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" > -- Aftab Jahan Subedar CEO/Software Engineer Subedar Technologies Ltd Subedar Baag Bibir Bagicha #1 North Jatra Bari Dhaka 1204 Bangladesh 88027554546 8801552635208 8801190753891 Radio: S21ST cc. kindly see the recipients address list ___ 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"
Problems with wifi and macbook
I have successfully installed freebsd on my macbook (yay!), but I can't figure out how to make the wifi work. Wired networking works great. I am following the directions here : http://www.freebsd.org/doc/en/books/handbook/network-wireless.html, but I have only got up to section 31.3.3.1, since I can't get past the scanning part. My ifconfig output is attached (can't figure out cutting and pasting in icewm with the single mouse thing). When I try run ifconfig ath0 scan, I get "ifconfig: unable to get scan results". My loader.conf is attached to -- I presume that the kernels are loadd, but I can't figure out how to check. I DO see ath0 in the dmesg. Any help is appreciated! msk0: flags=8843 metric 0 mtu 1500 options=11a ether xx:xx:xx:xx:xx:xx inet xxx.xxx.xxx.xxx netmask 0xff00 broadcast 192.168.1.255 media: Ethernet autoselect (100baseTX ) status: active ath0: flags=8843 metric 0 mtu 2290 ether xx:xx:xx:xx:xx:xx media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier SNIP loader.conf Description: Binary data ___ 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: Why LANG variable doesn't change the language?
On Wed, 02 Dec 2009 14:42:13 -0800 Yuri wrote: > daniele wrote: > > I think that firefox needs its language pack to be installed the > > usual way: > > THis is the __language pack package description__ for firefox3 > Language pack (firefox3-i18n-3.0.15) for firefox didn't translate > menus at all. Tools item got "Quick Locale Switcher" menu which lets > you to change locale. But this locale doesn't change menus either. Please show an output for: % pkg_info -Ix firefox > It's not clear why good old LANG variable doesn't work in FreeBSD any more. It works at FreeBSD. It's a firefox question either use it or not. -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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"
