STILL can't buy a Linux PC easily


 
Thread Tools Search this Thread
The Lounge What is on Your Mind? STILL can't buy a Linux PC easily
# 8  
Old 12-10-2010
Hi Corona688,

Yes, education would be excellent. I'm all for it.

But anybody who's used or watched the use of both OSX on a Mac and Windows on a PC can tell the difference between them. If the option to buy Linux PCs was available and easy, some people would buy. And they would talk. And others would learn a little and some would be curious to ask more questions. There would be a demand for Linux PCs.

But instead, we don't have the freedom to buy (at least in the US). If it's not the direct effort of Microsoft that's keeping them off the market, I wonder what is.
Login or Register to Ask a Question

Previous Thread | Next Thread

4 More Discussions You Might Find Interesting

1. Linux

How to easily identify socket given a PID on Linux?

I have the PID of a process running on Linux mymac 2.6.18-417.el5 #1 SMP Sat Nov 19 14:54:59 EST 2016 x86_64 x86_64 x86_64 GNU/Linux I need to get the ip & port i.e socket details of the given PID (32752). Based on a suggestion on my other thread i tried bash-3.2$ netstat -anpt | grep... (8 Replies)
Discussion started by: mohtashims
8 Replies

2. Shell Programming and Scripting

Easily search file and get line - little problem

hi, file1.txt: cell101 1 20.24.1.1 10 cell101 2 20.24.1.2 20 cell101 3 20.24.1.3 30 cell327 1 20.24.1.4 40 cell327 2 20.24.1.5 50 cell327 3 20.24.1.5 60 ... file2.txt: cell101 1 cell327 1 cell327 3 ... according to values in file2.txt, the script should search lines and get... (7 Replies)
Discussion started by: gc_sw
7 Replies

3. Fedora

Unix which can easily boot from a DVD

Hi, Really sorry if this is in the wrong place etc but I really need some big time newbie help :o I am a recent Maths graduate and have been invited to a 4 day job interview/assessment where I will be taught and tested on the following: "Fedora UNIX, Bash Scripting". Having no experience... (8 Replies)
Discussion started by: Rich147
8 Replies

4. UNIX for Dummies Questions & Answers

how to see all the subdirectories easily?

Suppose I have two directories a and b. Each directory has a few subdirectories, a1 a2 a3 and b1, b2, b3 respectively. Using ls, I can see a and b. Then I need cd a, ls, cd ../b, ls to see all the subdirectories. How to see all the directories and subdirectories easily, say using just one... (2 Replies)
Discussion started by: fld2007
2 Replies
Login or Register to Ask a Question
PARSEDATE(3)						   BSD Library Functions Manual 					      PARSEDATE(3)

NAME
parsedate -- date parsing function LIBRARY
System Utilities Library (libutil, -lutil) SYNOPSIS
#include <util.h> time_t parsedate(const char *datestr, const time_t *time, const int *tzoff); DESCRIPTION
The parsedate() function parses a datetime from datestr described in english relative to an optional time point and an optional timezone off- set in seconds specified in tzoff. If either time or tzoff are NULL, then the current time and timezone offset are used. The datestr is a sequence of white-space separated items. The white-space is optional the concatenated items are not ambiguous. An empty datestr is equivalent to midnight today (the beginning of this day). The following words have the indicated numeric meanings: last = -1, this = 0, first, next, or one = 1, second is unused so that it is not confused with ``seconds'', two = 2, third or three = 3, fourth or four = 4, fifth or five = 5, sixth or six = 6, seventh or seven = 7, eighth or eight = 8, ninth or nine = 9, tenth or ten = 10, eleventh or eleven = 11, twelfth or twoelve = 12. The following words are recognized in English only: AM, PM, a.m., p.m. The months: january, february, march, april, may, june, july, august, september, sept, october, november, december, The days of the week: sunday, monday, tuesday, tues, wednesday, wednes, thursday, thur, thurs, friday, saturday. Time units: year, month, fortnight, week, day, hour, minute, min, second, sec, tomorrow, yesterday. Timezone names: gmt, ut, utc, wet, bst, wat, at, ast, adt, est, edt, cst, cdt, mst, mdt, pst, pdt, yst, ydt, hst, hdt, cat, ahst, nt, idlw, cet, met, mewt, mest, swt, sst, fwt, fst, eet, bt, zp4, zp5, zp6, wast, wadt, cct, jst, east, eadt, gst, nzt, nzst, nzdt, idle. A variety of unambiguous dates are recognized: 69-09-10 For years between 69-99 we assume 1900+ and for years between 0-68 we assume 2000+. 2006-11-17 An ISO-8601 date. 10/1/2000 October 10, 2000; the common US format. 20 Jun 1994 23jun2001 1-sep-06 Other common abbreviations. 1/11 the year can be omitted As well as times: 10:01 10:12pm 12:11:01.000012 12:21-0500 Relative items are also supported: -1 month last friday one week ago this thursday next sunday +2 years Seconds since epoch (also known as UNIX time) are also supported: @735275209 Tue Apr 20 03:06:49 UTC 1993 RETURN VALUES
parsedate() returns the number of seconds passed since the Epoch, or -1 if the date could not be parsed properly. SEE ALSO
date(1), eeprom(8) HISTORY
The parser used in parsedate() was originally written by Steven M. Bellovin while at the University of North Carolina at Chapel Hill. It was later tweaked by a couple of people on Usenet. Completely overhauled by Rich $alz and Jim Berets in August, 1990. The parsedate() function first appeared in NetBSD 4.0. BUGS
1 The parsedate() function is not re-entrant or thread-safe. 2 The parsedate() function cannot compute days before the unix epoch (19700101). 3 The parsedate() function assumes years less than 0 mean - year, years less than 70 mean 2000 + year, years less than 100 mean 1900 + year. BSD
December 20, 2010 BSD