LinuxQuestions.org Member Success StoriesJust spent four hours configuring your favorite program? Just figured out a Linux problem that has been stumping you for months?
Post your Linux Success Stories here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Yeah!, you knew I could do it...
It take three freash installs to do it, but I did it. I now have Slackware 10.1 up and goin'.
That's rite,THREE. I had to reinstall it to git it to werk rite,but now ev'r'thang works the way it's s'pose to werk.(pat myself on the back) I do this as a hobby to stay busy and I think I did good.
Thanks guys... I am now the proud owner of a Slackware 10.1 'puter.
Say what ya wont to............
+ = my new system
System specs posted in earlier post so I wont boar ya with the details....
Congratulations for getting your Slackware system up and running, although I don't know why it took you three tries to get it running, even my first time with Slackware I got it running at the first install, and I even started out with Slackware, no other distro, and I am still learning more about Linux ....
How about writing correct English so that us non native English speakers don't have to struggle to understand your post Congratulations on getting Slackware to work.
I resent that... Although I am not a native Texan, I have lived in Texas since the age of 4. I don't speak in ebonics, and I am rather annoyed with those who do. Ebonics is not a language, but a form of stupidity. Yes, sure there are those who use slang, and I have used slang too, but in moderation, and there is nothing wrong with using slang here and there, but when someone writes sentences riddled with grammatical errors, that person needs to take an english course. I find it sad really, that there are some foreigners that speak better english than most Americans. Anyways, even if you were to speak with a true native Texan, I would still guarantee you that you would have a better chance of understanding a native Texan, than a person who speak in ebonics. Native Texan = Mostly heavy accent, maybe some changes in grammer, but still understandable. Person who speaks in ebonic = worse than a foreignerr speaking english, its as simple as that, and thats the same with the whole "L33T, SP33K" deal.
Edit: One other thing I would like to add, just hearing some people and the way they speak here in certain parts of the country, maybe the British should come back across the pond, and teach some of these people how to speak their own language. I've heard foreigners speak with better clarity than some people here. Anyways, thats my rant.
Originally posted by Jeebizz I resent that... Although I am not a native Texan, I have lived in Texas since the age of 4. I don't speak in ebonics, and I am rather annoyed with those who do. Ebonics is not a language, but a form of stupidity. Yes, sure there are those who use slang, and I have used slang too, but in moderation, and there is nothing wrong with using slang here and there, but when someone writes sentences riddled with grammatical errors, that person needs to take an english course. I find it sad really, that there are some foreigners that speak better english than most Americans. Anyways, even if you were to speak with a true native Texan, I would still guarantee you that you would have a better chance of understanding a native Texan, than a person who speak in ebonics. Native Texan = Mostly heavy accent, maybe some changes in grammer, but still understandable. Person who speaks in ebonic = worse than a foreignerr speaking english, its as simple as that, and thats the same with the whole "L33T, SP33K" deal.
Edit: One other thing I would like to add, just hearing some people and the way they speak here in certain parts of the country, maybe the British should come back across the pond, and teach some of these people how to speak their own language. I've heard foreigners speak with better clarity than some people here. Anyways, thats my rant.
Speaking is one thing. Typing phoenetically is completely different. You can speak with a Texas accent and be understood. Hell, I live in Tennessee where the accent is thick as well and I can understand most of them. But when one speaks unintelligably or as intelligent as they really are (meaning not very intelligent at all) then I get irritated. And when one types unintelligably and unintelligently then that's something totally different. If you have a Texas accent why does that make you want to type out words using a phoenetic Texas accent? THAT, my friend, is stupid. And to have sentence structure that resembles Ebonics...That is also very very stupid.
Resent it all you want. You just about said the same thing I did in your post about how irritating it is when native English speakers can't speak English properly. My post was just a little shorter than yours in saying it. Talk like an idiot then you get treated like you're an idiot. That's my policy.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.