You are not logged in.
hey inkaine.. thx
actually it should be an 64 bit laptop, but changing the mirrorlist to i686 repo worked! thx
Offline
Almost a month since release of the latest ISO. And bugs listed after. Will these be fixed, and the new ISOs release for the public? (As in me not being a tester.)
Birger
Offline
Hi. I'm new here. I installed both versions 32 and 64 bits and works pretty good. No errors.
Excuse my poor English.
Offline
Considering that kernel 2.6.28 will ship ext4 as a stable filesystem, will the next release support ext4 in the installation?
Offline
Considering that kernel 2.6.28 will ship ext4 as a stable filesystem, will the next release support ext4 in the installation?
When is 2.6.28 due out? I've been wanting to try ext4 as a more flexible replacement for JFS on my system but didn't want to switch until it was flagged stable.
Offline
andreaorru wrote:Considering that kernel 2.6.28 will ship ext4 as a stable filesystem, will the next release support ext4 in the installation?
When is 2.6.28 due out? I've been wanting to try ext4 as a more flexible replacement for JFS on my system but didn't want to switch until it was flagged stable.
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. Christmas/New Year may affect that though. I am waiting for ext4 and KDE 4.2 to make a new install.
Offline
Will new release include the updated initscripts so that proper bootsplash will be possible?
Offline
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...
Offline
So whats the fix for the root password?
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.
Offline
@Inkaine - I had this problem today. I boot the USB img and either press 'enter' or type 'arch' and get the x86_64 binaries. uname -m shows i686. Thanks for posting a work around.
@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.
Last edited by steve___ (2008-12-04 15:20:05)
Offline
This is a great image to work with. I like how it can boot both 32/64bit, have tar/gzip/sshd/ssh/rsync on the disk which are useful utilities for me to use.
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
Last edited by Tinuva (2008-11-28 10:03:41)
Offline
tpowa, thanks again for your work! I hope that release of archboot will be soon
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
Offline
Yes im still working on archboot, the most issues i see here:
- is the bad mirrorlist bug, which uses 64bit path in ftp installations, also fixed locally here.
- readlink i have to look at, could be that it is not in the binary list.
- lvm symlinks i already inlcuded.
About the usbimage, if you can show me a way to get a sane partition table for it i would be happy.
Offline
I have installed both 32 and 64 bit versions using both the cd and ftp methods with this iso, and so far the only real "issue" I had was the lack of the ntfs stuff in the package selection section. Not really a show stopper, but threw me off the first couple of times I installed cause I couldn't see my 1tb firewire drive and sdb1 both of which were ntfs formatted. Guess I should have payed attention to the package names I selected a little better.
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.
I got nothin'......
Offline
Ok added now readlink and fixed quickinst script.
Thanks for your report.
Offline
ntfs-3g moved to extra and is not part of [core] anymore you have to install it after reboot from [extra] repository
Offline
Dont get me wrong but is there a reason theres 2 isos instead of one that works better than both?
Combining forces and stuff like that..
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.
There shouldn't be any reason to learn more editor types than emacs or vi -- mg (1)
[You learn that sarcasm does not often work well in international forums. That is why we avoid it. -- ewaller (arch linux forum moderator)
Offline
archboot is my project, those isos are not the official ones.
Offline
Yes i know that. But thats not what i asked. Isnt the goal of both ISOs providing an "as perfect as possible" Archlinux installation media?
There shouldn't be any reason to learn more editor types than emacs or vi -- mg (1)
[You learn that sarcasm does not often work well in international forums. That is why we avoid it. -- ewaller (arch linux forum moderator)
Offline
The 'perfect' solution isn't always the same for everyone. I prefer tpowa's ISOs
flack 2.0.6: menu-driven BASH script to easily tag FLAC files (AUR)
knock-once 1.2: BASH script to easily create/send one-time sequences for knockd (forum/AUR)
Offline
finally, fixed the x86_64 selection bug uploading new diff files now, will report when new images are online.
Offline
New files uploaded, please continue in this thread:
http://bbs.archlinux.org/viewtopic.php?id=60385
thanks,
greetings
tpowa
Offline