Re: Jails working differently in FreeBSD-8
It may sound silly but can you confirm that sshd is running inside the jail? Er... that was the problem. Not enabled in rc.conf Please allow me to feel embarrassed ;) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Jails working differently in FreeBSD-8
Jails appear to be working differently in 8.0 compared with 7.x (due to the networking changes in 8 most likely). Anyway, I've created a jail in 8.0 and given it it's own IPv4 IP address. Problem is, when I attempt to SSH to this jail IP address, I'm arriving in the host environment, and not the jailed environment. In 7.x I would have landed inside the jail so what's going on in 8? Hopefully someone who has already solved this issue can help me out a bit. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ural driver stalls under FreeBSD7.1
Weongyo Jeong wrote: On Thu, Feb 26, 2009 at 06:04:17PM -0800, Sam Leffler wrote: Bengt Ahlgren wrote: Weongyo Jeong weongyo.je...@gmail.com writes: On Thu, Feb 26, 2009 at 01:20:36PM +0900, Nathan Butcher wrote: I have a Buffalo WLI-U2-KG54-AI wireless USB adaptor. It has been malfunctioning for quite a while under FreeBSD7.0 and 7.1 Typically, It works for a while until eventually it stalls data transfers completely. It always seems to do this after an unspecified amount of time. I know the hardware isn't at fault because the device works fine under Linux. Could you please check that `ifconfig ifname -bgscan' disabling the background scan helps your symptom? The above sounds like the same problem as this: http://lists.freebsd.org/pipermail/freebsd-mobile/2009-February/011376.html http://lists.freebsd.org/pipermail/freebsd-mobile/2009-February/011343.html The problem is in the background scanning logic in sys/net80211. I don't see how you come to this conclusion. ural is a totally different driver than ath and so far as I can recall you never found the cause for your problem w/ ath. Most of the usb wireless drivers do a haphazard job of synchronizing async tasks like bg scan with the foreground tx/rx processing. This can lead to firmware and/or usb issues. ath does not have these issues but I am aware of at least one problem w/ bg scanning in ath under RELENG_7 (that is not present in HEAD). I agree with sam because I saw some cases like stalls during background scanning that most of them I think it's caused by H/W miss-operation or miss-configuration by mistakes of driver. I'll do some testing without the bgscan and report back. (haven't had time recently) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
ural driver stalls under FreeBSD7.1
I have a Buffalo WLI-U2-KG54-AI wireless USB adaptor. It has been malfunctioning for quite a while under FreeBSD7.0 and 7.1 Typically, It works for a while until eventually it stalls data transfers completely. It always seems to do this after an unspecified amount of time. I know the hardware isn't at fault because the device works fine under Linux. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: sysinstall automatic partition labelling/sizing problem
Are you running i386 or amd64? 360MB _is_ a very tight fit for amd64 but you should make it unless you have some large, unexpected files lying around in your root partition. As a workaround, you could remove *.symbols from the old kernel files. Running amd64. The install was fresh so there were no extra files in / Looking at sysinstall, the default size is currently 512MB unless you have less than ~20GB, when it will start scaling down. maybe it needs to scale down just a little bit less than it already does although granted, not every install is going to experience a kernal recompile from source - well, ones that expect to be maintained anyway. Your options are: 1) Expand root (maybe use growfs and eat into your swap) 2) Avoid building unwanted modules via MODULES_OVERRIDE. Fair enough. This issue just bit me in the behind because I was expecting the 7.1 kernal and modules to take up about as much space as 7.0 ... but then I remember that dtrace found it's way into 7.1 plus a whole lotta code ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
sysinstall automatic partition labelling/sizing problem
Automatic labelling on 7.0 created about 360MB for my root partition on a 8GB disk. After a buildkernel into 7.1-PRERELEASE, the root partition was exhausted during the installkernel. Maybe automatic labelling in sysinstall needs to allocate more than 360MB in the root (/) partition if it's going to stay big enough to accomodate a buildkernel and installkernel from source. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI initiator tester wanted
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 You're correct. I removed lnc from the kernel config and added le, then recompiled the kernel. No more kernel messages about network interfaces. Joe Holden wrote: Nathan Butcher wrote: Danny Braniss wrote: snip lnc0: Missed packet -- no receive buffer Not sure what the cause was. Perhaps I was just thrashing out my virtual NIC... Yeah, thats an issue with the default vmware emulated nic... Ta, Joe -BEGIN PGP SIGNATURE- iD8DBQFGbPFocuckYiL1ACcRAs9DAKDlUlVZRZYEQdL+Vvwul4MkMpdpMACgoMKZ D8Qek1kksPGfij0fDTFuIe4= =/J8n -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI initiator tester wanted
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Danny Braniss wrote: Hi all, I'm in the last mile before crossing the beta-release line, so I'd like to get some input, and update the list of targets it supports. you can obtain the driver from: ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-2.0.92.tar.gz Just tried it out. Set up a vmware FreeBSD 6.2 install on my windows box. Installed the kernel module and initiator program and targeted it at an OpenSolaris machine running ZFS and exporting a 1GB volume over iSCSI on our network. Did a newfs on the imported iSCSI /dev/da0 and mounted it OK. Copied files over to it OK. Ran bonnie++ over it as an experiment. Had the following kernel message pop-up twice, however: lnc0: Missed packet -- no receive buffer Not sure what the cause was. Perhaps I was just thrashing out my virtual NIC... -BEGIN PGP SIGNATURE- iD8DBQFGZ8lGcuckYiL1ACcRAgOcAKCIjdUMGZe+e+eqq6wI5zu20kx5EgCeNO6F MUKU9HSk5IQUFVehTKs9vt4= =gKDc -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
