Re: firefox: after update -> version 23: can not swap tabs
On Mon, 14 Oct 2013 09:50:48 +0200 Matthias Apitz wrote: > El día Monday, October 14, 2013 a las 08:54:56AM +0200, O. Hartmann > escribió: > > > > > After the last major update of www/firefox to version 23 firefox > > rejects of moving/swapping the tabs. They are static now. I do not > > know whether this has to do with the "great pixman update", because > > coincidentally I made bot the pixman update and the update of > > firefox towards revision 23 slipped in. > > > > My ports system and the ports are kept up to day on a almost > > every-two-day basis or at least weekly. > > Hello, > > I have a 10-CURRENT r255948 from October 1st, with all ports from head > too, rev. r328930. > > FF is version 24.0 in the r328930 ports and the tabs can be moved fine > with drag and drop. > > HIH > > matthias > Sorry, FF is in my case 24, too: pkg info firefox firefox-24.0,1 Have you done updating the ports regarding 20130929 in /usr/ports/UPDATING? I did on all boxes and on all boxes I did the tab-stickyness is present. My ports tree is Revision: 330274, my OS is as reported above. signature.asc Description: PGP signature
firefox: after update -> version 23: can not swap tabs
After the last major update of www/firefox to version 23 firefox rejects of moving/swapping the tabs. They are static now. I do not know whether this has to do with the "great pixman update", because coincidentally I made bot the pixman update and the update of firefox towards revision 23 slipped in. My ports system and the ports are kept up to day on a almost every-two-day basis or at least weekly. The underlying OS is now FreeBSD 11.0-CURRENT #1 r256384: Sat Oct 12 18:34:38 CEST 2013 amd64. The question is: is this a kind of miscompilation or has there something minor changed and I didn't noticed that? User error? If some has a tip or hint, I'll appreciate it. Please CC me, I do not subscribe this list. Regards, Oliver signature.asc Description: PGP signature
Migration TeX/LaTeX: from teTeX --> TeXlive
I use for my day to day work teTeX, but I run more and more into several limitations due to the fact, teTeX isn't any more (and regretably) maintained/developed by Th. Esser (that is what I know). Well, TeXlive is now in the ports tree, but I had recently on a server, on which I tried to migrate, massive problems with the most recent CURRENT, where gcc is completely gone (luckily) and converters/iconv has been removed. I can not clearly say what causes the problems, since there seem to be remains of teTeX in the system, but they are needed for some essential facilities and I do not dare ripping them off. Before I start time consuming experiments, I'd like to ask whether there is a smooth way of migration. And for that, please enlighten me how I can extract those ports installed and needed by teTeX (a kind of port-traceback of required ports) and delete them, as far as they do not share common "being required by xxx port", too. Please CC me, I'm not subscribing this list. Regards and thanks, Oliver Hartmann signature.asc Description: PGP signature
Re: trouble with PostgreSQL 9.2 on FreeBSD 10.0-CURRENT: superuser can not autheticate anymore with md5 password hash set
On Tue, 13 Aug 2013 18:22:33 +0200 Terje Elde wrote: > On 13. aug. 2013, at 16:30, "O. Hartmann" > wrote: > > What is going wrong? > > Are you unable to connect, or do you get an error message? If you do, > what is it? > > Terje I always get this message: psql postgres pgsql Password for user pgsql: XX psql: FATAL: password authentication failed for user "pgsql" signature.asc Description: PGP signature
Re: trouble with PostgreSQL 9.2 on FreeBSD 10.0-CURRENT: superuser can not autheticate anymore with md5 password hash set
On Tue, 13 Aug 2013 17:55:06 +0300 Volodymyr Kostyrko wrote: > > 13.08.2013 17:30, O. Hartmann wrote: > >> For the past I ran PostgreSQL 9.2 servers on FreeBSD 10.0-CURRENT > >> successfully. But by now, out of the blue, login as the database's > >> supervisor "pgsql" remotely isn't possible any more. > >> > >> The appropriate lines in pg_hba.conf are: > >> > >> local all pgsql md5 > >> hostssl all pgsql 0.0.0.0/0 md5 > >> > >> The funny thing is: when login locally without providing a password > >> (swap md5 to trust in the "local" line) and setting the password > >> for the role "pgsql" via > >> > >> ALTER ROLE pgsql ENCRYPTED PASSWORD 'FooMe"; > > > > I guess ENCRYPTED means you are substituting FooMe with md5 hashed > > password correctly salted with role name as postgresql requires? > > Silly me, that's wrong. ENCRYPTED only means that password will be > stored encrypted on the disk. There's a side note about using > ENCRYPTED password with postgres in the docs though: > > "Note that older clients might lack support for the MD5 > authentication mechanism that is needed to work with passwords that > are stored encrypted." > Well, even if not ENCRYPTED it doesn't work anymore and prior to this failure, the passwords were stored md5 hashed via pgadmin3 all the time - and it worked. I made now another test. On a FreeBSD 9.2 box which is also running PostgreSQL 9.2 and to which I have access the way that is now rejected by the others, I did a login as the supervisor (pgsql) successfully and then set the password for that supervisor again with alter role pgsql with encrypted password 'FooMe'; (FooMe was the passowrd used before on the same system, it worked definitely) and - booom - I can not login anymore onto that machine! Something is definitely wrong. I have no idea what is wrong here. signature.asc Description: PGP signature
trouble with PostgreSQL 9.2 on FreeBSD 10.0-CURRENT: superuser can not autheticate anymore with md5 password hash set
For the past I ran PostgreSQL 9.2 servers on FreeBSD 10.0-CURRENT successfully. But by now, out of the blue, login as the database's supervisor "pgsql" remotely isn't possible any more. The appropriate lines in pg_hba.conf are: local all pgsql md5 hostssl all pgsql 0.0.0.0/0 md5 The funny thing is: when login locally without providing a password (swap md5 to trust in the "local" line) and setting the password for the role "pgsql" via ALTER ROLE pgsql ENCRYPTED PASSWORD 'FooMe"; or doing the same via pgadmin3 from remotely by also swapping md5 to trust in the line "hostssl" for global network, it seems I could alter/change the password for the supervisor pgsql. But restoring the password check by setting back "md5" leaves me locked out! By the way, this strange behaviour occurs on ALL(!) PostgreSQL 9.2 servers running on FreeBSD 10.0-CURRENT boxes. Ports databases/postgresql-XXX as well as FreeBSD is as of the latest sources and up to date. What is going wrong? Please CC me. Regards, Oliver signature.asc Description: PGP signature
Re: cursor keys not working on console
On Thu, 08 Aug 2013 21:18:15 -0400 Thomas Dickey wrote: > On Thu, Aug 08, 2013 at 07:53:04PM +0200, O. Hartmann wrote: > > The cursor keys on the consoles in freebsd CURRENT (no X11 virtual > > consoles, the FreeBSD consoles!) do not work for me. > > > > I use tcsh as the main shell. > > As set by default in /etc/ttys, the console's terminal type is > > xterm. Switching to > > > > setenv TERM cons25 > > > > solves the problem, but the menus in ports via make config look ugly > > and more ugly, but they are unusable with the setting "TERM=xterm". > > > > What is wrong here? Why are the cursor keys not working in the > > console/ports menu as expected when using tcsh/csh as default shell? > > from infocmp (cons25 vs xterm): > > kcub1: '\E[D', '\EOD'. > kcud1: '\E[B', '\EOB'. > kcuf1: '\E[C', '\EOC'. > kcuu1: '\E[A', '\EOA'. > > It's probably > > http://invisible-island.net/ncurses/ncurses.faq.html#cursor_appmode > > You would probably find > TERM=xterm-noapp > > and improvement. > Hello. Thanks, this works for me. I was wondering if others did not have the same problem, since I use only standard settings for the console (except that I use csh/tcsh instead of sh). Regards, Oliver signature.asc Description: PGP signature
cursor keys not working on console
The cursor keys on the consoles in freebsd CURRENT (no X11 virtual consoles, the FreeBSD consoles!) do not work for me. I use tcsh as the main shell. As set by default in /etc/ttys, the console's terminal type is xterm. Switching to setenv TERM cons25 solves the problem, but the menus in ports via make config look ugly and more ugly, but they are unusable with the setting "TERM=xterm". What is wrong here? Why are the cursor keys not working in the console/ports menu as expected when using tcsh/csh as default shell? Plese CC me. Regards, Oliver signature.asc Description: PGP signature
Re: mail/claws-mail: exporting mail filters?
On Sat, 08 Jun 2013 10:11:52 +0200 "Herbert J. Skuhra" wrote: > On Sat, 8 Jun 2013 09:04:12 +0200 > "O. Hartmann" wrote: > > > Since I use on several boxes private and in the deprtment the same > > email accounts, I'd like to export the mail filters I created and > > import them to other boxes. I didn't figure out yet how to perform > > this task on claws-mail. I realized that this is still a point > > "still under construction on close to every platform I used for > > mailing. > > > > Does anyone has an idea? > > 1. Ask on the claws mailing list? > 2. Use a search engine? > 3. Search the claws mailing list archive on gmane? > 4. Read the claws-mail man page? > 5. Copy ~/.claws-mail/matcherrc? > Thanks. O. signature.asc Description: PGP signature
mail/claws-mail: exporting mail filters?
I switched from Thunderbird to evolution and have now claws-mail on FreeBSD (Thunderbird coredumps on our OpenLDAP installation since years for now). Since I use on several boxes private and in the deprtment the same email accounts, I'd like to export the mail filters I created and import them to other boxes. I didn't figure out yet how to perform this task on claws-mail. I realized that this is still a point "still under construction on close to every platform I used for mailing. Does anyone has an idea? Please CC me, I'm not subscribing this list. Regards, Oliver signature.asc Description: PGP signature
mail/claws-mail: INBOX shows still moved or deleted mails, filtering not working properly
After a struggle with OpenLDAP and Thunderbird (core dumps all over the place when using Thunderbird with OpenLDAP backed users), I moved to Evolution, which is unsatisfying, since calendar function immediately makes Evolution crahs on all tested FreeBSD platforms (9.1-STABLE, 10.0-CURRENT). I tried mail/claws-mail for now and I'm surprised how "cryptic" and fast an email client can be, but I also have serious struggles with this email client. When fetch and filtering Emails from the account of our computer center's IMPA4 mail servers, the moved and even deleted emails remain visible (but greyished) in the INBOX or any other folder and marked deleted. Filtered and filter induced moves of mails also are greyed, still visible in the main INBOX of the email account but marked with the flag for new mail in INBOX. I can not delete them from INBOX. This behaviour is odd. I searched Grand Master Google for that and found relatively old bug reports about such behaviour, but that should be solved. I exclude misconfigurations, since I already configured those "immediate actions" as recommended. Nor Evolution nor thunderbird show that weird behaviour and they operate as expected on all mail actions. Maybe someone could give me a hint what to check. Personally, I consider this behaviour a bug and renders another email client unusable on FreeBSD, but I might be terribly wrong here and still suffer from a configuration inconvenience. Please CC me, I'm no subscriber of both lists. Thanks in advance, Oliver Hartmann ___ 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"
PostgreSQL 9.2: database replication on demand - easy way (Bucardo in ports not available)
Dear Sirs. I send my question to this list in the hope someone has the same problems and already found a solution. I will start explaining the background and my difficulties with recent solutions. We/I have a FreeBSD 10 box running a PostgreSQL 9.2 server containing literature references via RefDB, some sort of bugtracking via Bugzilla, several astronomical databases of the IAU (minor planet objects) and others. Those databases are kept and maintained on one single box at the department. Since a lot of the data is needed in my home office or at a lab with non-permanent internet connection, I desperately need to synchronize the databases kept on the "master" with some backup database systems acting as "master/slave" when they are online. The latter definition is fuzzy, since what I need is an automated synchronization of the "real" master with a sporadically upcoming "slave" at home or at field sites for my science where, as said, the internet connectivity isn't provided 24/7. I feel realy uncomfortable with the built-in streaming replication of PostgreSQL 9.2 since I never managed it to make a successful replication. As far as I understand, the streaming mechanism of PostgreSQL 9.X expects the "slaves" to be always online, to which the replication. I was said that Bucardo (http://bucardo.org/) would be the tool of choice, but FreeBSD ports seem not not have this tool. SLONY also is a way to complicated for my for just this task - or I'm to dumb to perform a solution that fits easily. Is someone out here who might have the same problems and already figured out how to solve this? I do not want to go into this crap "pg_dump", since I tried this many times and it failed due to some issues I never figured out why in PostgreSQL 9.2. Sorry being unspecific here, it is a long time since I tried this frustrating task and it boiled always down to some confusing "postgres/template1" issues when dumping the master and trying to update the "slave". Even following the textbook's suggestions ended up in a mess. Well, I appreaciate some hints and concepts (working, not hypothetical "could be's", those are floating enough around the FreeBSD related net). Thanks in advance and thanks for the patience, Oliver signature.asc Description: OpenPGP digital signature
Re: databases/postgresql: simple mirroring of a database or a whole server
On 01/15/13 13:14, Amitabh Kant wrote: > On Tue, Jan 15, 2013 at 4:24 PM, O. Hartmann > wrote: > >> Hello list. >> >> First, please set me CC, i do not subscribe this list. >> >> I'd like to ask for a mirroring solution of an important databse on my >> installations across at least three boxes. The setup is as follows. >> >> Operating system is FreeBSD 10.0/amd and 9.1-STABLE/amd64. A top of the >> OS there is on all machines in question port >> databases/postgresql92-server|client running. >> >> I have a database that needs to be synchronized/mirrored. A data >> consistency in a narrow timeframe isn't necessary. The database in >> question is a very important literature reference db which is maintained >> via a web interface and this is done mostly from a private box at home, >> which changes the local database set. This database is also used at the >> lab. Usually, I have to dump the db, send it via ssh/scp over the net to >> the target machine and restore it - and this at least three times. Since >> network connectivity isn't available for some technical reasons when I >> maintain the local db at home, this task is a pain, if I forget to >> dump/restore the database. The task maintaining the databases like that >> isn't appreciable. >> >> So, I looked out for a mirroring solution. I came across SLONY I/II, but >> I feel not very comfortable with the complicated setup. Although having >> had a howto, it dind't work properly. So I'm looking for something more >> simple. >> >> The data consistency within short timeframes isn't so important, so a >> mission critical mirroring isn't necessary. But I would be feel better >> having something more "automatic" that is synchronizing more than two or >> three machines automatically when network connectivity is available. >> >> Is there a solution - easy task - to handle such a scenario? >> >> Thanks in advance, >> Oliver >> >> > Since you are using postgresql 9.2, why don't you use the inbuilt > replication that comes with it. You might be interested in this page > http://www.postgresql.org/docs/9.2/static/high-availability.html . > > In case you face any difficulties, u can always head over to pgsql mailing > list. (pgsql-gene...@postgresql.org) > > Amitabh > Thank you very much for this hint! I'm new to the 9.X series, so I didn't realize that there is something new built-in. Valuable hint. Regards, Oliver signature.asc Description: OpenPGP digital signature
databases/postgresql: simple mirroring of a database or a whole server
Hello list. First, please set me CC, i do not subscribe this list. I'd like to ask for a mirroring solution of an important databse on my installations across at least three boxes. The setup is as follows. Operating system is FreeBSD 10.0/amd and 9.1-STABLE/amd64. A top of the OS there is on all machines in question port databases/postgresql92-server|client running. I have a database that needs to be synchronized/mirrored. A data consistency in a narrow timeframe isn't necessary. The database in question is a very important literature reference db which is maintained via a web interface and this is done mostly from a private box at home, which changes the local database set. This database is also used at the lab. Usually, I have to dump the db, send it via ssh/scp over the net to the target machine and restore it - and this at least three times. Since network connectivity isn't available for some technical reasons when I maintain the local db at home, this task is a pain, if I forget to dump/restore the database. The task maintaining the databases like that isn't appreciable. So, I looked out for a mirroring solution. I came across SLONY I/II, but I feel not very comfortable with the complicated setup. Although having had a howto, it dind't work properly. So I'm looking for something more simple. The data consistency within short timeframes isn't so important, so a mission critical mirroring isn't necessary. But I would be feel better having something more "automatic" that is synchronizing more than two or three machines automatically when network connectivity is available. Is there a solution - easy task - to handle such a scenario? Thanks in advance, Oliver signature.asc Description: OpenPGP digital signature
FreeBSD: GIT instaed of SVN?
When it comes to keeping sources, most developer and most large dislocated and non-centralized projects prefer GIT over Subversion. FreeBSD has moved from the ancient CVS to Subversion not long ago and I was wondering why freeBSD would have done this, since Subversion lacks in so many aspects of a modern revision system. Well, I face several odds now since I need a kind of hot replication system that replicates my Subversion repositories and I feel uncomfortable with the way Subversion performs this. I decided to move forward to GIT which seems more appropriate in any aspect and while I do not have so much legacy to carry on with, I think for me pesonally the move is more logical. But what is with the FreeBSD project? Are there any attempts or intentions to bring GIT also to the sources (the base system, the ports)? oh signature.asc Description: OpenPGP digital signature
PPPOED: reading data of line quality from the A/DSL modem
When using modern SoGo A/DSL routers, most devices do have fancy GUIs and information screens about the settings of the device and especially the line quality, like SNR, dampening et cetera. In my private office, I've setup a FreeBSD server acting like a gateway/router, replacing my oldish non-IPv6 capable ADSL modem/router. Using a secondary NIC connecting to the ADSL modem via PPPOED, I'd like to read some of the important statistsics from the device's chipset like line quality informations. Sometimes our line here go bad and with the setup at the moment, I can not check what's wrong. Also, I have no informations about the actual up- and downstream speed, which is also important to me. Since most professional/commercial ADSL routers/modems use opensource software, most prefereably Linux, I was wondering if there isn't a way to achieve those data from FreeBSD as well. I prefer the system's tools in favour over a port installation, but if there is a sophisticated software, I would appreciate a hint or tip. Thanks, Oliver P.S. Please set me CC, I do not subscribe this list. signature.asc Description: OpenPGP digital signature
Multiple SSID with WiFi adapter and hostapd?
I have a question for short (since I failed, possibly due to configuration inabilities of myself): is it possible to have multiple SSID on the very same WiFi hardware adapter (TP-Link Atheros based type)? Idea is, to have pseudo device wlan0 assigned to a SSID for the internal use and another SSID for guests, which is not allowed to access internal server infrastructure. I tried another pseudo device "wlan1" and configured it the very same way in /etc/hostapd.conf, but this failed. Please set me CC/email me, I do not subscribe the list. Thanks in advance and regards, oliver signature.asc Description: OpenPGP digital signature
Re: HELP! core dumps: install, mtree, et cetera all of the sudden after portmaster security/cyrus-sasl2
Am 08/16/12 21:44, schrieb Garrett Cooper: > On Thu, Aug 16, 2012 at 8:33 AM, Hartmann, O. > wrote: >> >> I ran into a very delicate and nasty situation. > > ... > >> On both FBSD 10 boxes, the installation of the port security/cyrus-sasl2 >> got corrupted by "install" and/or "mtree" dumping core and signalling >> SIGNAL 11. Booting into multiuser mode is impossible, login core dumps >> SIGNAL 11, many other daemons, too. The only way is to boot into single >> user mode. > > I'm not drawing a correlation between this and unrelated coredumping > processes. Me neither, I report this for completeness, since I'm not a OS developer, such a behaviour could hint/indicate people who are involved in the OS development, what is going on. Sorry when I'm trying to be too precise (precise as precise I can be without the exact terminology!). > >> An installation failed due to pkg(ng) was missing libarchive.so via >> portmaster or via core dumping install(1). By installing on one box, my >> home box, port security/cyrus-sasl2 manually, luckily install(1) and >> mtree(1) didn't coredump and it worked - and this precedure rescued me. >> But on my lab's development box, it doesn't work! > > Don't make delete-old-lib unless you have it moved off to compat > directories, or have rebuilt everything using the new libarchive. I didn't! As I wrote before, this mess happened on ALL(!) freeBSD 10.0-CURRENT boxes in the very same way when I updated/reinstalled security/cyrus-sasl2. Moreover: I can reproduce this on all boxes. All my boxes use OpenLDAP as a backend with SASL2 enabled (not used so far). > >> On this specific box, where this nasty problem also occured the same way >> by simply recompiling everything for port www/apache22, including the >> reinstallation of port security/cyrus-sasl2. Nearly every binary is >> suddenly coredumping (as on the home box). login, vi, install, devfs, >> syslogd, mtree, id, find ... a whole lot of binaries seem to be >> compromised by something I do not see (libsasl2.so perhaps?). > > truss the binaries to figure out exactly what's going wrong. I will try, but when this errative coredumps of binaries occur, nothing works properly that is using any kinf of dynamical loaded library! Only the binaries (static?) from /resucue/* do their work. > > A lot of this lost effort could be avoided (like others have posted on > the list more than once), by having a centralized package distribution > server, and by having VMs or jails and keeping snapshots with > pre-upgrade state on the package building machine to avoid "dead in > the water scenarios" like you're in right now. Yes, I'm working on this. it seems, that it becomes more relevant since I realized that FreeBSD suffers sometimes from misleaded ports or ports which suddenly are marked BROKEN and do not get compiled ... > >> I tried to help myself via copying /rescue/vi to /usr/bin/vi to have at >> least a working vi. But in /rescue, I can not find install or mtree. I'm >> not familiar with the sophisticated ways of /rescue. Where are >> install(1) and mtree(1)? > > I ran into this issue too a little while ago. I basically gave up on > recovering a VM and nuked and repaved it using a LiveCD with a chroot, > some cp -p'ing, etc. But yes.. it would be nice if I could have > recovered the system at least with a static toolchain: cc, binutils > [equivalent], mtree, install, etc. This is how I recovered the nasty broken box. The other one was easy to recover by reinstalling security/cyrus-sasl2. I'm quite sure that there is something very foul with something in LDAP or SASL2, since I can reproduce that proplem. I saw that rtdl-elf has got some quirks these days, I will try to go behind the date/version of the source tree when it was committed and check whether this is the problem. > > ... > >> Disabling this pkgng tag leads to reinstallation of missing packages, >> which are store in the pkgng sqlite format and not as ASCII anymore, but >> then I get >> /var/runld-elf.so.hints: No such file or directory >> Error: shared library "iconv.3" does not exist. > > service ldconfig start ? Yes ... sorry ... in the heat of the fight I forgot ... but it doesn't make the problem go away. > >> But most of the libs have never been touch! So what is the loader >> complaining about? > > ... > >> I tried to find rescue images and a rescue DVD of a snap shot server, >> but there is no way to crawl through the informations on the web pages >> towards a snapshot. All folders end up in 2011 and highly outdated >> (www.freebsd.org, I didn't look at mirrors since I thought the main >> server carries the most recent stuff). This isn't funny. No lead, no >> hint, even in the download section. >> >> If someone has some hints how to recompile the sources with an emergency >> booted disk, I highly appreciate some desater advice. Maybe the release >> of FreeBSD-10-CURRENT sources I compiled do have accidentally a nasty >> bug, so it would be nice to
HELP! core dumps: install, mtree, et cetera all of the sudden after portmaster security/cyrus-sasl2
I ran into a very delicate and nasty situation. On several boxes, FreeBSD 9.1-PRE and FreeBSD 10-CURRENT (build of CURRENT sources from yesterday, r239295 Wed August 15 17:04:51 CEST 2012 amd64, I had to recompile all requirements of port Apache22, since after the port update it core dumped. On FreeBSD 9.1-PRE, with pkg(ng), things went well. Recompilation and installation of all "portmaster -f apache-2.2" requirements went perfect. On both FreeBSD 10-CURRENT boxes it ended up in a mess, all of a sudden(!), while reinstalling port security/cyrus-sasl2, things started to fail in a dramatik way! On both FBSD 10 boxes, the installation of the port security/cyrus-sasl2 got corrupted by "install" and/or "mtree" dumping core and signalling SIGNAL 11. Booting into multiuser mode is impossible, login core dumps SIGNAL 11, many other daemons, too. The only way is to boot into single user mode. An installation failed due to pkg(ng) was missing libarchive.so via portmaster or via core dumping install(1). By installing on one box, my home box, port security/cyrus-sasl2 manually, luckily install(1) and mtree(1) didn't coredump and it worked - and this precedure rescued me. But on my lab's development box, it doesn't work! On this specific box, where this nasty problem also occured the same way by simply recompiling everything for port www/apache22, including the reinstallation of port security/cyrus-sasl2. Nearly every binary is suddenly coredumping (as on the home box). login, vi, install, devfs, syslogd, mtree, id, find ... a whole lot of binaries seem to be compromised by something I do not see (libsasl2.so perhaps?). I tried to help myself via copying /rescue/vi to /usr/bin/vi to have at least a working vi. But in /rescue, I can not find install or mtree. I'm not familiar with the sophisticated ways of /rescue. Where are install(1) and mtree(1)? Trying to reinstall security/cyrus-sasl2 from single-user fails due install coredumps. pkg(ng) fails due to missing libpkg.so.5 and even rejects being reinstalled. But /usr/local/lib/libpkg.so.0 is even there! Disabling the use of pkg with commenting out WITH_PKGNG=yes in /etc/make.conf leads to the above issues with mtree and install. Disabling this pkgng tag leads to reinstallation of missing packages, which are store in the pkgng sqlite format and not as ASCII anymore, but then I get /var/runld-elf.so.hints: No such file or directory Error: shared library "iconv.3" does not exist. But most of the libs have never been touch! So what is the loader complaining about? Well, I'm floating like a dead man in the water and I'm glad that one box survided although suffering from the same symptomes. I tried to find rescue images and a rescue DVD of a snap shot server, but there is no way to crawl through the informations on the web pages towards a snapshot. All folders end up in 2011 and highly outdated (www.freebsd.org, I didn't look at mirrors since I thought the main server carries the most recent stuff). This isn't funny. No lead, no hint, even in the download section. If someone has some hints how to recompile the sources with an emergency booted disk, I highly appreciate some desater advice. Maybe the release of FreeBSD-10-CURRENT sources I compiled do have accidentally a nasty bug, so it would be nice to update the sources and have a complete recompilation done. Thanks in advance, oh signature.asc Description: OpenPGP digital signature
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
On 06/22/12 08:22, Hans Petter Selasky wrote: > On Friday 22 June 2012 08:01:38 O. Hartmann wrote: >> I have a USB drive/stick, Lexar USB Flash drive as reported by FreeBSD >> shown below. >> When first used, I was able to put approx. 30 GB of data on it - it was >> visible to FreeBSD 9 and 10 as expected. >> A Linux system at the lab was also capable of recognizing it. After >> that, I tried to operate on the stick on a Notebook, FreeBSD 9, and >> another station, FreeBSD 10. But FreeBSD didn't recognize the USB drive >> anymore - sometimes, but this seems to be a gambling issue :-( >> >> Trying Linux on different hardware platforms and even those machines >> prior not recognizing the USB drive do recognize the drive as Lexar USB >> Flash drive with 64GB. That is Suse Linux (some 12.XX), that is Ubuntu >> 12.04, that is Windows 7 Pro/x64. I can format the drive, I can push and >> pull data from it. >> >> So, since the USB drive won't work with three different FreeBSD boxes >> (one running 9-STABLE, two 10-CURRENT, all systems most recent sources >> and buildworld from a day ago). >> I suspect either a weird configuration issue I use on all platforms in >> questions in common triggering the weird beviour - or FreeBSD is simply >> incapable of handling the 64GB drive. I do not have issues with USB >> drives with capacities of 32, 8 or 4 GB of different brands. >> >> As shown in the portion of the dmesg below, the USB drive is recognized >> physically. It doesn't matter whether USB port I use (I tried all >> available on all boxes and in most cases I use a Dell UltraSharp powered >> in-screen HUB). Since other OSes handle the drive as expected, I exclude >> hardware issues. >> >> All FreeBSD in common is the fact I use the new device ahaci/device ata >> CAM/ATA scheme with devcie scbus in the kernel (I use custom kernels!). >> >> Apart from trying a GENERIC kernel (which is next I will do this >> weekend), does anyone have similar experiences and probably solutions? >> >> Regards, >> oh >> >> ugen7.6: at usbus7 >> umass1: on >> usbus7 (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 >> (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error >> (probe0:umass-sim1:1:0:0): Retrying command >> (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 >> (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error >> (probe0:umass-sim1:1:0:0): Retrying command >> (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 >> (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error >> (probe0:umass-sim1:1:0:0): Retrying command >> (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 >> (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error >> (probe0:umass-sim1:1:0:0): Retrying command >> (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 >> (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error >> (probe0:umass-sim1:1:0:0): Error 5, Retries exhausted > > Hi, > > After plugging the device, try: > > usbconfig -d 7.6 add_quirk UQ_MSC_NO_INQUIRY > > Then re-plug it. > > I'm sorry to say a lot of USB flash sticks out there are broken and only > tested with the timing of MS Windows. Part of the problem is that it is > difficult to autodetect these issues, because once you trigger the non- > supported SCSI command, then the flash key stops working like you experience. > > I would be more than glad to open up an office to certify USB devices for use > with FreeBSD :-) > > --HPS > I tried the USB drive this morning with the recommended quirk shown above on FreeBSD 10.0-CURRENT #1 r237462: Sat Jun 23 01:00:35 CEST 2012 without success. I get the same error message as shown above. With or without quirk. I then started Windows 7 on the same box. The USB drive is seen as expected and reflects what I experienced on every other non-FreeBSD box and hardware in the lab on last week. I reformatted the USB drive with extFAT and standard block size on Windows 7. The USB drive is now seen again on FreeBSD and recognized as a drive. "Seen" in my sloppy terminology means: recognized as a disk. The hardware is recognized, but it is not recognized as a drive. The fact, that the very first time after I bought that USB drive, I was able to put several GB on it, use it on both FreeBSD 9-STABLE and 10-CURRENT, and then it broke, drives me nuts. Using the very same pen drive on other OSes even on the same hardware without issues makes me believe FreeBSD does have an issue, not the USB drive. I will fill the USB drive w
USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
I have a USB drive/stick, Lexar USB Flash drive as reported by FreeBSD shown below. When first used, I was able to put approx. 30 GB of data on it - it was visible to FreeBSD 9 and 10 as expected. A Linux system at the lab was also capable of recognizing it. After that, I tried to operate on the stick on a Notebook, FreeBSD 9, and another station, FreeBSD 10. But FreeBSD didn't recognize the USB drive anymore - sometimes, but this seems to be a gambling issue :-( Trying Linux on different hardware platforms and even those machines prior not recognizing the USB drive do recognize the drive as Lexar USB Flash drive with 64GB. That is Suse Linux (some 12.XX), that is Ubuntu 12.04, that is Windows 7 Pro/x64. I can format the drive, I can push and pull data from it. So, since the USB drive won't work with three different FreeBSD boxes (one running 9-STABLE, two 10-CURRENT, all systems most recent sources and buildworld from a day ago). I suspect either a weird configuration issue I use on all platforms in questions in common triggering the weird beviour - or FreeBSD is simply incapable of handling the 64GB drive. I do not have issues with USB drives with capacities of 32, 8 or 4 GB of different brands. As shown in the portion of the dmesg below, the USB drive is recognized physically. It doesn't matter whether USB port I use (I tried all available on all boxes and in most cases I use a Dell UltraSharp powered in-screen HUB). Since other OSes handle the drive as expected, I exclude hardware issues. All FreeBSD in common is the fact I use the new device ahaci/device ata CAM/ATA scheme with devcie scbus in the kernel (I use custom kernels!). Apart from trying a GENERIC kernel (which is next I will do this weekend), does anyone have similar experiences and probably solutions? Regards, oh ugen7.6: at usbus7 umass1: on usbus7 (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Error 5, Retries exhausted signature.asc Description: OpenPGP digital signature
FreeBSD 10/9: Lexar 64GB JumpDrive USB 2.0 isn't recognized anymore!
I have a Lexar 64GB USB 2.0 JumpDrive which worked in its "pristine" or "virgine" state very well. I used it yesterday, brand new, to fill it up with data. Some 30GB data got stored, I shut down the system (FreeBSD 10.0-CURRENT/amd64) and this morning, I put the USB drive out of the USB port (computer off) and took it to the office. At the office, neither a FreeBSD10.0-CURRENT box nor a FreeBSD 9.0-STABLE box (both moth recent buildworld) where able to recognize the drive! While the USB drive was recognized as /dev/da1s1 before, this time I see in the console something like this: ugen7.6: at usbus7 umass1: on usbus7 And nothing further anymore. On a Linux box (Suse) the USB drive can be read as well as on a Windows 7 box (I only read the content, I didn't write onto the USB drive on both systems). What is up? Since Windows and Linux can read/recognize the drive and FreeBSD not, I guess FreeBSD does have a problem with that kind of 64GB drive. I do not care of the data on the USB drive, so I'd like to GPART it. But without having a device node created, this is very unlikely to achieve. Any suggestions? Please CC my email, I'm not subscribing this specific list. Regards, Oliver signature.asc Description: OpenPGP digital signature
Re: CURRENT: buildworld fails
On 05/19/12 22:33, Garrett Cooper wrote: > On Sat, May 19, 2012 at 6:55 AM, O. Hartmann > wrote: >> Since approx. a week for now, I can not build FreeBSD 10.0-CURRENT/amd64 >> anymore! This happens to be on ALL(!) FreeBSD 10 boxes around here I >> maintain. > > ... > >> b) build and install /usr/src/lib via "make clean cleandepend depend obj >> all install" doesn't work anymore, it fails with >> ."/usr/src/lib/Makefile", line 179: Malformed conditional (${MK_NAND} != >> "no") >> "/usr/src/lib/Makefile", line 181: if-less endif > > Your mk files in /usr/share/mk are out of synch with your build tree. > If you opt out of using buildworld, then you need to do 'make -C > share/mk install' beforehand. > > Thanks, > -Garrett My problems became more desperate. Since May, 15th, I'm unable to compile a buildworld and I suspect I messed up my OS somehow. I have already completely deleted /usr/src and checked out via SVN again. Deleting /etc/src.conf and /etc/make.conf, performing buildworld with the system's original make.conf (using the legacy GCC 4.2.1) ends up with the below shown error. Try to compile with CLANG as suggested via the Wiki page and the attached /etc/src.conf gives a very short approach in how to trap into a error, also shown below. My problems occured around the May, 15th and hit ALL of my FreeBSD 10-CURRENT/amd64 boxes on which I do most time daily buildworld. Two of them could be fixed, I did this two days ago by cd /usr/src make installincludes make -C {lib|libexec|sbin ...} clean cleandepend depend obj all install On one specific machine it didn't work that way. I found out that several binaries in the system's tree remained dated on 15th May, so like "ld" or other essential pieces. Therefore I suspect a crushed system. Does anyhow do have any idea how to repair the system? I can compile a kernel, but I can not compile ports (or even update them, I receive multiple weird errors of missing header files or "changed" libstdc++.so. The idea was to take a very recent binary installation set and install this selective peice by piece over the existing installation, but I need to preserve /etc and other directories. Any ideas ? Help is appreciated and thanks in advance, Oliver [ BUILD with legacy gcc 4.2.1] ===> bin/ed (all) cc -O2 -pipe -DDES -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -c /usr/src/bin/ed/buf.c cc -O2 -pipe -DDES -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -c /usr/src/bin/ed/cbc.c cc -O2 -pipe -DDES -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -c /usr/src/bin/ed/glbl.c cc -O2 -pipe -DDES -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -c /usr/src/bin/ed/io.c cc -O2 -pipe -DDES -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -c /usr/src/bin/ed/main.c cc -O2 -pipe -DDES -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -c /usr/src/bin/ed/re.c cc -O2 -pipe -DDES -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-p
CURRENT: buildworld fails
Since approx. a week for now, I can not build FreeBSD 10.0-CURRENT/amd64 anymore! This happens to be on ALL(!) FreeBSD 10 boxes around here I maintain. Build is usually performed with CLANG, but also legacy gcc 4.2.1 build do fail. The error is always the same, as documented below. I allow to build with "WITH_BSD_SORT" in /etc/src.conf. CFLAGS and COPTFLAGS are set to -pipe -O3 -fno-strict-aliasing -march=native when compiling with CLANG, otherwise the standard is used as introduced by the vanilla sources. What I tried so far: a) build and install kernel -> works b) build and install /usr/src/lib via "make clean cleandepend depend obj all install" doesn't work anymore, it fails with ."/usr/src/lib/Makefile", line 179: Malformed conditional (${MK_NAND} != "no") "/usr/src/lib/Makefile", line 181: if-less endif c) make installincludes from /usr/src works. But it doesn't relief as I hoped. As the error below may suggest, there seems to be an issue with the libstc++ lib. Building ports also fails due to errors refering to libstdc++.so. I feel helpless at the moment since the problem seems only to be sticky with me around here. Do others around here also allow the build of new C++ stuff with WITH_LIBCPLUSPLUS= YES in /etc/src.conf? Regards, Oliver [...] clang++ -O2 -fno-strict-aliasing -pipe -pipe -O3 -fno-strict-aliasing -march=native -Qunused-arguments -fstack-protector -Wsystem-headers -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-conversion -Wno-switch -Wno-switch-enum -Wno-parentheses -I/usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/lib -I/usr/src/gnu/usr.bin/gperf -o gperf bool-array.o hash-table.o input.o keyword-list.o keyword.o main.o options.o output.o positions.o search.o version.o getline.o hash.o /usr/obj/usr/src/tmp/usr/lib/libstdc++.so:(*IND*+0x0): multiple definition of `std::basic_ifstream >::is_open() const' /usr/obj/usr/src/tmp/usr/lib/libstdc++.so:(*IND*+0x0): multiple definition of `std::basic_string, std::allocator >::_Rep::_M_set_length_and_sharable(unsigned long)' /usr/obj/usr/src/tmp/usr/lib/libstdc++.so:(*IND*+0x0): multiple definition of `std::basic_string, std::allocator >::_M_check_length(unsigned long, unsigned long, char const*) const' /usr/obj/usr/src/tmp/usr/lib/libstdc++.so:(*IND*+0x0): multiple definition of `std::basic_fstream >::is_open() const' /usr/obj/usr/src/tmp/usr/lib/libstdc++.so:(*IND*+0x0): multiple definition of `std::basic_istream >::ignore()' /usr/obj/usr/src/tmp/usr/lib/libstdc++.so:(*IND*+0x0): multiple definition of `std::basic_string, std::allocator >::_M_copy(wchar_t*, wchar_t const*, unsigned long)' /usr/obj/usr/src/tmp/usr/lib/libstdc++.so:(*IND*+0x0): multiple definition of `std::string::_M_assign(char*, unsigned long, char)' /usr/obj/usr/src/tmp/usr/bin/ld: Warning: size of symbol `_ZNSt13basic_istreamIwSt11char_traitsIwEE6ignoreEv@GLIBCXX_3.4' changed from 243 in /usr/obj/usr/src/tmp/usr/lib/libstdc++.so to 211 in /usr/obj/usr/src/tmp/usr/lib/libstdc++.so /usr/obj/usr/src/tmp/usr/lib/libstdc++.so:(*IND*+0x0): multiple definition of `std::basic_fstream >::is_open() const' /usr/obj/usr/src/tmp/usr/lib/libstdc++.so:(*IND*+0x0): multiple definition of `std::basic_string, std::allocator >::_M_move(wchar_t*, wchar_t const*, unsigned long)' /usr/obj/usr/src/tmp/usr/bin/ld: Warning: size of symbol `_ZNSbIwSt11char_traitsIwESaIwEE4_Rep26_M_set_length_and_sharableEm@GLIBCXX_3.4' changed from 19 in /usr/obj/usr/src/tmp/usr/lib/libstdc++.so to 24 in /usr/obj/usr/src/tmp/usr/lib/libstdc++.so /usr/obj/usr/src/tmp/usr/lib/libstdc++.so:(*IND*+0x0): multiple definition of `std::string::_M_move(char*, char const*, unsigned long)' /usr/obj/usr/src/tmp/usr/lib/libstdc++.so:(*IND*+0x0): multiple definition of `std::istream::ignore()' /usr/obj/usr/src/tmp/usr/bin/ld: Warning: size of symbol `_ZNKSs15_M_check_lengthEmmPKc@GLIBCXX_3.4' changed from 39 in /usr/obj/usr/src/tmp/usr/lib/libstdc++.so to 36 in /usr/obj/usr/src/tmp/usr/lib/libstdc++.so /usr/obj/usr/src/tmp/usr/lib/libstdc++.so:(*IND*+0x0): multiple definition of `std::basic_ofstream >::is_open() const' /usr/obj/usr/src/tmp/usr/lib/libstdc++.so:(*IND*+0x0): multiple definition of `std::basic_string, std::allocator >::_M_assign(wchar_t*, unsigned long, wchar_t)' /usr/obj/usr/src/tmp/usr/bin/ld: Warning: size of symbol `_ZNKSbIwSt11char_traitsIwESaIwEE15_M_check_lengthEmmPKc@GLIBCXX_3.4' changed from 39 in /usr/obj/usr/src/tmp/usr/lib/libstdc++.so to 36 in /usr/obj/usr/src/tmp/usr/lib/libstdc++.so /usr/obj/usr/src/tmp/usr/bin/ld: Warning: size of symbol `_ZNSi6ignoreEv@GLIBCXX_3.4' changed from 243 in /usr/obj/usr/src/tmp/usr/lib/libstdc++.so to 211 in /usr/obj/usr/src/tmp/usr/lib/libstdc++.so /usr/obj/usr/src/tmp/usr/lib/libstdc++.so:(*IND*+0x0): multiple definition of `std::basic_ifstream >::is_open() const' /usr/obj/usr/src/tmp/usr/lib/libstdc++.so:(*IND*+0x0): multiple definition of `std::string::_M_copy(char*, c
Re: OpenLDAP 2.4.31 on FreeBSD 10.0-CURRENT/amd64 broken!
On 05/06/12 01:55, Dimitry Andric wrote: > On 2012-05-05 17:54, Hartmann, O. wrote: >> Since Friday, I have on all of our FreeBSD 10.0-CURRENT/amd64 boxes >> massive trouble with net/openldap24-server (SASL enabled, so it is >> openldap-sasl-server). >> >> Last time OpenLDAP worked was Thursday last week, when obviously a >> problematic update to the OS was made > > I managed to reproduce the segfault you are seeing in slapd, which is > caused by a problem in libthr.so, introduced in r234947. > > Please apply the attached diff, rebuild lib/libthr and install it, and > then try your slapd tests again. Let us know. :) > > @David, can you please review this diff? It looks like there was a > mistake merging from Perforce, where you also moved the line: > > sc = SC_LOOKUP(wchan); > > to the top of the _sleepq_add() function, just before the call to > _sleepq_lookup(). If this isn't done, sc may be uninitialized when it > is dereferenced later on in the function. GREAT! Everything works perfectly as expected and in its status quo as before the inconvenience. The problems I faced with xdm and others were due to a configuration mistake by myself in etc/ldap.conf, which I introduced while searching for problems. Dimitry, my personal thank you. Seriously. Regards, Oliver Hartmann signature.asc Description: OpenPGP digital signature
Re: Terminal (TERM=xterm) on FreeBSD doesn not accept DEL or ALT key on/in a Linux YAST2 session
On 03/12/12 15:21, kpn...@pobox.com wrote: > On Mon, Mar 12, 2012 at 02:51:55PM +0100, O. Hartmann wrote: >> Administering Linux Suse boxes makes it opf need to login onto those >> boxes and use the well designed kiddy-cloaking scripting environment, >> called YAST/YAST2. >> >> The problem I face now is that I can not use DEL key to delete >> characters or even use the ALT key to enforce actions like ALT-e or >> ALT-d for enabling/disabling. >> >> I tried to set environment variable "TERM = xterm" to "TERM = cons25" >> since I thought this could be a problem with the terminal. But it >> wans't. Either the outdated X on FBSD causes problems or there is >> another issue. I desperately need some help ... > > Simple questions first just to be sure: > > You set TERM with the command "export TERM=xterm", correct? No extra spaces? Of course, it is either setenv TERM xterm in csh or TERM=xterm in bourne-alike shells. In my FreeBSD driven environment everything is fine and shiny, but when login into a Suse 12.1 box and doing a YAST2, DEL key does not work (produce nothing) and ALT-plus-key doesn't work either. But in several cases, I need to edit lines and confirm those changes with key shortcuts like ALT-e, for instance for "enable" is much appreciated than hopping around with the TAB key. > > And you are using xterm (not rxvt)? No, pure and plain and conservative xterm as it comes with the port and no extravagant terminal thingy. > > What happens when you use the DEL key? Except in YAST/YAST2, it works as expected ... > > I'm not familiar with YAST. Are you having problems at a normal shell > command line, or are you having problems in something run from a shell? I'm also not familiar with YAST (I start hating this crap), but I need it since I have not the scientific support on FreeBSD platforms I need as I have on Linux (we run TESLA driven boxes acting as supercomputers. Try it, "es ist, als würden Engel schieben ..."). Regards, Oliver signature.asc Description: OpenPGP digital signature
Terminal (TERM=xterm) on FreeBSD doesn not accept DEL or ALT key on/in a Linux YAST2 session
Administering Linux Suse boxes makes it opf need to login onto those boxes and use the well designed kiddy-cloaking scripting environment, called YAST/YAST2. The problem I face now is that I can not use DEL key to delete characters or even use the ALT key to enforce actions like ALT-e or ALT-d for enabling/disabling. I tried to set environment variable "TERM = xterm" to "TERM = cons25" since I thought this could be a problem with the terminal. But it wans't. Either the outdated X on FBSD causes problems or there is another issue. I desperately need some help ... Regards and thanks in advance, Oliver signature.asc Description: OpenPGP digital signature
print/cups: CUPS-1.5.0 IPP protocoll issues -> no printing possible on IPP capable network printers
We use a bunch of HP and Xerox printers across our network, all capable of being accessed via network over IPP protocoall (so they claim). Printing worked for me flawless on FreeBSD 8.2-STABLE, 9.0-CURRENT, now 9.0-STABLE on all boxes in question. Since updating cups to revision 1.5.0 (this is the most recent port version and I recently updated/recompiled the port and dependencies for all parts of CUPS either with CLANG and GCC 4.2.1), I get massive problems accessing printers on the network. Most HP printers accept a print job, but after accepting, CUPS reports printer has been stopped, can not obtain printer status. The job remains in the queue. Then I "restart" printer via CUPS, print job gets printed, but immediateley after printing has finished, the same problem occurs again: printer stopped - can not get printer status. Job remains still in the queue. Restarting printer via CUPS will start the game again, with the result of printing endless the same job, first in queue. I have to check whether the printer indeed has printed the job, delete the first queue entry, restart the printer again to get next job started ... and so on. A similar game on the Xerox printer facility. The printer reports "Unablae to get printer status", printing is here impossible! The XEROX printer is now attached to a Linux print server box running CUPS, an older CUPS on something like CentOS, I do not know what crap is running on the hardware. But: the printer works fine with older CUPS! Digging the internet revealed an issue reported in an Ubuntu forum/list, I already filed a PR (ports/164759). The Ubuntu report is about to be found here: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/877958 I was wondering if this "patch", whatever the Ubuntu fellows patched, couldn't be introduced to FreeBSD's CUPS port. Well, sorry about my impatience, but I'm floating like a dead man in the water, since I have to prepare printouts for a conference and printing is some kind of "neurological point" around here. Thanks for your patience ... Regards, Oliver signature.asc Description: OpenPGP digital signature
Re: FreeBSD 10.0-CURRENT/AMD64 (CLANG): lang/gcc46 fails to build
On 12/07/11 07:11, Steve Kargl wrote: > On Wed, Dec 07, 2011 at 05:56:31AM +0100, O. Hartmann wrote: >> config.status: creating ada/Makefile >> config.status: creating auto-host.h >> config.status: executing default commands >> gmake[2]: Leaving directory `/usr/ports/lang/gcc46/work/build' >> gmake[1]: *** [stage1-bubble] Error 2 >> gmake[1]: Leaving directory `/usr/ports/lang/gcc46/work/build' >> gmake: *** [bootstrap-lean] Error 2 >> *** Error code 1 >> >> Stop in /usr/ports/lang/gcc46. >> *** Error code 1 >> >> Stop in /usr/ports/lang/gcc46. >> >> ===>>> make failed for lang/gcc46 >> ===>>> Aborting update >> > > See if setting DISABLE_MAKE_JOBSi helps. > This doesn't work, either. In /etc/src.conf, I use WITH_ICONV=YES and _WITH_BSD_GREP=YES. Switching off WITH_ICONV seems to solve the problem on FreeBSD 10.0-CURRENT/amd64. I do not know whether OS versions below 10.0 do support the WITH_ICONV knob. This maybe is a hint to the problem. Regards, Oliver signature.asc Description: OpenPGP digital signature
FreeBSD 10.0-CURRENT/AMD64 (CLANG): lang/gcc46 fails to build
Hello. On FreeBSD 10.0-CURRENT/amd64 I run into the error shown below when updating the installation of the gcc46 compiler suite. The OS has been compiled via CLANG, binutils 2.22 are installed and has been installed either with the UNAME_r settings and WITH_FBSD10_FIX set in /etc/make.conf. I was wondering whether others would also see this on CURRENT. On all FreeBSD 9.0 boxes gcc46 compiles well. Regards, Oliver Configuring stage 1 in ./gcc clang -O3 -fno-strict-aliasing -pipe -march=native -I/usr/local/include -o fixincl fixincl.o fixtests.o fixfixes.o server.o procopen.o fixlib.o fixopts.o ../libiberty/libiberty.a echo timestamp > full-stamp gmake[3]: Leaving directory `/usr/ports/lang/gcc46/work/build/build-x86_64-portbld-freebsd9.9/fixincludes' gmake[3]: Entering directory `/usr/ports/lang/gcc46/work/build/libcpp' clang -I.././../gcc-4.6-20111202/libcpp -I. -I.././../gcc-4.6-20111202/libcpp/../include -I.././../gcc-4.6-20111202/libcpp/include -g -fkeep-inline-functions -W -Wall -Wwrite-strings -Wmissing-format-attribute -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -Wc++-compat -pedantic -Wno-long-long -I.././../gcc-4.6-20111202/libcpp -I. -I.././../gcc-4.6-20111202/libcpp/../include -I.././../gcc-4.6-20111202/libcpp/include -c -o charset.o -MT charset.o -MMD -MP -MF .deps/charset.Tpo .././../gcc-4.6-20111202/libcpp/charset.c .././../gcc-4.6-20111202/libcpp/charset.c:1371:1: error: conflicting types for 'cpp_interpret_string' cpp_interpret_string (cpp_reader *pfile, const cpp_string *from, size_t count, ^ .././../gcc-4.6-20111202/libcpp/include/cpplib.h:742:13: note: previous declaration is here extern bool cpp_interpret_string (cpp_reader *, ^ .././../gcc-4.6-20111202/libcpp/charset.c:1452:1: error: conflicting types for 'cpp_interpret_string_notranslate' cpp_interpret_string_notranslate (cpp_reader *pfile, const cpp_string *from, ^ .././../gcc-4.6-20111202/libcpp/include/cpplib.h:745:13: note: previous declaration is here extern bool cpp_interpret_string_notranslate (cpp_reader *, ^ 2 errors generated. gmake[3]: *** [charset.o] Error 1 gmake[3]: Leaving directory `/usr/ports/lang/gcc46/work/build/libcpp' gmake[2]: *** [all-stage1-libcpp] Error 2 gmake[2]: *** Waiting for unfinished jobs configure: creating cache ./config.cache checking build system type... x86_64-portbld-freebsd9.9 checking host system type... x86_64-portbld-freebsd9.9 checking target system type... x86_64-portbld-freebsd9.9 checking LIBRARY_PATH variable... ok checking GCC_EXEC_PREFIX variable... ok [...] checking linker *_sol2 emulation support... no checking linker --sysroot support... yes checking __stack_chk_fail in target C library... checking for __stack_chk_fail... yes yes checking dl_iterate_phdr in target C library... unknown Using ggc-page for garbage collection. checking whether to enable maintainer-specific portions of Makefiles... no Links are now set up to build a native compiler for x86_64-portbld-freebsd9.9. checking for exported symbols... yes checking for -rdynamic... yes checking for library containing dlopen... none required checking for -fPIC -shared... yes configure: updating cache ./config.cache configure: creating ./config.status config.status: creating as config.status: creating collect-ld config.status: creating nm config.status: creating Makefile config.status: creating ada/gcc-interface/Makefile config.status: creating ada/Makefile config.status: creating auto-host.h config.status: executing default commands gmake[2]: Leaving directory `/usr/ports/lang/gcc46/work/build' gmake[1]: *** [stage1-bubble] Error 2 gmake[1]: Leaving directory `/usr/ports/lang/gcc46/work/build' gmake: *** [bootstrap-lean] Error 2 *** Error code 1 Stop in /usr/ports/lang/gcc46. *** Error code 1 Stop in /usr/ports/lang/gcc46. ===>>> make failed for lang/gcc46 ===>>> Aborting update ===>>> Update for lang/gcc46 failed ===>>> Aborting update ===>>> You can restart from the point of failure with this command line: portmaster lang/gcc46 signature.asc Description: OpenPGP digital signature
multimedia/vlc: no graphical interface on FreeBSD 9 and 10
Since a while, vlc on my FreeBSD 10 and FreeBSD 9 boxes do not show a graphical interface anymore. Compiling multimedia/vlc works, either with the legacy gcc or clang. But either way I compile vlc, the result is always the same: no GUI. Instead, I receive the below show message: VLC media player 1.1.12 The Luggage (revision exported) Blocked: call to unsetenv("DBUS_ACTIVATION_ADDRESS") Blocked: call to unsetenv("DBUS_ACTIVATION_BUS_TYPE") [0x802080a70] main interface error: no suitable interface module [0x8020691b0] main libvlc error: interface "globalhotkeys,none" initialization failed [0x8020691b0] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface. [0x802080a70] main interface error: option qt-volume-complete does not exist [0x802080a70] skins2 interface error: no suitable dialogs provider found (hint: compile the qt4 plugin, and make sure it is loaded properly) [0x802080a70] skins2 interface error: cannot instanciate qt4 dialogs provider I tried several times to recompile everything vlc depends on, but with not success. I also tried to delete every configuration file vlc created in the past and my now suffer from legzy options, but that hadn't any effect - as far as I could catch each config file. Is anybody out here having had the same or similar problem and solved it? Regards, Oliver signature.asc Description: OpenPGP digital signature
port astro/stellarium: /usr/ports/astro/stellarium/work/stellarium-0.11.1/plugins/AngleMeasure/src/AngleMeasure.hpp, : File name too long,*** Error code 1
Hello, since a couple of days for now I have on FreeBSD 10.0-CURRENT/amd64, clang compiled, the following error updating or reinstalling or installing the port astro/stellarium: ===> Vulnerability check disabled, database not found ===> License GPLv2 accepted by the user ===> Found saved configuration for stellarium-0.11.1 ===> Extracting for stellarium-0.11.1 => SHA256 Checksum OK for stellarium-0.11.1.tar.gz. ===> Patching for stellarium-0.11.1 sed: /usr/ports/astro/stellarium/work/stellarium-0.11.1/src/core/external/fixx11h.h /usr/ports/astro/stellarium/work/stellarium-0.11.1/src/CMakeLists.txt /usr/ports/astro/stellarium/work/stellarium-0.11.1/plugins/TelescopeControl/src/TelescopeControl.hpp /usr/ports/astro/stellarium/work/stellarium-0.11.1/plugins/Oculars/src/Oculars.hpp /usr/ports/astro/stellarium/work/stellarium-0.11.1/plugins/CompassMarks/src/CompassMarks.hpp /usr/ports/astro/stellarium/work/stellarium-0.11.1/plugins/TextUserInterface/src/TextUserInterface.hpp /usr/ports/astro/stellarium/work/stellarium-0.11.1/plugins/Supernovae/src/Supernovae.hpp /usr/ports/astro/stellarium/work/stellarium-0.11.1/plugins/SolarSystemEditor/src/SolarSystemEditor.hpp /usr/ports/astro/stellarium/work/stellarium-0.11.1/plugins/Satellites/src/Satellites.hpp /usr/ports/astro/stellarium/work/stellarium-0.11.1/plugins/HelloStelModule/src/HelloStelModule.hpp /usr/ports/astro/stellarium/work/stellarium-0.11.1/plugins/TimeZoneConfiguration/src/TimeZoneConfiguration.hpp /usr/ports/astro/stellarium/work/stellarium-0.11.1/plugins/AngleMeasure/src/AngleMeasure.hpp : File name too long *** Error code 1 Stop in /usr/ports/astro/stellarium. *** Error code 1 I have no idea what the error cuases. I tried to delete everything and reinstall, but the error seems to be very sticky. I checked the /usr/ports partition (UFS2, UFS-Journaling on) several time for errors, but it seems to be clean. Any ideas what's going on? Regards, Oliver signature.asc Description: OpenPGP digital signature
Scientific toolchaing for planetary geo-imaginery: USGS ISIS3
Does someone do science with FreeBSD and coincidently reading this mailing list and (another) coincidently do planetary science and wish to process satellite images via the opensource software toolchain ISIS3 from USGS? Regards Oliver signature.asc Description: OpenPGP digital signature
Re: /sys/amd64/conf/DEFAULTS
Am 11/08/11 14:12, schrieb Niclas Zeising: > On 11/08/11 12:36, O. Hartmann wrote: >> Sorry for the boring question, but is the default configuration file >> /sys/amd64/conf/DEFAULTS anywhere include in a regular configuration >> file for the kernel while building the kernel? >> >> I looked for include statements in GENERIC, but didn't find one. I use >> custom kernel config files and adapt most changes from the NOTES files >> in the sources tree. >> >> With the today's update of README in /sys/amd64/conf I realised some >> important changes, so this triggered my question. >> >> I simply made an additional "include" in the custom config file, but if >> this isn't necessary, I'll delete it again. And I'm interested in how >> the kernel is built from. It is a very convenient way to type simply >> "make kerne" in /usr/src/, but it vanishes to much of the complexity and >> understanding how the system builds and could cause problems. >> >> Thanks for your patience and tahnks in advance, >> >> Regards, >> Oliver > > From my understanding of things, the DEFAULTS kernel configuration file > is automatically included into the build by config(8). There is no need > to include it into the generic using the "include" statement. It was > first added 6 years ago, on October 27 2005. > Regards! Thank you very much. ___ 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"
/sys/amd64/conf/DEFAULTS
Sorry for the boring question, but is the default configuration file /sys/amd64/conf/DEFAULTS anywhere include in a regular configuration file for the kernel while building the kernel? I looked for include statements in GENERIC, but didn't find one. I use custom kernel config files and adapt most changes from the NOTES files in the sources tree. With the today's update of README in /sys/amd64/conf I realised some important changes, so this triggered my question. I simply made an additional "include" in the custom config file, but if this isn't necessary, I'll delete it again. And I'm interested in how the kernel is built from. It is a very convenient way to type simply "make kerne" in /usr/src/, but it vanishes to much of the complexity and understanding how the system builds and could cause problems. Thanks for your patience and tahnks in advance, Regards, Oliver signature.asc Description: OpenPGP digital signature
multimedia/vlc: suddenly no graphical interface
On all of my used FreeBSD 9.0-RCX and FreeBSD 10.0-CURRENT boxes (all amd64 and CLANG compiled), I do not have a graphical user interface in VLC anymore. Instead, calling vlc most recent 1.1.11), I get this error: VLC media player 1.1.11 The Luggage (revision exported) Blocked: call to unsetenv("DBUS_ACTIVATION_ADDRESS") Blocked: call to unsetenv("DBUS_ACTIVATION_BUS_TYPE") [0x8020521b0] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface. [0x80205ad70] main interface error: option qt-volume-complete does not exist [0x80205ad70] skins2 interface error: no suitable dialogs provider found (hint: compile the qt4 plugin, and make sure it is loaded properly) [0x80205ad70] skins2 interface error: cannot instanciate qt4 dialogs provider [0x8020521b0] main libvlc error: interface "default" initialization failed Recompiling the multimedia/vlc port did not help, also unsuccessful was the recompilation of any qt4-port installed on the system. I also tried to find the local configuration files in my home directory and delete them, without any success. Is there something wrong with the DBUS subsystem named in the error? Help appreciated, thanks. Regards, Oliver ___ 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 10.0-CURRENT/amd64: Weirdness with LOCALE settings: ghostswitching in csh?
Hello. I realised something weird in FreeBSD 10.-CURRENT/amd64 (CLANG compiled), build as from today (buildworld). Working the whole day coding some pyhton scripts and committing the code to my subversion server (most recent subversion from the ports collection, the server is a FreeBSD 9.0-RC1/amd64 box, also system compiled with CLANG, most recent as compiled world of today), suddenly, oy of the blue, trying again to commit I get this error: svn: warning: cannot set LC_CTYPE locale svn: warning: environment variable LC_CTYPE is de_DE.ISO-8859-1 svn: warning: please check that your locale name is correct Checking csh shell setting with 'locale": LANG= LC_CTYPE="C" LC_COLLATE="C" LC_TIME="C" LC_NUMERIC="C" LC_MONETARY="C" LC_MESSAGES="C" LC_ALL= Checking my settings from /etc/csh.cshrc and ./.cshrc or .login reveals localised settings for some of the locales as I need those: (set in $HOME/.cshrc) setenv LC_CTYPE"de_DE.ISO-8859-1" setenv LC_TIME "de_DE.ISO-8859-1" setenv LC_MONETARY "de_DE.ISO-8859-1" What is going on? I realised this behaviour now several times, first time I thought I did something and I couldn't remember, but this time, only two terminal windows were opened and the whole day committing data to the repository wasn't an issue. Is there an explanation for this? Regards, Oliver signature.asc Description: OpenPGP digital signature
The future of FreeBSD at Yahoo!
The press in Germania is full of some statements, that Google is about to overtake Yahoo!. As far as I know, Yahoo! is one of the more popular and bigger, if not the biggest and last stronghold of a FreeBSD driven infrastructure. Despite the fact that even Google funded lots of coding for FreeBSD, I had the impression that Yahoo! might be one of the biggest contributor. And not to mention the psychological effect of hearing that such a company is utilizing a project like FreeBSD for potential newcomers in the business. So, what is about the future of FreeBSD? Does FreeBSD have a site where all the goods that has been first invented by the FreeBSD/BSD folks or all the things that are thought about to come in future are shown/listed? Crawling the mailing lists is a really nasty work. Thanks for having patience, Oliver ___ 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"
Dell Poweredge 1950 III (PE_SC3): replacement SAS controller to acceess drives >= 3TB
Hello out there. We run a Dell PowerEdge 950 III (PE_SC3) Server with FreeBSD 8.2-STABLE. This Server is equipted with a SAS controller, residing, as far as I could observe, on a PCIe slot. Its kernel message is: mpt0: port 0xec00-0xecff mem 0xfc4fc000-0xfc4f,0xfc4e-0xfc4e irq 16 at device 0.0 on pci1 mpt0: [ITHREAD] mpt0: MPI Version=1.5.14.0 mpt0: Capabilities: ( RAID-0 RAID-1E RAID-1 ) mpt0: 0 Active Volumes (2 Max) mpt0: 0 Hidden Drive Members (14 Max) The pciconf -lcv output is as: mpt0@pci0:1:0:0:class=0x01 card=0x1f101028 chip=0x00581000 rev=0x08 hdr=0x00 vendor = 'LSI Logic (Was: Symbios Logic, NCR)' device = 'SAS 3000 series, 8-port with 1068E -StorPort' class = mass storage subclass = SCSI cap 01[50] = powerspec 2 supports D0 D1 D2 D3 current D0 cap 10[68] = PCI-Express 1 endpoint max data 256(4096) link x4(x8) cap 05[98] = MSI supports 1 message, 64 bit cap 11[b0] = MSI-X supports 1 message in map 0x14 enabled ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected This controller obviously isn't capable of handling 3TB harddrives and I need it to be replaced - but I do not know what type and brand of controller is suitbale for the Dell PowerEdge III. We already contacted our support, but they rejected support, since the BIOS of this server isn't capable of booting off 3 TB harddrives due to the 32bit limitations. Well, I need the controller to attach 3 and 4 TB drives, we still boot off from legacy BIOS capable < 2,2 TB drives, so I see no issue to replace the SAS controller. I'm a bit afraid of buying something "out of the blue" since the dimensions of this little controller board seems small. I hope someone already made a decission to buy such a replacement for their similar or exact the same system and can help me out. We do not need RAID, nor SAS 2.0 capabilities, just JBOD. Thanks a lot in advance, Oliver P.S. Please also reply to my email, I'm not subsribing "questions" in case you reply. 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"
Thunderbird 6.0.2/7.0: Crashing when using with OpenLDAP backend
I run in a problem on FreeBSD 9.0-BETA3/10.0-CURRENT using OpenLDAP (Cyrus SASL2 aktivated) and OpenLDAP backend (most recent client and server). Thunderbird 6.0.2 and 7.0 coredumps with signal 11. I hadn't any chance to check whether this also happens on 8.2-STABLE, but I'll check this as soon as possible, since I run the same OpenLDAP backend and configuration (also the Cyrus SASL2 libs, most recent from ports). The boxes in question do have FreeBSD 9.0-BETA3/10.0-CUR compiled with CLANG and Thunderbird is also compiled with CLANG. Does anyone else experience these issues? Regards, Oliver ___ 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"
Point Cloud Library (PCL)
Hello. Does anyone knows whether there is a port of the Point Cloud Library (PCL), which seems to be a subproject of OpenCV? Any hints or tips are welcome. Regards, Oliver ___ 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: Heavy I/O blocks FreeBSD box for several seconds
On 07/06/11 12:37, arrowdodger wrote: 2011/7/6 O. Hartmann When performing an update on the ports tree via "portsnap fetch update" or when checking out (or) large Subversion repositories or when copying large data files (~ 50 to 250 GB in size, results from numerical modelings) or when compiling world, FreeBD 9.0 and FreeBSD 8.2-STABLE tend to "freeze" for several seconds or drop overall performance dramatically for seconds. On boxes with only console- or terminal access (no GUI) a running 'vi' gets stuck for seconds while one of the processes producing heavy I/O is running, or the output of a 'cat' of a large file stops for several seconds. Using X11, this phenomenon gets even worse and the 'freezing' tends to persist sometimes for more than 10 or 15 seconds. I've also had (and still having) this problem on FreeBSD 7.2-RELEASE and 8-STABLE with both UFS and ZFS. Though, i've been running FreeBSD not on powerful servers, but on laptops (2-core CPU's, 2 GB of RAM). But still, KDE4 on Linux performs much better during high disk IO. I read about issues with the old codebase of X11 in FreeBSD's ports used, which could be the cause of some performance problems, but I wouldn't expect those I/O-triggered blockings on boxes without any GUI. I saw Linux very often performing tremendously better when used as a workstation or desktop, but this is often gained on the costs of other subsystems. I followed a very hard-to-understand discussion about grouping threads related to ttys which seems to get higher priorized in Linux to make the GUI more fluent, but this is definitely on cost of other subsystems, which in consequence gets less priorized. But even without GUI, Linux seems to perform I/O much better on multicore-/multiprocessor boxes than FreeBSD *.X and 9.X). Today I looked at some benchmarks performed by Phoronix/openbenchmark.org (http://www.phoronix.com/scan.php?page=article&item=freebsd8_ubuntu910&num=9) and it seems that threaded I/O is an issue in FreeBSD (compared to Linux). I have no glue how to "tune" those bottlenecks away in FBSD. I use SCHED_ULE on all machines, since it is supposed to be performing better on multicore boxes, but there are lots of suggestions switching back to the old SCHED_4BSD scheduler. Oliver ___ 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"
Heavy I/O blocks FreeBSD box for several seconds
When performing an update on the ports tree via "portsnap fetch update" or when checking out (or) large Subversion repositories or when copying large data files (~ 50 to 250 GB in size, results from numerical modelings) or when compiling world, FreeBD 9.0 and FreeBSD 8.2-STABLE tend to "freeze" for several seconds or drop overall performance dramatically for seconds. On boxes with only console- or terminal access (no GUI) a running 'vi' gets stuck for seconds while one of the processes producing heavy I/O is running, or the output of a 'cat' of a large file stops for several seconds. Using X11, this phenomenon gets even worse and the 'freezing' tends to persist sometimes for more than 10 or 15 seconds. The boxes in question are all 64Bit, do have 2 to 8 CPUs/cores (no SMT) and not less than 8 GB of RAM (the 8 core box is a dual socket Dell server with two 4-core C2D-type XEON CPUs and 16 GB of RAM). All these boxes uses ZFS filesystems for data along with UFS2 for the OS. On a notebook with a relative modern Core-5 dual core CPU and 4 GB RAM (running FreeBSD 9.0-CURRENT/amd64), not ZFS, all UFS, with a 500GB harddrive at 5400 upm (Dell Latitude E6510), this phenomenon is even worse. Heavy disk I/O blocks the GUI for nearly half a minute, even when no X11 is activated, the console gets stuck for a while. First I thought this could be a problem with the "slow" harddrive, but I tried also a Linux Ubuntu 11.04 on the box and forcing heavy I/O by copying the large files in question from one location on the disk to another is performed even faster and without any freezing of a console or GUI (used EXT4 filesystem). I'm curious about this behavior. I use FreeBSD as my favourite HPC platform as far as this is possible with FreeBSD, but I realized this bottleneck when it comes to heavy I/O and I'd like to know whether this is only a "superficial" phenomenon (like caused by the outdated X11 version FreeBSD use or a low priorized tty handling, means only the observer "realize" a performance drop). I've got not the time to investigate this deeper (I'd like to perform some benchmarks on the notebook if it is available again, but my knowledge on Linux/Ubuntu is very limited and the how-to setting up FreeBSD and Linux to match each other on the same hardware could be tricky). My kernel setups on FreeBSD are mostly the GENERIC kernel with extracted drivers I do not use (like some USB devices, SAS/SCSI adaptors etc. we do not use, et cetera), nothing special. Either way I follow the tips presented in "tuning(7)" or not, the phenomenon is present. Thanks, Oliver ___ 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: devel/anjuta: creating project does not offer project's dialog.
On 07/01/11 09:35, Konstantin Tokarev wrote: 01.07.2011, 11:06, "O. Hartmann" And, for those actively developing, is there a good alternative to Anjuta (no KDevelop, since I do not like KDE and do not have KDE). Thanks, Oliver Depending on what you need you can try: Geany Vim Eclipse Qt Creator Actually, KDevelop does not require you to run KDE, it just needs KDE libraries. Thanks for your fast response. My target is mostly C, not C++, so I had my difficulties with QTCreator. I'll give KDevelop a try again ... Regards, Oliver ___ 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"
devel/subversion: svn: Couldn't perform atomic initialization svn: database schema has changed
Since yesterday I receive on any try on a commit this error message from my subversion server: svn: Couldn't perform atomic initialization svn: database schema has changed svn: Your commit message was left in a temporary file: Searching for this error (which appeared after portsupdate via portmaster yesterday) reveal several postings saying this is due to a bug in SQLite 3.7.7/3.7.7-1, which has been fixed already in 3.7.7-2. As far as I realize, SQLite was part of an update these days, so I'm wondering if anybody else has been sumbled into the problem. Or is this problem caused by something else? I'm a bit like a dead man in the water since no commit to the server is possible anymore. At this very moment, I recompile sqlite and everything that depends on it, hoping it could only be triggered by some errornes portmaster thingis. Thanks in advance, Oliver ___ 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"
devel/anjuta: creating project does not offer project's dialog.
Using Anjuta as my potentially IDE, I realize a weird behaviour since my last try years ago. Anjuta was supposed to show a dialog about when creating a new project. Documentation explicitely mention this. But in my case (a newly installed anjuta), selecting a C-project, GTK+, then ends up in the final requester "Summary". Confirmation does not even show any created files or something else. This happens with all potentially to be created projects. Importing a hand-installed GNU autotools backed up project works fine, superficially spoken. The boxes running Anjuta are all AMD64 and running most recent FreeBSD 9.0-CURRENT/amd64. Version of ports anjuta is reported to be 2.32, but webpage of the anjuta project reports 2.28. Am I missing something? And, for those actively developing, is there a good alternative to Anjuta (no KDevelop, since I do not like KDE and do not have KDE). Thanks, Oliver ___ 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: Dell PowerEdge 1950: MPT0 doesn't recogniz hard drive > 2TB
On 06/29/11 15:57, Joshua Boyd wrote: 2011/6/29 O. Hartmann mailto:ohart...@zedat.fu-berlin.de>> Questions: a) Is this an issue of FreeBSD 8.2-STABLE or is it a firmware/BIOS issue which can be solved? Hi Oliver, Neither, unfortunately. The 1068E based cards do not support drives over 2TB. See here: http://kb.lsi.com/KnowledgebaseArticle16399.aspx -- Joshua Boyd E-mail: boy...@jbip.net <mailto:boy...@jbip.net> http://www.jbip.net Hello Joshua. Thanks for the fast response. Yes, you're right. I revealed by several postings in the net that the controller in question is not capable of handling disks > 2TB. It's a pitty. Oliver ___ 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"
Dell PowerEdge 1950 with LSI SAS1068E/aka DeLL SAS-6 HBA: howto update firmware with FreeBSD?
We run a Dell PowerEdge 1950 Server which is equipted with a LSI Logic LSISAS1068E SAS HBA, branded as a Dell SAS-6 HBA (MPT). The firmware is dated to 2007 and is not capable of handling hard disks larger than 2 TB. We got now a 3 TB SATA harddrive (WD WD30EZRX) which doesn't get recognized properly and is traeted as a 2TB disk. I found at Dell's website a proper firmware for this type of SAS controller, but I wasn't able to flash a new firmware (firmware found at http://support.dell.com/support/downloads/format.aspx?c=us&cs=19&l=en&s=dhs&deviceid=13856&libid=46&releaseid=R197383&vercnt=3&formatcnt=0&SystemID=PWE_1950&servicetag=&os=WNET&osl=en&catid=-1&dateid=-1&typeid=-1&formatid=-1&impid=-1&checkFormat=true). This fails. The windows alternative is not applicable, how should it ... A FreeDOS solution - like LSI Logic offers - is obviously not in sight at Dell, the offer a RedHat only solution. I tried with a FedoraLive CD (Fedora15, 64Bit), but the process fails either with a non-found builVer.sh-error or, when using a emergency-Linux CD like Knoppix 6.4.4 (famous in Germany), it's missing some utilities (rpm, stty or whatsoever). So, I'm floating like a dead man in the water, having a full old 2 TB harddrive, an exchange 3TB harddrive which is recognized as 2 TB harddrive and no chance to update the controller's firmware. Is anybody out here with a solution under FreeBSD? The box is running FreeBSD 8.2-STABLE with a most recent buildworld. Thanks in advance, Oliver P.S. Please CC me, I'm not subscribing list "questions". ___ 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"
Dell PowerEdge 1950: MPT0 doesn't recogniz hard drive > 2TB
On a Dell PowerEdge 1950, BIOS from 2007, a freshly installed WD 3 TB SATA 6GB harddrive doesn't get recognized as 3 TB disk, it is reported as 2TB disk only. The box is running FreeBSD 8.2-STABLE (see below the dmesg excerpt). The drive is configured as ZFS pool on top of a GPT partition. I tried the 3 TB harddrive on a FreeBSD 9.0-CURRENT box with Intel ICH10R SATA chipset and it worked fine, was reported as 2.7TB drive as expected. I found some postings concerning mptutil not dealing with HD > 2TB, but this issue seems not to be a tool-issue. Questions: a) Is this an issue of FreeBSD 8.2-STABLE or is it a firmware/BIOS issue which can be solved? b) regarding to a), how can I update the BIOS/MPT firmware of the Dell PowerEdge 1950? Is there an option to do this via USB? As I said, the firmware is quite old, it's from 2007. Thanks in advance, Oliver == Copyright (c) 1992-2011 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.2-STABLE #266 r223622: Tue Jun 28 09:38:38 CEST 2011 r...@thusnelda.geoinf.fu-berlin.de:/usr/obj/usr/src/sys/THUSNELDA amd64 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU E5420 @ 2.50GHz (2493.76-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x10676 Family = 6 Model = 17 Stepping = 6 Features=0xbfebfbff Features2=0xce3bd AMD Features=0x20100800 AMD Features2=0x1 TSC: P-state invariant real memory = 17179869184 (16384 MB) avail memory = 16522498048 (15757 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs FreeBSD/SMP: 2 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 ioapic0: Changing APIC ID to 8 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 cryptosoft0: on motherboard aesni0: No AESNI support. acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) ipmi0: KCS mode found at io 0xca8 on acpi ipmi0: KCS error: ff Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 [...] mpt0: port 0xec00-0xecff mem 0xfc4fc000-0xfc4f,0xfc4e-0xfc4e irq 16 at device 0.0 on pci1 mpt0: [ITHREAD] mpt0: MPI Version=1.5.14.0 mpt0: Capabilities: ( RAID-0 RAID-1E RAID-1 ) mpt0: 0 Active Volumes (2 Max) mpt0: 0 Hidden Drive Members (14 Max) [...] ipmi0: IPMI device rev. 0, firmware rev. 2.10, version 2.0 ipmi0: Number of channels 4 ipmi0: Attached watchdog da0 at mpt0 bus 0 scbus0 target 0 lun 0 da0: Fixed Direct Access SCSI-5 device da0: 300.000MB/s transfers da0: Command Queueing enabled da0: 715404MB (1465149168 512 byte sectors: 255H 63S/T 91201C) da1 at mpt0 bus 0 scbus0 target 1 lun 0 da1: Fixed Direct Access SCSI-5 device da1: 300.000MB/s transfers da1: Command Queueing enabled da1: 2097151MB (4294967295 512 byte sectors: 255H 63S/T 267349C) ses0 at mpt0 bus 0 scbus0 target 8 lun 0 ses0: Fixed Enclosure Services SCSI-5 device ses0: 300.000MB/s transfers ses0: SCSI-3 SES Device cd0 at ata0 bus 0 scbus2 target 0 lun 0SMP: AP CPU #3 Launched! cd0: Removable CD-ROM SCSI-0 device cd0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #7 Launched! SMP: AP CPU #4 Launched! SMP: AP CPU #6 Launched! SMP: AP CPU #5 Launched! ___ 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: kernel: install: mps.ko.symbols: No such file or directory
On 05/23/11 23:55, Garrett Cooper wrote: On Mon, May 23, 2011 at 11:44 AM, O. Hartmann wrote: On 05/23/11 18:10, Garrett Cooper wrote: On May 23, 2011, at 5:55 AM, Dimitry Andric wrote: Shouldn't DEBUG_FLAGS be the proper usage in this particular case? Mmmhhh, I changed .if defined(DEBUG)&& !defined(INSTALL_NODEBUG)&& \ [...] to .if defined(DEBUG_FLAGS)&& !defined(INSTALL_NODEBUG)&& \ [...] and everything runs smooth ... Please update to r29 and see if things are fixed. Thanks! -Garrett Done! And working! Thanks, Oliver ___ 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: kernel: install: mps.ko.symbols: No such file or directory
On 05/23/11 18:10, Garrett Cooper wrote: On May 23, 2011, at 5:55 AM, Dimitry Andric wrote: Shouldn't DEBUG_FLAGS be the proper usage in this particular case? -Garrett ___ freebsd-curr...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" Mmmhhh, I changed .if defined(DEBUG) && !defined(INSTALL_NODEBUG) && \ [...] to .if defined(DEBUG_FLAGS) && !defined(INSTALL_NODEBUG) && \ [...] and everything runs smooth ... Oliver ___ 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: kernel: install: mps.ko.symbols: No such file or directory
On 05/23/11 14:52, Ivan Klymenko wrote: В Mon, 23 May 2011 10:03:42 +0200 "O. Hartmann" пишет: On 05/23/11 00:37, Garrett Cooper wrote: On May 22, 2011, at 2:42 PM, O. Hartmann wrote: Building kernel and modules with CLANG (did not try with gcc) results in corrupted system with following error message. Operating system is most recent svn update of FreeBSD 9.0-CURRENT/amd64: URL: svn://svn.freebsd.org/base/head Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 222199 Node Kind: directory Schedule: normal Last Changed Author: rmacklem Last Changed Rev: 222199 Last Changed Date: 2011-05-22 23:04:32 +0200 (So, 22 Mai 2011) After doing some review of the checkins made recently and per our offline discussion, it might be r222188 that's causing issues. How did you issue the build (did you run buildworld buildkernel, or just buildkernel, KERNFAST, etc)? Thanks, -Garrett I've blown away /usr/obj, did a svn update in /usr/src this morning (but there were no updates) and issued make buildworld&& make buildkernel Both went well. But make installkernel still fails installing mps.ko.symbols (which is not found). Oliver ___ freebsd-curr...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" I change the line: .if defined(DEBUG)&& !defined(INSTALL_NODEBUG)&& \ on .if (defined(DEBUG) || defined(DEBUG_FLAGS))&& !defined(INSTALL_NODEBUG)&& \ in the file /sys/conf/kmod.mk A diff shows this: Index: /usr/src/sys/conf/kmod.mk === --- /usr/src/sys/conf/kmod.mk (revision 222180) +++ /usr/src/sys/conf/kmod.mk (working copy) @@ -286,7 +286,8 @@ _kmodinstall: ${INSTALL} -o ${KMODOWN} -g ${KMODGRP} -m ${KMODMODE} \ ${_INSTALLFLAGS} ${PROG} ${DESTDIR}${KMODDIR} -.if defined(DEBUG_FLAGS) && !defined(INSTALL_NODEBUG) +.if defined(DEBUG) && !defined(INSTALL_NODEBUG) && \ +(defined(MK_KERNEL_SYMBOLS) && ${MK_KERNEL_SYMBOLS} == "yes") ${INSTALL} -o ${KMODOWN} -g ${KMODGRP} -m ${KMODMODE} \ ${_INSTALLFLAGS} ${PROG}.symbols ${DESTDIR}${KMODDIR} .endif I reverted manually the changed lines to the previous ones and everthing went smooth. Oliver ___ 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: kernel: install: mps.ko.symbols: No such file or directory
On 05/23/11 10:36, O. Hartmann wrote: On 05/23/11 00:37, Garrett Cooper wrote: On May 22, 2011, at 2:42 PM, O. Hartmann wrote: Building kernel and modules with CLANG (did not try with gcc) results in corrupted system with following error message. Operating system is most recent svn update of FreeBSD 9.0-CURRENT/amd64: URL: svn://svn.freebsd.org/base/head Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 222199 Node Kind: directory Schedule: normal Last Changed Author: rmacklem Last Changed Rev: 222199 Last Changed Date: 2011-05-22 23:04:32 +0200 (So, 22 Mai 2011) After doing some review of the checkins made recently and per our offline discussion, it might be r222188 that's causing issues. How did you issue the build (did you run buildworld buildkernel, or just buildkernel, KERNFAST, etc)? Thanks, -Garrett Maybe a hint, I do not know: root@ase: [src] svn diff -r 222185 sys/conf/kmod.mk Index: sys/conf/kmod.mk === --- sys/conf/kmod.mk (revision 222185) +++ sys/conf/kmod.mk (working copy) @@ -286,7 +286,8 @@ _kmodinstall: ${INSTALL} -o ${KMODOWN} -g ${KMODGRP} -m ${KMODMODE} \ ${_INSTALLFLAGS} ${PROG} ${DESTDIR}${KMODDIR} -.if defined(DEBUG_FLAGS) && !defined(INSTALL_NODEBUG) && ${MK_KERNEL_SYMBOLS} == "yes" +.if defined(DEBUG) && !defined(INSTALL_NODEBUG) && \ + (defined(MK_KERNEL_SYMBOLS) && ${MK_KERNEL_SYMBOLS} == "yes") ${INSTALL} -o ${KMODOWN} -g ${KMODGRP} -m ${KMODMODE} \ ${_INSTALLFLAGS} ${PROG}.symbols ${DESTDIR}${KMODDIR} .endif I'll try on another box with the same OS version I have access to in my lab and report ... Oliver All boxes running the most recent FreeBSD 9.0-CURRENT/amd64, compiled with CLANG, suffer from this error. I'll try with gcc compiled system later ... Oliver ___ 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: kernel: install: mps.ko.symbols: No such file or directory
On 05/23/11 00:37, Garrett Cooper wrote: On May 22, 2011, at 2:42 PM, O. Hartmann wrote: Building kernel and modules with CLANG (did not try with gcc) results in corrupted system with following error message. Operating system is most recent svn update of FreeBSD 9.0-CURRENT/amd64: URL: svn://svn.freebsd.org/base/head Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 222199 Node Kind: directory Schedule: normal Last Changed Author: rmacklem Last Changed Rev: 222199 Last Changed Date: 2011-05-22 23:04:32 +0200 (So, 22 Mai 2011) After doing some review of the checkins made recently and per our offline discussion, it might be r222188 that's causing issues. How did you issue the build (did you run buildworld buildkernel, or just buildkernel, KERNFAST, etc)? Thanks, -Garrett Maybe a hint, I do not know: root@ase: [src] svn diff -r 222185 sys/conf/kmod.mk Index: sys/conf/kmod.mk === --- sys/conf/kmod.mk(revision 222185) +++ sys/conf/kmod.mk(working copy) @@ -286,7 +286,8 @@ _kmodinstall: ${INSTALL} -o ${KMODOWN} -g ${KMODGRP} -m ${KMODMODE} \ ${_INSTALLFLAGS} ${PROG} ${DESTDIR}${KMODDIR} -.if defined(DEBUG_FLAGS) && !defined(INSTALL_NODEBUG) && ${MK_KERNEL_SYMBOLS} == "yes" +.if defined(DEBUG) && !defined(INSTALL_NODEBUG) && \ +(defined(MK_KERNEL_SYMBOLS) && ${MK_KERNEL_SYMBOLS} == "yes") ${INSTALL} -o ${KMODOWN} -g ${KMODGRP} -m ${KMODMODE} \ ${_INSTALLFLAGS} ${PROG}.symbols ${DESTDIR}${KMODDIR} .endif I'll try on another box with the same OS version I have access to in my lab and report ... Oliver ___ 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: kernel: install: mps.ko.symbols: No such file or directory
On 05/23/11 00:37, Garrett Cooper wrote: On May 22, 2011, at 2:42 PM, O. Hartmann wrote: Building kernel and modules with CLANG (did not try with gcc) results in corrupted system with following error message. Operating system is most recent svn update of FreeBSD 9.0-CURRENT/amd64: URL: svn://svn.freebsd.org/base/head Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 222199 Node Kind: directory Schedule: normal Last Changed Author: rmacklem Last Changed Rev: 222199 Last Changed Date: 2011-05-22 23:04:32 +0200 (So, 22 Mai 2011) After doing some review of the checkins made recently and per our offline discussion, it might be r222188 that's causing issues. How did you issue the build (did you run buildworld buildkernel, or just buildkernel, KERNFAST, etc)? Thanks, -Garrett I've blown away /usr/obj, did a svn update in /usr/src this morning (but there were no updates) and issued make buildworld && make buildkernel Both went well. But make installkernel still fails installing mps.ko.symbols (which is not found). Oliver ___ 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: kernel: install: mps.ko.symbols: No such file or directory
On 05/23/11 00:37, Garrett Cooper wrote: On May 22, 2011, at 2:42 PM, O. Hartmann wrote: Building kernel and modules with CLANG (did not try with gcc) results in corrupted system with following error message. Operating system is most recent svn update of FreeBSD 9.0-CURRENT/amd64: URL: svn://svn.freebsd.org/base/head Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 222199 Node Kind: directory Schedule: normal Last Changed Author: rmacklem Last Changed Rev: 222199 Last Changed Date: 2011-05-22 23:04:32 +0200 (So, 22 Mai 2011) After doing some review of the checkins made recently and per our offline discussion, it might be r222188 that's causing issues. How did you issue the build (did you run buildworld buildkernel, or just buildkernel, KERNFAST, etc)? Thanks, -Garrett___ freebsd-curr...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" There were some changes in /usr/src/sys/conf/kmod.mk which seem to issue the problem. My buildcommand sequence is: make buildworld && make kernel && make installworld The sequence make buildworld always performs well. Also the sequence make buildkernel is all right. The installation then fails. Regards, Oliver ___ 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"
kernel: install: mps.ko.symbols: No such file or directory
Building kernel and modules with CLANG (did not try with gcc) results in corrupted system with following error message. Operating system is most recent svn update of FreeBSD 9.0-CURRENT/amd64: URL: svn://svn.freebsd.org/base/head Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 222199 Node Kind: directory Schedule: normal Last Changed Author: rmacklem Last Changed Rev: 222199 Last Changed Date: 2011-05-22 23:04:32 +0200 (So, 22 Mai 2011) The error is: ===> mps (install) install -o root -g wheel -m 555 mps.ko /boot/kernel install -o root -g wheel -m 555 mps.ko.symbols /boot/kernel install: mps.ko.symbols: No such file or directory *** Error code 71 Stop in /usr/src/sys/modules/mps. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/obj/usr/src/sys/THOR. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. ___ 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"
editors/libreoffice: can not compile, crash on FreeBSD 9.0-CUR/amd64
On all of my FreeBSD 9.0-CURRENT/amd64 boxes LibreOffice 3.3.X crashes after starting and dumping core with signal 8. The boxes are all FreeBSD 9.0-CURRENT/amd64, the most recent version. The ports are up to date, I also tried to recompile every necessary port without success. On all FreeBSD 9.0-CURRENT/amd64 boxes compiling LibreOffice 3.3.2 fails with the following error message. Any hints? Entering /usr/ports/editors/libreoffice/work/libreoffice-build-3.3.2.2/build/libreoffice/sw/util Compiling: sw/unxfbsdx.pro/misc/sw_dflt_version.c Compiling: sw/unxfbsdx.pro/misc/swd_dflt_version.c Compiling: sw/unxfbsdx.pro/misc/swui_dflt_version.c Compiling: sw/unxfbsdx.pro/misc/msword_dflt_version.c Compiling: sw/unxfbsdx.pro/misc/vbaswobj_dflt.uno_version.c Making:swall.lib Making:swui.lib Making:libswfx.so Making:libswdfx.so Making:libswuifx.so Making:libmswordfx.so Making:libvbaswobjfx.uno.so Making:swen-US.res Making:swde.res Compiling: rsc_sw sw deliver Module 'sw' delivered successfully. 245 files copied, 0 files unchanged --- Oh dear - something failed during the build - sorry ! For more help with debugging build errors, please see the section in: http://wiki.documentfoundation.org/Development internal build errors: ERROR: error 65280 occurred while making /usr/ports/editors/libreoffice/work/libreoffice-build-3.3.2.2/build/libreoffice/pyuno/source/loader it seems that the error is inside 'pyuno', please re-run build inside this module to isolate the error and/or test your fix: --- /usr/local/bin/bash cd /usr/ports/editors/libreoffice/work/libreoffice-build-3.3.2.2/build/libreoffice source ./FreeBSDAMDEnv.Set.sh cd pyuno build when the problem is isolated and fixed exit and re-run 'make' from the top-level sometimes (sadly) it is necessary to rm -Rf unxfbsdx.pro in a module. gmake: *** [stamp/build] Error 1 *** Error code 1 Stop in /usr/ports/editors/libreoffice. *** Error code 1 Stop in /usr/ports/editors/libreoffice. ___ 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: Heads up: was Re: error building kernel: nfs_clvfsops.o: In function `nfs_mount':, nfs_clvfsops.c:(.text+0x1638): undefined reference to `nfs_diskless_valid'
On 04/26/11 15:54, Rick Macklem wrote: Since today's source (FreeBSD 9.0-CURRENT/amd64 (source is: Revision: 221060) update I get the follwoing error while building the kernel (options NFSD/options NFSCL instead of options NFSSERVER/options NFSCLIENT): cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -march=native -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -W issing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys -I/usr/src/s s/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --par m large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-ss 3 -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror vers.c linking kernel nfs_clvfsops.o: In function `nfs_mount': nfs_clvfsops.c:(.text+0x1638): undefined reference to `nfs_diskless_valid' nfs_clvfsops.c:(.text+0x1652): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1658): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1689): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x16d1): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1712): undefined reference to `nfsv3_diskless' nfs_clvfsops.o:nfs_clvfsops.c:(.text+0x171b): more undefined references to `nfsv3_diskless' follow nfs_clvfsops.o: In function `nfs_mount': nfs_clvfsops.c:(.text+0x1e19): undefined reference to `nfs_diskless' nfs_clvfsops.c:(.text+0x1e2a): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1e31): undefined reference to `nfs_diskless' nfs_clvfsops.c:(.text+0x1e3d): undefined reference to `nfs_diskless' nfs_clvfsops.c:(.text+0x1e44): undefined reference to `nfs_diskless' nfs_clvfsops.c:(.text+0x1e4a): undefined reference to `nfs_diskless' nfs_clvfsops.c:(.text+0x1e50): undefined reference to `nfs_diskless' nfs_clvfsops.o:nfs_clvfsops.c:(.text+0x1e57): more undefined references to `nfs_diskless' follow nfs_clvfsops.o: In function `nfs_mount': nfs_clvfsops.c:(.text+0x1e65): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1e6b): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1e73): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1e79): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1e80): undefined reference to `nfs_diskless' nfs_clvfsops.c:(.text+0x1e87): undefined reference to `nfs_diskless' nfs_clvfsops.c:(.text+0x1e8e): undefined reference to `nfs_diskless' nfs_clvfsops.c:(.text+0x1e94): undefined reference to `nfs_diskless' nfs_clvfsops.c:(.text+0x1e9a): undefined reference to `nfs_diskless' nfs_clvfsops.o:nfs_clvfsops.c:(.text+0x1ea0): more undefined references to `nfs_diskless' follow nfs_clvfsops.o: In function `nfs_mount': nfs_clvfsops.c:(.text+0x1eb3): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1ebd): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1ec4): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1ecb): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1ed2): undefined reference to `nfsv3_diskless' nfs_clvfsops.o:nfs_clvfsops.c:(.text+0x1ed9): more undefined references to `nfsv3_diskless' follow nfs_clvfsops.o: In function `nfs_mount': nfs_clvfsops.c:(.text+0x1f18): undefined reference to `nfs_diskless' nfs_clvfsops.c:(.text+0x1f1e): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1f33): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1f3a): undefined reference to `nfs_diskless' nfs_clvfsops.c:(.text+0x1f4b): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1f52): undefined reference to `nfs_diskless' nfs_clvfsops.c:(.text+0x1f5e): undefined reference to `nfs_diskless' nfs_clvfsops.c:(.text+0x1f6a): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1f71): undefined reference to `nfs_diskless' nfs_clvfsops.c:(.text+0x1f78): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1f83): undefined reference to `nfs_diskless_valid' nfs_clvfsops.c:(.text+0x1fcc): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1fd3): undefined reference to `nfs_diskless' nfs_clvfsops.c:(.text+0x1fd9): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x20ae): undefined reference to `nfsv3_diskless' nfs_clvfsops.o:(.data+0x1f8): undefined reference to `nfsv3_diskless' nfs_clvfsops.o:(.data+0x258): undefined reference to `nfsv3_diskless' nfs_clvfsops.o:(.data+0x2b8): undefined reference to `nfs_diskless_valid' *** Error code 1 Oops, you'll have to add "options NFS_ROOT" to your kernel config until I commit a fix. This should be fixed by r221066. You will need to do a fresh "config KERNEL" etc after upgrading past r221032. (I should have sent an email w.r.t. this yesterday, sorry.) rick I d
error building kernel: nfs_clvfsops.o: In function `nfs_mount':, nfs_clvfsops.c:(.text+0x1638): undefined reference to `nfs_diskless_valid'
Since today's source (FreeBSD 9.0-CURRENT/amd64 (source is: Revision: 221060) update I get the follwoing error while building the kernel (options NFSD/options NFSCL instead of options NFSSERVER/options NFSCLIENT): cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -march=native -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -W issing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys -I/usr/src/s s/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --par m large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-ss 3 -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror vers.c linking kernel nfs_clvfsops.o: In function `nfs_mount': nfs_clvfsops.c:(.text+0x1638): undefined reference to `nfs_diskless_valid' nfs_clvfsops.c:(.text+0x1652): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1658): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1689): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x16d1): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1712): undefined reference to `nfsv3_diskless' nfs_clvfsops.o:nfs_clvfsops.c:(.text+0x171b): more undefined references to `nfsv3_diskless' follow nfs_clvfsops.o: In function `nfs_mount': nfs_clvfsops.c:(.text+0x1e19): undefined reference to `nfs_diskless' nfs_clvfsops.c:(.text+0x1e2a): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1e31): undefined reference to `nfs_diskless' nfs_clvfsops.c:(.text+0x1e3d): undefined reference to `nfs_diskless' nfs_clvfsops.c:(.text+0x1e44): undefined reference to `nfs_diskless' nfs_clvfsops.c:(.text+0x1e4a): undefined reference to `nfs_diskless' nfs_clvfsops.c:(.text+0x1e50): undefined reference to `nfs_diskless' nfs_clvfsops.o:nfs_clvfsops.c:(.text+0x1e57): more undefined references to `nfs_diskless' follow nfs_clvfsops.o: In function `nfs_mount': nfs_clvfsops.c:(.text+0x1e65): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1e6b): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1e73): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1e79): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1e80): undefined reference to `nfs_diskless' nfs_clvfsops.c:(.text+0x1e87): undefined reference to `nfs_diskless' nfs_clvfsops.c:(.text+0x1e8e): undefined reference to `nfs_diskless' nfs_clvfsops.c:(.text+0x1e94): undefined reference to `nfs_diskless' nfs_clvfsops.c:(.text+0x1e9a): undefined reference to `nfs_diskless' nfs_clvfsops.o:nfs_clvfsops.c:(.text+0x1ea0): more undefined references to `nfs_diskless' follow nfs_clvfsops.o: In function `nfs_mount': nfs_clvfsops.c:(.text+0x1eb3): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1ebd): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1ec4): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1ecb): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1ed2): undefined reference to `nfsv3_diskless' nfs_clvfsops.o:nfs_clvfsops.c:(.text+0x1ed9): more undefined references to `nfsv3_diskless' follow nfs_clvfsops.o: In function `nfs_mount': nfs_clvfsops.c:(.text+0x1f18): undefined reference to `nfs_diskless' nfs_clvfsops.c:(.text+0x1f1e): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1f33): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1f3a): undefined reference to `nfs_diskless' nfs_clvfsops.c:(.text+0x1f4b): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1f52): undefined reference to `nfs_diskless' nfs_clvfsops.c:(.text+0x1f5e): undefined reference to `nfs_diskless' nfs_clvfsops.c:(.text+0x1f6a): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1f71): undefined reference to `nfs_diskless' nfs_clvfsops.c:(.text+0x1f78): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1f83): undefined reference to `nfs_diskless_valid' nfs_clvfsops.c:(.text+0x1fcc): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x1fd3): undefined reference to `nfs_diskless' nfs_clvfsops.c:(.text+0x1fd9): undefined reference to `nfsv3_diskless' nfs_clvfsops.c:(.text+0x20ae): undefined reference to `nfsv3_diskless' nfs_clvfsops.o:(.data+0x1f8): undefined reference to `nfsv3_diskless' nfs_clvfsops.o:(.data+0x258): undefined reference to `nfsv3_diskless' nfs_clvfsops.o:(.data+0x2b8): undefined reference to `nfs_diskless_valid' *** Error code 1 ___ 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"
XIO: fatal IO error 35 (Resource temporarily unavailable) on X server ":0.0"
Updating ports and source of my FreeBSD 9.0-CURRENT/amd64 host, equipted with a AMD/ATi HD4830 graphics board driven by X11 xf86-video-ati driver (which has been recently update as far as I saw), resulted this morning in an 'un-login-able' box. I see the xdm-login requester, but after successfully login, I see for a second the desktop (windowmaker), but X11 immediately dies and resets to the xdm requester again. Login from another box and examining the ~/.xsession-errors shows only this entry: --- foo.bar.org being added to access control list XIO: fatal IO error 35 (Resource temporarily unavailable) on X server ":0.0" after 29 requests (29 known processed) with 0 events remaining. wmaker warning: got signal 15 - exiting... --- Recompiling xdm and xorg-server ( I did this desperately in the first place) didn't help very much. I do not dare to update all the other boxes in my lab, since I suspect a similar problem since they have all the same or similar hardware (AMD graphics hardware, running X11, running FreeBSD 9.0-CURRENT/amd64). What to do? What changed? Regards, Oliver ___ 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: User authentication on Linux with FreeBSD OpenLDAP backend fails: pam_ldap: error trying to bind as user/Failed password for
On 03/18/11 17:02, Dan Nelson wrote: In the last episode (Mar 18), O. Hartmann said: I try to use a FreeBSD OpenLDAP (FreeBSD 8.2-STABLE/amd64, most recent OpenLDAP/openldap-sasl-server-2.4.24) as an authentication backend for an UBUNTU 10.10 server (using openldap 2.4.23). Most of the installation on the Ubuntu server has been successfully done (I'm not familiar with Linux, but it seems that things like pam and ldap are quite similar to FreeBSD's installation). From the Linux/Ubuntu server, I'm able to get all users and groups via 'getent passwd' and 'getent group', even 'id' on an OpenLDAP backed up user is successfully. But when it comes to a login via sshd, login fails with this error (loged on Linux Ubuntu in /var/log/auth.log): Mar 18 12:01:00 freyja sshd[26824]: Failed password for testuser from 192.168.0.128 port 40734 ssh2 Mar 18 12:01:23 freyja sshd[26854]: pam_ldap: error trying to bind as user "uid=testuser,ou=users,dc=geoinf,dc=freyja,dc=com" (Confidentiality required) "Confidentiality required" means that the server is refusing to authenticate over a non-encrypted connection. Try switching pam_ldap to ldaps (in your pam ldap.conf, either change your "uri" lines to ldaps:// or add the line "ssl on") and see if that works. I managed it! My FreeBSD OpenLDAP-server have had in it's config DIT (cn=config) the follwoing entries, which seems to confuse Linux (but not the FreeBSD clients, no matter why): olcSecurity: simple_bind=256 After reducing this security strenth value down to olcSecurity: simple_bind=128 everything works fine so far. At the moment, I have no explanation for this. Either FreeBSD clients are always binding with a higher security strength level or ignoring this. Thanks, Oliver ___ 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: Freebsd Firefox problems
On 03/19/11 16:37, Sander Janssen wrote: I have finally managed to solve this issue. Upgrading to 8.2 didn't solve anything. But after I installed ccache I decided to recompile all my installed ports in the hope that it solved my problems. After recompiling all my ports (1000 ports, including openoffice). The problem still persisted. But after reading another thread I removed pulse audio support from libcanberra and this solved the problem. I first removed gstreamer support as well but this does not cause the problem. Regards, Sander my installation of libcanberra doesn't have pulse-audio enabled anymore since enabling pulse-audio support in several other libs and apps resulted in problems updating via portmaster (as far as I can recall). At this very moment, my firefox seems to be ok. Regards, Oliver On 07/10/10 09:37, Hartmann, O. wrote: On 07/10/10 02:46, Sander Janssen wrote: Hello, I am currently having the same problems you were having with firefox 3.6 on FreeBSD in February (I found the threads on the Freebsd-Ports mailing list). The thread doesn't seem to come up with an answer and I am wondering if you managed to solve the problem? I am talking about firefox crashing when you use a context menu. I have tried a portupgrade -Rf firefox to try to recompile every depency but nothing has any effect. In my case thunderbird works correctly. Any information would be useful. Thanks in advance, Sander Hello. I have still this obscure problems. When "gettext" was updated and we have had to update any dependend port, within this procedure Firefox 3.6 worked correctly as expected. But after the update was performed, everything remained as it was before. I did several times portmaster -f (which is the same as -R with portupgrade) to build every necessary port, but with no effect. I also performed the one-day-taking gettext update and, additionaly, I recompiled every port (nearly 1000 on my systems). No effect. When delegating the client firefox to another X terminal, say to my workstation at home (login with ssh -Y for X11 portforwarding), no problems occur, so I guess the problem is riggered by X11 on the local machine and especially with the ATI radeonhd driver (which does not work correctly on many boxes and with low end Radeon HD 46XX or 47XX cards). I have no idea. I use Opera for now on the machine in question. Regards, Oliver ___ 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: User authentication on Linux with FreeBSD OpenLDAP backend fails: pam_ldap: error trying to bind as user/Failed password for
On 03/18/11 17:02, Dan Nelson wrote: In the last episode (Mar 18), O. Hartmann said: I try to use a FreeBSD OpenLDAP (FreeBSD 8.2-STABLE/amd64, most recent OpenLDAP/openldap-sasl-server-2.4.24) as an authentication backend for an UBUNTU 10.10 server (using openldap 2.4.23). Most of the installation on the Ubuntu server has been successfully done (I'm not familiar with Linux, but it seems that things like pam and ldap are quite similar to FreeBSD's installation). From the Linux/Ubuntu server, I'm able to get all users and groups via 'getent passwd' and 'getent group', even 'id' on an OpenLDAP backed up user is successfully. But when it comes to a login via sshd, login fails with this error (loged on Linux Ubuntu in /var/log/auth.log): Mar 18 12:01:00 freyja sshd[26824]: Failed password for testuser from 192.168.0.128 port 40734 ssh2 Mar 18 12:01:23 freyja sshd[26854]: pam_ldap: error trying to bind as user "uid=testuser,ou=users,dc=geoinf,dc=freyja,dc=com" (Confidentiality required) "Confidentiality required" means that the server is refusing to authenticate over a non-encrypted connection. Try switching pam_ldap to ldaps (in your pam ldap.conf, either change your "uri" lines to ldaps:// or add the line "ssl on") and see if that works. Well, I tried several things now and I do not understand this world anymore :-( For short again: The conceptional setup I use is a working concept within all FreeBSD boxes around here autheticating users via our OpenLDAP server, also ran by FreeBSD (8.2-STABLE/amd64). On the Linux/Ubuntu 10.10 server I tried the following: ldapsearch: ldap_sasl_interactive_bind_s: Confidentiality required (13) additional info: TLS confidentiality required ldapsearch -xZ: ...listing of the DIT of the LDAP server looking up an user ID definitely within the DIT: positive response from the LDAP server. I also can obtain passwd/group informations via getent passwd/group. I also checked the connection to the LDAPserver with the SSL credetials by openssl s_client -connect LDAPserver:636 -showcerts and receive a lot of informations CONNECTED(0003) depth=1 /C [...] verify error:num=19:self signed certificate in certificate chain verify return:0 --- Certificate chain 0 s:/C=DE/ST [...] -BEGIN CERTIFICATE- MIIDljCCAv+gAwIBA [...] -END CERTIFICATE- 1 s:/C [...] i:/C=DE [...] -BEGIN CERTIFICATE- MIIDojCC[...] -END CERTIFICATE- --- Server certificate subject=/C [...] issuer=/C [...] --- No client certificate CA names sent --- SSL handshake has read 2175 bytes and written 421 bytes --- New, TLSv1/SSLv3, Cipher is AES256-SHA Server public key is 2048 bit Secure Renegotiation IS supported Compression: NONE Expansion: NONE SSL-Session: Protocol : TLSv1 Cipher: AES256-SHA Session-ID: 2FCAD4AAFD18AD13013AE6A8BFF872036DAC94174F0DE626E8FF0C7F98FC7EE3 Session-ID-ctx: Master-Key: X Key-Arg : None TLS session ticket: - b5 48 c7 cc 09 99 fb a5-0e 1e 75 1b 4f aa a1 69 .Hu.O..i 0010 - 37 a5 4f c7 [...] Start Time: 1300547707 Timeout : 300 (sec) Verify return code: 19 (self signed certificate in certificate chain) --- I guess this signals everything is all right with the certificate connecting via SSL/TLS. I'm not familiar with Linux/Ubuntu's PAM setup, the setup has been done via apt-get/installation of the appropriate tools and facilities (ldap, pam_ldap, nss_ldap). I've no idea what's going wrong ... There is also some kind of weirdness around here. While login in via ssh (or better: trying to login via ssh), I received this: Mar 19 16:44:39 freyja sshd[1625]: Did not receive identification string from 125.88.109.121 Mar 19 16:44:40 freyja sshd[1623]: Failed password for ohartmann from XXX.XXX.XXX.XXX port 52686 ssh2 Mar 19 16:45:01 freyja CRON[1626]: pam_unix(cron:session): session opened for user root by (uid=0) Mar 19 16:45:01 freyja CRON[1626]: pam_unix(cron:session): session closed for user root IP 125.88.109.121 is located in China, 125.88.109.121 Server Details IP address: 125.88.109.121 Server Location: Guangzhou, Guangdong in China ISP: ChinaNet Guangdong Province Network ___ 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: User authentication on Linux with FreeBSD OpenLDAP backend fails: pam_ldap: error trying to bind as user/Failed password for
On 03/18/11 17:02, Dan Nelson wrote: In the last episode (Mar 18), O. Hartmann said: I try to use a FreeBSD OpenLDAP (FreeBSD 8.2-STABLE/amd64, most recent OpenLDAP/openldap-sasl-server-2.4.24) as an authentication backend for an UBUNTU 10.10 server (using openldap 2.4.23). Most of the installation on the Ubuntu server has been successfully done (I'm not familiar with Linux, but it seems that things like pam and ldap are quite similar to FreeBSD's installation). From the Linux/Ubuntu server, I'm able to get all users and groups via 'getent passwd' and 'getent group', even 'id' on an OpenLDAP backed up user is successfully. But when it comes to a login via sshd, login fails with this error (loged on Linux Ubuntu in /var/log/auth.log): Mar 18 12:01:00 freyja sshd[26824]: Failed password for testuser from 192.168.0.128 port 40734 ssh2 Mar 18 12:01:23 freyja sshd[26854]: pam_ldap: error trying to bind as user "uid=testuser,ou=users,dc=geoinf,dc=freyja,dc=com" (Confidentiality required) "Confidentiality required" means that the server is refusing to authenticate over a non-encrypted connection. Try switching pam_ldap to ldaps (in your pam ldap.conf, either change your "uri" lines to ldaps:// or add the line "ssl on") and see if that works. Well, in /etc/ldap.conf there is "ssl start_tls" and this should do the thing. I use nearly exact the same configuration as I do on all the FreeBSD boxes connecting to the same OpenLDAP server. I tried issuing 'ldapsaerach -xZZ -h hostIP' and I get ldap_start_tls: Connect error (-11) additional info: (unknown error code) looking deeper into the debug stuff with 'ldapsaerach -xZZ -h hostIP' I receive at the end TLS: peer cert untrusted or revoked (0x42) TLS: can't connect: (unknown error code). ldap_err2string ldap_start_tls: Connect error (-11) additional info: (unknown error code) Obviously, my certificate (self signed, openssl verify cacert.pem gives: OK) isn't found or there is something wrong with it. The certificate is located in /usr/local/etc/cacerts/cacert.pem and in Ubuntu's /etc/ldap.conf there is this line: tls_cacertfile usr/local/etc/cacerts/cacert.pem is referring to the certificate. ___ 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"
User authentication on Linux with FreeBSD OpenLDAP backend fails: pam_ldap: error trying to bind as user/Failed password for
Hello. I try to use a FreeBSD OpenLDAP (FreeBSD 8.2-STABLE/amd64, most recent OpenLDAP/openldap-sasl-server-2.4.24) as an authentication backend for an UBUNTU 10.10 server (using openldap 2.4.23). Most of the installation on the Ubuntu server has been successfully done (I'm not familiar with Linux, but it seems that things like pam and ldap are quite similar to FreeBSD's installation). From the Linux/Ubuntu server, I'm able to get all users and groups via 'getent passwd' and 'getent group', even 'id' on an OpenLDAP backed up user is successfully. But when it comes to a login via sshd, login fails with this error (loged on Linux Ubuntu in /var/log/auth.log): Mar 18 12:01:00 freyja sshd[26824]: Failed password for testuser from 192.168.0.128 port 40734 ssh2 Mar 18 12:01:23 freyja sshd[26854]: pam_ldap: error trying to bind as user "uid=testuser,ou=users,dc=geoinf,dc=freyja,dc=com" (Confidentiality required) Mar 18 12:01:25 freyja sshd[26854]: Failed password for testuser from 192.168.0.128 port 54156 ssh2 I'm able to login from other systems (FreeBSD 9 and 8) via this specific OpenLDAP server. Does anyone has a glue? Please set me CC, I'm not subscribing this list. Thanks in advance and regards, Oliver ___ 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: FreeBSD CURRENT custom ISO install image: howto?
On 03/16/11 19:10, Al Plant wrote: O. Hartmann wrote: I'm desperately looking for howto creating my own FreeBSD 9.0-CURRENT/amd64 custom installation DVD. Google delivers a lot of outdated stuff and I wasn't able to find some hints in the handbook, so maybe one here can help. I've already all sources via 'svn' (no CVS) on the local box. The intention is to be able to use new bsdinstall instead of sysinstall for having GPT partitions. Please set me CC if responding. Thanks in advance, Oliver ___ 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" Aloha Oliver, On the list is Manolis Kiagias. He makes install disks possible. I also copied him on this reply. He helped me with making an install disk for my projects and he can most likely point you to his how to methods. Hello out there. Thank you very much. The last time I tried making a install media from a local installation is quite a lot of years since. I found " man release(7)" very helpful, but at the end it turns out that I didn't understood what is happening. I tried to fullfill all prerequisites needed to make a release, i.e. 1) having a populated /usr/src (SVN managed), I recently made a 'make buildworld', I created a suitable release-folder to chroot to for the release and I issued MAKE_DVD=yes and MAKE_ISOS=yes to ensure the build of ISO images for a DVD. I'll show the command issued at the end. But the build-process seems to drop everything it builds into /usr/src/release (from where the commande 'make release' has to be issued as docuemnted in 'release (7)'. Here's the command: Folders /home/release and /usr/src exists, 'make buildworld' has been issued and successfully finished. The following commands are issued regarding the release (7) manpage: cd /usr/src/release make release SVNROOT=/usr/src NODOC=yes MAKE_DVD=yes MAKE_ISOS=yes\ CHROOTDIR=/home/release BUILDNAME=SOMETHING_NEW I do not ommit TARGET_ARCH and TARGET since I do not crossbuild (I'm on amd64). The outcome is that the make-release process seems to flood /usr/src/release as it never 'chroot' to the given CHROOTDIR. I'm not familiar with this and I exepct this to be a kind of mistake. Correct me if I'm wrong. Regards, Oliver ___ 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 CURRENT custom ISO install image: howto?
I'm desperately looking for howto creating my own FreeBSD 9.0-CURRENT/amd64 custom installation DVD. Google delivers a lot of outdated stuff and I wasn't able to find some hints in the handbook, so maybe one here can help. I've already all sources via 'svn' (no CVS) on the local box. The intention is to be able to use new bsdinstall instead of sysinstall for having GPT partitions. Please set me CC if responding. Thanks in advance, Oliver ___ 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"
Dell iDRAC JViewer and FreeBSD 9.0: not working, help!
We use a Dell rack system with a JAVA based virtual console facility, iDRAC6, which works well when used via Windows 7 or some Linux boxes. On FreeBSD 9.0/amd64 (most recent) with JAVA diablo-jdk-1.6.0.07.02_13 Java Development Kit 1.6.0_07.02 openjdk6-b22_2 Oracle's Java 6 virtual machine release under the GPL v2 installed, I receive the virtual console after referring 'javaws' (Java WebStarter) as the appropriate application staring a kind of *.jnl application, but I receive an error: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.javaws.Launcher.executeApplication(Launcher.java:1293) at com.sun.javaws.Launcher.executeMainClass(Launcher.java:1239) at com.sun.javaws.Launcher.doLaunchApp(Launcher.java:1086) at com.sun.javaws.Launcher.run(Launcher.java:105) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.UnsatisfiedLinkError: com.ami.iusb.FloppyRedir.GetKeyboardName()Ljava/lang/String; at com.ami.iusb.FloppyRedir.GetKeyboardName(Native Method) at com.ami.iusb.FloppyRedir.ReadKeybdType(FloppyRedir.java:454) at com.ami.kvm.jviewer.hid.KVMClient.get_keybd_type(KVMClient.java:731) at com.ami.kvm.jviewer.hid.KVMClient.startRedirection(KVMClient.java:723) at com.ami.kvm.jviewer.gui.JViewerApp.OnVideoStartRedirection(JViewerApp.java:452) at com.ami.kvm.jviewer.gui.JViewerApp.OnConnectToServer(JViewerApp.java:435) at com.ami.kvm.jviewer.JViewer.main(JViewer.java:110) ... 9 more I do not understand much why JAVA, platform independent, is not working with FreeBSD as expected. Linux- und Windows are working. Any help? Oliver ___ 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: xorg-driver/xf86-video-ati-6.14.0: Worse performance since last update
On 03/08/11 19:32, Roland Smith wrote: On Tue, Mar 08, 2011 at 07:16:05PM +0100, O. Hartmann wrote: Since the last update of Xorg stuff, including the xf86-video-ati-6.14.0, the video performance of all of our AMD/ATi-driven boxes went worse. The bad performance also occur with the recommendations made in ports/UPDATING for driver "radeon". Without those recommendated adding of options even with a working xorg.conf file the performance stays worse. The recommendations have been removed from UPDATING; with the exception of the "DynamicPM" option, all the others are at their default settings and therefore not necessary. All right, I already adjusted my xorg.conf towards the initial state ... Worse means: using vlc (also after recompilation after upgrades made!), videos are massively bumpy and can not be watched with vlc-screen fully expanded to 1900x1200 pixel with HD4830 graphics card - this worked perfectly before. Check out the logfile '/var/log/Xorg.0.log' if you see anything unusual. Well, for the untrained eye there seems nothing wrong, except the non-existent acceleration ... see below. Moving windows around now looks like having chunks of video content floating around - as on unaccelerated/slow graphics boards. When looking at the logfile '/var/log/Xorg.0.log', does it say the following; (II) RADEON(0): Acceleration enabled (II) RADEON(0): Set up textured video I see this: (II) RADEON(0): MC_FB_LOCATION : 0x00ef00d0 0x001f (II) RADEON(0): MC_AGP_LOCATION : 0x003f (==) RADEON(0): Backing store disabled (WW) RADEON(0): Direct rendering disabled (EE) RADEON(0): Acceleration initialization failed (II) RADEON(0): Acceleration disabled Personally, I have built this port with one of the patches removed. In my case the patch in question hung my machine every time! (there was quite a large thread about it on the mailing-list) Try removing the patch /usr/ports/x11-drivers/xf86-video-ati/files/patch-src-radeon_driver.c and re-install the driver. If that works you can make the change permanent like this: # cd /usr/ports/x11-drivers/xf86-video-ati/files # truncate -s 0 patch-src-radeon_driver.c # chflags schg,sunlnk patch-src-radeon_driver.c Roland Well, yesterday or two days ago there was a change of the port x11-drivers/xf86-video-ati. The file patch-src-radeon_driver.c has gone. But the problems still occur (but not that harsh as before). I realize on all AMD driven graphicsystems this "bumpyness", even on those graphics cards, HD4830, which are supposed to deliver a acceptable performance for every day's usage, show now a kind of being cut-off and they are no longer faster than the crappy HD4670 or HD4770 which we also use in some FBSD 9.0 boxes. ___ 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: xpdf can not print via cups if started from firefox
On 03/11/11 16:44, Warren Block wrote: On Fri, 11 Mar 2011, O. Hartmann wrote: On 03/11/11 01:13, Polytropon wrote: Maybe you're experiencing a caching problem? I would guess that as you stated there is a temporary file, this should not happen (in relation to Firefox) there should at least be an error message. Did you try to enter the full command into xpdf's printing dialog, e. g. "/usr/local/bin/lpr -P", just in case the .xpdfrc setting hasn't been read upon program start? Yes, I did, still the same problem. I have the strange feeling that a firefox-started xpdf doesn't know anything about CUPS and its printing queues. I try to figure out how to log this ... With a stock lpr/lpd, Firefox and xpdf work as expected. My .xpdfrc is: psFile "| lpr -Plaser" "laser" is the queue for my laser printer, defined in /etc/printcap. If the real BSD lpr is being called, you should see errors in /var/log/lpd-errs. There's a CUPS on FreeBSD article: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/cups/index.html Using xpdf or any other printing client works well with my setup, even xpdf called from a terminal prints correctly, reports pages, access etc. in /var/log/cups/access_log|pages_log as expected. ___ 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: xpdf can not print via cups if started from firefox
On 03/11/11 01:13, Polytropon wrote: On Thu, 10 Mar 2011 11:38:19 +0100, "O. Hartmann" wrote: On 03/08/11 16:51, Warren Block wrote: On Tue, 8 Mar 2011, O. Hartmann wrote: I've got a weird problem here. Very often I download scientific papers as pdf from protals and they got opened via firefox3 with the configured propper utility, in this case xpdf. In such a case, printing is impossible. I hit the print button, a popup shows up with the configured CUPS printing queue, but hitting OK doesn't have any effect. The funny thing is: when opening the same PDF (it is stored in /tmp/) with xpdf by starting xpdf from a terminal, printing on the same queue works well. In your .xpdfrc, do you specify a full path to the CUPS lpr? I did now and it hasn't any effect. Maybe you're experiencing a caching problem? I would guess that as you stated there is a temporary file, this should not happen (in relation to Firefox) there should at least be an error message. Did you try to enter the full command into xpdf's printing dialog, e. g. "/usr/local/bin/lpr -P", just in case the .xpdfrc setting hasn't been read upon program start? Yes, I did, still the same problem. I have the strange feeling that a firefox-started xpdf doesn't know anything about CUPS and its printing queues. I try to figure out how to log this ... ___ 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: xpdf can not print via cups if started from firefox
On 03/08/11 16:51, Warren Block wrote: On Tue, 8 Mar 2011, O. Hartmann wrote: I've got a weird problem here. Very often I download scientific papers as pdf from protals and they got opened via firefox3 with the configured propper utility, in this case xpdf. In such a case, printing is impossible. I hit the print button, a popup shows up with the configured CUPS printing queue, but hitting OK doesn't have any effect. The funny thing is: when opening the same PDF (it is stored in /tmp/) with xpdf by starting xpdf from a terminal, printing on the same queue works well. In your .xpdfrc, do you specify a full path to the CUPS lpr? I did now and it hasn't any effect. ___ 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-driver/xf86-video-ati-6.14.0: Worse performance since last update
Since the last update of Xorg stuff, including the xf86-video-ati-6.14.0, the video performance of all of our AMD/ATi-driven boxes went worse. The bad performance also occur with the recommendations made in ports/UPDATING for driver "radeon". Without those recommendated adding of options even with a working xorg.conf file the performance stays worse. Worse means: using vlc (also after recompilation after upgrades made!), videos are massively bumpy and can not be watched with vlc-screen fully expanded to 1900x1200 pixel with HD4830 graphics card - this worked perfectly before. Moving windows around now looks like having chunks of video content floating around - as on unaccelerated/slow graphics boards. What's wrong? ___ 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: xpdf can not print via cups if started from firefox
On 03/08/11 16:51, Warren Block wrote: On Tue, 8 Mar 2011, O. Hartmann wrote: I've got a weird problem here. Very often I download scientific papers as pdf from protals and they got opened via firefox3 with the configured propper utility, in this case xpdf. In such a case, printing is impossible. I hit the print button, a popup shows up with the configured CUPS printing queue, but hitting OK doesn't have any effect. The funny thing is: when opening the same PDF (it is stored in /tmp/) with xpdf by starting xpdf from a terminal, printing on the same queue works well. In your .xpdfrc, do you specify a full path to the CUPS lpr? No, I do not. And while making this confession, I'll change this as soon as possible and report back. I guess this is a very good hint ... Oliver ___ 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: xpdf can not print via cups if started from firefox
On 03/08/11 11:43, Leslie Jensen wrote: On 2011-03-08 09:38, O. Hartmann wrote: Hello. I've got a weird problem here. Very often I download scientific papers as pdf from protals and they got opened via firefox3 with the configured propper utility, in this case xpdf. In such a case, printing is impossible. I hit the print button, a popup shows up with the configured CUPS printing queue, but hitting OK doesn't have any effect. The funny thing is: when opening the same PDF (it is stored in /tmp/) with xpdf by starting xpdf from a terminal, printing on the same queue works well. I realized that the change of this behaviour occured a long time ago when the cups printing system got an update. I never figured out what's the diffrence between starting xpdf via terminal and starting via firefox. My first guess was that my local ~/.xpdfrc does have effect, as the right configured CUPS printing queue showed up, but even the firefox-started xpdf client shows the right printing queue, so this implies that xpdf also reads my ~/.xpdfrc. I'm not sure what's going wrong. I have no clue what kind of paper information is passed to xpdf by being called via firefox. Any help appreciated. Thanks, Oliver ___ 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" Have you made the printer as system default in CUPS? Then you should be able to "print with command" lp from xpdf. /Leslie Yes I have. But this doesn't work anyway. With a terminal started xpdf either each queue existent in CUPS works with an opened PDF, even the standard 'lp' queue. But the PDF never reaches the printer when started via firefox. When xpdf is started from inside firefox, the .xpdfrc seems to be read since changes to the default printer queue in .xpdfrc takes immediately effect, but hitting printing/OK never produces a result. ___ 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: xpdf can not print via cups if started from firefox
How to 'configure' this? Firefox3 allows only selecting applications via 'Preferences' Menu. Trying to configure xpdf manually via "about"config" results in can-not-find-application-tag, means: tehre is nothing to look at. On 03/08/11 09:49, Kristofer M White wrote: Does configuring firefox to launch something like "xterm -e xpdf" rather than just "xpdf" dump any errors to the term when trying to print? "O. Hartmann" wrote: Hello. I've got a weird problem here. Very often I download scientific papers as pdf from protals and they got opened via firefox3 with the configured propper utility, in this case xpdf. In such a case, printing is impossible. I hit the print button, a popup shows up with the configured CUPS printing queue, but hitting OK doesn't have any effect. The funny thing is: when opening the same PDF (it is stored in /tmp/) with xpdf by starting xpdf from a terminal, printing on the same queue works well. I realized that the change of this behaviour occured a long time ago when the cups printing system got an update. I never figured out what's the diffrence between starting xpdf via terminal and starting via firefox. My first guess was that my local ~/.xpdfrc does have effect, as the right configured CUPS printing queue showed up, but even the firefox-started xpdf client shows the right printing queue, so this implies that xpdf also reads my ~/.xpdfrc. I'm not sure what's going wrong. I have no clue what kind of paper information is passed to xpdf by being called via firefox. Any help appreciated. Thanks, Oliver ___ 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"
xpdf can not print via cups if started from firefox
Hello. I've got a weird problem here. Very often I download scientific papers as pdf from protals and they got opened via firefox3 with the configured propper utility, in this case xpdf. In such a case, printing is impossible. I hit the print button, a popup shows up with the configured CUPS printing queue, but hitting OK doesn't have any effect. The funny thing is: when opening the same PDF (it is stored in /tmp/) with xpdf by starting xpdf from a terminal, printing on the same queue works well. I realized that the change of this behaviour occured a long time ago when the cups printing system got an update. I never figured out what's the diffrence between starting xpdf via terminal and starting via firefox. My first guess was that my local ~/.xpdfrc does have effect, as the right configured CUPS printing queue showed up, but even the firefox-started xpdf client shows the right printing queue, so this implies that xpdf also reads my ~/.xpdfrc. I'm not sure what's going wrong. I have no clue what kind of paper information is passed to xpdf by being called via firefox. Any help appreciated. Thanks, Oliver ___ 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: GRASS: 6.4.0: where is the postgresql (pg) driver?
On 03/07/11 16:26, wen heping wrote: 2011/3/7 O. Hartmann: Hello. I desperately try to connect to a PostgreSQL DB server using GRASS (6.4.0 as from the recent ports). The documentation of GRASS, even the most recent one, reports using the 'driver=pg' option. Having already set up a database in PostgreSQL (server 9.0.4), the admin user properly specified is capable to connect from console (terminal) or pgadmin3 client. But using GRASS, only 'dbf', 'sqlite' and 'ogr' as drivers are offered. I tried to figure out whether 'ogr' could cover postgresql connects, but there isn't any information about that, not even in GRASS' documentation (I haven't found any yet). I suspect the 'pg'-driver isn't correctly included in GRASS so I'd like to ask someone already has used PostgreSQL as the DB backend for GRASS GIS. It is obviously pg-driver was not correctly included in grass ports, there is even no PGSQL macro in plist :) I shall try to fix it tomorrow. wen Thanks in advance. Oliver Thank you in advance. Oliver ___ 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"
GRASS: 6.4.0: where is the postgresql (pg) driver?
Hello. I desperately try to connect to a PostgreSQL DB server using GRASS (6.4.0 as from the recent ports). The documentation of GRASS, even the most recent one, reports using the 'driver=pg' option. Having already set up a database in PostgreSQL (server 9.0.4), the admin user properly specified is capable to connect from console (terminal) or pgadmin3 client. But using GRASS, only 'dbf', 'sqlite' and 'ogr' as drivers are offered. I tried to figure out whether 'ogr' could cover postgresql connects, but there isn't any information about that, not even in GRASS' documentation (I haven't found any yet). I suspect the 'pg'-driver isn't correctly included in GRASS so I'd like to ask someone already has used PostgreSQL as the DB backend for GRASS GIS. Thanks in advance. Oliver ___ 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"
LibreOffice 3.3.0: incapable of opening M$ Office Excel sheets which could be opened by OO 3.2.1
I got a serious problem: LibeOffice 3.3.0 rejects opening Microsoft Office Excel created spreadsheets with an 'internal import error'. Is there anything to be aware of or is this a real bug? Regards, Oliver ___ 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"
port reinstall does not update /var/db/pkg (libreoffice)
Libreoffice undergoes a lot of chenges these days, so updating the port from siurce takes more than four hours on my boxes. On one of the, running FreeBSD 9.0-CUR/amd64, portmaster fails to update to libreoffice-3.3.0_3, process quits with random strange errors. Doing the job from ports/editors/libreoffice via 'make reinstall' works fine, but this does not update /var/db/pkg/libreoffice-3.3.0_3 properly, so that everytime I perform "portmaster -av", libreoffice shows up again, claiming being libreoffice-3.3.0_1, wanting to be updated to libreoffice-3.3.0_3 (not realising that it is already libreoffice-3.3.0_2, because I updated sunday the last time and after the today's update it is de facto libreoffice-3.3.0_3, but /var/db/pkg/libreoffice-3.3.0_1 clains still to be libreoffice-3.3.0_1). How to fix this? ___ 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"
top: where to find process state descriptions (i.e. STATE usem)?
Hello. Try to find docs about the process states shown in top, but I can't find any hint for explanations what the abbrev. do mean. I have a problem with a scientific program using OpenMP showing STATE 'usem' in top. Problem: the small program is much slower on a dual or four core CPU using OpenMP than using only a single core (single thread never show state 'usem' in top). Any help? Thanks in advance, and regards, Oliver ___ 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: editors/openoffice-org-3.3.0: serious issue with X11
On 02/03/11 14:12, Robert Huff wrote: Alexandre writes: On Thu, Feb 3, 2011 at 10:14 AM, Pavlo Greenbergwrote: > [SNIP] > But I'm agree with you, OOo's behavior after the last update is abnormal. Why not give a try to LibreOffice, that is in ports : http://www.freshports.org/editors/libreoffice/ I switched yesterday, having not known it was available. It seems to work on all OOo-generated material (as one would expect), and build cleanly and (subjectively) somewhat faster than OO. (This is on an 4x3ghz amd64 machine with 8 gb of memory.) Robert Huff LibreOffice seems not to be that kind of 'replacement' I'd expected. Trying to start 'spadmin' for setting up printers fails with some libraries not found - I had to append paths to the right (weird) lib-path to /etc/ld-elf.so.conf. Done this, spadmin and sibblings will start but whatever I do have as printers (CUPS based on all of our systems), I'm incapable of having these printers for usage listed in LibreOffice! OpenOffice works fine. ___ 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: editors/openoffice-org-3.3.0: serious issue with X11
On 02/03/11 11:51, Alexandre wrote: On Thu, Feb 3, 2011 at 10:14 AM, Pavlo Greenberg mailto:sir_...@onet.com.ua>> wrote: [SNIP] But I'm agree with you, OOo's behavior after the last update is abnormal. Why not give a try to LibreOffice, that is in ports :Â http://www.freshports.org/editors/libreoffice/ I'll try, but when I installed/updated OO, I explicitely looked for LibreOffice (that was a couple of days ago, when OO 3.3.0 got into the ports), but it wasn't there. I'll try. Thanks for that hint. Oliver ___ 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: editors/openoffice-org-3.3.0: serious issue with X11
On 02/02/11 10:25, Anonymous wrote: "O. Hartmann" writes: Hello. I just upgraded openoffice-3.2.1 to openoffice-org-3.3.0 and found myself in a serious issue. Opening openoffice works only sporadically, in most cases I get the error: XDM authorization key matches an existing client!/usr/local/openoffice.org-3.3.0/openoffice.org3/program/soffice.bin X11 error: Can't open display: Set DISPLAY environment variable, use -display option or check permissions of your X-Server (See "man X" resp. "man xhost" for details) Have you tried to add the following to xdm-config DisplayManager*authName: MIT-MAGIC-COOKIE-1 or adjusting permissions using xhost(1)? I did. Adding DisplayManager*authName: MIT-MAGIC-COOKIE-1 to xdm-config didn't make the problem disappear, only a global 'xhost +' helped. I also tried xhost + localhost:0.0 and all IP- or name-based combinations even FQDN/IP of the host, without success, except pure 'xhost +'. ___ 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"
editors/openoffice-org-3.3.0: serious issue with X11
Hello. I just upgraded openoffice-3.2.1 to openoffice-org-3.3.0 and found myself in a serious issue. Opening openoffice works only sporadically, in most cases I get the error: XDM authorization key matches an existing client!/usr/local/openoffice.org-3.3.0/openoffice.org3/program/soffice.bin X11 error: Can't open display: Set DISPLAY environment variable, use -display option or check permissions of your X-Server (See "man X" resp. "man xhost" for details) Deleting .Xauthority or restarting the session via resetting xdm/Xorg or removing ~/.openoffice didn't help anyway. Any suggestions are appreciated. Thanks in advance, Oliver ___ 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: FreeBSD 9/ZFS: Striped Pool (2 disks) migrating to mirror (onto additional disk)
On 01/26/11 21:47, Christer Solskogen wrote: On Wed, Jan 26, 2011 at 9:42 PM, Dan Nelson wrote: ZFS lets you add and detach mirrors on the fly, since you're not changing the capacity of the pool itself. Sure, you're going to lose the contents of the large 2TB drive, but that's sort of assumed. You can't convert 4TB of non-mirrored disks into 2TB of mirrored disks without losing 2TB of space. Just make sure you have less than 2TB total used data on all volumes, and copy the data off the 2TB filessytem onto the striped 1+1TB one before repartitioning and adding the mirrors. zpool attach [-f] pool device new_device The problem is that you cant attach a drive to a vdev that consists of two striped disks. All right, I see there is no way without any kind of trade-off. My thinking was simple, I thought since the two physical 1TB disks build one joint pool of 2TB overall capacity, I could simply 'mirror' this pool to another disk of the same capacity. Is there a way to 'send' via ZFS the data of the pool to the backup disk, like a snapshot from one pool to another one? Oliver ___ 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 9/ZFS: Striped Pool (2 disks) migrating to mirror (onto additional disk)
I've got a problem. For performance reasons I use two 1TB harddrives as a single pool, and as far as I know, ZFS on recent FreeBSD 9/amd64 treats suchs pools 'striped'. Well, I can measure a performance gain in writing and reading. Well, for backup, I use an additional 2TB disk, ZFS, compressed, the backup is done manually via rsync (i'm looking for more suitable simple backup solutions). My question is: is it possible to migrate the two-disk pool without data loss into a mirrored pool by adding the one 2TB-disk? Comments appreciated, thanks in advance, Oliver ___ 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: CURRENT: Issue with ZFS and 2TB WD HDD (WDC WD20EURS-63Z9B1 80.00A80)
On 11/29/10 19:32, James R. Van Artsdalen wrote: O. Hartmann wrote: Attached to the system are three WD harddrives with ZFS as filesystem on GPT partitioning scheme. Please send the output of "camcontrol devlist" and "zpool status" on FreeBSD-8.1. Then export the pool in FreeBSD-8.1, boot FreeBSD-9 with verbose booting and send the output of "camcontrol devlist", "zpool import BACKUP" and the part of /var/log/messages that shows FreeeBSD searching for the pool during the import. Appended, you'll find some of the requested data. There is no valuable dmesg/message output, due to the simple fact, that after yesterday's "make world" and another import try the BACKUP00 pool was imported. The only thing to report is, that while importing the BACKUP00 pool, which is on devise ada3, I got an message on console like: Nov 29 21:13:36 <0.2> thor kernel: ZFS WARNING: Unable to attach to ada1. This strange message always came up when importing the BACKUP00 pool (BACKUP is a typo, sorry for the inconvenience) and when it was about to fail. It might be useful to know what disk controller is being used. => 34 3907029101 ada3 GPT (1.8T) 344062- free - (2.0M) 4096 3907025039 1 freebsd-zfs (1.8T) It is not related to your problem, but how did that unused space wind up before partition 1? Well, my fault. I initiated the partitions with the "-b 4096" option set for the first partition. It was so nice and at ease playing around with gpart ... And here comes the data requested: #FreeBSD 8.2-PRE/amd64 -- camcontrol devlist at scbus4 target 0 lun 0 (pass0,ada0) at scbus5 target 0 lun 0 (pass1,ada1) at scbus6 target 0 lun 0 (pass2,ada2) at scbus7 target 0 lun 0 (pass3,ada3) at scbus9 target 0 lun 0 (cd0,pass4) #FreeBSD 9.0-CURRENT/amd64 -- camcontrol devlist at scbus4 target 0 lun 0 (pass0,ada0) at scbus5 target 0 lun 0 (pass1,ada1) at scbus6 target 0 lun 0 (pass2,ada2) at scbus7 target 0 lun 0 (pass3,ada3) at scbus8 target 0 lun 0 (pass4,ada4) at scbus9 target 0 lun 0 (cd0,pass5) (needed to swap 1st and 5th drive since FBSD 8 was installed with MBR and no labels and needed device special file for mounting partitions while on FreeBSD 9 I used the first time GPT partitioning scheme with labeling for mounting via /etc/fstab) #FreeBSD 8 zpool status: pool: BACKUP00 state: ONLINE scrub: none requested config: NAMESTATE READ WRITE CKSUM BACKUP00ONLINE 0 0 0 ada3p1ONLINE 0 0 0 errors: No known data errors pool: THOR00 state: ONLINE scrub: none requested config: NAMESTATE READ WRITE CKSUM THOR00 ONLINE 0 0 0 ada1p1ONLINE 0 0 0 ada2p1ONLINE 0 0 0 errors: No known data errors #FreeBSD 8 pciconf -lcv (for the requested controller) ah...@pci0:0:31:2: class=0x010601 card=0x82d41043 chip=0x3a228086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '6 port SATA AHCI Controller' class = mass storage subclass = SATA cap 05[80] = MSI supports 16 messages enabled with 1 message cap 01[70] = powerspec 3 supports D0 D3 current D0 cap 12[a8] = SATA Index-Data Pair cap 09[b0] = vendor (length 6) Intel cap 2 version 0 In kernel config, I use AHCI driver modell, not the atapi one, but I guess this is obvious due to 'adaXX' ... And by the way, the 2 TB drive in question is sold as a 'PVR/VCR video special device", I mistakenly ordered this one since it promissed low power, high sustain-reliability (it is used for backups), but some web sites claim that the controller of this specific, expensive 2 TB hdd deals different with errornous blocks read or written out - I can not verify this, since I have no technical paper nor do I understand much of HDD electrical engineering ... Regards, Oliver ___ 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"
subversion authentication via SASL2 using a OpenLDAP backend
Hello. I just try to authenticate users of our subversion repository via sasl2 against a running OpenLDAP backend (all services running on FreeBSD 8.2-PRE/8.1 and 7.3). After setting up a config file /usr/local/etc/sasl2/svn.conf containing the following: pwcheck_method: auxprop auxprop_plugin: ldap ldapdb_uri: ldap://ldap.host ldapdb_mech:PLAIN DIGEST-MD5 ANONYMOUS EXTERNAL CRAM-MD5 OTP #ldapdb_rc: /usr/local/etc/sasl2/ldaprc ldapdb_startls: yes log_level: 7 and a proper olcAuthzRegexp in the cn=config container of OpenLDAP like uid=([^,]*),cn=realm,cn=plain,cn=auth uid=$1,ou=users,dc=domain,dc=foo I never see any attempt of subversion connecting to the OpenLDAP server via sasl2. I can not even proff whether my setups in the LDAP are correct or not, since the subversion try of autheticate seems to run into nowhere. After several tries of importing something (I assume having set up properly svnserv.conf and authz in the subversion repos for this specific case) I receive this message on the console: svn: Authentication error from server: SASL(-13): user not found: no secret in database svn: Your commit message was left in a temporary file: Besides, I already installed the port /usr/ports/security/cyrus-sasl2-ldapdb but it does not help. Can anybody give a hint or tip? Thanks in advance, Oliver ___ 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: CURRENT: Issue with ZFS and 2TB WD HDD (WDC WD20EURS-63Z9B1 80.00A80)
On 11/29/10 17:41, Leonidas Tsampros wrote: "O. Hartmann" writes: I'm running a newly setup FreeBSD 9.0-CURRENT/amd64 SMP box. The former OS was FreeBSD 8.1-PRE/amd64. Attached to the system are three WD harddrives with ZFS as filesystem on GPT partitioning scheme. Two 1TB HDD are spanning a volume with 2 TB capacity which is quite fast due to parallel access through ZFS. The underlying layout is, as mentioned, GPT, bot devices are named /dev/ada1p1 and /dev/ada2p1. The thir drive is a WD Caviar Green 2TB HDD acting as a compressed ZFS backup media, also based on a GPT partitioning scheme and known as device /dev/ada3p1. In FreeBSD 8.2-PRE/amd64 I can use the JBOD volume resembled from two 1TB HDD without problems, mounting is all right, dismounting, also with the 2TB HDD, labeld as BACKUP00 volume in ZFS. Doing a "zpool export" on both ZFS volumes works fine in FBSD 8, importing is also no problem. The system's log does not show any kind of irregularities, errors or something else indicating soemthing weird with one of the three devices. Exporting both volumes in FreeBSD 8 works. But importing them in FreeBSD 9.0-CURRENT/amd64 as with the most recent make world of today fails on the 2TB HDD (ZFS pool/volume BACKUP00). Issuing "zpool import BACKUP00" results in cannot import 'BACKUP': no such pool available and on console I receive message ZFS WARNING: Unable to attach to ada1 But the drive is and was ada3! Looking with zpool status, I get the follwoing picture: pool: BACKUP00 state: FAULTED status: One or more devices could not be used because the label is missing or invalid. There are insufficient replicas for the pool to continue functioning. action: Destroy and re-create the pool from a backup source. see: http://www.sun.com/msg/ZFS-8000-5E scrub: none requested config: NAMESTATE READ WRITE CKSUM BACKUP00FAULTED 0 0 0 corrupted data ada3 UNAVAIL 0 0 0 corrupted data pool: THOR00 state: ONLINE scrub: none requested config: NAMESTATE READ WRITE CKSUM THOR00 ONLINE 0 0 0 ada1p1ONLINE 0 0 0 ada2p1ONLINE 0 0 0 errors: No known data errors This picture differs from what I see i FreeBSD 8.2-PRE/amd issuing the same command! I did a full "zpool scrub" on both pools - no effect. Surprisingly, the GPT partition of the pool BACKUP00 isn't shown in FreeBSD 9, while I see ada3p1 in FreeBSD 8.2. gpart show ada3 lists this: => 34 3907029101 ada3 GPT (1.8T) 344062- free - (2.0M) 4096 3907025039 1 freebsd-zfs (1.8T) The drive in question is a WesternDigital Caviar Green WD ( at scbus7 target 0 lun 0 (pass3,ada3)). Can someone explain what#s going on? The drive in question is one of the new 4k sized physical block devices. Why is FreeBSD 8 dealing with the HDD, FreeBSD 9 not? Any help at this point? Hope the volume is not lost. Thanks in advance, Oliver Hi Oliver, just a wild guess and maybe completely wrong: are the ZFS version numbers and zpool version numbers the same across 8.1 and 9-CURRENT ? Best Regards, Leonidas Hello Leonidas, both pools are versioned '15', that is the most recent version in 9.0-CURRENT and 8.2-PRE. One of the both pools, that one spanned over two 1 TB hard drives, works perfectly. The backup pool on the 2TB hdd does not. It seems that the partitioning information got lost in FreeBSD 9. The hdd in question is one of that new 2TB drives of WD with 4k blocks ... maybe I made a mistake when initiatet the GPT layout ... (started the partition at block 4096 with the '-b'-option of 'gpart add'). Greetings, Oliver ___ 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"
CURRENT: Issue with ZFS and 2TB WD HDD (WDC WD20EURS-63Z9B1 80.00A80)
I'm running a newly setup FreeBSD 9.0-CURRENT/amd64 SMP box. The former OS was FreeBSD 8.1-PRE/amd64. Attached to the system are three WD harddrives with ZFS as filesystem on GPT partitioning scheme. Two 1TB HDD are spanning a volume with 2 TB capacity which is quite fast due to parallel access through ZFS. The underlying layout is, as mentioned, GPT, bot devices are named /dev/ada1p1 and /dev/ada2p1. The thir drive is a WD Caviar Green 2TB HDD acting as a compressed ZFS backup media, also based on a GPT partitioning scheme and known as device /dev/ada3p1. In FreeBSD 8.2-PRE/amd64 I can use the JBOD volume resembled from two 1TB HDD without problems, mounting is all right, dismounting, also with the 2TB HDD, labeld as BACKUP00 volume in ZFS. Doing a "zpool export" on both ZFS volumes works fine in FBSD 8, importing is also no problem. The system's log does not show any kind of irregularities, errors or something else indicating soemthing weird with one of the three devices. Exporting both volumes in FreeBSD 8 works. But importing them in FreeBSD 9.0-CURRENT/amd64 as with the most recent make world of today fails on the 2TB HDD (ZFS pool/volume BACKUP00). Issuing "zpool import BACKUP00" results in cannot import 'BACKUP': no such pool available and on console I receive message ZFS WARNING: Unable to attach to ada1 But the drive is and was ada3! Looking with zpool status, I get the follwoing picture: pool: BACKUP00 state: FAULTED status: One or more devices could not be used because the label is missing or invalid. There are insufficient replicas for the pool to continue functioning. action: Destroy and re-create the pool from a backup source. see: http://www.sun.com/msg/ZFS-8000-5E scrub: none requested config: NAMESTATE READ WRITE CKSUM BACKUP00FAULTED 0 0 0 corrupted data ada3 UNAVAIL 0 0 0 corrupted data pool: THOR00 state: ONLINE scrub: none requested config: NAMESTATE READ WRITE CKSUM THOR00 ONLINE 0 0 0 ada1p1ONLINE 0 0 0 ada2p1ONLINE 0 0 0 errors: No known data errors This picture differs from what I see i FreeBSD 8.2-PRE/amd issuing the same command! I did a full "zpool scrub" on both pools - no effect. Surprisingly, the GPT partition of the pool BACKUP00 isn't shown in FreeBSD 9, while I see ada3p1 in FreeBSD 8.2. gpart show ada3 lists this: =>34 3907029101 ada3 GPT (1.8T) 344062- free - (2.0M) 4096 3907025039 1 freebsd-zfs (1.8T) The drive in question is a WesternDigital Caviar Green WD (WD20EURS-63Z9B1 80.00A80> at scbus7 target 0 lun 0 (pass3,ada3)). Can someone explain what#s going on? The drive in question is one of the new 4k sized physical block devices. Why is FreeBSD 8 dealing with the HDD, FreeBSD 9 not? Any help at this point? Hope the volume is not lost. Thanks in advance, Oliver ___ 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: porting software to FreeBSD, what to do if Makefile lacks?
On 11/18/10 13:52, Rob Farmer wrote: 2010/11/18 O. Hartmann: Well, in this case, it would really be a 'nice to have', maybe this is worth a PR? Try asking on the ports@ list. I'm not sure what the criteria is for something being listed there - if something isn't going to be used by very many ports, it may not be worth adding, from a bloat point of view. I would say it is probably safe for your port to assume csh is /bin/csh, though. I'll do, thanks ;-) Oliver ___ 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: porting software to FreeBSD, what to do if Makefile lacks?
On 11/18/10 03:12, Rob Farmer wrote: On Wed, Nov 17, 2010 at 16:58, O. Hartmann wrote: Thanks. I got it. But it seems that my first porting task run into some difficulties for the advanced porters, since there is no autotool environment. By the way, the global environment variable ${CSH} seems to be noneexistent, instead ${SH} exists. Interesting - I assumed it would be listed in bsd.commands.mk, but it seems to not be. Most of the base system tools are. In any case, glad to hear you got it working. Well, in this case, it would really be a 'nice to have', maybe this is worth a PR? ___ 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: porting software to FreeBSD, what to do if Makefile lacks?
On 11/17/10 22:01, Rob Farmer wrote: 2010/11/17 O. Hartmann: Hello. I try to create a port of a software which does not have a Makefile and is build via a propriate csh script. Installation is done temporarely into some lib's and exe's subfolder withing the source folder, so I need to tell the top level Makefile of the port to use a specific build script instead implying having Makefile and a home-brewn install script, which takes the binaries and libs out of the temporary folders and install them at the proper places within the FreeBSD's tree. How can I perform these two tasks? You want to override the do-build target, something like: do-build: ${CSH} ${WRKSRC}/build-script.csh For the install, do the same with the do-install target. Unless your install script is particularly long or complicated, it will probably be best to put it right into the port's Makefile. Then you can use the INSTALL macros to ensure permissions are set correctly, binaries are stripped if the user doesn't specify WITH_DEBUG, etc. If you haven't already, check out the Porter's Handbook - it will familiarize you with important guidelines and covers a lot of common problems: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/ Thanks. I got it. But it seems that my first porting task run into some difficulties for the advanced porters, since there is no autotool environment. By the way, the global environment variable ${CSH} seems to be noneexistent, instead ${SH} exists. Regards, Oliver ___ 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"
porting software to FreeBSD, what to do if Makefile lacks?
Hello. I try to create a port of a software which does not have a Makefile and is build via a propriate csh script. Installation is done temporarely into some lib's and exe's subfolder withing the source folder, so I need to tell the top level Makefile of the port to use a specific build script instead implying having Makefile and a home-brewn install script, which takes the binaries and libs out of the temporary folders and install them at the proper places within the FreeBSD's tree. How can I perform these two tasks? Please set my CC, I'm not subscribing this list. Thanks in advance, Oliver ___ 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: FreeBSD-similar build-from-source Linux?
On 11/10/10 20:15, "C. Bergström" wrote: O. Hartmann wrote: The NVIDIA FreeBSD driver provides the cuda libraries for linux compatibilty. So 32-bit Linux Cuda applications should work on FreeBSD. There are some other, very serious questions. AMD calims that they made the specs of their 3D chipset internals public. The docs had big missing chunks which I tried to get clarification on and got some help and then it just one day stopped There is OpenCL as an open standard Try to find the validation test suite.. ($$$) , there is the CLANG/LLVM project even for FreeBSD Apple licenses it and doesn't publish all opencl work. (or I think may not even contribute to the opencl side at all anymore.. someone correct me) to become the new standard compiler and, not at last, there is work done on drivers for AMD graphics boards but there is no, not even rudimentary, support for GPGPU. I preferr a clean open source solution, but at the moment, it seems to be the best and easiest path to switch to an operating system that is fully supported, even 64 bit. Side question - Why care in the least bit about AMD? Their hw sucks and their software is a joke.. (if you bought Evergreen I'm sorry..) By the way - way is the hardware crap? Can you please be more specific? AMD claims to have a higher effective double precision throughput than nVidia, they also claim not having cut off most of their double precision capable facilities like nVidia even on their mass market products (but I'm not sure about that since this fact is very often hidden by intention). Their software doesn't really matter since I most FreeBSD users use the open source driver. Well, I never saw a working 64 bit capable driver on FreeBSD, that's right. Please do not understand this as a tricky question, I'm serious, since I plan to purchase new hardware for my computer at home (FreeBSD) and even for my lab's computer(s). And by the way, no, I havn't bought 'Evergreen', I have much more disappointing HD4830 and not properly working HD4770 and HD4670 ... (not GPGPU capable by design). There's no such thing as a complete open source GPGPU solution as of today (to the best of my knowledge) ./C ___ 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: FreeBSD-similar build-from-source Linux?
On 11/10/10 20:15, "C. Bergström" wrote: O. Hartmann wrote: The NVIDIA FreeBSD driver provides the cuda libraries for linux compatibilty. So 32-bit Linux Cuda applications should work on FreeBSD. There are some other, very serious questions. AMD calims that they made the specs of their 3D chipset internals public. The docs had big missing chunks which I tried to get clarification on and got some help and then it just one day stopped Well, speaking of those like me, following the official statements of the PR units of HW venodrs like AMD and others, did not realize this. I never read before about this sudden stop on any list. Yes, I realize sometimes that things, even the great HW venodrs claim, are not that what they claim to be when shdding light on this. But until this second I believed AMD opened their specs for the community. Well, maybe the trigger of opening the specs where a result of AMDs desastrous downfall after 2006, so today, after they got both feet on terra firma again, they may decide acting different ... There is OpenCL as an open standard Try to find the validation test suite.. ($$$) Your point, I must confess. , there is the CLANG/LLVM project even for FreeBSD Apple licenses it and doesn't publish all opencl work. (or I think may not even contribute to the opencl side at all anymore.. someone correct me) Isn't OpenCL maintained by the Khronos Group? Apple, for instance, develop their own stuff on the basis of OpenCL and LLVM, but they do not publish back to the community, that's right. But this shouldn't be an excuse for the lack of support. to become the new standard compiler and, not at last, there is work done on drivers for AMD graphics boards but there is no, not even rudimentary, support for GPGPU. I preferr a clean open source solution, but at the moment, it seems to be the best and easiest path to switch to an operating system that is fully supported, even 64 bit. Side question - Why care in the least bit about AMD? Their hw sucks and their software is a joke.. (if you bought Evergreen I'm sorry..) Well, look at my first statement. Until now I believe and believed AMD offered more than others of their 3D specs to the open source community, to provide support to real open source GPU drivers. Obviously this isn't true anymore. But why hasn't this been made public? AMD earns a lot of money even from those people like me which remain in the strong believing that they made their contribution to the open source OS community. But at the moment, looking at my hardware running FreeBSD, I realize that I have more and better running hardware based on nVidia and their BLOB than hardware based on AMD. But this is individual. There's no such thing as a complete open source GPGPU solution as of today (to the best of my knowledge) Well, not completely open source, but there is an nVidia CUDA solution even for 64 Bit Linux and none for FreeBSD! And as far as I know, I can use it for free - assuming I run a supported Linux. ./C Oliver ___ 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: FreeBSD-similar build-from-source Linux?
On 11/10/10 19:07, App Deb wrote: 2010/11/10 O. Hartmann: Hello out there, well, my question may sound heretic, but since we use mostly Linux based systems in our scientific environment and FreeBSD seems to lack in severe support in GPGPU/CUDA capable graphics boards I need to setup a kind of Linux facility to ensure having the software and tools I need for my work. I'm looking for a Linux distribution that is similar handled like FreeBSD, where I'm able to rebuild the whole system from sources, not even the the Linux kernel, also the GNU tools and the packages. Maybe there are some people out here having already taken this step. Any suggestion is appreciated, The NVIDIA FreeBSD driver provides the cuda libraries for linux compatibilty. So 32-bit Linux Cuda applications should work on FreeBSD. Well, 32-Bit isn't realistic in a scientific environment! There are some 'tricks' and 'tweaks' out making CUDA working on FreeBSD with Linux binaries, but, simply for instance, portions of our computing system rely on OpenLDAP and I do have severe problems making OpenLDAP authorised users available to some IDL applications running on FreeBSD boxes within the linuxulator. This is only one small but very effective trap one can step into. There are some other, very serious questions. AMD calims that they made the specs of their 3D chipset internals public. There is OpenCL as an open standard, there is the CLANG/LLVM project even for FreeBSD to become the new standard compiler and, not at last, there is work done on drivers for AMD graphics boards but there is no, not even rudimentary, support for GPGPU. I preferr a clean open source solution, but at the moment, it seems to be the best and easiest path to switch to an operating system that is fully supported, even 64 bit. ___ 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"