1 |
On Friday, July 1 at 10:36 (-0500), Harry Putnam said: |
2 |
|
3 |
> Albert Hopkins <marduk@×××××××××××.org> writes: |
4 |
> |
5 |
> > On Tuesday, June 28 at 10:57 (-0400), Albert Hopkins said: |
6 |
> > |
7 |
> >> Anyway, I will rebuild an image with AHCI support and upload it |
8 |
> >> shortly. |
9 |
> > |
10 |
> > Done, uploaded to the same place: |
11 |
> > |
12 |
> > http://starship.python.net/crew/marduk/base-dist.vmdk.bz2 |
13 |
> > |
14 |
> > I also made the image bigger (10GB). Oddly enough, it compresses |
15 |
> > smaller than the other by a couple of megs. |
16 |
> |
17 |
> In case you are interested, I had problems with that appliance. |
18 |
> |
19 |
> [I'm running virutal box] |
20 |
> |
21 |
> I followed James W's walk thru of how to use it with Virtual box. |
22 |
> |
23 |
> There is apparently no `portage' installed which meant that emerge |
24 |
> would fail since /etc/make.profile is a dangling link. |
25 |
|
26 |
Yeah, sorry if I didn't mention before. In the interest of size, I |
27 |
remove the portage tree (and also kernel sources) before creating the |
28 |
image. So in order to do portage-related stuff one must first: |
29 |
|
30 |
# emerge --sync |
31 |
|
32 |
> Once that was |
33 |
> resolved I kept getting really strange output from emerge. It appeared |
34 |
> to be the output of something like vmstat or maybe the upper portion |
35 |
> of `top'. Stuff about user loads and such... right after the first |
36 |
> few lines of emerge output, and nothing was getting emerged. |
37 |
> |
38 |
> Very possible it is pilot error; here is what the output of emerging |
39 |
> gpm looks like: |
40 |
> |
41 |
> Calculating dependencies... done! |
42 |
> [ebuild N ] sys-libs/gpm-1.20.6 USE="(-selinux)" 1,251 kB |
43 |
> |
44 |
> Total: 1 package (1 new), Size of downloads: 1,251 kB |
45 |
> |
46 |
> >>> Verifying ebuild manifests |
47 |
> >>> Emerging (1 of 1) sys-libs/gpm-1.20.6 |
48 |
> >>> Jobs: 0 of 1 complete, 1 running Load avg: 1.75, 1.16, 0.95 |
49 |
> |
50 |
> And there it stays... so emerge does not work. |
51 |
|
52 |
This appears normal to me... |
53 |
|
54 |
Oh perhaps because I have "--jobs=2" in EMERGE_DEFAULT_OPTS |
55 |
in /etc/make.conf. That's what the output normally looks like if you |
56 |
use --jobs... |
57 |
|
58 |
Nevertheless the output definately looks normal (to me). You can change |
59 |
make.conf to suit your tastes. |
60 |
|
61 |
> So it appears, so far, the appliance is not usable on Vbox. |
62 |
|
63 |
Should still be usable. |
64 |
|
65 |
> Oh, I'm referring to the 4GB version. The 10GB version demands a |
66 |
> password so couldn't even start on it. |
67 |
|
68 |
That should not be the case with it requiring a password, or else I |
69 |
uploaded the wrong image. Nevertheless, I'll upload another one |
70 |
shortly. |
71 |
|
72 |
-a |