- WLUG - wlug.mailman3.com

Re: [Wlug] 2 month + Linux Kernel consulting job

by Josh Huber

Lee Keyser-Allen <lkeyser(a)WPI.EDU> writes: > Doh.. damn reply-to: address Indeed, it's pretty interesting that even after several people have accidentally posted private messages to the list this broken header munging still takes place. On a technical list no less! ttyl, -- Josh Huber

May 9, 2002

Re: [Wlug] 2 month + Linux Kernel consulting job

by Lee Keyser-Allen

Doh.. damn reply-to: address :P -- Lee Keyser-Allen lkeyser(a)wpi.edu WPI CS 2002

May 9, 2002

Re: [Wlug] 2 month + Linux Kernel consulting job

by Lee Keyser-Allen

On Thu, 9 May 2002, Greg Donovan wrote: > We are seeking a consultant to perform some work for a customer of ours > leveraging Linux kernel and SCSI skills. It is a two month+ assignment with > a customer here in the Boston area. The work would be performed full time > on our customer's site. Here is a brief description of the work: What is the approximate time frame for this job (when would it start?) I have extensive Linux driver development experience, but I wouldn't be available until mid-july. If that still works for you, you can find my resume at http://www.jumblebox.com/~lkeyser/resume.html Cheers, Lee -- Lee Keyser-Allen lkeyser(a)wpi.edu WPI CS 2002

May 9, 2002

2 month + Linux Kernel consulting job

by Greg Donovan

Dear WLUG, Thank you for allowing me to send this communication to your members. Optimal Engineering Partners provides embedded software and hardware development expertise within the communications, wireless, storage, and medical industries. Cumulatively the founding employees of Optimal Engineering possess many years of knowledge and contacts within these sectors, and the extent of our expertise within this space will be evident in the quality and responsiveness of the services we provide. We are seeking a consultant to perform some work for a customer of ours leveraging Linux kernel and SCSI skills. It is a two month+ assignment with a customer here in the Boston area. The work would be performed full time on our customer's site. Here is a brief description of the work: Our client is completing a port of Linux 2.42 to their fault tolerant platform and need assistance in finishing the effort. Must have strong debugging skills, storage SCSI or Fiber Channel and Linux kernel experience. Linux SCSI is a major plus. Please feel free to contact me if you or someone you know might be a match for this role. We pay a generous referral fee. Thank you. -Greg Greg Donovan OPTIMAL ENGINEERING PARTNERS "Resources and Expertise for Embedded Systems Development" (978) 256-1113 ext 103 gdonovan(a)optimaleng.com

May 9, 2002

Re: [Wlug] stderr v. stdout

by jkinz＠ultranet.com

On Thu, May 09, 2002 at 09:41:07AM -0400, Bill Mills-Curran wrote: > I can't believe I'm revisiting this yet again... I'm struggling with > identifying "standard practice" for deciding when to write to stdout > v. stderr. In particular, I'm working with processes associated with > software maintenance (building, copying, SCM, etc.). I'd love to find > a definitive whitepaper on the subject. Does anyone have any Bill - I don't think I've ever seen a whitepaper addressing this particular subject, but the standard practice is very easy to identify. I have a very straightforward approach to this issue. 1. For all Unix commands - say nothing unless the command fails or encounters an error condition. All error messages go to stderr. 2. For all filters (programs which produce output on stdout) only the normal program output goes to stdout. Many normal Unix commands can be used as filters. Like "ls" for example. All error messages go to stderr. 3. Any debugging info activated by command line options or environment variables should go to stderr. For tools used in building software, like "make" emulate make's behavior which follows rule 1 above. Commands executed by make are echoed to stdout and all diagnostic info is directed to stderr. If you invoke the following makefile with the command "make 1>/dev/null" you will see only the diagnostic output. Invoked by just "makefile" gives you both. ###### Makefile starts here. all: boo foo boo: echo "stdout OUTPUT" > /dev/null foo: glarf STDERR ONLY nadba ############# makefile ends here.

May 9, 2002

stderr v. stdout

by Bill Mills-Curran

I can't believe I'm revisiting this yet again... I'm struggling with identifying "standard practice" for deciding when to write to stdout v. stderr. In particular, I'm working with processes associated with software maintenance (building, copying, SCM, etc.). I'd love to find a definitive whitepaper on the subject. Does anyone have any pointers? TIA, Bill

May 9, 2002

Re: [Wlug] timezone

by Baris Hasdemir

yes it has timeconfig baris On Wed, 8 May 2002 12:57:00 -0400 (EDT) Karl Hiramoto wrote: > > It's been a couple of years since i've used slack. > > But redhat has a util called "tzselect" > debian has a util called "tzconfig" > > does slack have anything similar? > > > On Wed, 8 May 2002, Baris Hasdemir wrote: > > > hi, > > > > I have a strange-for-me problem. I am one of those paranoid guys, who has > > added"ntpdate time.nist.gov" to the crontab to be executed every day. > > > > the problem is that, every night the system time is set 1 hour earlier of > > the actual time. i.e it is executed at 23:00 and is set to 22:00 after > > ntpdate, as far as I could observe. I am pretty confused about the subject. > > Tried different timezone names, etc, hence more confused. > > > > I also have a problem with the name of the timezone. which timezone name do > > you choose guys? US/Eastern? America/Newyork? GMT+5? EST? EDT? or any other? > > I am using slackware-current. set the timezone to America/New_York and > > whenever I send a mail, sylpheed shows my timezone as GMT-4 and > > #date > > shows my timezone as EDT. > > > > any comments. other than removing the crontab job? :) > > > > thanks, > > baris > > _______________________________________________ > > Wlug mailing list > > Wlug(a)mail.wlug.org > > http://mail.wlug.org/mailman/listinfo/wlug > > > > -- > > ¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø > Karl Hiramoto <karl(a)hiramoto.org> > Work: 978-425-2090 ext 25 > Cell: 508-517-4819 > Personal web page: http://karl.hiramoto.org/ > Zoop Productions: http://www.zoop.org/ > KTEQ Rapid City: http://www.kteq.org/ > AOL IM ID = KarlH420 > ¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø > > To generalize is to be an idiot. > -- William Blake > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > >

May 8, 2002

Re: [Wlug] timezone

by Karl Hiramoto

It's been a couple of years since i've used slack. But redhat has a util called "tzselect" debian has a util called "tzconfig" does slack have anything similar? On Wed, 8 May 2002, Baris Hasdemir wrote: > hi, > > I have a strange-for-me problem. I am one of those paranoid guys, who has added > "ntpdate time.nist.gov" to the crontab to be executed every day. > > the problem is that, every night the system time is set 1 hour earlier of the > actual time. i.e it is executed at 23:00 and is set to 22:00 after ntpdate, as > far as I could observe. I am pretty confused about the subject. Tried different > timezone names, etc, hence more confused. > > I also have a problem with the name of the timezone. which timezone name do you > choose guys? US/Eastern? America/Newyork? GMT+5? EST? EDT? or any other? I am > using slackware-current. set the timezone to America/New_York and whenever I > send a mail, sylpheed shows my timezone as GMT-4 and > #date > shows my timezone as EDT. > > any comments. other than removing the crontab job? :) > > thanks, > baris > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > -- ¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø Karl Hiramoto <karl(a)hiramoto.org> Work: 978-425-2090 ext 25 Cell: 508-517-4819 Personal web page: http://karl.hiramoto.org/ Zoop Productions: http://www.zoop.org/ KTEQ Rapid City: http://www.kteq.org/ AOL IM ID = KarlH420 ¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø To generalize is to be an idiot. -- William Blake

May 8, 2002

Re: [Wlug] PowerMac CD-ROM

by Josh Huber

jeff <jmr71769(a)earthlink.net> writes: > you have my vote for apt-get ;) Yes, apt-get is nice but it does miss some things since it doesn't handle Recommends, etc. > dselect isn't bad...if you spare the time to learn it... Indeed. But, I really hate dselect. Personally, I think aptitude is a _much_ better frontend to the packaging system. If you do upgrade from potato to woody, make sure after changing your sources.list to woody you upgrade dpkg and apt-get first, and install apt-utils: <edit /etc/apt/sources.list> apt-get update apt-get install dpkg apt-get apt-utils apt-get dist-upgrade done. ;) ttyl, -- Josh Huber

May 8, 2002

Re: [Wlug] timezone

by Michael Frysinger

i have ntpd constantly running and my /etc/localtime is linked to /usr/share/zoneinfo/US/Eastern ... this is Slackware 8.0 running hwclock shows my time as the current time that it should be ... the /usr/share/zoneinfo/ setup seems to be distro dependent so only slackware peeps should be able to give help on this one ... -mike ----- Original Message ----- From: "Baris Hasdemir" <penguen(a)hasdemir.com> To: "wlug" <wlug(a)mail.wlug.org> Sent: Wednesday, May 08, 2002 05:04 Subject: [Wlug] timezone > hi, > > I have a strange-for-me problem. I am one of those paranoid guys, who has added > "ntpdate time.nist.gov" to the crontab to be executed every day. > > the problem is that, every night the system time is set 1 hour earlier of the > actual time. i.e it is executed at 23:00 and is set to 22:00 after ntpdate, as > far as I could observe. I am pretty confused about the subject. Tried different > timezone names, etc, hence more confused. > > I also have a problem with the name of the timezone. which timezone name do you > choose guys? US/Eastern? America/Newyork? GMT+5? EST? EDT? or any other? I am > using slackware-current. set the timezone to America/New_York and whenever I > send a mail, sylpheed shows my timezone as GMT-4 and > #date > shows my timezone as EDT. > > any comments. other than removing the crontab job? :) > > thanks, > baris > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

May 8, 2002