| 1 |
your seed stage1 was probably corrupt. You need to rebuild |
| 2 |
your seed stage, then build stage2 and stage3 from that... |
| 3 |
As the seed stage I think populates the pam stuff. |
| 4 |
|
| 5 |
-Brad |
| 6 |
|
| 7 |
> On Wed, Feb 25, 2004 at 09:21:07AM -0500, Brad House wrote: |
| 8 |
>> make sure your livecd-stage1 grabs kudzu,hotplug,and livecd-tools |
| 9 |
>> the default-runscript.sh should do an rc-update add autoconfig default |
| 10 |
>> which runs both kudzu and hotplug to auto-detect hardware, then runs |
| 11 |
>> dhcpcd on the network controllers found. |
| 12 |
> |
| 13 |
> Ah. I didn't have kudzu; I'd thought that was x86-specific, so I removed |
| 14 |
> it. |
| 15 |
> It's back in. livecd-tools wasn't in the sparc64 livecd-stage1 I started |
| 16 |
> from, either, so I've re-added it. I use the supplied |
| 17 |
> default-runscript.sh, |
| 18 |
> so that part's fine. |
| 19 |
> |
| 20 |
> I'm still getting the same PAM error, however. I added the line |
| 21 |
> |
| 22 |
> GRP_STAGE23_USE="pam tcpd readline nls ssl gpm perl python berkdb acl |
| 23 |
> ncurses" |
| 24 |
> |
| 25 |
> to the file /etc/make.profile/make.defaults on the system I'm doing these |
| 26 |
> builds on, and reran catalyst stage2, stage3, livecd-stage1, and |
| 27 |
> livecd-stage2, and yet the PAM stuff apparently didn't get picked up. The |
| 28 |
> /etc/pam.d directory on the LiveCD only contains files for screen and |
| 29 |
> sshd. |
| 30 |
> Do I need to start over at stage1? Or, do I need to put that specification |
| 31 |
> somewhere else? |
| 32 |
> |
| 33 |
> -- |
| 34 |
> gentoo-dev@g.o mailing list |
| 35 |
> |
| 36 |
> |
| 37 |
> |
| 38 |
|
| 39 |
|
| 40 |
-- |
| 41 |
gentoo-dev@g.o mailing list |
Archives