Re: Recommended working IDE
On Sat, Nov 19, 2011 at 12:51:18PM +1100, John Tate wrote: Misc, I've had troubles with eclipse and anjuta. Eclipse does not want to run, anjuta seems to be missing it's symbol browser in anjuta-extras. Anjuta actually works, but when I open a project it gives me an error. I've already posted what it is, so search. Is there an IDE that works? What is it? Perhaps I should just learn emacs. Though, I really like anjuta. Are there any IDE recommendations apart anjuta, eclipse, and vim and emacs editors available? As I said, i'll look at the anjuta issue within the next 48h. Meanwhile you can have a look at codeblocks. -- Antoine
Goi Quoc Te Chat Luong Cao - Dung Thu Mien Phi
ifonemobi.com Da; CH Va;$ DIa;N THOa: I QUa;C Ta: CHa:$T LF/a;NG CAO - HiC*L#n nay nhu cCLu goL#i DiC*L#n thoaL#i Di quC4Lc tC*L Dang laL nhu cCLu khaL phC4LbiC*Ln DC*L liC*n hC*L# vF!Li ngF0F!Li thCn, baL#n beL, DC4Li taLc trC*n thC*L giF!Li vF!Li chi phiL nhF0 cF0F!Lc nC4L#i haL#t. - DDL#c trF0ng cuLa Ifonemobi.com: LC da; ch va;% Dia;n thoa:!i qua;c ta:? cha:%t lF0a;#ng cao, cC3 tha; dC9ng ga; i trC*n mC!y tCnh, ga; i trC*n di Da;ng Smart Phone bao ga;m nhia;u ha; Dia;u hC nh khC!ch nhau - iOS - Android - Noikia - Windowsphone ( cC!c Dia;n thoa:!i pha; bia:?n nhF0 IPhone - IPad I, II, Samsung Galaxy, Nexus Prime - E71 - HTC), cC!c da; ch va;% nC y da;1a trC*n na;n net, cho cha:%t lF0a;#ng ta;t nha:%t va;i cF0a;c phC tha:%p nha:%t. - VC o pha:'n DDng kC= DC*L DDng kyL mC4L#t taLi khoaL n, taL i chF0F!ng triLnh vC*L maLy tiLnh, di DC4L#ng DC*L goL#i, ca:#m nha:n cha:%t lF0a;#ng trF0a;c khi tia:?n hC nh mua tha:;. Va;i cha:%t lF0a;#ng 3G - Wifi hia;n ta:!i ba:!n cC3 tha; ca:#m nha:n cha:%t lF0a;#ng vC tCnh tia;n da;%ng ca;'a da; ch va;% - cC3 tha; ga; i qua;c ta:? cF0a;c ra:; hF!n na;i ha:!t a; ba:%t ka;3 na;i DCu, khC4ng nha:%t thia:?t pha:#i nga;i trF0a;c mC!y tCnh ma;i cC3 tha; ga; i qua;c ta:?. Ta:I PHa:N Ma;M Ta:#i trC*n mC!y tCnh Ta:#i trC*n Di Da;ng XEM THC M GIC CF/a;C Ta:$T Ca: CCC QUa;C GIA NgoC i ra Da; xem vC bia:?t thC*m thC4ng tin chi tia:?t va; cC!ch tha;)c DDng kC= ga; i tha; - hF0a;ng da:+n chi tia:?t - hF0a;ng da:+n mua tha:; = QuC= khC!ch vui lC2ng truy ca:p website ca;'a chC:ng tC4i : www.ifonemobi.com hoDL#c website cuL a caLc DaL#i lyL: www.uvoiz.com ( liC*n ha;: Mr Sa; 0908 366 110) www.okvoiz.vn ( liC*n ha;: Mr HF0ng 0919 15 15 16) www.cavoiz.com (liC*n ha;: Mr HF0ng 0919 15 15 16) Na:?u quC= khC!ch hC ng khC4ng mua;n nha:n mail nC y (UNSUBSCRIBE) ,xin vui lC2ng click vC o DCy ! [IMAGE][IMAGE]
Re: How to destroy softraid partition
On 18.11.2011 P3. 15:50 Q., Nigel Taylor wrote: On 11/18/11 13:29, Ivo Chutkin wrote: Hi all, How can I destroy softraid partition on disk? I was playing with sofraid, now I want to install fresh copy on same disk. When I try to delete raid partition disklebel reports: disklebel: ioctl DIOCWDINFO: Open partition would move or shrink disklebel: unable to write lebel How can I delete this partition? It is snapshot from 16.11.2011. I am not able to extract dmesg, it is HP microserver with no com port. Thanks for the help, Ivo Hi, I recently hit the same problem, when trying to change a partition. I booted using bsd.rd then I could do what I wanted with disklabel. Nigel Hi guys, Unfortunately both solutions does not help. I booted bsd.rd and disklabel reports the same errors. If I issue bioctl -d sd2 (which is the softraid disk made from sd0 and sd2) it does not find it. In dmesg there is sd2 and softraid on it. Any suggestions? Thanks for the help, Ivo
Re: Recommended working IDE
* John Tate j...@johntate.org [2011-11-19 12:51+1100]: Is there an IDE that works? What is it? nvi, ksh.
Re: gkrellm and uuid's for filesystems
* John Tate j...@johntate.org [2011-11-19 11:46+1100]: Also, where do I get started on learning to make ports? http://openbsd.org/faq/ports/index.html. I have a hard time understanding you were unable to find docs on this.
Re: How to destroy softraid partition
On 11/19/11 07:07, Ivo Chutkin wrote: ... Hi guys, Unfortunately both solutions does not help. I booted bsd.rd and disklabel reports the same errors. If I issue bioctl -d sd2 (which is the softraid disk made from sd0 and sd2) it does not find it. In dmesg there is sd2 and softraid on it. Any suggestions? Thanks for the help, Ivo dd zeros over the first few MB of each softraid host partitions (use the 'rsdX' devices), reboot. Softraid? There ain't no softraid here! Probably killing a fly with a rapid-action shotgun, but should work. Unfortunately, your reports are almost completely devoid of hard info, so its entirely possible you are doing things wrong. Nick.
Re : OpenBSD ipsec gateway behind a router
MJ LAN1 (192.168.10.0/24) -- OpenBSD .99 -- .254 Router IPx -- Internet -- IPy IPSec_GW (Vendor) -- LAN2 (192.168.20.0/24) MJ As you can see the OpenBSD 4.9 server sits on the LAN1 and has one physical interface. MJ When it wants to access to the internet, its address 192.168.10.99 is natted in IPx and that's how the IPSec_GW(Vendor) sees the source packets. I would recommend to get a computer with 2 network interfaces. Otherwise it's going to be very complicated at best. /24 (on the left) is for sure not going to work. Hello Boris, I just wanted to give you a feedback about this configuration. It works. I'm able to ping a machine on LAN2 from LAN1. The OpenBSD ipsec gateway has only one physical interface. I haven't done anything special to make it work except adding a specific route on my LAN1 computer to LAN2 with NH OpenBSD .99 and enable net.inet.ip.forwarding
makewhatis on /usr
Hi, From weekly output : Rebuilding whatis databases: /usr/libexec/makewhatis: Can't create /usr/share/man/whatis.db: Read-only file system Should not whatis.db be in /var/... ? From hier(7) : /usr/ Contains the majority of user utilities and applications. share/Architecture independent data files. man/ Manual pages. Is it really a manual page ?
Re: makewhatis on /usr
Thomas de Grivel tho...@lowh.net writes: Hi, From weekly output : Rebuilding whatis databases: /usr/libexec/makewhatis: Can't create /usr/share/man/whatis.db: Read-only file system Should not whatis.db be in /var/... ? From hier(7) : /usr/ Contains the majority of user utilities and applications. share/Architecture independent data files. man/ Manual pages. Is it really a manual page ? Shouldn't the index of manual pages be with the manual pages? -- http://www.wistly.net
Re: makewhatis on /usr
On 11/19/11 15:40, Carson Chittom wrote: Thomas de Griveltho...@lowh.net writes: Hi, From weekly output : Rebuilding whatis databases: /usr/libexec/makewhatis: Can't create /usr/share/man/whatis.db: Read-only file system Should not whatis.db be in /var/... ? From hier(7) : /usr/ Contains the majority of user utilities and applications. share/Architecture independent data files. man/ Manual pages. Is it really a manual page ? Shouldn't the index of manual pages be with the manual pages? Yeah and let's put the reader there too ?
Re: makewhatis on /usr
On Sat, Nov 19, 2011, Carson Chittom wrote: Thomas de Grivel tho...@lowh.net writes: Hi, From weekly output : Rebuilding whatis databases: /usr/libexec/makewhatis: Can't create /usr/share/man/whatis.db: Read-only file system Should not whatis.db be in /var/... ? From hier(7) : /usr/ Contains the majority of user utilities and applications. share/Architecture independent data files. man/ Manual pages. Is it really a manual page ? Shouldn't the index of manual pages be with the manual pages? Should /etc/passwd be stored in /home instead? I think a readonly (or NFS shared) /usr is supposed to work, so anything that's regularly written should be in /var. That's what /var is for, after all.
Re: makewhatis on /usr
Hi Thomas, Thomas de Grivel wrote on Sat, Nov 19, 2011 at 03:32:03PM +0100: From weekly output : Rebuilding whatis databases: /usr/libexec/makewhatis: Can't create /usr/share/man/whatis.db: Read-only file system Should not whatis.db be in /var/... ? I think you have a point. Specifically, /var/db/man/. Having cron(8) scripts write to /usr is ugly. I don't see why mounting /usr readonly should require disabling makewhatis(8). Right now, Kristaps and myself are rewriting makewhatis(8) and apropos(1) anyway, the databases will be renamed from whatis.db to mandoc.db and mandoc.index, and their format will be completely different, using db(3) instead of plain text. That might be a good time to move variable content out of /usr. At the apropriate time, i'll bring this up among developers. Please be patient for a few months, but remind me when you see a commit to src/etc/weekly or src/usr.sbin/pkg_add enabling mandocdb(8), but nothing happened regarding the placement of mandoc databases before that. Regarding the latter, watch out for commits to src/usr.bin/mandoc/mandocdb.h, where the paths used by mandocdb(8) and apropos(1) are defined; or, in case we redesign that, to src/usr.bin/mandoc/mandocdb.c and src/usr.bin/mandoc/apropos_db.c, where these paths are used. I'm not going to move whatis.db files around at this point. They are close to retirement, anyway. Thanks for bringing this up, Ingo
Re: test(1)
On Fri, Nov 18, 2011 at 11:04:12PM -0700, Barry Grumbine wrote: man [ used to give me the test(1) manpage, doesn't anymore. Is that something that needs fixin'? something weird, right enough. the man page is still installed (/usr/share/man/man1/[.1), but man(1) does not pick it up. ingo, could this be anything to do with the code that determines whether pages exist pre-formatted or not, and try to display the more recent of the two? jmc
Re: makewhatis on /usr
On Sat, Nov 19, 2011 at 04:31:57PM +0100, Ingo Schwarze wrote: Hi Thomas, Thomas de Grivel wrote on Sat, Nov 19, 2011 at 03:32:03PM +0100: From weekly output : Rebuilding whatis databases: /usr/libexec/makewhatis: Can't create /usr/share/man/whatis.db: Read-only file system Should not whatis.db be in /var/... ? I think you have a point. Specifically, /var/db/man/. Having cron(8) scripts write to /usr is ugly. I don't see why mounting /usr readonly should require disabling makewhatis(8). I disagree: manpage directories are self-contained. If I add or remove a directory to my man configuration, it shouldn't require a rebuild of the database for other directories. Hence having a whatis.db per-man directory root. If you want to move those to /var/db/man or something, you'd better be prepared to have database file names that depend on the root directory being used.
Re: makewhatis on /usr
On Sat, Nov 19, 2011 at 10:14:44AM -0500, Ted Unangst wrote: On Sat, Nov 19, 2011, Carson Chittom wrote: Thomas de Grivel tho...@lowh.net writes: Hi, From weekly output : Rebuilding whatis databases: /usr/libexec/makewhatis: Can't create /usr/share/man/whatis.db: Read-only file system Should not whatis.db be in /var/... ? From hier(7) : /usr/ Contains the majority of user utilities and applications. share/Architecture independent data files. man/ Manual pages. Is it really a manual page ? Shouldn't the index of manual pages be with the manual pages? Should /etc/passwd be stored in /home instead? I think a readonly (or NFS shared) /usr is supposed to work, so anything that's regularly written should be in /var. That's what /var is for, after all. Under normal circumstances, /usr/share/man/whatis.db is NOT written to: makewhatis(8) does not even try to write the file if it didn't change. That particular problem only triggers after you upgrade your system if /usr is mounted read-only. That's one reason it's done at the end of make build: once you're done, you can remount /usr read-only.
Re: makewhatis on /usr
Hi Marc, Marc Espie wrote on Sat, Nov 19, 2011 at 05:40:38PM +0100: On Sat, Nov 19, 2011 at 04:31:57PM +0100, Ingo Schwarze wrote: Thomas de Grivel wrote on Sat, Nov 19, 2011 at 03:32:03PM +0100: From weekly output : Rebuilding whatis databases: /usr/libexec/makewhatis: Can't create /usr/share/man/whatis.db: Read-only file system Should not whatis.db be in /var/... ? I think you have a point. Specifically, /var/db/man/. Having cron(8) scripts write to /usr is ugly. I don't see why mounting /usr readonly should require disabling makewhatis(8). I disagree: manpage directories are self-contained. If I add or remove a directory to my man configuration, it shouldn't require a rebuild of the database for other directories. Hence having a whatis.db per-man directory root. If you want to move those to /var/db/man or something, you'd better be prepared to have database file names that depend on the root directory being used. I fully agree with all that, and having per-hierarchy databases in /var/db/man - one for /usr/share/man, one for /usr/X11R6/man, one for /usr/local/man, one for each additional directory the user configures in man.conf(5) - is indeed what i hope to do. Yours, Ingo
Re: makewhatis on /usr
On Sat, 19 Nov 2011 18:05:42 +0100, Ingo Schwarze wrote: Hi Marc, Marc Espie wrote on Sat, Nov 19, 2011 at 05:40:38PM +0100: On Sat, Nov 19, 2011 at 04:31:57PM +0100, Ingo Schwarze wrote: Thomas de Grivel wrote on Sat, Nov 19, 2011 at 03:32:03PM +0100: From weekly output : Rebuilding whatis databases: /usr/libexec/makewhatis: Can't create /usr/share/man/whatis.db: Read-only file system Should not whatis.db be in /var/... ? I think you have a point. Specifically, /var/db/man/. Having cron(8) scripts write to /usr is ugly. I don't see why mounting /usr readonly should require disabling makewhatis(8). I disagree: manpage directories are self-contained. If I add or remove a directory to my man configuration, it shouldn't require a rebuild of the database for other directories. Hence having a whatis.db per-man directory root. If you want to move those to /var/db/man or something, you'd better be prepared to have database file names that depend on the root directory being used. I fully agree with all that, and having per-hierarchy databases in /var/db/man - one for /usr/share/man, one for /usr/X11R6/man, one for /usr/local/man, one for each additional directory the user configures in man.conf(5) - is indeed what i hope to do. I think what Marc meant is that whatis.db/mandoc.db should be in the same directory as their corresponding manpages. And I agree on that point, especially in the case of NFS-mounted /usr: One shouldn't have to run mandocdb to be able to run apropos(1) for the pages on the remote machine. And even worse, what happens if the remote machine is updated or packages are added? The client in such a setup will have an outdated database without being aware of it. mandoc.db should be in the same directory as the manpages it was generated from, and need not be writable by machines that don't have write access to the pages themselves. With respect to the weekly makewhatis, I think that's a bug in the weekly(8) script: It should not blindly assume that every database listed in man.conf(5) is on a writable filesystem.
Re: test(1)
Hi, Barry Grumbine wrote on Fri, Nov 18, 2011 at 11:04:12PM -0700: man [ used to give me the test(1) manpage, doesn't anymore. Is that something that needs fixin'? i have moved this thread to tech@, sending a patch. Look for: Subject: escape man(1) arguments from glob(3) Thanks, Barry, for reminding me of this issue. Ingo
Re: makewhatis on /usr
Hi Pascal, Pascal Stumpf wrote on Sun, Nov 20, 2011 at 01:18:27AM +0100: On Sat, 19 Nov 2011 18:05:42 +0100, Ingo Schwarze wrote: Marc Espie wrote on Sat, Nov 19, 2011 at 05:40:38PM +0100: On Sat, Nov 19, 2011 at 04:31:57PM +0100, Ingo Schwarze wrote: Thomas de Grivel wrote on Sat, Nov 19, 2011 at 03:32:03PM +0100: From weekly output : Rebuilding whatis databases: /usr/libexec/makewhatis: Can't create /usr/share/man/whatis.db: Read-only file system Should not whatis.db be in /var/... ? I think you have a point. Specifically, /var/db/man/. Having cron(8) scripts write to /usr is ugly. I don't see why mounting /usr readonly should require disabling makewhatis(8). I disagree: manpage directories are self-contained. If I add or remove a directory to my man configuration, it shouldn't require a rebuild of the database for other directories. Hence having a whatis.db per-man directory root. If you want to move those to /var/db/man or something, you'd better be prepared to have database file names that depend on the root directory being used. I fully agree with all that, and having per-hierarchy databases in /var/db/man - one for /usr/share/man, one for /usr/X11R6/man, one for /usr/local/man, one for each additional directory the user configures in man.conf(5) - is indeed what i hope to do. I think what Marc meant is that whatis.db/mandoc.db should be in the same directory as their corresponding manpages. And I agree on that point, especially in the case of NFS-mounted /usr: One shouldn't have to run mandocdb to be able to run apropos(1) for the pages on the remote machine. And even worse, what happens if the remote machine is updated or packages are added? The client in such a setup will have an outdated database without being aware of it. mandoc.db should be in the same directory as the manpages it was generated from, and need not be writable by machines that don't have write access to the pages themselves. Hmm, probably you are right: The mandoc database only needs to be changed when manual pages are added to or removed from the tree, so /FOO/man/mandoc.db is _not_ more volatile than /FOO/man/man*/* and /FOO/bin/* themselves. With respect to the weekly makewhatis, I think that's a bug in the weekly(8) script: It should not blindly assume that every database listed in man.conf(5) is on a writable filesystem. Since weekly(8) just calls makewhatis(8) without any arguments, it can't do much about the fact that some directories might be locally mounted and writeable, while others may be on NFS and read-only. Besides, calling /usr/libexec/makewhatis by hand has to deal with those issues as well. Thus, the right solution probably is to have makewhatis(8) - or in the future, mandocdb(8) -, when running without arguments, test whether each database is writeable, before scanning the associated directory, and in case it is not, just skip the directory. On the other hand, when a directory is explicitly specified on the command line, the current behaviour is probably optimal: Build the database, if it did not change, be happy, otherwise, try to move the new one into its place, and if that fails, complain. Yours, Ingo
altq on a variable bandwidth interface
is there a way to set up altq+priq on an internet connection with highly variable/unknown bandwidth? I'd like to create a simple one layer queue system that prioritizes empty ACKs over anything else (always, all the time, no matter the load or congestion). it looks like priq is the way to do this, but all the documentation I can find seems to say you have to type in a hard number, which won't work for my case.
cd boot panic on 5.0 but not 4.9 or earlier
first off, apologies if this is a known issue. I didn't see anything relevant in the release notes/changes, and nothing came up in a google search. I have an older pentium 3 machine. 450mhz cpu, 100mhz bus, intel sun river 440bx motherboard, 128mb of ram (of which something like 12 are being used for the onboard video). generic seagate 10gb ata drive connected with one ribbon cable, cd drive connected with another. no pci cards or other addons. a couple days ago I tried to install 5.0 release via the install50.iso I downloaded off a mirror. however, the installer doesn't get very far. it completely loads the ram disk, but then it kernel panics instantly with a 'trap type 6'. no messages about found hardware or anything, it prints out the copyright message and the panic message all in one swift motion. I don't even get enough text to scroll the disk prompt off the top of the screen. nothing I do changes this behavior. I have tried the following: - typing boot -c at the boot prompt (still panics) - disabling different combinations of things in the bios - swapping cd drives - swapping ata cables - swapping which ata port the cd was connected to - swapped ram - ran a memtest overnight - verified the checksum on the install50.iso - tried booting from cd50.iso now, the fun part is that this only happens with 5.0, I can boot and install off the 4.9 and 4.5 'install##.iso' cds just fine. I don't have the knowledge or hardware to try and debug this via serial, and I can't try booting off a floppy because I threw out all my floppy drives years ago. I can give a dmesg from 4.9 if people think it might help.
Re: altq on a variable bandwidth interface
On Sat, Nov 19, 2011 at 08:58:46PM -0500, quartz wrote: is there a way to set up altq+priq on an internet connection with highly variable/unknown bandwidth? I'd like to create a simple one layer queue system that prioritizes empty ACKs over anything else (always, all the time, no matter the load or congestion). it looks like priq is the way to do this, but all the documentation I can find seems to say you have to type in a hard number, which won't work for my case. This is usually impossible. The packets get re-queued in the modem or whatever device is next to the choke point, and any prioritization you configure becomes useless. Typically the only way around it is to send at a rate slightly lower than the choke point bandwidth, so the buffer of the modem never starts to get utilized. If the bandwidth is variable, you're screwed. You can try if your modem or other device supports DiffServ or 802.1q priority tags. Some DSL modems do, which helps - DSL has an extra perk of the extra headers causing more overhead for small packets, so you need a shaper that can account for that, or you need to configure the max rate lower than what the line is capable of with large packets.
Which version of Firefox most secure?
In both the Packages list (for 5.0) and Ports, there are various different versions of Firefox, such as 3.5.xx, 3.6.xx, 7.x.xx, etc., all seemingly separately maintained software for each of these. Is there a version that is considered more safe/secure to use since there are several different options of which version one can choose?
Re: altq on a variable bandwidth interface
The packets get re-queued in the modem or whatever device is next to the choke point, and any prioritization you configure becomes useless. yeah, I hadn't really thought of it that way, but that makes sense. You can try if your modem or other device it's an optical terminal connected to a fiber line in this case, if that helps any. supports DiffServ or 802.1q priority tags. by any chance, is there a utility that comes with 4.9 release or through the ports tree that can use to test this easily?
Re: Which version of Firefox most secure?
On Sun, Nov 20, 2011 at 5:41 AM, James Hozier guitars...@yahoo.com wrote: In both the Packages list (for 5.0) and Ports, there are various different versions of Firefox, such as 3.5.xx, 3.6.xx, 7.x.xx, etc., all seemingly separately maintained software for each of these. Is there a version that is considered more safe/secure to use since there are several different options of which version one can choose? 3.4.xx because of JRE 3.6.xx because last supported version of 3.x line from Mozilla 7.x.xx actual stable from Mozilla
