1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA256 |
3 |
|
4 |
|
5 |
In doing some quick google searches, nothing came up in the way of running |
6 |
2.6 on a SPARCStation. How about trying this (as previously suggested by |
7 |
Martin, albeit pretty far down in his post... ;) |
8 |
|
9 |
rm /etc/make.profile |
10 |
|
11 |
ln -s /usr/portage/profiles/default-linux/sparc/sparc32/2006.1/2.4 /etc/make.profile |
12 |
|
13 |
emerge --sync # if you haven't yet |
14 |
|
15 |
emerge -uDav world |
16 |
|
17 |
emerge -av silo |
18 |
|
19 |
|
20 |
brant williams |
21 |
FCAA CDCA 20BC 3925 D634 F5C4 7420 6784 4DEB 6002 |
22 |
|
23 |
|
24 |
|
25 |
On Tue, 18 Sep 2007, Aggelos wrote: |
26 |
|
27 |
> Date: Tue, 18 Sep 2007 00:42:52 +0300 |
28 |
> From: Aggelos <marmango@××××××××.gr> |
29 |
> Reply-To: gentoo-sparc@l.g.o |
30 |
> To: gentoo-sparc@l.g.o |
31 |
> Subject: Re: [gentoo-sparc] emerging of silo fails |
32 |
> |
33 |
> Thanks a lot for your help Martin. ;) |
34 |
> As I said in previous replies, the only problem I face keeping me from |
35 |
> moving to kernel 2.6 is its un-bootable size for sparc32. |
36 |
> |
37 |
> If there is a user running a 2.6 kernel on a sparcstation5 or the like, |
38 |
> I would appreciate it if he can post his .config. |
39 |
> |
40 |
> Aggelos. |
41 |
> |
42 |
> on 09/18/2007 12:11 AM Dereck Martin wrote the following: |
43 |
>> Like I said before, I highly recommend you just use the latest profile |
44 |
>> for the sparc it will give you a 2.6 kernel and such. I don't know the |
45 |
>> reasons why you still need a 2.4 kernel, but if you do still need it |
46 |
>> here is how I would go about setting up a overlay for an older profile. |
47 |
>> |
48 |
>> with an overlay, an emerge --sync doesn't wipe out the profiles or |
49 |
>> packages so it remains in a static state. |
50 |
>> |
51 |
>> I also highly recommend you read the documentation for creating and |
52 |
>> managing ebuilds. Chances are you will need to do "ebuild |
53 |
>> filename.ebuild digest" and some other things when doing this method. |
54 |
>> |
55 |
>> I also for warn that this is probably not a desirable method, but if you |
56 |
>> really want to keep your system in a old profile that isn't maintained |
57 |
>> it is about the only way to do so. |
58 |
>> |
59 |
>> Well if you are looking to preserve an older profile like the recently |
60 |
>> removed 2006.0 profile, you have to get a portage snapshot of a 2006.0 |
61 |
>> profile. |
62 |
>> |
63 |
>> Most of the mirrors have removed the 2006.0 profile, but some haven't |
64 |
>> yet. A good example would be |
65 |
>> |
66 |
>> |
67 |
>> http://gentoo.mirrors.tds.net/gentoo/releases/snapshots/2006.0/portage-20060123.tar.bz2 |
68 |
>> |
69 |
>> Download that portage snapshot and perform the following commands |
70 |
>> |
71 |
>> cd /usr/local |
72 |
>> mkdir portage |
73 |
>> mv /dir-to-downloaded-snapshot/portage-20060123.tar.bz2 . |
74 |
>> tar xjf portage-20060123.tar.bz2 |
75 |
>> |
76 |
>> this will create a portage structure in /usr/local/portage what gentoo |
77 |
>> calls a portage overlay. |
78 |
>> |
79 |
>> Then echo PORTDIR_OVERLAY="/usr/local/portage" >> /etc/make.conf |
80 |
>> |
81 |
>> This will tell portage to recognize the overlay when using emerge and |
82 |
>> stuff. |
83 |
>> |
84 |
>> Then create a symlink to the 2006.0 profile in the |
85 |
>> /usr/local/portage/profiles directory instead of the regular |
86 |
>> /usr/portage/profiles |
87 |
>> |
88 |
>> So it would be like this |
89 |
>> |
90 |
>> rm /etc/make.profile |
91 |
>> ln -s /usr/local/portage/profiles/<path to profile> /etc/make.profile |
92 |
>> |
93 |
>> The only draw back is when you try to emerge certain apps that have been |
94 |
>> completely removed form the current portage distfiles you'll have to |
95 |
>> find the file else where and place it in the distfiles your self. This |
96 |
>> is common for patches and such. Most of the time the ebuild has various |
97 |
>> locations to retrieve the file, and you will have to cross your fingers |
98 |
>> and hope it is in one of the locations. =) |
99 |
>> |
100 |
>> I recommend scouring the gentoo SVN and looking at all ebuild files |
101 |
>> including the deleted ones and downloading the required patches by hand |
102 |
>> found in the "files" directory of the application package you are |
103 |
>> wanting. You will need to do this if an ebuild is unmaintained, like in |
104 |
>> the instance of openMosix |
105 |
>> |
106 |
>> In writing this i noticed that the sparc32 2006.1 profile has a 2.4 |
107 |
>> kernel profile. So you should be good to go at least until next year |
108 |
>> probably. Make sure you /etc/make.profile is linked to that profile |
109 |
>> first and if it is not then you might resolve a lot of problems by doing |
110 |
>> that. |
111 |
>> |
112 |
>> A lot of people do this on a per application basis. Like my self. I |
113 |
>> basically just do this for openMosix and delete all the other data out |
114 |
>> of the portage overlay except the openMosix stuff and the profile. |
115 |
> -- |
116 |
> gentoo-sparc@g.o mailing list |
117 |
> |
118 |
> |
119 |
-----BEGIN PGP SIGNATURE----- |
120 |
Version: GnuPG v1.4.7 (GNU/Linux) |
121 |
|
122 |
iD8DBQFG7v8qdCBnhE3rYAIRCBPkAJ4i82lHP3wqWYQ0Ut/Ahv4V248YtQCffjHK |
123 |
nvjvccP/Kw7SO15+gWSRITE= |
124 |
=E5h5 |
125 |
-----END PGP SIGNATURE----- |
126 |
-- |
127 |
gentoo-sparc@g.o mailing list |