Gary G. Hendershot wrote:
> It appears that edits to the instructions for building the disk.img and
> burning the CF card are being made. This is a noble undertaking. I
> struggled to figure out a build pattern that works for me. A good step by
> step document on this would be most useful.
>
> The issues/problems/resolutions I brought up will hopefully provide those of
> you who know what you are doing with some insight into what the unwashed
> masses are struggling with. Stuff that seems mindless and obvious to many
> of you, may indeed be a mystery of the universe some of us.
>
> Derrick is correct about my description of using "makeimage.sh". I
> miss-spoke. Where I get the problem is when I use "dd" to actually copy the
> disk.img to the CF card. This seems to work more reliably when there are no
> pre-existing partitions on the CF card.
>
> I am playing with various sizes for disk.img. This is probably why removing
> previous partitions helps for my situation. Now that you mention it, this
> makes perfect sense. If image size is same, no need to clear old partition.
> Cool.
>
> DD and CAT both work pretty much the same? No significant
> advantage/disadvantage to either. Cool.
>
> Derrick was also correct about the use of "cat" or "dd" against the device,
> not an individual partition. For this one I blame fat fingers on the
> keyboard. Knew what I wanted to say but my devious digits sabotaged me.
>
> These are examples of why I would be hesitant to attempt to modify the
> documentation myself. I fear instructions from me would be more confusing
> than helpful. But I hope the issues I highlighted might help anyone who
> takes this task on to better understand their audience. Many of us out here
> know just enough about what we are doing to be very dangerous.
>
> What I did was create a "cheat sheet". The cheat sheet is just a simple
> text document with the build steps laid out. I quite literally "cut &
> paste" the commands into a terminal window to perform my build. As I don't
> do it everyday, this helps me because a month from now I would have
> forgotten how to do it. My cheat sheet follows.
>
>
> GHendershot's build cheat sheet:
>
>
> Get the latest:
> Start in /root/
>
Don't be root!
Otherwise, dd does have some advantages over cat. Cat is completely
unaware of blocks and does exactly what it is supposed to do (read/write
data). It is the most used (and abused unix command).
Technically speaking dd is preferred over cat for this purpose. dd is
aware of disk blocks and can even do cool things like seek, skip, block
conversions, etc. It's a much better tool for the job although either
will work.
Eventually, we will ahve fakeroot working and a GRUB enabled image will
be selectable from the build system. This is optimal. It will do cool
things like autosize the ext2 partition, etc.
--
Kristian Kielhofner
_______________________________________________
Astlinux-users mailing list
[email protected]
http://lists.kriscompanies.com/mailman/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to [EMAIL
PROTECTED]
