It is not forcing, it is having a message sink into stubborn blindfold brains. *gg*
Yes, you are right, a message should be worded so that the receiver can remember it.
But we know, that outta there are way enough lads with their brains shut down to doze mode - a well placed shout aka *wake up* is always a good means to draw attention upon something.
You see, it is something completely different (tm). Not forcing but making sure that a message is received and able to sink in. What the recipient does with the message is another story.
stay safe. You are right. I just have another point of view upon the whole thing.
ps: In real life you 'd need to shout to me anyway for I wouldna understand something spoken in low voice.
Kernel Compiling Problems
Re:Kernel Compiling Problems
I seriously doubt the usefulness of this. The http://www.cygwin.com/setup.exe approach has the advantage of always giving you up-to-date packages, and you only have to download what you want to install (instead of the whole thing, which is rather huge).beyond infinity wrote: I could put a CD_ROM image online on my web-site to download for the Not-Cygwin fanatics: it is the whole cygwin installation tree xfree86 included. I'll see to it...
The Cygwin setup procedure is hard to beat in usefulness.
Now there's a point. Just provide the howto and leave the distro to RedHat.It also contains a howto: how to install this stuff and get basic x services shared thou' the LAN.
Every good solution is obvious once you've found it.
-
BI lazy
Re:Kernel Compiling Problems
biasing is sometimes ... well, no words.
it doesn't work out. I 've got only 100 mb webspace and the *compressed* package I've compiled for my own private and business usage is about 160 MB. So, no chance to get it online. *sigh*
useability:
Imagine you install cygwin on several computers. Having to retrieve the packages from the remote server via slow internet connections for each and every install is like a pain in the @$$. Retrieve them once, burn them on a cdrom or put expose them in a samba share (i've done both and it works with eleganza) and do the software population thing without much hassle. Think it from the Net Admin side of things.
it doesn't work out. I 've got only 100 mb webspace and the *compressed* package I've compiled for my own private and business usage is about 160 MB. So, no chance to get it online. *sigh*
useability:
Imagine you install cygwin on several computers. Having to retrieve the packages from the remote server via slow internet connections for each and every install is like a pain in the @$$. Retrieve them once, burn them on a cdrom or put expose them in a samba share (i've done both and it works with eleganza) and do the software population thing without much hassle. Think it from the Net Admin side of things.
Re:Kernel Compiling Problems
100% d'accord. That's why the first question of the setup.exe is:BI lazy wrote: Imagine you install cygwin on several computers. Having to retrieve the packages from the remote server via slow internet connections for each and every install is like a pain in the @$$.
* Install from Internet
* Download from Internet
* Install from local Directory
Every good solution is obvious once you've found it.