You are not logged in.
I too think that the tarball release is a great idea...I would however have to counterpoint one of the arguments made above against the current installer:
2) You don't need to worry about arch's install CD having support for your network card (will it be able to do an FTP install if my only network interface is ipw2100?)
You are right, the auto-detecting script might not always catch all network cards, but that doesn't mean you're SOL...you also have the option of selecting it manually, and full use of the other virtual consoles to load whatever you may need.
Offline
I too think that the tarball release is a great idea...I would however have to counterpoint one of the arguments made above against the current installer:
butters wrote:2) You don't need to worry about arch's install CD having support for your network card (will it be able to do an FTP install if my only network interface is ipw2100?)
You are right, the auto-detecting script might not always catch all network cards, but that doesn't mean you're SOL...you also have the option of selecting it manually, and full use of the other virtual consoles to load whatever you may need.
My point is that Arch is not a distro defined by its installer. I bet I'm not the only person on these forums that would recommend taking every Arch developer off the installer projects and reassigning them to pacman, documentation, and infrastructure projects. There are LiveCD projects that have put massive amounts of work into making it boot and autodetect a broad selection of hardware. Why replicate the work, and why suggest that users install from an inferior boot medium?
In the case of Gentoo, the alternative guide to installing from Knoppix was incredibly popular because you have a full desktop environment with networking throughout the installation. With Arch it's a little more work, since you "need" an Arch-specific script in order to install. Mounting the Arch iso as a loopback to access quickinst is a good first step, and the base tarball is the next step.
You really only need a few pieces of information from the user to do an Arch install:
1) which partitions are for Arch?
2) what is the mountpoint for each?
3) what filesystems for partitions other than swap?
<or select autoformat whole drive for Arch>
4) any other bootable partitions?
<or select use existing bootloader>
That's it. It's all about how to get the system on the disk and how to boot it. With this information you can set up fstab and menu.lst (which should be called grub.conf btw). From lsmod (livecd) and /usr/src/linux/.config you can create a zealous (safe) modules section for rc.conf, and that's all you need to ensure a clean standalone reboot. With coldplug/hotplug these days the modules stuff might not be necessary for any hardware devices essential for proper boot.
Installation is really simple. No need to go and make it hard.
Offline
Arch is a meta distribution. ![]()
"Be conservative in what you send; be liberal in what you accept." -- Postel's Law
"tacos" -- Cactus' Law
"t̥͍͎̪̪͗a̴̻̩͈͚ͨc̠o̩̙͈ͫͅs͙͎̙͊ ͔͇̫̜t͎̳̀a̜̞̗ͩc̗͍͚o̲̯̿s̖̣̤̙͌ ̖̜̈ț̰̫͓ạ̪͖̳c̲͎͕̰̯̃̈o͉ͅs̪ͪ ̜̻̖̜͕" -- -̖͚̫̙̓-̺̠͇ͤ̃ ̜̪̜ͯZ͔̗̭̞ͪA̝͈̙͖̩L͉̠̺͓G̙̞̦͖O̳̗͍
Offline
Arch is a meta distribution.
Thankfully other people are gifted in brevity, unlike myself.
Offline
cactus wrote:Arch is a meta distribution.
Thankfully other people are gifted in brevity, unlike myself.
I like how not even that sentence was brief ![]()
Offline
In the case of Gentoo, the alternative guide to installing from Knoppix was incredibly popular
emmmm
Mr Green
Offline
(sorry to be posting to a really old thread - but it seems to be timeless)
Correct me if I'm wrong, I'm an ex-gentoo-arch-noob.
Gentoo allows me to downgrade (for the most part, if the ebuild is available.)
From what I've seen so far, on Arch, you're on your own.
For example. pacman -S fluxbox will get you version 1.0rc3
On gentoo, you get the choice of
1.0_rc3_p4949
1.0_rc3_p4944
1.0_rc3-r3
1.0_rc3-r2
1.0_rc3-r1
1.0_rc3
0.9.15.1-r2
(only the bottom two are considered stable - Jul 10th NZ time)
If I think there's a bug in the latest stable version, on Gentoo I can downgrade say to 0.9.15.1-r2.
In Arch, I'm not sure how easy that is. Gentoo really shines in this regard. Does Arch?
Last edited by ristretto (2007-07-09 23:59:26)
Offline
pacman is designed only to 'upgrade'. I quote because you can upgrade to lower package revisions if you have them... but you have to explicitly state their location. I was going to suggest the nluug.nl mirror as a place to find older packages, but it seems they don't have them anymore. But I'm sure one of them still keeps older ones.
Additionally, you can make your own older packages by changing the version number in a program's PKGBUILD; most of the time, that's all that's required. Once that completes, just 'pacman -U pkg-file' and you've successfully downgraded.
Oh, almost forgot: if you haven't run pacman -Sc(c), look in /var/cache/pacman/pkg/ if you want to downgrade to a previously installed version.
...
Offline
Unfortunately this is a new install. It never had Fluxbox .9 on it, so I can't downgrade locally.
Thanks for the ideas. I'll see if I can build my own .9 package now.
Offline
You can always grab older PKGBUILDs from CVS.
Offline
I've never understood why people say Gentoo is always up to date ; it simply isn't true. Gnome, for example, is still in 2.16. Yes, there are 2.18 ebuilds but there will be little support for anything in testing.
Arch is significantly more up to date in its 'default' form than Gentoo, and on my machine, it's faster as well.
Offline
I don't think *I* said it was up-to-date. I did say there were stable choices of fluxbox that weren't the latest.
Offline
At my eyes arch is more similar to slackware than to gentoo... ![]()
Offline
ristretto: if you want a different version, take a look at abs and changing a PKGBUILD's version to the one you want.
As it is, Arch tends to package the latest stable version.
Offline