https is faster on amd64?
http://devcentral.f5.com/weblogs/macvittie/archive/2011/01/31/dispelling-the-new-ssl-myth.aspx according to the SSL Performance table it says that the transactions per second is 2-3 times better using 64bit kernels opposite to 32bit kernels? is this true, or i am just misunderstanding something Thank you! ___ 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
OpenSSH could be faster...then why don't they path it??
https://www.psc.edu/networking/projects/hpn-ssh/hpn-v-ssh-tput.jpg
SCP and the underlying SSH2 protocol implementation in OpenSSH is network
performance limited by statically defined internal flow control buffers. These
buffers often end up acting as a bottleneck for network throughput of SCP,
especially on long and high bandwith network links. Modifying the ssh code to
allow the buffers to be defined at run time eliminates this bottleneck. We have
created a patch that will remove the bottlenecks in OpenSSH and is fully
interoperable with other servers and clients. In addition HPN clients will be
able to download faster from non HPN servers, and HPN servers will be able to
receive uploads faster from non HPN clients. However, the host receiving the
data must have a properly tuned TCP/IP stack.
My question is: So Why Does the original OpenSSH has limited statically
defined internal flow control buffers?? It could be way faster, even 10x!!
With the HPN-SCP path it could be the descendant of FTP! Why aren't there any
OpenSCP packages? ('normal SCP+HPN-SCP path+no local user needed for
SCP'ing+chroot by default')
Any opinions?
Thank you!
___
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
if the file changes send email about diff
I have 2 script. Script A, Script B. Script A is regulary watching the dhcpacks [dhcp release is configured to 2mins] in the logs, for the past 2 minutes. it writes the MAC addresses to a file [/dev/shm/dhcpacks-in-last-2min.txt] every 2 minutes. Ok, this is working, active clients are in this file. Super! Script B: http://pastebin.com/raw.php?i=wvhwhPWu I'm trying to create a script, that watches the changes in /dev/shm/dhcpacks-in-last-2min.txt file [in every 1 sec]. Ok. But: my watcher script [the pastebined] is not working fine...sometime it works, sometime it send that someone XY logged out, but it's not true! nothing happened, and the problem is not in the Script A. Can someone help me point out, what am i missing? How can i watch a file [in every sec], that contains only MAC addresses, and if someone doesn't get dhcpack in 2 minutes, the file /dev/shm/dhcpacks-in-last-2min.txt changes, and that clients MAC address will be gone from it, and i need to know, who was it [pastebined my script..but somethings wrong with it]. Thank you for any help..i've been pathing my script for days now.. :\ ___ 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: OpenSSH could be faster...then why don't they path it??
In response to kellyremo kellyr...@zoho.com: https://www.psc.edu/networking/projects/hpn-ssh/hpn-v-ssh-tput.jpg SCP and the underlying SSH2 protocol implementation in OpenSSH is network performance limited by statically defined internal flow control buffers. These buffers often end up acting as a bottleneck for network throughput of SCP, especially on long and high bandwith network links. Modifying the ssh code to allow the buffers to be defined at run time eliminates this bottleneck. We have created a patch that will remove the bottlenecks in OpenSSH and is fully interoperable with other servers and clients. In addition HPN clients will be able to download faster from non HPN servers, and HPN servers will be able to receive uploads faster from non HPN clients. However, the host receiving the data must have a properly tuned TCP/IP stack. My question is: So Why Does the original OpenSSH has limited statically defined internal flow control buffers?? It could be way faster, even 10x!! Because it's unstable?: If you are experiencing disconnects due to a failure in buffer_append_space please let us know. We're currently tracking some problems with this and we're trying to gather more information to help resolve it. Also, I'm having trouble understanding how people like that get grants to do work like that. On the one hand, they obviously know enough about cryptography to make improvements. On the other hand, they can't seem to get a grip on the fact that the code will need to have a license before anyone can grab it and incorporate it. I can't find anywhere on that page where it tells me what terms I am allowed to use those patches under. Also, it would be nice if those folks kept track of dates. Like, how long have those patches be available? There's not a single date on any of those pages or the files involved. The reason I point this out is because OpenSSL is _extremely_ sensitive software. I don't want to see any large changes to it released until they've been in testing for months, if not years. For all we know, these speed improvements are riddled with dozens of security flaws. Also, any reason why you're asking these questions of FreeBSD and not of the OpenSSL project? -- Bill Moran http://www.potentialtech.com http://people.collaborativefusion.com/~wmoran/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.2 prerelease, virtualbox, and windows guests that freeze...
On Saturday 05 February 2011 22:12:45 Eric Schuele wrote: All, I have a laptop running 8.2-prerelease GENERIC. I have virtualbox ose 3.2.12 from ports (and kmod as well). I've only installed windows guests in vbox. I've installed windows 2008 server 64, windows vista 64bit, and windows 7 32bit. I have the vbox hdd images on an NTFS filesystem mounted using fuse. My box is a dual boot machine between FreeBSD and Windows. My desire is to be able to utilize the same virtual machine in vbox on both my Windows and FreeBSD installations. I can successfully utilize the virtuals in vbox (same version) in Windows. However when I utilize any of the virtual machines in FreeBSD, they run for several minutes and eventually freeze. Freeze may not necessarily be the correct term. All windows processes on the virtual machine begin to die. First one process, then another, then all. Hard to explain, which may not help my cause here. But, most important fact... in Windows they work fine... under FreeBSD they run for a while and then cease to run. When the VM is good and dead, it is always dead with the little vbox virtual hard disk LED lit up (no idea if that is important). Previously, they would run for a *very* short time. seconds? minutes? and then die (sometimes I couldn't login). I disabled sound support and now they run for 10-15 minutes. Had one run for an hour or two the other day, but can't reproduce that. Usually 10-15 minutes max. Network works fine inside the virtual. I'm new to VirtualBox on FreeBSD. I've used it a bit on Windows with good results. I did try a windows guest on a non fuse filesystem just to rule that out, but had same issue. What else could I provide that might allow someone to point me in the right direction here? Thanks. -- Regards, Eric Eric; My advice to you is that you change the file system on drive that holds the VMs files from NTFS to EXT2. NTFS file systems on FreeBSD or even Linux are OK only for doing small r/w stuff. I use the ntfs-3g which is really good but don't trust NTFS for heavy usage under those OSs. Sometimes it's not even trustable under windows itself. EXT on the other hand, is very stable in FreeBSD and has very good drivers for any version of 32/64 windows (Ext2IFS_1_11a) so you can access you vdi files. hope this helps. -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio YET!!] (99% winblows FREE) ___ 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
Set tty resolution using hint.sc.0.flags with VESA
Hello, I don't like much to use allscreens_flags to set my tty resolution because it's done at the end of /etc/rc process. I know we can edit the hint.sc.0.flags in /boot/device.hints to set the resolution at the earliest stage. I want to use the 1366x768 mode : # vidcontrol -i mode [... snip ...] 496 (0x1f0) 0x001f G 1366x768x32 D 8x16 0xa 64k 64k 0xc000 4128k To use this mode I should write hint.sc.0.flags=0x1f00180 where 80 means VESA mode following the sc(4) manpage. It seems that my resolution is like 1024x768 when I bootup and not the one I want. However when I use vidcontrol MODE_496 after boot it works pretty well. Is there something wrong on my line ? Cheers, -- 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: nedit problem
On 02/06/11 00:53, b. f. wrote: Fred Boatwright wrote: After updating all ports on 8.1-RELEASE, nedit has a problem. The right mouse button works ok in the toolbar but if it is pressed in the text area, for example to copy a block of text, the cursor changes shape and the X session becomes completely locked up. I have to stop X and restart it. I have tried to deinstall nedit and rebuild it but this didn't help. It is nedit-5.5 with Motif 2.2.3. This is a known problem with many Motif-based applications, arising from a bug in recent versions of Xorg. It has been corrected upstream, and it is likely that this problem will be fixed when the ports freeze ends shortly after the release of FreeBSD 7.4 and 8.2, if not before. If you can't wait, you can try using the patches from: http://www.freebsd.org/cgi/query-pr.cgi?pr=154510 b. ___ 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 I will just use another editor for a while. Thanks for the help. Best regards, Fred ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.2 prerelease, virtualbox, and windows guests that freeze...
On 02/06/2011 09:23, Mario Lobo wrote: On Saturday 05 February 2011 22:12:45 Eric Schuele wrote: All, I have a laptop running 8.2-prerelease GENERIC. I have virtualbox ose 3.2.12 from ports (and kmod as well). I've only installed windows guests in vbox. I've installed windows 2008 server 64, windows vista 64bit, and windows 7 32bit. I have the vbox hdd images on an NTFS filesystem mounted using fuse. snip Eric; My advice to you is that you change the file system on drive that holds the VMs files from NTFS to EXT2. Thanks for the suggestion, however, I've already tried this (sorta). From my original post... I did try a windows guest on a non fuse filesystem just to rule that out, but had same issue. I suppose it may have been a little less than clear. By non fuse filesystem I actually meant UFS. The problem still persisted. NTFS file systems on FreeBSD or even Linux are OK only for doing small r/w stuff. I use the ntfs-3g which is really good but don't trust NTFS for heavy usage under those OSs. Sometimes it's not even trustable under windows itself. I realize NTFS on fBSD has been shaky in the past, but had heard it had come a long way these days. It does seem to work well for all my purposes, except these VMs. Had hoped NTFS was not the issue. EXT on the other hand, is very stable in FreeBSD and has very good drivers for any version of 32/64 windows (Ext2IFS_1_11a) so you can access you vdi files. I've not tried the EXT IFS for windows yet, nor had I heard much regarding their success or failure. If your willing to go out on a limb and say very good drivers for any version of 32/64 windows... I'll give it a try, and post my results. :) Thanks. hope this helps. -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio YET!!] (99% winblows FREE) -- Regards, Eric signature.asc Description: OpenPGP digital signature
Re: Set tty resolution using hint.sc.0.flags with VESA
Hello! [fluffy@Beastie] ~$ cat /boot/device.hints|grep sc.0 hint.sc.0.at=isa hint.sc.0.flags=0x180 hint.sc.0.vesa_mode=0x1f0 07.02.2011, 01:50, David Demelier demelier.da...@gmail.com: Hello, I don't like much to use allscreens_flags to set my tty resolution because it's done at the end of /etc/rc process. I know we can edit the hint.sc.0.flags in /boot/device.hints to set the resolution at the earliest stage. I want to use the 1366x768 mode : # vidcontrol -i mode [... snip ...] 496 (0x1f0) 0x001f G 1366x768x32 D 8x16 0xa 64k 64k 0xc000 4128k To use this mode I should write hint.sc.0.flags=0x1f00180 where 80 means VESA mode following the sc(4) manpage. It seems that my resolution is like 1024x768 when I bootup and not the one I want. However when I use vidcontrol MODE_496 after boot it works pretty well. Is there something wrong on my line ? Cheers, -- 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 -- Dima Panov (flu...@freebsd.org) KDE@FreeBSD team Facebook: http://www.facebook.com/?id=10181104157 ___ 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
kern.crit messages
I have a server I installed 8.1-RELEASE on and believe I screwed up when rebuilding the kernel to support QUOTA because now that I am troubleshooting these weird messages in the log, I find I am actually running 9.0-CURRENT. I had a ports file as below when I pulled the source to rebuild the kernel... *default host=cvsup9.us.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=. *default release=cvs delete use-rel-suffix compress src-all Using the tag above caused my issue? Now I see some troubling messages in my logs... Feb 6 11:25:23 kern.crit backup kernel: lock order reversal: Feb 6 11:25:23 kern.crit backup kernel: 1st 0xff8014bbbe58 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2659 Feb 6 11:25:23 kern.crit backup kernel: 2nd 0xff002b9d6400 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:283 Feb 6 11:25:23 kern.crit backup kernel: KDB: stack backtrace: Feb 6 11:25:23 kern.crit backup kernel: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a Feb 6 11:25:23 kern.crit backup kernel: _witness_debugger() at _witness_debugger+0x2e Feb 6 11:25:23 kern.crit backup kernel: witness_checkorder() at witness_checkorder+0x807 Feb 6 11:25:23 kern.crit backup kernel: _sx_xlock() at _sx_xlock+0x55 Feb 6 11:25:23 kern.crit backup kernel: ufsdirhash_acquire() at ufsdirhash_acquire+0x33 Feb 6 11:25:23 kern.crit backup kernel: ufsdirhash_add() at ufsdirhash_add+0x19 Feb 6 11:25:23 kern.crit backup kernel: ufs_direnter() at ufs_direnter+0x662 Feb 6 11:25:23 kern.crit backup kernel: ufs_makeinode() at ufs_makeinode+0x291 Feb 6 11:25:23 kern.crit backup kernel: VOP_CREATE_APV() at VOP_CREATE_APV+0x8d Feb 6 11:25:23 kern.crit backup kernel: vn_open_cred() at vn_open_cred+0x46a Feb 6 11:25:23 kern.crit backup kernel: kern_openat() at kern_openat+0x181 Feb 6 11:25:23 kern.crit backup kernel: syscallenter() at syscallenter+0x1aa Feb 6 11:25:23 kern.crit backup kernel: syscall() at syscall+0x4c Feb 6 11:25:23 kern.crit backup kernel: Xfast_syscall() at Xfast_syscall+0xe2 Feb 6 11:25:23 kern.crit backup kernel: --- syscall (5, FreeBSD ELF64, open), rip = 0x80078118c, rsp = 0x7fffad48, rbp = 0x7fffb73f --- I also find this message with dmesg... ad8: 152627MB Seagate ST3160811AS 3.AAE at ata4-master UDMA100 SATA ad9: 953869MB Seagate ST31000528AS CC3E at ata4-slave UDMA100 SATA GEOM: ad8s1: geometry does not match label (255h,63s != 16h,63s). ad10: 152627MB Seagate ST3160811AS 3.AAE at ata5-master UDMA100 SATA ad11: 953869MB Seagate ST31000528AS CC3E at ata5-slave UDMA100 SATA GEOM: ad9s1: geometry does not match label (255h,63s != 16h,63s). uhub0: 2 ports with 2 removable, self powered uhub1: 2 ports with 2 removable, self powered uhub2: 2 ports with 2 removable, self powered uhub3: 2 ports with 2 removable, self powered GEOM: ufsid/4c7aa872e9a44575: geometry does not match label (255h,63s != 16h,63s). GEOM: ad10s1: geometry does not match label (255h,63s != 16h,63s). GEOM: ad11s1: geometry does not match label (255h,63s != 16h,63s). uhub4: 8 ports with 8 removable, self powered ar0: 152627MB Intel MatrixRAID RAID1 status: READY ar0: disk0 READY (master) using ad8 at ata4-master ar0: disk1 READY (mirror) using ad10 at ata5-master ar1: 953869MB Intel MatrixRAID RAID1 status: READY ar1: disk0 READY (master) using ad11 at ata5-slave ar1: disk1 READY (mirror) using ad9 at ata4-slave SMP: AP CPU #1 Launched! WARNING: WITNESS option enabled, expect reduced performance. ugen1.2: Rextron at usbus1 ukbd0: USB on usbus1 kbd2 at ukbd0 ums0: USB on usbus1 ums0: 5 buttons and [XYZ] coordinates ID=1 Trying to mount root from ufs:/dev/ar0s1a lock order reversal: 1st 0xff0002cdd818 ufs (ufs) @ /usr/src/sys/kern/vfs_lookup.c:501 2nd 0xff801497ff78 bufwait (bufwait) @ /usr/src/sys/ufs/ffs/ffs_softdep.c:11309 3rd 0xff0002d4fbd8 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2111 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a _witness_debugger() at _witness_debugger+0x2e witness_checkorder() at witness_checkorder+0x807 __lockmgr_args() at __lockmgr_args+0xd42 ffs_lock() at ffs_lock+0x8c VOP_LOCK1_APV() at VOP_LOCK1_APV+0x9b _vn_lock() at _vn_lock+0x47 vget() at vget+0x7b vfs_hash_get() at vfs_hash_get+0xd5 ffs_vgetf() at ffs_vgetf+0x48 softdep_sync_metadata() at softdep_sync_metadata+0x5e3 ffs_syncvnode() at ffs_syncvnode+0x213 ffs_truncate() at ffs_truncate+0x557 ufs_direnter() at ufs_direnter+0x47b ufs_makeinode() at ufs_makeinode+0x291 VOP_CREATE_APV() at VOP_CREATE_APV+0x8d vn_open_cred() at vn_open_cred+0x46a kern_openat() at kern_openat+0x181 syscallenter() at syscallenter+0x1aa syscall() at syscall+0x4c Xfast_syscall() at Xfast_syscall+0xe2 --- syscall (5, FreeBSD ELF64, open), rip = 0x80072f18c, rsp = 0x7fffead8, rbp = 0 --- lock order reversal: 1st 0xff8014bbbe58 bufwait (bufwait) @
Re: kern.crit messages
On Sun, Feb 06, 2011 at 12:04:59PM -0500, Robert Fitzpatrick rob...@webtent.org wrote: I have a server I installed 8.1-RELEASE on and believe I screwed up when rebuilding the kernel to support QUOTA because now that I am troubleshooting these weird messages in the log, I find I am actually running 9.0-CURRENT. I had a ports file as below when I pulled the source to rebuild the kernel... *default host=cvsup9.us.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=. *default release=cvs delete use-rel-suffix compress src-all Using the tag above caused my issue? Now I see some troubling messages in my logs... Just looking for advice on what to do about all this, can someone help? By using the line: *default release=cvs tag=. for src-all collection you definitely grabbed -current sources. I'm not sure if downgrading by make world is supported but you could try. Backup first, try later.. -- Vallo ___ 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: OpenSSH could be faster...then why don't they path it??
On Sun, Feb 06, 2011 at 08:42:27AM -0500, Bill Moran wrote: Also, I'm having trouble understanding how people like that get grants to do work like that. On the one hand, they obviously know enough about cryptography to make improvements. On the other hand, they can't seem to get a grip on the fact that the code will need to have a license before anyone can grab it and incorporate it. I can't find anywhere on that page where it tells me what terms I am allowed to use those patches under. A lack of concern for specific licensing seems to be a big problem in the open source world -- particularly the copyleft world. Many people seem to think that if they say open source it means GPL, and they don't have to tell anyone they're releasing it under the terms of the GPL. The license ends up buried under some second-order subdirectory in a tarball that isn't the supposedly preferred means of getting the software in question. Occasionally, the same kind of lack of concern is employed with distributing something under some other open source license, and occasionally an announcement that something is open source comes with the author's assumption that no license is needed at all. It drives me up the wall. Also, it would be nice if those folks kept track of dates. Like, how long have those patches be available? There's not a single date on any of those pages or the files involved. The reason I point this out is because OpenSSL is _extremely_ sensitive software. I don't want to see any large changes to it released until they've been in testing for months, if not years. For all we know, these speed improvements are riddled with dozens of security flaws. I agree that dates are important, too. These days, there is little or no execuse for offering open source software to the world without storing it in a publicly accessible version control system's repository, which will automatically track commit dates for everything anyway. Also, any reason why you're asking these questions of FreeBSD and not of the OpenSSL project? I think we're discussing OpenSSH rather than OpenSSL. Am I mistaken? They are not the same project. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgpYQp3xqsNOx.pgp Description: PGP signature
Re: Set tty resolution using hint.sc.0.flags with VESA
On 06/02/2011 17:52, Dima Panov wrote: Hello! [fluffy@Beastie] ~$ cat /boot/device.hints|grep sc.0 hint.sc.0.at=isa hint.sc.0.flags=0x180 hint.sc.0.vesa_mode=0x1f0 absolutely great! But where did you find these vesa_mode setting? It's not documented anywhere. Cheers, -- 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: kern.crit messages
On Sun, 06 Feb 2011 12:04:59 -0500 Robert Fitzpatrick rob...@webtent.org wrote: I have a server I installed 8.1-RELEASE on and believe I screwed up when rebuilding the kernel to support QUOTA because now that I am troubleshooting these weird messages in the log, I find I am actually running 9.0-CURRENT. I had a ports file as below when I pulled the source to rebuild the kernel... *default host=cvsup9.us.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=. *default release=cvs delete use-rel-suffix compress src-all Using the tag above caused my issue? Yes, with ports tag=. just means the latest version, with the base system it means the latest CURRENT, you should have used RELENG_8_1_0_RELEASE or RELENG_8_1 Now I see some troubling messages in my logs... I believe CURRENT has a lot of additional debug on by default, and presumably you now have a mismatched kernel and userland, so it's not surprizing. Just looking for advice on what to do about all this, can someone help? If you have only built the kernel and only built it once you should have the old 8.1 version as a backup. ___ 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: kern.crit messages
On 2/6/2011 12:20 PM, Vallo Kallaste wrote: By using the line: *default release=cvs tag=. for src-all collection you definitely grabbed -current sources. I'm not sure if downgrading by make world is supported but you could try. Backup first, try later.. Thanks. Can someone confirm these steps as the best way to attempt to get back to a 8.1 kernel I originally installed... 1. update my tag line to 8_1 2. update my source tree 3. run 'make world' I have backup already. I ask because in the handbook it says 'Do not use make world'... http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html I was going to just rebuild the kernel with the proper source tree. -- Robert rob...@webtent.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: Set tty resolution using hint.sc.0.flags with VESA
David Demelier wrote: hint.sc.0.vesa_mode=0x1f0 ... absolutely great! But where did you find these vesa_mode setting? It's not documented anywhere. Look again: syscons(4), in the Synopsis and the Driver Flags section. b. ___ 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: nedit problem
On 02/06/11 00:53, b. f. wrote: Fred Boatwright wrote: After updating all ports on 8.1-RELEASE, nedit has a problem. The right mouse button works ok in the toolbar but if it is pressed in the text area, for example to copy a block of text, the cursor changes shape and the X session becomes completely locked up. I have to stop X and restart it. I have tried to deinstall nedit and rebuild it but this didn't help. It is nedit-5.5 with Motif 2.2.3. This is a known problem with many Motif-based applications, arising from a bug in recent versions of Xorg. It has been corrected upstream, and it is likely that this problem will be fixed when the ports freeze ends shortly after the release of FreeBSD 7.4 and 8.2, if not before. If you can't wait, you can try using the patches from: http://www.freebsd.org/cgi/query-pr.cgi?pr=154510 b. ___ 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 I have tried several editors that are horrible. Axe installed from packages dumps core. There were a lot of warnings that later versions of libraries were installed than axe was expecting. Does the maintainer need to know this? Can you tell me how to install the Xorg patch to make nedit work? I have not worked with getting source code or compiling from source. I can do the edit on another computer. Best regards, Fred ___ 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: kern.crit messages
On Sun, Feb 6, 2011 at 12:10 PM, Robert Fitzpatrick rob...@webtent.orgwrote: Thanks. Can someone confirm these steps as the best way to attempt to get back to a 8.1 kernel I originally installed... 1. update my tag line to 8_1 2. update my source tree For step 3, you can something like make buildkernel make installkernel but you may not have to do that if the /boot/kernel.old is a match your currect userland as mentioned previously. simply move it /boot/kernel after you have tested it. -- 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
Re: 8.2 prerelease, virtualbox, and windows guests that freeze...
On Sat, Feb 5, 2011 at 7:12 PM, Eric Schuele e.schu...@computer.org wrote: What else could I provide that might allow someone to point me in the right direction here? You can try recompiling virtualbox with debug options and see if it spits out any pertinent messages. I have no problems with Windows guests on VDI, ZVOL, raw file, or raw partitions. Vbox also logs data per VM, you can check that. Another possibility is that you have mismatched versions of guest additions. If that were the problem, it would show up in the Vbox logs. -- 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
Re: Why does my 8.2-RC3 dvd1 boot DOS?
SERIOUS APOLOGIES! I've found out my dvd is marginal, or possibly the drive. What seemed like a bad dvd apparently resulted in a scan (by the BIOS?) until it found a boot loader it understood, PC-DOS it said, which was one of several I discovered in grepping the ISO file. I should have done freebsd-update ! Chuck Bacon - c...@cape.com I downloaded it yesterday. Here's the facts: 1. md5 matches CHECKSUM.MD5 2. When I boot off the BIOS, it takes a half minute or so, and then: voila! PC-DOS boots, and for all the world look as though it will boot a larger system; except it doesn't have a clue. Here's the hypothesis: The FreeBSD-8.3-RC3 boot loader doesn't satisfy my BIOS, and the BIOS looks through the dvd until it finds one of the DOS boot loaders provided by some fdisk variant. Any ideas why? If nothing else, I'll download disc1. Praps that'll work! Many thanks, Chuck Bacon -- c...@cape.com ABHOR SECRECY -- DEFEND PRIVACY ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.2 prerelease, virtualbox, and windows guests that freeze...
On Sun, Feb 6, 2011 at 11:09 AM, Eric Schuele e.schu...@computer.orgwrote: I realize NTFS on fBSD has been shaky in the past, but had heard it had come a long way these days. It does seem to work well for all my purposes, except these VMs. Had hoped NTFS was not the issue. ntfs/ntfs-3g is foolhardy at best in linux *and* fbsd ... it's trashed so many drives.partitions on me it's not even funny anymore... and I never did much w/ them except small stuff anyway. If you need to access the volumes in *nix/windows then why not FAT32 then? I use a FAT32 drive for my music so I can access it in any OS reliably and the drive is now 6+ years old. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.2 prerelease, virtualbox, and windows guests that freeze...
On Sunday 06 February 2011 13:09:47 Eric Schuele wrote: Thanks for the suggestion, however, I've already tried this (sorta). From my original post... I did try a windows guest on a non fuse filesystem just to rule that out, but had same issue. I suppose it may have been a little less than clear. By non fuse filesystem I actually meant UFS. The problem still persisted. NTFS file systems on FreeBSD or even Linux are OK only for doing small r/w stuff. I use the ntfs-3g which is really good but don't trust NTFS for heavy usage under those OSs. Sometimes it's not even trustable under windows itself. My bad!. Sorry!. But it seems that you're right. Looks like the issue is not the FS then. If you're building from the ports, try the svn version from: https://svn.bluelife.at/index.cgi/blueports It's already version 4.0.2 there. I realize NTFS on fBSD has been shaky in the past, but had heard it had come a long way these days. It does seem to work well for all my purposes, except these VMs. Had hoped NTFS was not the issue. I've not tried the EXT IFS for windows yet, nor had I heard much regarding their success or failure. If your willing to go out on a limb and say very good drivers for any version of 32/64 windows... I'll give it a try, and post my results. :) Forgive me if it sounded on a limb. Didn't mean to look like that. The only reason I mentioned it is because it's exactly the way I've been using. I have triple boot system. BSD AMD64, XP32 and Win7 64 and the IFS driver works flawlessly on both windows, and all 3 Vboxes accessing the same VDIs. Because of that, I believe I may have got carried away by saying any win version. regards, -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio YET!!] (99% winblows FREE) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Why does my 8.2-RC3 dvd1 boot DOS?
On Sun, Feb 06, 2011 at 03:48:45PM -0500, Chuck Bacon wrote: SERIOUS APOLOGIES! I've found out my dvd is marginal, or possibly the drive. What seemed like a bad dvd apparently resulted in a scan (by the BIOS?) until it found a boot loader it understood, PC-DOS it said, which was one of several I discovered in grepping the ISO file. I should have done freebsd-update ! Chuck Bacon - c...@cape.com Chuck, where on the DVD is the copy of PC-DOS? I downloaded it yesterday. Here's the facts: 1. md5 matches CHECKSUM.MD5 2. When I boot off the BIOS, it takes a half minute or so, and then: voila! PC-DOS boots, and for all the world look as though it will boot a larger system; except it doesn't have a clue. Here's the hypothesis: The FreeBSD-8.3-RC3 boot loader doesn't satisfy my BIOS, and the BIOS looks through the dvd until it finds one of the DOS boot loaders provided by some fdisk variant. Any ideas why? If nothing else, I'll download disc1. Praps that'll work! Many thanks, Chuck Bacon -- c...@cape.com ABHOR SECRECY -- DEFEND PRIVACY Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html pgpmjqCKMdtLI.pgp Description: PGP signature
Re: 8.2 prerelease, virtualbox, and windows guests that freeze...
On Sunday 06 February 2011 17:48:45 Chris Brennan wrote: On Sun, Feb 6, 2011 at 11:09 AM, Eric Schuele e.schu...@computer.orgwrote: I realize NTFS on fBSD has been shaky in the past, but had heard it had come a long way these days. It does seem to work well for all my purposes, except these VMs. Had hoped NTFS was not the issue. ntfs/ntfs-3g is foolhardy at best in linux *and* fbsd ... it's trashed so many drives.partitions on me it's not even funny anymore... and I never did much w/ them except small stuff anyway. If you need to access the volumes in *nix/windows then why not FAT32 then? I use a FAT32 drive for my music so I can access it in any OS reliably and the drive is now 6+ years old. FAT32 max file size is 4Gig. -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio YET!!] (99% winblows FREE) ___ 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: if the file changes send email about diff
On Sun, Feb 6, 2011 at 2:33 PM, kellyremo kellyr...@zoho.com wrote: I have 2 script. Script A, Script B. Script A is regulary watching the dhcpacks [dhcp release is configured to 2mins] in the logs, for the past 2 minutes. it writes the MAC addresses to a file [/dev/shm/dhcpacks-in-last-2min.txt] every 2 minutes. Ok, this is working, active clients are in this file. Super! Script B: http://pastebin.com/raw.php?i=wvhwhPWu I'm trying to create a script, that watches the changes in /dev/shm/dhcpacks-in-last-2min.txt file [in every 1 sec]. Ok. But: my watcher script [the pastebined] is not working fine...sometime it works, sometime it send that someone XY logged out, but it's not true! nothing happened, and the problem is not in the Script A. Can someone help me point out, what am i missing? How can i watch a file [in every sec], that contains only MAC addresses, and if someone doesn't get dhcpack in 2 minutes, the file /dev/shm/dhcpacks-in-last-2min.txt changes, and that clients MAC address will be gone from it, and i need to know, who was it [pastebined my script..but somethings wrong with it]. You are attempting to re-invent the wheel called revision control system ;) Your FreeBSD box has a simple revision control system called 'rcs'. It will do the most things you are trying to emulate in your shell script. Read the rcsintro(1) man page how to get started. ___ 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: kern.crit messages
On Sun, 6 Feb 2011 12:21:02 -0600, Adam Vande More amvandem...@gmail.com wrote: On Sun, Feb 6, 2011 at 12:10 PM, Robert Fitzpatrick rob...@webtent.orgwrote: Thanks. Can someone confirm these steps as the best way to attempt to get back to a 8.1 kernel I originally installed... 1. update my tag line to 8_1 2. update my source tree For step 3, you can something like make buildkernel make installkernel but you may not have to do that if the /boot/kernel.old is a match your currect userland as mentioned previously. simply move it /boot/kernel after you have tested it. Refer to the comment section of /usr/src/Makefile for an explaination of the correct procedure of the updating process: 1. `cd /usr/src' (or to the directory containing your source tree). 2. `make buildworld' 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). [steps 3. 4. can be combined by using the kernel target] 5. `reboot'(in single user mode: boot -s from the loader prompt). 6. `mergemaster -p' 7. `make installworld' 8. `make delete-old' 9. `mergemaster' (you may wish to use -U or -ai). 10. `reboot' 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) You'll also see what the different make targets are representing (e. g. make world = buildworld + installworld, no kernel). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: nedit problem
Fred Boatwright wrote: On 02/06/11 00:53, b. f. wrote: Fred Boatwright wrote: After updating all ports on 8.1-RELEASE, nedit has a problem. The right mouse button works ok in the toolbar but if it is pressed in the text area, for example to copy a block of text, the cursor changes shape and the X session becomes completely locked up. I have to stop X and restart it. I have tried to deinstall nedit and rebuild it but this didn't help. It is nedit-5.5 with Motif 2.2.3. This is a known problem with many Motif-based applications, arising from a bug in recent versions of Xorg. It has been corrected upstream, and it is likely that this problem will be fixed when the ports freeze ends shortly after the release of FreeBSD 7.4 and 8.2, if not before. If you can't wait, you can try using the patches from: http://www.freebsd.org/cgi/query-pr.cgi?pr=154510 I have tried several editors that are horrible. Axe installed from packages dumps core. There were a lot of warnings that later versions of libraries were installed than axe was expecting. Does the maintainer need to know this? Sadly, there is no maintainer for that port. But yes, you should file a Problem Report (PR), so that people will know that there may be a problem: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/problem-reports/index.html Can you tell me how to install the Xorg patch to make nedit work? I have not worked with getting source code or compiling from source. I can do the edit on another computer. Get an up-to-date ports tree. (If you don't know what that means, read the relevant portions of the FreeBSD Handbook.) Place the attached patch (or a trimmed version of the patch from the PR that I cited earlier) in ports/x11-servers/xorg-server/files under a name like 'patch-dix__events.c', that begins with 'patch-', and doesn't overwrite any of the existing patches. In the ports/x11-servers/xorg-server directory, run 'make deinstall clean install make clean', or use your favorite third-party port updating tool to force an update of that port. (If you want to create a backup package of your patched version of xorg-server, and you are not using a port updating tool with this feature, then either 'make package' in that directory before running the final 'make clean', or use 'pkg_create -b xorg-server-*'.) I'm assuming that you are already using the latest version of x11-servers/xorg-server; if instead you are using an earlier version, and packages that depend on it, you will probably need to update them as well. b. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.2 prerelease, virtualbox, and windows guests that freeze...
Net, I've formatted drives as fat32 that were well over 4gb. In fact I have an external 120gb we datavault that's fat32 -- Sent from my Droid On Feb 6, 2011 5:25 PM, Mario Lobo l...@bsd.com.br wrote: On Sunday 06 February 2011 17:48:45 Chris Brennan wrote: On Sun, Feb 6, 2011 at 11:09 AM, Eric Schuele e.schu...@computer.org wrote: I realize NTFS on fBSD has been shaky in the past, but had heard it had come a long way these days. It does seem to work well for all my purposes, except these VMs. Had hoped NTFS was not the issue. ntfs/ntfs-3g is foolhardy at best in linux *and* fbsd ... it's trashed so many drives.partitions on me it's not even funny anymore... and I never did much w/ them except small stuff anyway. If you need to access the volumes in *nix/windows then why not FAT32 then? I use a FAT32 drive for my music so I can access it in any OS reliably and the drive is now 6+ years old. FAT32 max file size is 4Gig. -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio YET!!] (99% winblows FREE) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.2 prerelease, virtualbox, and windows guests that freeze...
On 02/06/2011 11:35, Adam Vande More wrote: On Sat, Feb 5, 2011 at 7:12 PM, Eric Schuele e.schu...@computer.org wrote: What else could I provide that might allow someone to point me in the right direction here? You can try recompiling virtualbox with debug options and see if it spits out any pertinent messages. I have no problems with Windows guests on VDI, ZVOL, raw file, or raw partitions. Vbox also logs data per VM, you can check that. Logs might be nice. Where would I find these. Or are they only present with debug builds (which I am building now) Another possibility is that you have mismatched versions of guest additions. If that were the problem, it would show up in the Vbox logs. I thought of that... even though vbox does not complain of a mismatch, I went ahead and removed them from a machine and added them back in from my FreeBSD host. No improvement unfortunately. -- Regards, Eric signature.asc Description: OpenPGP digital signature
Re: 8.2 prerelease, virtualbox, and windows guests that freeze...
On 02/06/2011 21:17, Eric Schuele wrote: On 02/06/2011 11:35, Adam Vande More wrote: On Sat, Feb 5, 2011 at 7:12 PM, Eric Schuele e.schu...@computer.org wrote: What else could I provide that might allow someone to point me in the right direction here? You can try recompiling virtualbox with debug options and see if it spits out any pertinent messages. I have no problems with Windows guests on VDI, ZVOL, raw file, or raw partitions. Vbox also logs data per VM, you can check that. Logs might be nice. Where would I find these. Or are they only present with debug builds (which I am building now) Ok... found the logs. :) Looks as if each machine has 4 log files, and that the set of files is from the last run. Anything in there I could post to help diagnose? Another possibility is that you have mismatched versions of guest additions. If that were the problem, it would show up in the Vbox logs. I thought of that... even though vbox does not complain of a mismatch, I went ahead and removed them from a machine and added them back in from my FreeBSD host. No improvement unfortunately. -- Regards, Eric signature.asc Description: OpenPGP digital signature
Debian GNU/kFreeBSD
Hello, I have heard that Debian project has replaced the Linux kernel in their distribution with FreeBSD kernel and have released Debian GNU/kFreeBSD. Since this version, they will release Debian GNU/kFreeBSD as a stable port. What is this all about? What will be consequences for FreeBSD? Will a lot of FreeBSD users move to that distribution? Good Luck Bahman Kahinpour ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.2 prerelease, virtualbox, and windows guests that freeze...
On Sun, Feb 6, 2011 at 7:03 PM, Chris Brennan xa...@xaerolimit.net wrote: Net, I've formatted drives as fat32 that were well over 4gb. In fact I have an external 120gb we datavault that's fat32 Max per file, not the whole partition. Virtual machines generally store the whole disk as a single file, though Vmware has an option to split it up for these situations. -- Rob Farmer ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.2 prerelease, virtualbox, and windows guests that freeze...
On Sun, Feb 6, 2011 at 9:23 PM, Eric Schuele e.schu...@computer.org wrote: Ok... found the logs. :) Looks as if each machine has 4 log files, and that the set of files is from the last run. Anything in there I could post to help diagnose? Let's see what's in the most recent log of an affected VM. If you have any funky options like page fusion enabled disable them. What the output of gstat(8) and top(1) look like when you reach this degraded state? -- 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
Re: Debian GNU/kFreeBSD
In the last episode (Feb 07), Bahman Kahinpour said: I have heard that Debian project has replaced the Linux kernel in their distribution with FreeBSD kernel and have released Debian GNU/kFreeBSD. Since this version, they will release Debian GNU/kFreeBSD as a stable port. What is this all about? What will be consequences for FreeBSD? Will a lot of FreeBSD users move to that distribution? I expect Debian users will try GNU/kFreeBSD and like it so much they wtill switch to full FreeBSD. -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Debian GNU/kFreeBSD
I have heard that Debian project has replaced the Linux kernel in their distribution with FreeBSD kernel and have released Debian GNU/kFreeBSD. Since this version, they will release Debian GNU/kFreeBSD as a stable port. What is this all about? As you can see from their webpages, they replaced the Linux kernel with a patched FreeBSD 8.1 kernel, but kept most of the rest of the Debian base system and packaging system. It's for users who prefer a FreeBSD kernel, but want a Debian userland and packages, and don't have a problem with the different licenses. Gentoo has a similar project: http://www.gentoo.org/proj/en/gentoo-alt/bsd/fbsd/ There are also some NetBSD-base derivatives. What will be consequences for FreeBSD? Will a lot of FreeBSD users move to that distribution? Well, only time will tell, but I doubt that either will completely replace the other in the near future. There has already been some interaction between the two projects -- I remember a few recent changes made in FreeBSD because of feedback from Debian users and developers. b. ___ 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
