1 |
Thanks a lot for your help Martin. ;) |
2 |
As I said in previous replies, the only problem I face keeping me from |
3 |
moving to kernel 2.6 is its un-bootable size for sparc32. |
4 |
|
5 |
If there is a user running a 2.6 kernel on a sparcstation5 or the like, |
6 |
I would appreciate it if he can post his .config. |
7 |
|
8 |
Aggelos. |
9 |
|
10 |
on 09/18/2007 12:11 AM Dereck Martin wrote the following: |
11 |
> Like I said before, I highly recommend you just use the latest profile |
12 |
> for the sparc it will give you a 2.6 kernel and such. I don't know the |
13 |
> reasons why you still need a 2.4 kernel, but if you do still need it |
14 |
> here is how I would go about setting up a overlay for an older profile. |
15 |
> |
16 |
> with an overlay, an emerge --sync doesn't wipe out the profiles or |
17 |
> packages so it remains in a static state. |
18 |
> |
19 |
> I also highly recommend you read the documentation for creating and |
20 |
> managing ebuilds. Chances are you will need to do "ebuild |
21 |
> filename.ebuild digest" and some other things when doing this method. |
22 |
> |
23 |
> I also for warn that this is probably not a desirable method, but if you |
24 |
> really want to keep your system in a old profile that isn't maintained |
25 |
> it is about the only way to do so. |
26 |
> |
27 |
> Well if you are looking to preserve an older profile like the recently |
28 |
> removed 2006.0 profile, you have to get a portage snapshot of a 2006.0 |
29 |
> profile. |
30 |
> |
31 |
> Most of the mirrors have removed the 2006.0 profile, but some haven't |
32 |
> yet. A good example would be |
33 |
> |
34 |
> |
35 |
> http://gentoo.mirrors.tds.net/gentoo/releases/snapshots/2006.0/portage-20060123.tar.bz2 |
36 |
> |
37 |
> Download that portage snapshot and perform the following commands |
38 |
> |
39 |
> cd /usr/local |
40 |
> mkdir portage |
41 |
> mv /dir-to-downloaded-snapshot/portage-20060123.tar.bz2 . |
42 |
> tar xjf portage-20060123.tar.bz2 |
43 |
> |
44 |
> this will create a portage structure in /usr/local/portage what gentoo |
45 |
> calls a portage overlay. |
46 |
> |
47 |
> Then echo PORTDIR_OVERLAY="/usr/local/portage" >> /etc/make.conf |
48 |
> |
49 |
> This will tell portage to recognize the overlay when using emerge and |
50 |
> stuff. |
51 |
> |
52 |
> Then create a symlink to the 2006.0 profile in the |
53 |
> /usr/local/portage/profiles directory instead of the regular |
54 |
> /usr/portage/profiles |
55 |
> |
56 |
> So it would be like this |
57 |
> |
58 |
> rm /etc/make.profile |
59 |
> ln -s /usr/local/portage/profiles/<path to profile> /etc/make.profile |
60 |
> |
61 |
> The only draw back is when you try to emerge certain apps that have been |
62 |
> completely removed form the current portage distfiles you'll have to |
63 |
> find the file else where and place it in the distfiles your self. This |
64 |
> is common for patches and such. Most of the time the ebuild has various |
65 |
> locations to retrieve the file, and you will have to cross your fingers |
66 |
> and hope it is in one of the locations. =) |
67 |
> |
68 |
> I recommend scouring the gentoo SVN and looking at all ebuild files |
69 |
> including the deleted ones and downloading the required patches by hand |
70 |
> found in the "files" directory of the application package you are |
71 |
> wanting. You will need to do this if an ebuild is unmaintained, like in |
72 |
> the instance of openMosix |
73 |
> |
74 |
> In writing this i noticed that the sparc32 2006.1 profile has a 2.4 |
75 |
> kernel profile. So you should be good to go at least until next year |
76 |
> probably. Make sure you /etc/make.profile is linked to that profile |
77 |
> first and if it is not then you might resolve a lot of problems by doing |
78 |
> that. |
79 |
> |
80 |
> A lot of people do this on a per application basis. Like my self. I |
81 |
> basically just do this for openMosix and delete all the other data out |
82 |
> of the portage overlay except the openMosix stuff and the profile. |
83 |
-- |
84 |
gentoo-sparc@g.o mailing list |