Text 5769, 116 rader
Skriven 2006-04-20 08:12:00 av James Bradley (1:134/77.0)
     Kommentar till en text av Maurice Kinal
Ärende: PPoint in Linux
=======================
Maurice Kinal wrote James Bradley on 04-16-06 20:12

 MK> No real big deal, and everything, including rc
 MK> files, can be configured later once you get it
 MK> installed with 'pkgtool'.  It uses 'dialog' to
 MK> choose options etc.  Very nicely done.

Noted.

 JB> bewildering.
 MK> Don't worry about it.  Just install the 'D'

Like telling a person in free fall, not to worry about the approaching ground?
<G> 

I tried loading everything. The only files that seemed to burn badly, concerned
KDE. I'm sure my life will not be worse for that, but I did want at least the
whole development package, just to simplify my exploration efforts later. When
I discover how large my branches are apt to get, I'll likely return to more
partitions, and streamline the setup then. 

 MK> mencoder is concerned you'll want to add a few
 MK> libs.  You'll get there.

So will Christmas. (-; I just loaded up on laser printers Tuesday, so I'm off
to the lp docs next. Oh, and a USB-sneakernet session seemed to save nothing
from a Lexmark tooth-pulling session. <RRRR!!!> 

You know, the easier and prettier they try to make these sites, the stupider
they seem to be. Ya, `wget' should be a breeze, and an FTP transfer rocks, but
when I start opening a dozen instances of IExporer, I get (No pun!) a little
frustrated. I can see how a regular user of these products could eat up most of
a day procuring what they need, but for me, if I don't have it in forty minutes
I have to come back another day to open the same dozen instances of a browser I
don't really like. I know life could be worse, but equally I know it can be
better than this drunken barn-dance. Maybe they are trying to sell their CD
distribution packages, that tell you exactly how many times to "click on Next".
NEXT!!! Indeed.

Sorry... I feel better now. 

 JB> I think my first chore, is to modify a "theme" so I can get a bigger
 JB> font into the menus.

 MK> :-)  I suppose.

You glib so-and-so. <LOL>

 JB> I read here, <?> about changing run-levels to activate a change made
 JB> something or another. Isn't the run-levels where one selects if they
 JB> load a network config or not, go straight to the GUI login, or reboot
 JB> endlessly? (...) I just envisioned a person could boot to a "no-NIC"
 JB> and if they wanted to plug in a PCMCIA NIC/modem/dock/whatever, they
 JB> go to the next run-level to activate the PC cards.

 MK> Okay.  I've never done it that way so I am not
 MK> sure.  I always did it more or less by hand as
 MK> the connectivity varied from place to place so
 MK> automagic stuff seldom worked for me,

DOS speak, we would copy the two init files we wanted for that session to the
startup files we boot to. Doing so could call any number of customized setups.
Later, it became easier to branch inside the startup files, so one could call
":everything" plus ":Network" or any number of different subsets. Using my
Linux hair-brain-scheme - seeing we are limited to six subsets if we hijack the
GUI stub, and losing two right at the gate - doesn't seem as prudent as I first
imagined. Workable, AFAICT, but a futile study no less when, if bashing about
doesn't solve it, a custom kernel would. Same destination, different paths. (No
pun intended.)

 MK> laptop-wise.  Once I got the appropriate card
 MK> loaded for the connection via pcmcia-cs I had a
 MK> couple bash scripts that I could pass parameters
 MK> to, or they'd look get the parameters via 'cat'
 MK> and/or 'cut', and fire up either dhcpcd or ppp
 MK> and connect.
 MK>  Once that happened then 'ifconfig' would show
 MK> the dynamic ip number of the card and off I'd
 MK> go.  Piece of cake.

There you go with the cake again. You must be a thousand pounds by now. <G+D> 

I'm starting to understand some of the basic functions to bash. Doing so, I am
beginning to appreciate its simplicity. Complexity comes on an as-needed basis.
<G> Do you know of a LDP that encapsulates when to use alias, bash script, or
runscript and the like? A long time ago, I was apt to `alias simple="prog
-option=# ..."' to an executable. I had started writing simple bash scripts to
`less /var/log/dmesg' for myself lately. I know choices are the genius to the
OS, but a FAQ for the intermediate user might be a good thing too.

 MK> I haven't done this in years now as I don't care
 MK> much for laptops.  I think I could do better ...
 MK> with an unlimited budget of course.  :-)

Briefcase Mark III:

'01, a few "Pocket-PC", land in a Cash Converter, and I decide to buy one.
Found a second hand HD. Friend tosses me a CPU. Buy some ram f/ebay at almost a
two-fer. 56K Sportster VDF *external* (WHA???) at Sally Anne for pennies, and
all sorts of USB stuff that cost me like the dirt it was made from. Plug it
into a UPS (or other battery cluster) with vid-goggles, and Bradley can use it
onboard a commercial airplane flight. Because the cord from the cheap-butt
goggles seems pooched, I picked up a cheap-butt LCD so I could again, use it on
a flight. Now, I need a vacation so I can give it a trial run.

No, an unlimited budget is not needed for thousands of man-hours of
entertainment! Since then, the device has seen Mandrake, (2 version, or more)
RH, Fedora, Deb, Mepis, Zen, and now Slack. ...And the fun's just begun! <BWEG>



... 'am' B'ad'
___ MultiMail/Linux v0.47

--- Maximus 3.01
 * Origin: -=-= Calgary Organization CDN (403) 242-3221 (1:134/77)