As far as I know, the number of heads and sectors-per-track bximage
reports is just a convenient fiction. Cylinders * heads * spt *
512(block size) = image size.
Why do you need that specific geometry?
Terry
Philip A. Prindeville wrote:
> I'm trying to "pre-image" Astlinux for a CF of a given
I'm trying to "pre-image" Astlinux for a CF of a given size and geometry, but
when I do:
./bximage -q -hd -mode=flat -size=1953 runnix.img
fdisk reports back to me that the partition table of the image runnix.img is
C=3968, H=16, S=63.
I need it to be H=64, S=63 to be correct.
Anyone know how
Running it now on net4801... Smooth install, great additions to web interface
and under the hood, everything works. AWESOME job guys
- Original Message
From: Darrick Hartman
To: AstLinux Users Mailing List ;
AstLinux Developers Mailing List
Sent: Sun, November 1, 2009 8:58:24 PM
Further 0.7 observations...
1. Migration from Zaptel to DAHDI following astlinux.org documentation
seems to have worked perfectly.
2. The VPMADT032 (or whatever it's called) hardware echo-canceller
which comes with the TDM410P looks as though it works out of the box
(as far as dmesg is concerned
Thanks for the fix, Lonnie. Interestingly, I have read at least one
opinion that IE's placement of the scrollbar within the element is
correct, and other browsers are those which are incorrectly
interpreting the CSS spec. I think this is the best solution for now,
and is likely to have a long enoug
