On 16/09/12 13:12, Steven Chamberlain wrote:
[...]
> You might see more clearly what ifup is doing with the -v switch.
>
> It looks like a different error happens first.
Yep; turns out that dhclient is failing because the device has failed to
be initialised because wpa-supplicant is confused. I t
When trying to make wireless work on my eee 701, trying to ifup the
interface produces:
ifconfig: ioctl (SIOCAIFADDR): Invalid argument
Can't attach interface ath0 to bpf device /dev/bpf0: No such device or
address
Failed to bring up ath0.
/dev/bpf0 is present but doesn't appear as if there's a d
On 07/09/12 23:28, Steven Chamberlain wrote:
[...]
> Now with softupdates, metadata changes might cancel out in-memory and
> they get written out a whole block at a time, so write latency is hardly
> relevant any more.
Yup, that seems decidedly plausible. Turns out that the spinning disk on
the am
On 07/09/12 13:23, Steven Chamberlain wrote:
[...]
> Plain UFS could be expected to be slow. Because it is unjournalled, I
> think metadata updates are forced to be synchronous.
On my amd64 box, plain UFS goes like greased lightning --- I was very
impressed. That's a much more modern hard drive,
I've tried installing kFreeBSD on an eee 701 laptop I had spare. While
it runs fine and the installation went flawlessly, it took about three
hours to do the bare-bones installation...
Investigation shows that something very odd is going on with the
filesystem. While dd to files shows respectable
I notice that the Linux UFS driver in the Debian kernels is compiled
with UFS2 write support disabled.
This would appear to be because write support is considered
experimental. However, it would apppear that it's been like this since
*at least* 2009.
Does anyone know what the current status of th
On 25/08/12 22:20, Steven Chamberlain wrote:
[...]
> I already suspected that grub-probe is having trouble with msdos
> extended partitions, at least with ZFS.
[...]
msdos extended partitions are apparently very special. Alas, I run XP,
and need five partitions on that disk, so I don't really have
On 19/08/12 12:13, Steven Chamberlain wrote:
[...]
> Although I think it might be better to use the slightly larger 'netinst'
> image, and fetch it via jigdo (so your caching proxy can cache the
> individual deb/udeb files it builds the ISO from) :
>
> http://cdimage.debian.org/cdimage/daily-build
On 11/08/12 21:13, Steven Chamberlain wrote:
[...]
> That could be the recently-fixed grub-installer bug (#613430: /proc not
> mounted in the target); unfortunately the fix didn't make it into the
> beta1 installer, but it should be fixed in sid_d-i daily builds;
>
> http://cdimage.debian.org/cdi
I've just tried to install kFreeBSD, to give it a try. I have a
dual-boot Windows/Linux-Debian system, and was using a spare partition.
I was using the FreeBSD 9 mini.iso image.
The installation worked fine, but I don't actually have a running
system. Issues include:
- I had some trouble finding
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florian Weimer wrote:
[...]
> Is ZFS producton-ready? On Solaris, Sun recommends to reformat and
> restore from backup should your system panic on boot:
Personally, I find the following comment from the FreeBSD ZFS tuning
guide most scary:
> To use
ure these were
all due to my dodgy hardware, but I still wouldn't recommend kfreebsd-6
to anyone.
Has the installer been upgraded to use kfreebsd-7 yet?
- --
David Given
d...@cowlark.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Moz
David Given wrote:
[...]
> For the second, the supplied FreeBSD kernel only appears to include the
> fwe driver, which is alas non-standard. I'd need the fwip driver in
> order to interoperate with Linux. Is there any reason why fwip isn't
> built other than that nobody
David Given wrote:
> I'd like to experient with d/bsd as I think it's an extremely
> interesting idea, and one I've been looking for for a while.
Damn. Sorry, that wasn't supposed to arrive twice --- I posted from the
wrong account and thought it'd be bounced.
ude the
fwe driver, which is alas non-standard. I'd need the fwip driver in
order to interoperate with Linux. Is there any reason why fwip isn't
built other than that nobody's needed it before --- as it is rather
niche? If not, can anyone point me at a guide on how to build and
instal
I'd like to experient with d/bsd as I think it's an extremely
interesting idea, and one I've been looking for for a while.
Unfortunately, my test hardware is rather elderly and is a bit lacking
in ports. This means that my only networking options are wireless, and
I'm a WPA shop not a WEP one, or
16 matches
Mail list logo
