thanks,
greetings
tpowa
IMO the official iso is better than this one but its far from perfect. In fact both missing features the other one has and vice versa.
]]>My only question is, was there a reason the ntfs packages were removed from the package list?
Otherwise, I am happy with with my nice new 64bit install.
]]>About the usbimage, if you can show me a way to get a sane partition table for it i would be happy.
]]>And here is the description of a bug I found:
quickinst script doesn't check whether the "pacman -Sy base" succeeded or not. Due to this quickinst always returns 0 (ok) no matter what result of "pacman -Sy base" was.
I think, it's a bug, because it isn't possible for user to identify that installation failed from outside of the quickinst (for example from custom script using quickinst as installer).
Please fix this bug in release (along with "readlink -f" bug ). Here is somewhat like patch:
if [ "$INSTMODE" = "ftp" ]; then
$PACMAN -r $DESTDIR --config /tmp/pacman.conf -Sy base || {
echo
echo "Package installation FAILED."
echo
exit 1
}
fi
What I'd like to know, how can one customize this image? (I downloaded the usb image file) I can't mount the disk on a regular linux system, at least not the normal way.
I would like to customize it a bit as I boot up from this image a lot and just want to customize a few things to make like a bit easier for myself when creating/dumping OS images from linux systems I work with. Instead of using software like acronis ect I like to just tar up the whole OS while booted from a usb stick and send it over the network to a remote system for storage. Eg:
tar cfzv - . | ssh root@10.0.0.12 "cat > /mnt/images/servername-20081121.tgz"
For example this is what fdisk shows me:
wadavid mnt # fdisk /dev/sdc -l
Disk /dev/sdc: 8254 MB, 8254390272 bytes
254 heads, 62 sectors/track, 1023 cylinders
Units = cylinders of 15748 * 512 = 8062976 bytes
Disk identifier: 0xb0bcd68eThis doesn't look like a partition table
Probably you selected the wrong device.Device Boot Start End Blocks Id System
/dev/sdc1 ? 204685 220349 123339962 78 Unknown
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(518, 102, 15) logical=(204684, 50, 50)
Partition 1 has different physical/logical endings:
phys=(743, 0, 62) logical=(220348, 103, 15)
Partition 1 does not end on cylinder boundary.
/dev/sdc2 ? 27488 76744 387841909+ 10 OPUS
Partition 2 has different physical/logical beginnings (non-Linux?):
phys=(205, 7, 0) logical=(27487, 94, 14)
Partition 2 has different physical/logical endings:
phys=(920, 235, 50) logical=(76743, 99, 34)
Partition 2 does not end on cylinder boundary.
/dev/sdc3 ? 118718 240589 959615034 8b Unknown
Partition 3 has different physical/logical beginnings (non-Linux?):
phys=(260, 125, 54) logical=(118717, 116, 56)
Partition 3 has different physical/logical endings:
phys=(893, 46, 60) logical=(240588, 206, 35)
Partition 3 does not end on cylinder boundary.
/dev/sdc4 ? 1911 2439 4161536 a OS/2 Boot Manager
Partition 4 has different physical/logical beginnings (non-Linux?):
phys=(269, 111, 50) logical=(1910, 37, 51)
Partition 4 has different physical/logical endings:
phys=(0, 0, 0) logical=(2438, 168, 56)
Partition 4 does not end on cylinder boundary.Partition table entries are not in disk order
@Don-DiZzLe - it sounds like you're getting the same error. Have a look at your pacman cache (ls /var/cache/pacman/pkg/) to confirm.
]]>chroot: cannot run command 'passwd': Exec format error
If i cant set the root password, then i cant login after the installation is done since chroot also does not work.
]]>The recent linux kernel release cycles have been a little under 3 months, and .27 was released mid-October - so that would make it early January.
It seems it might even be earlier. At Phoronix they already speculate with early to mid December. And given the regular release schedule with one rc per week, 8 rc's before final this is a realistic expectation.
But back on topic regarding test install img's. What's different to previous images (I had used both the 2008.3 and 2008.6 img files at least once each) is that after dd'ing them to the usb stick you cannot shrink the partition and create another one on the stick anymore. But you cannot write anything onto the install partition either. Thus you lose alot of capacity. I just bought a new one today after my previous broke - 2 GB is the smallest you can get nowadays and 4 GB was even cheaper. What a waste...
]]>