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
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
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
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
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
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
-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
-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:
