David Douthitt wrote:
>
> Matthew Schalit wrote:
> >
> > David Douthitt wrote:
> > >
> > > Matthew Schalit wrote:
> > Just lengthen the timeout to be the same as the previous timeouts,
> > 30 sec's I think, and make the timeout a variable somewhere
> > so that people can set it as short as 2 sec.
>
> That timeout only happens during setup; once you're set up it should go
> away.
Ok the timeout only happends during the first setup, and after that
goes away. That's was my problem. The first time through, I had no idea
that setup was going to run, and it sounded very important. However,
due to the relatively short timeout, I never got a chance to run
setup and was left at a login prompt. I suggest a 30 sec timeout so
that a new user has time to read that far and decide.
> > It wouldn't have been an issue, I'm pretty sure, if the README mentioned
> > that acfg, apkg, setup.sh, and configure.sh were the keys to building
> > the router. I pieced that info together with a few 'find's to get passed
> > my confusion, but that's where the string of clarity broke down.
>
> setup.sh and configure.sh are not "used" in the normal way by a general
> user; a user should never have to know where these scripts are or what
> they are.
> Why do you need to know about configure.sh and setup.sh?
I'm sorry if I've been confusing. Based on experience with 2.9.4,
I could have gotten by without configure.sh and setup.sh. The fact
that there was the option to configure and later an option to setup
conferred the idea to me that Oxygen was either customized to work
differently than 2.9.4 or was built so that success would be achieved
easiest using configure and setup. Either way, it was my best guess
that I'd find glory using configure and setup.
I had no problem with configure. It asked me if I wanted to do
it and I had time to consider that and decide yes. From that point
on I suppose I never would even need to know that configure.sh was
responsible or used.
Then after configure, a whole mess of screen data went by and I was
reading it while the setup (y or n) timeout expired. I had already
made the decision to attempt to set this up, so I was distraught because
I was not given enough time to realize that decision. I missed my
chance to setup.
So at a root prompt, I had no idea what had been missed, and I could
only draw the conclusion that I had a nonfunctional system because I
missed setup. Therefore, I needed to find and run setup.
I hope that's a better explanation.
> > I'll give ya 10 bucks to tell me some more kernel tricks :)
>
> Heh heh.
I was serious :)
> > > > 7) acfg usage.
>
> > > I'm confused.
>
> > It's no biggy. I just booted off one diskette so
> > 1) acfg didn't run after logging in.
> > 2) instead I saw acfg usage.
> > 3) -i option looked nice.
> > 4) I couldn't run acfg -i without loading dialog.lrp and libm.lrp.
> > 5) How do I load those?
> > 6) I didn't know there was also apkg at that point. So I kept looking
> > for acfg options to load packages. It wasn't clear, because I was
> > new and didn't know about the names of the 4 apps you use to setup,
> > apkg, acfg, configure.sh, setup.sh
>
> Ahhh.... this makes more sense I think. However, doesn't the message
> for acfg -i detail that you must load dialog and libm from another disk?
Yes there's that message, but I didn't know about apkg or was getting it
mixed up with acfg.
When I log in I see the motd. The last part of the motd is this:
> Use one of them as your second disk to use the menu based
> configuration utility, or load the two packages dialog.lrp
> and libm.lrp.
>
> usage: acfg -e <pkg> ....
> acfg -a ....
> acfg -h ....
> acfg -i ....
> acfg -l .......
If you simply add "using apkg" as in:
Use one of them as your second disk to use the menu based
configuration utility, or load the two packages dialog.lrp
and libm.lrp using apkg.
Then the new user would be faced with both crucial commands
right there. I sort of wonder if I'm the only one who got
a little confused.
> The readme goes into a lot of detail about apkg; did you read that?
Many times. It didn't help the fact that somehow I got apkg and acfg
intertwined into one command. That confusion was short lived, though.
I'd expect most people would figure it out like I did.
> I don't know which version of Dec. 2000 you used; the recent versions
> force you to read the readme...
I used the Dec 2000 from leaf that I downloaded this week.
I read the files a few times, but didn't study them. I wanted
to dive in and get a feel for it, because I was excited just being
able to make the large diskette and have it boot :)
Is there an Oxygen mailing list somewhere?
Thanks,
Matthew
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
