'svn up' problem on amd64
Hello, Advice? I have not seen this before: (685) @ 2:22:16 cd /usr/src (686) @ 2:22:18 svn up Updating '.': Skipped 'sys' -- Node remains in conflict At revision 241794. Summary of conflicts: Skipped paths: 1 (687) @ 2:22:43 - more background information: ZFS Subsystem ReportSun Oct 21 02:32:36 2012 System Information: Kernel Version: 901000 (osreldate) Hardware Platform: amd64 Processor Architecture: amd64 ZFS Storage pool Version: 28 ZFS Filesystem Version: 5 FreeBSD 9.1-RC2 #0 r241106: Mon Oct 1 18:26:44 UTC 2012 root 2:32AM up 4 days, 18:32, 7 users, load averages: 0.14, 0.10, 0.08 Darrel ___ 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: 'svn up' problem on amd64
On 21/10/2012 07:35, Darrel wrote: Advice? I have not seen this before: (685) @ 2:22:16 cd /usr/src (686) @ 2:22:18 svn up Updating '.': Skipped 'sys' -- Node remains in conflict At revision 241794. Summary of conflicts: Skipped paths: 1 (687) @ 2:22:43 For some reason svn thinks your local copy of sys conflicts with the copy from the repo. That could happen if you have local patches or similar, but svn would usually prompt you to merge any such. Also this seems to have affected people completely innocent of any such changes. Assuming you've checked out the stable/9 branch then I think this (untested) command should resolve the problems: # cd /usr/src # svn merge --accept theirs-full ^/stable/9 Use 'svn info' to see what the URL setting for your repo is -- you can just paste that in as is instead of '^/stable/9', or you can use the shorthand '^' which stands for the text from the 'Repository Root' setting plus the rest of the URL string. Note that the 'theirs-full' method of resolving conflicts will tend to wipe out any local changes you may have. If that is a concern, then you could try using the 'edit' method instead. (As the name suggests, this puts you in an editor showing the conflicting merge results, and requires you to edit things into what the result of the mmerge should have been.) Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: pppoe configuration and dns name resolution
Hi This time I configured as simple as possible with minimal settings, and voila things worked. I successfully connected to internet in both cases - DHCP server disabled in adsl modem, and DHCP server enabled in adsl modem. Thanks all of you guys for helping. :) Here are config files: ## /etc/rc.config hostname=jacks_lappy ifconfig_fxp0=DHCP # The below line is to be used if DHCP server on adsl # modem is disabled. #ifconfig_fxp0=inet 192.168.1.4 netmask 255.255.255.0 # This is assigned to telnet to adsl modem and configure it, # if you don't wanna communicate with modem, remove # this line. It doesn't affect ppp connectivity, in any way - # I tried removing it and got connected successfully. sshd_enable=YES moused_enable=YES powerd_enable=YES # Set dumpdev to AUTO to enable crash dumps, NO to disable dumpdev=AUTO hald_enable=YES dbus_enable=YES --- ## /etc/ppp/ppp.conf: default: set log Phase tun command adsl: set device PPPoE:fxp0 #MRU is optional too, you can remove it # w/o affecting ppp connectivity. set mru 1492 #set mtu 1492 # This was the cause of failure. # See man ppp for more info. # If MTU is set, ppp will not accept MRU values less than MTU. # e.g. MTU = 1492. Now if your ISP has MTU = 1460(my case), then # ppp on your PC, will not connect to ppp server at your ISP side. # So DO NOT set MTU explicitly. set authname myusername set authkey mypassword set dial set login add default HISADDR enable dns # a must, if DHCP server is enabled in adsl modem # and if you don't wanna edit /etc/resolv.conf # each time before connecting tp ISP's ppp server. #Now you don't need to touch /etc/resolv.conf - My /etc/resolv.conf is updated each time I start ppp, so I didn't needed to edit it. I simply started ppp via ppp -ddial adsl I also didn't start ppp at bootup, as it requires that your adsl modem must be powered on before FreeBSD begins booting, which is not the usual case for me. Also, as soon as I started ppp, an ip address is assigned to tun0 interface by ISP, while fxp0 was assigned its ip address via DHCP server enabled in adsl modem, even before I attempted to dial ppp. That is expected. I also tested this configuration with DHCP server disabled in adsl modem and it too worked successfully, except I need to chnage the line fxp0=DHCP to manually assigned ip address one, no other change was needed. The problem might be I was I trying to explcitly set MTU to be 1492, which ppp takes as minimum value - ie no MTU value less than 1492 is agreed upon by user ppp. My ISP's MTU was 1460, and since 1460 1492, so ppp was not agreeing upon MTU value and no connection was made. Thanks again all of you guys for sorting this out. :) Mean while I created a script to start and stop ppp service for a profile. This script is specifically written for csh/tcsh shell - the default one for FreeBSD, so some changes need to be made if it is to be run in other shells. Just go to c shell and type pppdo profilename start | stop where 'profilename' is the desired profilename defined in etc/ppp/ppp.conf, and either you 'start' ppp or 'stop' ppp. Here goes the script: pppdo.sh #!/bin/csh if ( $#argv != 2 ) then echo Usage: $0 ppp_profile start | stop exit endif switch ($2) case start: /usr/sbin/ppp -ddial $1 ; breaksw case stop: killall -INT ppp killall -HUP ppp ; breaksw default: echo $0 : Invalid Cmd ; breaksw endsw - NOTE: before executing this script make sure it is executable If not, type this at shell: chmod +x ./pppdo.sh After executing this script try pinging to a remote site to confirm connectivity, e.g. type this at shell: ping -c5 freebsd.org If you get 0.0% packet loss, then you made it! So, the only files that require modifications are /etc/ppp/ppp.conf and /etc/rc.conf No other file need to be modified to use user ppp, no matter whether DHCP server on your adsl modem is enabled or disabled, it doesn't matter - just use the configuration mention above. Then use the script as: ./pppdo adsl start to start the ppp profile named adsl(tun0 interface is created), and use ./pppdo adsl stop to stop the ppp. This will destroy the tun0 interface too. PS: The user account from which this script is to be run, must be a member of network group too, though network group need not to be the user's login group. This is the requirement of user ppp itself, and not of this script. Regards -- Jack ___
`pkg_add -r mongodb` failed
Hello. I have a problem with MongoDB installation: asus# pkg_add -r mongodb Fetching http://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9-stable/Latest/mongodb.tbz... Done. === Creating users and/or groups. Using existing group 'mongodb'. Creating user 'mongodb' with uid '922'. pw: user 'mongodb' already exists pkg_add: command 'if ! /usr/sbin/pw usershow mongodb /dev/null 21; then echo Creating user 'mongodb' with uid '922'.; /usr/sbin/pw useradd mongodb -u 922 -g 922 -c MongoDB pseudo-user -d /var/db/mongodb -s /bin/sh; else echo Using existing user 'mongodb'.; fi' failed # cat /etc/passwd | grep mongodb mongodb:*:922:922:MongoDB pseudo-user:/var/db/mongodb:/bin/sh # cat /etc/group | grep mongodb mongodb:*:922: # id mongodb id: mongodb: no such user # pw userdel mongodb pw: no such user `mongodb' # uname -a FreeBSD asus.home 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 01:47:53 UTC 2012 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 It seems that binary package is broken. -- Best regards, Alex Alexeev http://twitter.com/afiskon ___ 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: `pkg_add -r mongodb` failed
On 21/10/2012 12:45, Alexandr Alexeev wrote: Hello. I have a problem with MongoDB installation: asus# pkg_add -r mongodb Fetching http://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9-stable/Latest/mongodb.tbz... Done. === Creating users and/or groups. Using existing group 'mongodb'. Creating user 'mongodb' with uid '922'. pw: user 'mongodb' already exists pkg_add: command 'if ! /usr/sbin/pw usershow mongodb /dev/null 21; then echo Creating user 'mongodb' with uid '922'.; /usr/sbin/pw useradd mongodb -u 922 -g 922 -c MongoDB pseudo-user -d /var/db/mongodb -s /bin/sh; else echo Using existing user 'mongodb'.; fi' failed # cat /etc/passwd | grep mongodb mongodb:*:922:922:MongoDB pseudo-user:/var/db/mongodb:/bin/sh # cat /etc/group | grep mongodb mongodb:*:922: # id mongodb id: mongodb: no such user # pw userdel mongodb pw: no such user `mongodb' # uname -a FreeBSD asus.home 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 01:47:53 UTC 2012 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 It seems that binary package is broken. At a guess there are added user records in /etc/master.passwd which haven't been processed into /etc/pwd.db This will confuse applications trying to use pw(8). Try running: # pwd_mkdb -p /etc/master.passwd Now 'id mongodb' should acknowledge the existence of the mongodb account, and you should be able (re)install the mongodb pkg without it complaining so much. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: `pkg_add -r mongodb` failed
Thanks! BTW, MongoDB port has the same error: === Installing for mongodb-2.0.6_1 === Generating temporary packing list === Checking if databases/mongodb already installed === Creating users and/or groups. Using existing group `mongodb'. Creating user `mongodb' with uid `922'. pw: user 'mongodb' already exists *** Error code 74 Stop in /usr/ports/databases/mongodb. *** Error code 1 Stop in /usr/ports/databases/mongodb. === Installation of mongodb-2.0.6_1 (databases/mongodb) failed === Aborting update Terminated === You can restart from the point of failure with this command line: portmaster flags databases/mongodb How should one report errors in such cases? On Sun, Oct 21, 2012 at 4:04 PM, Matthew Seaman matt...@freebsd.org wrote: On 21/10/2012 12:45, Alexandr Alexeev wrote: Hello. I have a problem with MongoDB installation: asus# pkg_add -r mongodb Fetching http://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9-stable/Latest/mongodb.tbz... Done. === Creating users and/or groups. Using existing group 'mongodb'. Creating user 'mongodb' with uid '922'. pw: user 'mongodb' already exists pkg_add: command 'if ! /usr/sbin/pw usershow mongodb /dev/null 21; then echo Creating user 'mongodb' with uid '922'.; /usr/sbin/pw useradd mongodb -u 922 -g 922 -c MongoDB pseudo-user -d /var/db/mongodb -s /bin/sh; else echo Using existing user 'mongodb'.; fi' failed # cat /etc/passwd | grep mongodb mongodb:*:922:922:MongoDB pseudo-user:/var/db/mongodb:/bin/sh # cat /etc/group | grep mongodb mongodb:*:922: # id mongodb id: mongodb: no such user # pw userdel mongodb pw: no such user `mongodb' # uname -a FreeBSD asus.home 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 01:47:53 UTC 2012 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 It seems that binary package is broken. At a guess there are added user records in /etc/master.passwd which haven't been processed into /etc/pwd.db This will confuse applications trying to use pw(8). Try running: # pwd_mkdb -p /etc/master.passwd Now 'id mongodb' should acknowledge the existence of the mongodb account, and you should be able (re)install the mongodb pkg without it complaining so much. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey -- Best regards, Alex Alexeev http://twitter.com/afiskon ___ 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: `pkg_add -r mongodb` failed
On 21/10/2012 13:46, Alexandr Alexeev wrote: Thanks! BTW, MongoDB port has the same error: === Installing for mongodb-2.0.6_1 === Generating temporary packing list === Checking if databases/mongodb already installed === Creating users and/or groups. Using existing group `mongodb'. Creating user `mongodb' with uid `922'. pw: user 'mongodb' already exists *** Error code 74 Stop in /usr/ports/databases/mongodb. *** Error code 1 Stop in /usr/ports/databases/mongodb. === Installation of mongodb-2.0.6_1 (databases/mongodb) failed === Aborting update Terminated === You can restart from the point of failure with this command line: portmaster flags databases/mongodb How should one report errors in such cases? In this case, I'm afraid it looks very much as if the problem is local to your system, and nothing wrong with the port itself. As the databases/mongodb port uses the generic mechanisms for handling USERS and GROUPS it's likely that if there was a problem with the databases/mongodb port, then you'ld be seeing similar problems with any port that uses the same mechanism. There would be an excess of complaints from many users that would be hard to miss. No such complaining has been observed. In short: something is wrong in the password database on your system specifically, which is causing the installation of databases/mongodb to throw errors. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: 9.1 and gmirror with GPT?
On Sun, 21 Oct 2012, Lucas B. Cohen wrote: On 2012.10.20 20:17, free...@johnea.net wrote: Just wondering if 9.1 will bring any improvement to the situation of creating a full disk geom mirror while also using GPT partition table? I'm curious about what this is about. Could you refer me to an article or a discussion where this issue is described ? The GPT backup partition tables goes at the end of a disk, the same place gmirror(8) and other GEOM modules keep metadata. If GPT partitions are created inside a mirror, the backup GPT table is no longer at the end of the disk. Hiroki Sato created a patch which fixed the gptboot complaints, but there was concern about the nonstandard location of the backup table. At present, MBR partitioning is recommended with gmirror(8). ___ 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: Spam and more spam
On Sun, 21 Oct 2012, Erich Dollansky wrote: could t be that everybody can post now on this list without being registered and without having administrator's approval? It actually has been that way forever. There may be certain rules that trigger moderation in some cases, but usually not. The reason for the open list is that questions@ has been given as a support address in documents, and some feel that should remain open. Should we move to a list where only registered users can write just to avoid the spam problem and not forcing a human to approve all e-mails from addresses which are not registered? The forums are that way already: http://forums.freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.1 and gmirror with GPT?
On 10/21/2012 07:32 AM, Warren Block wrote: On Sun, 21 Oct 2012, Lucas B. Cohen wrote: On 2012.10.20 20:17, free...@johnea.net wrote: Just wondering if 9.1 will bring any improvement to the situation of creating a full disk geom mirror while also using GPT partition table? I'm curious about what this is about. Could you refer me to an article or a discussion where this issue is described ? The GPT backup partition tables goes at the end of a disk, the same place gmirror(8) and other GEOM modules keep metadata. If GPT partitions are created inside a mirror, the backup GPT table is no longer at the end of the disk. Hiroki Sato created a patch which fixed the gptboot complaints, but there was concern about the nonstandard location of the backup table. At present, MBR partitioning is recommended with gmirror(8). Thank you Warren. That sums it up. Lucas, I found this blag post informative: https://koitsu.wordpress.com/2012/09/18/using-freebsd-graid-geom-raid/ There are also several interesting posts on Michael Lucas' blag, such as: http://blather.michaelwlucas.com/archives/1071 This is a good discussion thread that dives into a specific configuration and the implications: http://freebsd.1045724.n5.nabble.com/disk-partitioning-with-gmirror-gpt-gjournal-RFC-td4912676.html I've tried to determine which came first GEOM or GPT. It seems GEOM is actually older, dating from FreeBSD 5, around 2003. While GPT seems to have been integrated with what is now known as UEFI in the later half of that decade. It also seems greedy of GPT to require both the first and last sectors of the disk. This seems to almost guarantee it will have issues with other low level disk formatting tools. Of course, given the history of the WinTel partnership, perhaps not interoperating with other tools was a design specification 8-) https://en.wikipedia.org/wiki/GUID_Partition_Table In any case, the upcoming wide spread use of UEFI/GPT (i.e. windoze on commodity PCs) compared to the FreeBSD specific nature of GEOM, pretty much insures that it will have to be GEOM that changes to accommodate this conflict. Even given the denial of who is David and who is Goliath, in the fact that the GEOM developers don't seem to consider this their bug: http://www.freebsd.org/cgi/query-pr.cgi?pr=162147 It seems inevitable that the FreeBSD devs will have to capitulate and find another way to store the GEOM meta-data or we're going to loose the great benefits of whole disk mirrors under GEOM. [please proceed with tongue in cheek] This may not occur any time soon, as time progresses at a different rate for BSD than it does with the rest of the world. A great example is this sentence from the Architecture Handbook: The Universal Serial Bus (USB) is a new way of attaching devices to personal computers. Of course USB is roughly 20 years old now 8-) There are some other great quotes regarding the new computer input device, called the mouse. [safe to freely operate tongue again] In any case, it seems my new 9.1-RC2 installation will be MBR partitioned with whole disk GEOM mirror. This motherboard is BIOS based, not UEFI. It's become fairly de rigueur to accommodate the 4K sector size disks with fdisk and MBR partitioning. As we propel forward into SSDs this may not stay the case. Any other comments or caveats are very greatly appreciated... johnea ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
how many memory is needed for FreeBSD 9 ?
Hi, I'm updating an old laptop running FreeBSD 8.1 with 64 MB ram (44MB available) but now FreeBSD 9.1 panics at boot time: panic: kmem_malloc(4194304): kmem_map too small: 24584192 allocated? Any work-around? Thanks regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how many memory is needed for FreeBSD 9 ?
On Sun 2012-10-21 18:21:59 UTC+0200, Patrick Lamaiziere (patf...@davenulle.org) wrote: I'm updating an old laptop running FreeBSD 8.1 with 64 MB ram (44MB available) but now FreeBSD 9.1 panics at boot time: panic: kmem_malloc(4194304): kmem_map too small: 24584192 allocated? That's one very old laptop. I think you'll need to install more memory or downgrade FreeBSD to an earlier version. 9.1-RELEASE isn't available yet, only 9.1-RC1 RC2. Given it's prerelease code it's plausible the 9.1-RC2 kernel requires more memory at boot than 9.1-REL will. Attempting to boot 9.0-REL from CD on your laptop should answer that question. From my limited testing under VirtualBox, 96 MB RAM is about the lower limit that will allow FreeBSD 9.1-RC2 to boot before the swap partition is enabled. Any less and the kernel will freeze or panic at boot. This was with the amd64 version though, not i386. ___ 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
pkgng and the old pkg_* programs
Now that portmaster officially supports pkgng I've converted to using it. Is there any reason to keep the old pkg_* programs around, or can I delete them and add WITHOUT_PKGTOOLS to my /etc/src.conf? I'm running RELEASE-9.0 on amd64 and will update to REL-9.1 as soon as it arrives if that matters. ___ 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: i3 window manager 4.3 Build error on FreeBSD
On 19/10/2012 01:24, Rod Person wrote: Hello, I'm trying to build the latest version of i3 on FreeBSD since the port has not been updated yet, and I get the following error when building. [i3] YACC src/cfgparse.y [i3] CC src/cfgparse.tab.c [i3] LEX src/cfgparse.l flex: can't open src/cfgparse.yy.c gmake: *** [src/cfgparse.yy.c] Error 1 I have flex 2.5.37 bison 2.5.1 installed from ports. If this is not the FreeBSD port ask i3 team. -- David Demelier ___ 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: pkgng and the old pkg_* programs
On 21/10/2012 18:10, Arthur Chance wrote: Now that portmaster officially supports pkgng I've converted to using it. Is there any reason to keep the old pkg_* programs around, or can I delete them and add WITHOUT_PKGTOOLS to my /etc/src.conf? I'm running RELEASE-9.0 on amd64 and will update to REL-9.1 as soon as it arrives if that matters. There is no particularly good reason to keep pkg_tools around once you've made the switch to pkgng. pkgng should provide replacements for all the pkg_tool functionality and slot into its place quite smoothly. However, I'm not sure that there's been adequate testing on a pkg_tools-free setup, so it is not entirely outside the bounds of possibility that you might run into some odd problems. If you do, please report what happens, as that's definitely a bug that needs fixing. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: i3 window manager 4.3 Build error on FreeBSD
On Sun, 21 Oct 2012 19:35:59 +0200 David Demelier demelier.da...@gmail.com wrote: On 19/10/2012 01:24, Rod Person wrote: Hello, I'm trying to build the latest version of i3 on FreeBSD since the port has not been updated yet, and I get the following error when building. [i3] YACC src/cfgparse.y [i3] CC src/cfgparse.tab.c [i3] LEX src/cfgparse.l flex: can't open src/cfgparse.yy.c gmake: *** [src/cfgparse.yy.c] Error 1 I have flex 2.5.37 bison 2.5.1 installed from ports. If this is not the FreeBSD port ask i3 team. I did...being FreeBSD specific they sent me here. Either way, someone else helped me out. -- Rod Person http://www.rodperson.com First we got population. The world today has 6.8 billion people. That's headed up to about 9 billion. Now if we do a really great job on new vaccines, health care, reproductive health services, we lower that by perhaps 10 or 15 percent. - Bill Gates ___ 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: i3 window manager 4.3 Build error on FreeBSD
On 21/10/2012 19:51, Rod Person wrote: On Sun, 21 Oct 2012 19:35:59 +0200 David Demelier demelier.da...@gmail.com wrote: On 19/10/2012 01:24, Rod Person wrote: Hello, I'm trying to build the latest version of i3 on FreeBSD since the port has not been updated yet, and I get the following error when building. [i3] YACC src/cfgparse.y [i3] CC src/cfgparse.tab.c [i3] LEX src/cfgparse.l flex: can't open src/cfgparse.yy.c gmake: *** [src/cfgparse.yy.c] Error 1 I have flex 2.5.37 bison 2.5.1 installed from ports. If this is not the FreeBSD port ask i3 team. I did...being FreeBSD specific they sent me here. Either way, someone else helped me out. Tell us how it can help someone else :) -- David Demelier ___ 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
Fw: i3 window manager 4.3 Build error on FreeBSD
Sorry, I thought the list was included by the responder Begin forwarded message: Date: Fri, 19 Oct 2012 23:05:01 +0200 From: Herbert J. Skuhra hsku...@eumx.net To: Rod Person rodper...@rodperson.com Cc: d...@freebsd.org Subject: Re: i3 window manager 4.3 Build error on FreeBSD On Thu, 18 Oct 2012 19:24:43 -0400 Rod Person rodper...@rodperson.com wrote: Hello, I'm trying to build the latest version of i3 on FreeBSD since the port has not been updated yet, and I get the following error when building. [i3] YACC src/cfgparse.y [i3] CC src/cfgparse.tab.c [i3] LEX src/cfgparse.l flex: can't open src/cfgparse.yy.c gmake: *** [src/cfgparse.yy.c] Error 1 The commands that fail are: flex -i -o src/cfgparse.yy.c ../i3-4.3/src/cfgparse.l flex -i -o i3-config-wizard/cfgparse.yy.c i3-config-wizard/cfgparse.l The below commands work: flex -i -osrc/cfgparse.yy.c ../i3-4.3/src/cfgparse.l flex -i -oi3-config-wizard/cfgparse.yy.c i3-config-wizard/cfgparse.l So making the port to build is very simple. You can try my patch: http://oslo.ath.cx/i3-wm_4_3.diff I've cc'ed the port maintainer. Regards, Herbert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how many memory is needed for FreeBSD 9 ?
On 21 October 2012 12:49, andrew clarke m...@ozzmosis.com wrote: On Sun 2012-10-21 18:21:59 UTC+0200, Patrick Lamaiziere (patf...@davenulle.org) wrote: I'm updating an old laptop running FreeBSD 8.1 with 64 MB ram (44MB available) but now FreeBSD 9.1 panics at boot time: panic: kmem_malloc(4194304): kmem_map too small: 24584192 allocated? That's one very old laptop. I think you'll need to install more memory or downgrade FreeBSD to an earlier version. 9.1-RELEASE isn't available yet, only 9.1-RC1 RC2. Given it's prerelease code it's plausible the 9.1-RC2 kernel requires more memory at boot than 9.1-REL will. Attempting to boot 9.0-REL from CD on your laptop should answer that question. From my limited testing under VirtualBox, 96 MB RAM is about the lower limit that will allow FreeBSD 9.1-RC2 to boot before the swap partition is enabled. Any less and the kernel will freeze or panic at boot. This was with the amd64 version though, not i386. Keep in mind that the installer will take some memory on top of what is needed to boot FreeBSD. -- -- ___ 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
Question regarding a server with an unsupported old version
Hello to all, My name is Rei Okamoto posting from Japan. I'm very new to FreeBSD and please pardon and caution me if anything I post is in any way inappropriate. Here's a problem I'm facing right now. I started working for a company this month as a sole engineerer, given all my tasks with virtually no manuals other than IP addresses, IDs and PWs. (Dangerous, but not such a rare case in this country) One of the clients is running the web site using FreeBSD 4.7. Although it is surely the best to renew the server to newest machine and OS, the client is reluctant to do so because of money. So a long story short, because I need to do some testing, I've installed FreeBSD 4.11 to the VirtualBox as a test server in my local PC and got the network connected. I want to build the test server as close to the actual server as possible, such as considering the OS's version 4.11 to be close enough to 4.7, but as I try to install PHP4 with a following command, pkg_add -r php4-4.3.6.tgz I get an error message below. Error: FTP Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-4.11-release/Latest/php4-4.3.6.tgz: File unavailable (e.g., file not found, no access) So you probably can figure out the rest of the story, it is all too old to make a near duplication of the server. Is there any suggestion on what I can do other than convincing the client to renew the server? (which I am doing but already been politely refused) Pardon me for the long message, and thank you in advance for all replies. Thank you, Rei Okamoto ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
How to list /etc/fstab in new BFSD label?
Aloha, I cant find any How TO on writing the hardware devices into /etc/fstab to mount and find how the DVD and CD players get connected. (This happens to be with a test box FreeBSD 10.* which has worked fine other than that.) The BSD install I understand is also for FreeBSD 9.* as well. fd0, /floppy, acd0 /cdrom, acd1 DVD, do not come up although they are in /dmesg list. Any help would be appreciated. ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 7.2 - 8.0 - 9* + email: n...@hdk5.net All that's really worth doing is what we do for others.- Lewis Carrol ___ 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: Question regarding a server with an unsupported old version
Hi, On Mon, 22 Oct 2012 11:31:36 +0900 Rei Okamoto okam...@mix-net.co.jp wrote: One of the clients is running the web site using FreeBSD 4.7. this is not a real fresh installation. Although it is surely the best to renew the server to newest machine and OS, the client is reluctant to do so because of money. There is still the option to use a supported version of FreeBSD. You can have a try with 7.4. Some hardware support was taken out with 8. But if 8 works, take 8.3. as I try to install PHP4 with a following command, I doubt that you will get this anywhere anymore. Is there any suggestion on what I can do other than convincing the client to renew the server? (which I am doing but already been politely refused) Just try a newer FreeBSD version. 7.4 is currently still supported. Of course, it also could be that 9.1 is running on this hardware. This would be perfect. But I do not know if you can get the client's web sites running on a current PHP version. Erich ___ 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: Question regarding a server with an unsupported old version
Dear Rei, One of the clients is running the web site using FreeBSD 4.7. [...] pkg_add -r php4-4.3.6.tgz I get an error message below. Error: FTP Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-4.11-release/Latest/php4-4.3.6.tgz: File unavailable (e.g., file not found, no access) I believe that PHP4 (and most of the ports used in the server of your client) are not supported anymore. You would be able to download it from somewhere, there must exist archives, but you'd have to build everything by hand. Is there any suggestion on what I can do other than convincing the client to renew the server? (which I am doing but already been politely refused) 1) build a new system, with new Apache, new PHP, etc. and port the web site of your client to the new system. Let the client test and approve it, an install that on his old hardware. 2) get your boss approve the fact that the server of the client is ou of date and cannot be maintened anymore. Then you charge the client for colocation (electricity and internet) but the client is responsible for the maintenance. Best regards, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Question regarding a server with an unsupported old version
On Sun, Oct 21, 2012 at 9:31 PM, Rei Okamoto okam...@mix-net.co.jp wrote: Hello to all, My name is Rei Okamoto posting from Japan. I'm very new to FreeBSD and please pardon and caution me if anything I post is in any way inappropriate. Here's a problem I'm facing right now. I started working for a company this month as a sole engineerer, given all my tasks with virtually no manuals other than IP addresses, IDs and PWs. (Dangerous, but not such a rare case in this country) One of the clients is running the web site using FreeBSD 4.7. Although it is surely the best to renew the server to newest machine and OS, the client is reluctant to do so because of money. So a long story short, because I need to do some testing, I've installed FreeBSD 4.11 to the VirtualBox as a test server in my local PC and got the network connected. I want to build the test server as close to the actual server as possible, such as considering the OS's version 4.11 to be close enough to 4.7, but as I try to install PHP4 with a following command, pkg_add -r php4-4.3.6.tgz I get an error message below. Error: FTP Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-4.11-release/Latest/php4-4.3.6.tgz: File unavailable (e.g., file not found, no access) So you probably can figure out the rest of the story, it is all too old to make a near duplication of the server. Is there any suggestion on what I can do other than convincing the client to renew the server? (which I am doing but already been politely refused) Pardon me for the long message, and thank you in advance for all replies. You can find an archive of packages released with FreeBSD 4.11 here: ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old-releases/i386/4.11-RELEASE/packages/All/ However, you'll find the packages are different than those released with your original version. A move from 4.7 to 4.11 doesn't really gain you much. Better off to start a migration strategy or leave it alone. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
HI
Hi, We were just reviewing your website and found it very interesting. I really like your website and services you are providing. As you know that smartphones market is continuously growing and thousands of mobile applications download every day. So, I was wondering that if you would also like to develop a smartphone app for your company or for your client. I would like to offer you our Custom Mobile Application Service. We can develop various type of Mobile application for multiple platforms like iPhone/iPad and Android as per your requirement. So, if you have any idea/concept to develop a mobile application then we can definitely help you to develop the same. Please review our website to more about us and our services. http://www.moopli.com/ We, Moopli are a Mobile Application division of Narola Infotech. We provide mobile application development services to develop Multimedia Applications, Communication Applications, Business Applications, Finance Applications and Web Service Based Applications. Our Strengths: - 7 years of successful operations - 68 team members - Technology/Process maturity - 500+ satisfied clients Our Skilled Team: - 56 Experienced Programmers/Developers - 6 Business Analyst - 2 Project Manager - 4 Graphic Designers Our Technology Expertise: iOS SDK (iPhone/iPad), Android SDK , PHP, ASP .NET (2.0, 3.5), and expert in their related CMS and frameworks. See our Team at work: http://www.narolainfotech.com/video-narola-infotech.html Let me know your views and we can discuss further on this. I would be happy to share our past work details with you. I look forward to your positive reply!!! Regards, A.Butani Moopli.com | Mobile Application Division of Narola Infotech Note: - Though this is not an automated email, we keep on sending out these emails to all those people whom we find eligible of using our services. To unsubscribe from future mails (i.e., to ensure that we do not contact you again for this matter), please reply NO. ___ 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
Strange I/O problem on Freenas 0.7.2
Hi all. I'm having a very weird problem with a friends Freenas set-up. I'm trying to backup his data before migrating to nas4free or just plain FreeBSD. The setup is as follows: HP Microserver N36. 2BG Mem (1713 MB Usable) (no swap) 4 x 2000GB (ST2000DL003-9VT166 Seagate) drives in a graid5 setup. Initially he had no problems with the setup. Samba share was fine and he populated the raid set with 3TB of data, but somewhere along the line the disk I/O went VERY slow. I initially thought this might be raid related and did some tests but actually found the problem to be on the discs. [root@freenas ~]# diskinfo -c /dev/ad4 /dev/ad4 512 # sectorsize 2000398934016 # mediasize in bytes (1.8T) 3907029168 # mediasize in sectors 3876021 # Cylinders according to firmware. 16 # Heads according to firmware. 63 # Sectors according to firmware. ad:5YD2VEWQ # Disk ident. I/O command overhead: time to read 10MB block 0.250736 sec =0.012 msec/sector time to read 20480 sectors 79.653738 sec =3.889 msec/sector calculated command overhead =3.877 msec/sector [root@freenas ~]# diskinfo -t /dev/ad4 /dev/ad4 512 # sectorsize 2000398934016 # mediasize in bytes (1.8T) 3907029168 # mediasize in sectors 3876021 # Cylinders according to firmware. 16 # Heads according to firmware. 63 # Sectors according to firmware. ad:5YD2VEWQ # Disk ident. Seek times: Full stroke: 250 iter in 124.649884 sec = 498.600 msec Half stroke: 250 iter in 52.112172 sec = 208.449 msec Quarter stroke: 500 iter in 167.991252 sec = 335.983 msec Short forward:400 iter in 72.027133 sec = 180.068 msec Short backward: 400 iter in 150.708625 sec = 376.772 msec Seq outer: 2048 iter in 5.748059 sec =2.807 msec Seq inner: 2048 iter in 119.395823 sec = 58.299 msec Transfer rates: outside: 102400 kbytes in 39.207296 sec = 2612 kbytes/sec middle:102400 kbytes in 113.757181 sec = 900 kbytes/sec inside:102400 kbytes in 153.438159 sec = 667 kbytes/sec S.M.A.R.T. is not reporting any issues either and the speeds are similar on all the drives. No errors in /var/log either. Any help or suggestions would be appreciated. Regards Henti ___ 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