i586 setup steps

3z · 2004-02-17 06:26:09

I've successfully setup AL using the i586 floppy image thru FTP Install using the i586 repo at ftp://ftp.archlinux.org/testing/i586

Machine: AMD K6-2 350 Mhz

Steps:
- Get the floppy image from ftp://ftp.archlinux.org/testing/i586/floppy_images
- Boot those floppies following the installation guide, boot-root-modules
- Run /arch/setup (still same with the installation guide)
- Before step 2.3 FTP Install #6, Select Packages, goto 2nd console (Alt-F2) and search for pacman.conf
(can't remember the exact dir, i think is some temp folder)
- Edit pacman.conf at the [current] repo to ftp://ftp.archlinux.org/testing/i586 and comment out the rest, so that u will get the i586 packages instead of the normal i686 packages
- Continue installation follow the guide (Alt-F1) until finished

Note:
Once successful installed AL, edit the /etc/pacman.conf to point to i586 repo like:
ftp://ftp.archlinux.org/testing/i586
ftp://ftp.ibiblio.org/pub/Linux/distrib … ting/i586/
or other mirrors

Inputs are welcome..
..and AL rocks!!

3z · 2004-02-17 06:32:47

:arrow: Have some Q though

I notice the i586 repo (ftp://ftp.archlinux.org/testing/i586) has some packages that are not in the current.db

Does that mean I'll need to download manually and install??

:arrow: Suggestion
- Maybe the maintainers can update the floppy image so the pacman can get from i586 repo directly
- Update the current.db for i586

just notice this thread is more suitable to be posted in User Contributions

sarah31 · 2004-02-17 06:36:16

post install:

make sure that your pacman.conf remains pointed to the the repo above (ftp.archlinux.org/testing/i586)

make sure you edit your /etc/makepkg.conf and change the i686 references to i586.

you will have to build everything yourself and put it in a local repo as i586 is, when i last heard, undeveloped.

take great care when building to make sure teh PKGBUILD has no hard coded i686 references.

sarah31 · 2004-02-17 06:39:07

3z wrote:

:arrow: Suggestion
- Maybe the maintainers can update the floppy image so the pacman can get from i586 repo directly
- Update the current.db for i586

it is not currently being developed. nothing has been done on it since i last worked on it in very early december.

3z · 2004-02-17 14:05:17

may I know where to look for process of building packages for i586??

and is the packages updated as frequent as the i686 repo?? how many maintainers r there??

3z · 2004-02-17 15:03:38

i think an example would be easier to follow

let's say now I need i586 package for wireless_tools which is in the extra repo, which most probably won't be ported to the i586 repo.

what's the steps needed to compile the wireless_tools into i586 package, and how do I contribute it back to the i586 repo so other can use??

sarah31 · 2004-02-17 16:29:36

as i said i586 is unmaintained and is almost three months behind i686.

there have been no packages upgraded since early december.

there are no maintainers for i586 and i have no idea how you can contribute to it since it is wildly out of date already.

apeiro · 2004-02-17 23:50:02

sarah31 wrote:

as i said i586 is unmaintained and is almost three months behind i686.

Yea, the packages on the ftp site haven't been touched much. I do have a box at home that keeps the 586 current set more-or-less up to date. I'll update the servers' packages in the next week or so, after I've got the disk images updated for 0.6.

andy · 2004-02-18 00:52:21

Cool !
Isn't it a waste to compile all the packages and then just use them for *one* machine ;-) ....

apeiro · 2004-02-18 02:00:57

Oh yes, quite. But I'm building them on an i686 machine, so I wanted to test them all on an i586 one first, before releasing them to the rest of you. Just to make sure they work n' all.

3z · 2004-02-18 03:09:20

i think it wont be just *one* machine..

a lot of ppl are having old pc/notebook that lying around doing nothing and would like to make use of it like me.

I think AL is good with its minimum distribution and easy maintainance, it would be nice to use it for reviving those old hardware as router/firewall/server/..

:?: Anyway, my Q are not answered yet:
- How to build i586 packages? or where to find the info

Who knows.. I might have the time to update and test i586 packages and become the 'official i586 maintainer'

sarah31 · 2004-02-18 03:15:53

you build them with abs and makepkg.

the only thing to make sure of is that your makepkg.conf has i586 and not i686 CFLAGS/CXXFLAGS.

you have to make sure the builds do not have static references to i686.

you have to be sure that no k6 code sneaks in either.

read the arch manual and that will give you an idea on what needs to be done.

maintain i586 on your own (even with kde and gnome removed from current) takes a lot of time and you have to be able to trouble shoot when a build fails.

since you are using the builds (in most cases) that are also used for i686 you have to be able to commnunicate with the package maitainers and if they are busy you have to be willing to fix the package yourself then file a bug with the fix.

it took me two months to rebuild the entire testing tree you now are using.

3z · 2004-02-18 04:14:26

well done!

anyway, starting to read the ABS
if I've Q, where is the proper thread for ABS??

sarah31 · 2004-02-18 04:27:41

i suppose you can ask questions in the makepkg forum or even visit occasionally on the irc channel and get help/ ask questions live with developers and other users.

phunni · 2004-05-05 16:21:06

sarah31 wrote:

as i said i586 is unmaintained and is almost three months behind i686.
there have been no packages upgraded since early december.
there are no maintainers for i586 and i have no idea how you can contribute to it since it is wildly out of date already.

So - is i586 maintained now? I was planning on installing it on my home LAN server this evening, but I might not bother if it's way out of date

That said - it's got to be more up to date than my current Mandrake 9.0 installation...

link · 2004-08-01 12:14:53

Doesn't look like its maintained. The packages are still from December.
I'd be very interested in donating some CPU time to building i586 packages. Is it possible to become an Arch Linux "ports" maintainer? Similar to Debian's porters. How much interest is there in a i586 port to begin with. It seems like its kinda of a small following.

Xentac · 2004-08-03 05:23:56

My current i586 repo is almost 100% up to date (current that is). As it stands, the system doesn't scale well, so it only works with my one build machine.

I will put in the time (sometime) to make it distributed.

Because it's the beginning of the month, I can actually get Judd to start mirroring my repo...

Arch Linux

#1 2004-02-17 06:26:09

i586 setup steps

#2 2004-02-17 06:32:47

Re: i586 setup steps

#3 2004-02-17 06:36:16

Re: i586 setup steps

#4 2004-02-17 06:39:07

Re: i586 setup steps

#5 2004-02-17 14:05:17

Re: i586 setup steps

#6 2004-02-17 15:03:38

Re: i586 setup steps

#7 2004-02-17 16:29:36

Re: i586 setup steps

#8 2004-02-17 23:50:02

Re: i586 setup steps

#9 2004-02-18 00:52:21

Re: i586 setup steps

#10 2004-02-18 02:00:57

Re: i586 setup steps

#11 2004-02-18 03:09:20

Re: i586 setup steps

#12 2004-02-18 03:15:53

Re: i586 setup steps

#13 2004-02-18 04:14:26

Re: i586 setup steps

#14 2004-02-18 04:27:41

Re: i586 setup steps

#15 2004-05-05 16:21:06

Re: i586 setup steps

#16 2004-08-01 12:14:53

Re: i586 setup steps

#17 2004-08-03 05:23:56

Re: i586 setup steps

Board footer