On 08/11/2014 02:28 AM, Gordan Bobic wrote:
On 08/11/2014 12:28 AM, Robert Moskowitz wrote:
On 08/10/2014 07:06 PM, Gordan Bobic wrote:
On 08/10/2014 11:57 PM, Robert Moskowitz wrote:
In particular I am seeing
/etc/group.rpmnew
/etc/gshadow.rpmnew
/etc/shadow.rpmnew
What should I do with the rpmnew files?
Same thing you would do if it were RHEL, CentOS and Scientific.
_Probably_ delete them.
You have to figure out if there are any new entries and capture those
before you delete them...
Just thought maybe you would say, nothing new here, just move along. :)
That's more or less what I did say, if you sort the files and do a
diff there shouldn't be anytthing particularly different between them,
other than maybe the password hashes (or lack thereof).
My build process is working. I have done it 3 times. I have not only
what it takes to go from 'scratch', but my saved tar files from F19 so
others can benefit. Even xz image for the minimual that can just be
xzcat on to an 8Gb card and go. Next will be the xz that will be
current for updates as of today.
If you are using an image, please make sure you do:
dd if=/dev/zero of=/scrub bs=8MB; rm -f /scrub
Now I am thinking clearer, and I prepared the SDcard with:
dd if=/dev/zero of=/dev/sdb bs=1M
Then laid down the partition table and partitions. So I think the
'minimal' image is as tight as it is likely to be. And it is only 70Mb
larger than your tarball plus it contains all the F19 Cubieboard files.
Only complaint can be that my sdb3 partition is larger perhaps than needed.
before you create the image to zero out the free space. That is one of
the reasons I don't use images. The other is that block devices are
always of slightly different sizes, so you have to make a minimal
partition and the user has to resize it after the first boot.
I already did the first boot, at least for Cubieboard 2 (others may thus
require another 1st boot, and maybe have to start with the tarballs).
So I might think you run the xzcat, resize, then boot away.
A better way, IMO, is gdisk instructions (possibly a text file you can
pipe into it sgdisk?) plus a tar ball as it generally results in a
smaller file.
I am getting exhausted. I DID try and figure out gdisk, but went with
parted.
Of course these files will need homes.
Happy to put them on the download server.
I would say the F19 tarballs and the minimal compressed image are
ready. The updated image, I have to run that zeroing stuff and try
again. 1Gb is too big.
The minimal xz is 446Mb. I did
not use any xz options, just ran it. Though I zeroed out the SDcard
before building so it would compress as well as possible with defaults.
Deleting the log files and zeroing out the free space after creating
the image should also help.
Will do.
_______________________________________________
users mailing list
[email protected]
http://lists.redsleeve.org/mailman/listinfo/users
