Re: Silly DNS question (underscore in hostname)
> (I detest FUD, even if it's aimed at a target I also dislike.) (sigh) You're right. I could swear that just before I posted my comment I had read (parts of) a rant (with examples) about how Microsoft disregards the DNS hostname rules on the Internet, but maybe I was hallucinating - I now can't find anything like that anywhere on the WWW. Given Microsoft's history I've gotten into the habit of assuming any account of their misbehavior to be true but, of course, that isn't license to repeat crap. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Silly DNS question (underscore in hostname)
After refreshing my memory here: http://en.wikipedia.org/wiki/Hostname ...which references (what appear to be) the relevant RFCs, I recall that underscores are definitely not legal, but the corner cases (and instances of blatant [cough]Microsoft[cough] disregard) are interesting... ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: [semi-OT] configuring DNS, virtual hosting on dreamhost (?)
> Well, there's another way that anyone really interested could find > out: you could just *ask the people at Dreamhost* :) As I've said, the domain in question has already been set up in a way that satisfies requirements for the moment, so we don't have a problem needing a solution. This is just me being curious about the gap (however small) in the "chain of custody" WRT configuring domains at dreamhost.com (and elsewhere?) and their apparent reliance (however inconsequential) on Security By Obscurity. Yes, I could have waited until that family was once again reachable so I could quiz the kid about the details of whatever tools he used. Yes, I could have slogged through the process of trying to extract that info from dreamhost.com even though I'm not a customer. But I instead hoped to DISCUSS my [semi-OT] curiosity on this gnhlug-DISCUSS channel because it's possibly of interest to others who may wonder about the mechanics and arcana of the DNS. Merry fscking Saturnalia. (sheesh...!) ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: [semi-OT] configuring DNS, virtual hosting on dreamhost (?)
> [...] You're basically relinquishing all control of the domain to > DreamHost, until and unless you change the delegation to nameservers > you control. Your involvement -- and control -- is now nil. > Presumably you're okay with that, or you wouldn't have done it. Right. As you say, I have relinquished DNS control by delegating to dreamhost's servers. What I don't understand is how he *acquired* control as nobody ever contacted me to verify that I intended him to do as he did. > [...] To put it another way: I can configure a virtual hosting > section in the Apache httpd.conf on my home PC here Right, but you're authorized to do whatever you want on your systems while I assume he is not supposed to have free rein in the dreamhost DNS. What if another dreamhost customer decides to redirect the new domain to somewhere else? How does dreamhost decide who's entitled to make such changes? (sorry if I'm being dense - Wassail!) ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
[semi-OT] configuring DNS, virtual hosting on dreamhost (?)
I purchased a domain name registration from GoDaddy as a gift for a friend. His kid (who already has a domain registered at dreamhost.com) agreed to work with me to initialize things such that the new domain points at the family's page on shutterfly.com. So I asked the kid to tell me what to use for the A record and he said, "Oh, don't worry about that - just set the domain server entries to point at nsX.dreamhost.com and I'll handle the rest." Being busy, I did as he suggested without thinking about it further; sure enough, when I later opened http://newDomain.com/ with my browser it redirected to their shutterfly.com page just as he predicted. Then I started to wonder how he could have arranged that without any further involvement from me. I claim that I understand the basics of the trickery behind (some types of) virtual WWW hosting: when your browser sends a GET to the machine of record for the domain in question, that GET mentions the desired hostname and that info is then used to redirect (via something like a "301 Moved Permanently") to a machine that is serving the desired pages. What I don't understand is how the kid could arrange all that without involving me, the nominal owner of the domain in question. He's not available to supply details just now but he indicated that he intended to use the standard tools dreamhost.com supplies to accomplish this. Since I was never contacted after setting the nameserver entries it appears to me that those tools give him the power to mess with *any* such domain, as long as dreamhost.com is specified as the nameserver in the DNS record. Could that be? Yikes... ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
CLAIMED: wounded WRT54GL v1.1
Item is spoken for. And here's hoping that next time I'll remember to mention up front that I'm in Chelmsford so you folks in the Great White North can know that I'm not really in your neighborhood... ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
FREE: wounded WRT54GL v1.1
I just unearthed my WRT54GL that was working fine until earlier this year when it suddenly lost the ability to communicate via the Enet port used for the WAN connection. AFAIK the unit is still otherwise in working order and if reflashed appropriately could probably be put back into service using the remaining 4 Enet ports as they still appeared to work fine. However, when the unit failed I just replaced it with one from Netgear and don't foresee having time for that sort of hackery any time soon, so if anybody wants it they're welcome to it... ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: New HP dv6 laptop and Knoppix (recovering data from damaged drive)
> I ended up pulling out a SATA USB 3.5 hard drive enclosure, > booting Knoppix 6.01. Several 'fdisk -l' and 'dd if=/dev/baddisk > of=/dev/gooddisk' I was able to copy partition information, a > working boot sector, and the HP recovery partition. The first whole > disk copy was not successful as it stopped on the bad OS sector, > a second attempt to copy the 2nd largest recovery sector worked. Note that dd_rescue (rather than plain old dd) will atempt to continue the copy operation even when it encounters bad sectors, writing nulls to the destination in place of the missing data, thereby often enabling recovery of your data from those regions of the resultant image corresponding to the undamaged parts of the original. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Looking for stuff that you forgot to throw out
>Here's an article from somebody who's discouraged about LaCrosse >Technology's gear and their attitude toward Linux compatibility: > > http://www.linuxjournal.com/content/hows-weather ...but then immediately after that I noticed these more encouraging notes: http://www.weather-watch.com/smf/index.php/topic,10727.msg83039.html#msg83039 http://www.weather-watch.com/smf/index.php/topic,10727.0.html http://open3600.fast-mail.nl/tiki-index.php ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Looking for stuff that you forgot to throw out
>> It is a La Crosse WS-3610. > Looks like it's OEM'ed by these people: > >http://www.heavyweather.info/new_english_us/3610set.html > > The software spec sheet claims it only works with Win 98 or later, >and needs 128 MB RAM. If that's true, and that software is the same >software you have (and not some new generation), chances are it's not >going to run on Win 3.x or that 486 at all. In the past I've used dedicated machines that could passively sniff RS232 data and control signals but I'm assuming that if you had access to a gizmo like that you'd have mentioned it. Here's an article from somebody who's discouraged about LaCrosse Technology's gear and their attitude toward Linux compatibility: http://www.linuxjournal.com/content/hows-weather ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Looking for stuff that you forgot to throw out
> The customer support person at the weather station manufacturer was > pretty insistent that USB dongles don't work. I suspect that their > internal micro doesn't have a UART. It doesn't even connect to RxD. Can you reveal the make and model of this weather station? ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: [semi-OT] QIC2 streaming cartridge tape lossage
>> Nice how the 9-track serpentine >> layout makes it possible for a single medium flaw to trash the bit stream >> in 9 different places at once... >-/ > > Unfortunately, I think most tape systems are multi-track -- >everything from ancient reel-to-reel stuff to the latest LTO. Right, but formats like reel-to-reel (you know, the ones they showed spinning in old timey movies & TV to indicate awesome computing power?) were 9-track parallel. QIC2 used 9-track serpentine, meaning the bits were layed down serially on one "track" and when End-Of-Tape was reached in one direction they'd move the head so it was over a new track and start the tape back in the other direction, again and again as often as as 9 times. So my point is that a single flaw in the tape wouldn't just trash your stream of 9 parallel bits at one point but trash your single serial bit stream in as many as 9 places. Think of a scratch in an LP. I knew all this at the time but since I'd only occasionally seen tapes be unreadable when pulled from storage I thought I'd chance it. I didn't realize their half-life was so short... <>___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
[semi-OT] QIC2 streaming cartridge tape lossage
I finally got around to the task of re-archiving the data in my mongrel collection of tapes (QIC2 format 1/4" Streaming Cartridge) that's been nicely stored in its two copier-paper boxes since forever. I figured I could reduce the physical space required down to a handful of DVDs while simultaneously moving to a format not associated with steam power. Although I was in the habit of verifying readbility after creating archive tapes I apparently waited too long to engage in this exercise because it's been a very disappointing experience and I've only been able to recover a portion of my data. Luckily, I've not lost anything too precious but on the (admittedly slim) chance that anybody else out there is using this ancient medium I'd like to urge you to immediately change over to, well, basically *anything* more reliable like, say, smoke signals in a hurricane. Most of my tapes were written between 1993 and 2001. Brand names include 3M, Wang, DEI, Carlisle, Maxell, Platinum, ICL and Verbatim along with various unbranded distro tapes and such. Regardless of brand, I've seen such a poor yield that at this point I'm pleasantly surprised when I'm able to fully retrieve data from any of them. I claim that my kit isn't the problem - I have use of two Archive Viper SCSI drives that in their day were top-notch, and most of these tapes were written by the same model of (and in many instances the self-same) drive which is, of course, not supposed to matter anyway. Data path is from external enclosure via high-grade SCSI cable, properly terminated, using an Adaptec 2930B that's ID'd by the PCI subsystem as AIC-7860. Kernel is 2.6.30-2-686. General operability is seemingly confirmed by the fact that some tapes can be read at will, time after time. I'm seeing several types of mechanical failure related to the internal drive belt loop inside the cartridge: - The belt has stretched and won't move the tape. (workaround: use one from another cannibalized cartridge) - The belt breaks during operation. (workaround: see above) - Slack tape fails to maintain proper contact with head and "retension" commands don't have desired effect. (workaround: disassemble cartridge and retension by hand) Fortunately, cartridges from most manufacturers are easy to open up for emergency surgery, though their parts are usually not interchangeable. I'm also seeing various medium failures where the bits just seem to have fallen off the tape and are irretrievable despite heroic efforts by the drive firmware to retry, reposition, re-align, rewind, recalibrate, re-whatever ad nauseum. It's obvious from the annoying "shoe-shining" sound when the drive is having trouble. Nice how the 9-track serpentine layout makes it possible for a single medium flaw to trash the bit stream in 9 different places at once... >-/ ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: mismatch_cnt != 0, member content mismatch, but md says the mirror is good
> As I understand it, the explanation in question applies to swap > partitions only. (Swap is somewhat unique in that the kernel can > "know" a given block on disk will never be read again.) Yah, you're referring to the case where a page that's just been written out is immediately dirtied again so those freshly written disk data are abandoned since they're no longer the most recent bits representing the page in question. He indicates that he thinks this might also be possible for memory mapped files but now that I've read it again I confess I don't understand his follow-up: > This can conceivably happen with out swap being part of the picture, > if memory mapped files are used. However in this case it is less > likely to remain out-of-sync and dirty file data will be written > out soon, where as there is no guarantee that dirty anonymous > pages will be written to swap in any particular hurry, or at any > particular location. ...so I guess the only thing we know for sure is that these guys know the problem exists and don't believe it to be dire. FWIW, as in your case the MD device this was reported against is not engaged in any swapping. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/ ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: mismatch_cnt != 0, member content mismatch, but md says the mirror is good
Saw the warning in question today on a CentOS5.4 box so I STFW and found these: http://forum.nginx.org/read.php?24,16699 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=405919 ...with a plausible (and somewhat comforting) nuts&bolts level explanation toward the bottom of the latter. Summary: annoying but apparently not harmful. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Does the on-disk image of an executable ever change?
> Have you done straight (non-hashed) content-comparison of any of > these files? Are they actually gratuitously different in content, > or are they just truncated on one system? MD5sums are effectively > dependant on file-size The files were the same size but differed in various locations (no more than 1Kb worth but in multiple places) as reported by cmp -l, the results of which I did not preserve - sorry. I am now not completely certain whether those differences were due to something benign like prelink or from some sort of bitrot. That would be worth knowing. > What prompted this investigation in the first place? You wrote > "behaving strangely"..., but can you give some elucidation as to > what that means? Of three nominally identical machines (loaded from the same installation media) that each wanted be both NFS client and NFS server to the other two, all three could be clients but one silently refused to be a server; no diagnostics, no messages, no outward indication of failure but the other two machines always got "server reports permission denied". Reinstalling the ailing system seems to have fixed it. (?) ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
yum reinstall / rpm --verify
Situation improving. Ben suggested that something like this:
yum reinstall $( rpm -qa --qf '%{name}\n' )
...would be one way to refresh the on-disk images along with the
corresponding MD5 sums in the RPM database, but some kind of RPM
dependency hell (maybe just in my situation?) made that all-at-once
approach unworkable so I changed it to a one-at-a-time affair, thus:
while read p ; do
echo "" BEGIN "${p}" ;
yum reinstall -y --verbose "${p}";
echo "#" DONE "${p}" ;
done < <(rpm -qa --qf '%{name}\n' | sort -u)
...in order to get as many packages as possible reinstalled while not
allowing the b0rken ones to bring everything to a halt; I figured I could
deal with those later. The downside of this approach is that it appears
that a *lot* of initialization (computing a current package list and
dependency graph, finding a repository, etc) is repeated for each package
instead of it being amortized across the whole set. The upside is that,
for whatever reason, it appears all packages got reinstalled with no
sign of the dependency problems seen with the all-at-once approach. (?)
As that loop cranked ponderously along (~4hrs) it all seemed to be
working more or less as hoped except that for every package this message
was shown:
Warning: scriptlet or other non-fatal errors occurred during transaction.
...with no explanation or other indications of trouble. Maybe if I had
boosted the verbosity or debug levels an explanation might have been
provided but I was far enough along that I didn't't want to interrupt it.
Now rpm --verify --all reports no MD5 errors except the expected ones
for locally modified config files. Even with prelink active - Yay!
I'll note one other (trivial) problem - the dbus-devel packages that
are present in both their i386 and x86_64 incarnations seem to fsck up
the verification phase by presenting conflicting MD5 lists for some of
their files. When I had both packages present the command "rpm --verify
dbus-devel" showed this sort of stuff:
.
.
.
..5./usr/share/devhelp/books/dbus/api/structBusData.html
..5./usr/share/devhelp/books/dbus/api/structDBusAddressEntry.html
..5./usr/share/devhelp/books/dbus/api/structDBusAllocatedSlot.html
..5./usr/share/devhelp/books/dbus/api/structDBusArrayLenFixup.html
..5./usr/share/devhelp/books/dbus/api/structDBusAtomic.html
..5./usr/share/devhelp/books/dbus/api/structDBusAuth.html
..5./usr/share/devhelp/books/dbus/api/structDBusAuthClient.html
..5./usr/share/devhelp/books/dbus/api/structDBusAuthCommandName.html
..5.
/usr/share/devhelp/books/dbus/api/structDBusAuthMechanismHandler.html
..5./usr/share/devhelp/books/dbus/api/structDBusAuthServer.html
..5./usr/share/devhelp/books/dbus/api/structDBusAuthStateData.html
..5./usr/share/devhelp/books/dbus/api/structDBusBabysitter.html
..5./usr/share/devhelp/books/dbus/api/structDBusCondVarPThread.html
..5./usr/share/devhelp/books/dbus/api/structDBusConnection.html
..5./usr/share/devhelp/books/dbus/api/structDBusCounter.html
..5./usr/share/devhelp/books/dbus/api/structDBusCredentials.html
..5./usr/share/devhelp/books/dbus/api/structDBusDataSlot.html
..5.
/usr/share/devhelp/books/dbus/api/structDBusDataSlotAllocator.html
..5./usr/share/devhelp/books/dbus/api/structDBusDataSlotList.html
..5./usr/share/devhelp/books/dbus/api/structDBusDirIter.html
..5./usr/share/devhelp/books/dbus/api/structDBusError.html
.
.
.
...but now that I've removed the i386 version and reinstalled the x86_64
version all is well. >-/
___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Does the on-disk image of an executable ever change?
I'm running an rpm --verify --all pass on those machines right now and it's showing quite a few indications of unexpected differences based on the info recorded in the RPM database. Ben is right; that's a very nice feature of RPM. When I captured the output in a file and then said things like this: grep -e '^..5' /tmp/rpmVerifyLog ...I was unpleasantly surprised to see results like this: . . . SM5T c /etc/sysconfig/iptables-config S.5T c /etc/yum.repos.d/adobe-linux-i386.repo S.5T /sbin/parted S.5T /sbin/partprobe S.5T /usr/bin/mcopidl S.5T /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/perllocal.pod S.5T /usr/sbin/avcstat S.5T /usr/sbin/getenforce S.5T /usr/sbin/getsebool S.5T /usr/sbin/matchpathcon S.5T /usr/sbin/selinuxenabled S.5T /usr/sbin/setenforce S.5T /usr/sbin/togglesebool S.5T c /etc/yum.repos.d/rpmforge.repo S.5T c /usr/share/config/kdm/kdmrc S.5T /usr/bin/gsf-office-thumbnailer S.5T /usr/bin/animate S.5T /usr/bin/compare S.5T /usr/bin/composite S.5T /usr/bin/conjure S.5T /usr/bin/convert S.5T /usr/bin/display S.5T /usr/bin/identify S.5T /usr/bin/import S.5T /usr/bin/mogrify S.5T /usr/bin/montage S.5T /usr/share/hwdata/videoaliases/nv.xinf S.5..U.T c /etc/ntp/ntpservers . . . ...so that system seems to have suffered disk corruption or compromise; I'm assuming the former given the large number of affected files but I guess I can't rule out the latter. FYI, the man page provides this interpretation: The format of the output is a string of 8 characters, a possible attribute marker: c %config configuration file. d %doc documentation file. g %ghost file (i.e. the file contents are not included in the package payload). l %license license file. r %readme readme file. from the package header, followed by the file name. Each of the 8 characters denotes the result of a comparison of attribute(s) of the file to the value of those attribute(s) recorded in the database. A single "." (period) means the test passed, while a single "?" (question mark) indicates the test could not be performed (e.g. file permissions prevent reading). Otherwise, the (mnemonically emBoldened) character denotes failure of the corresponding --verify test: S file Size differs M Mode differs (includes permissions and file type) 5 MD5 sum differs D Device major/minor number mismatch L readLink(2) path mismatch U User ownership differs G Group ownership differs T mTime differs ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Does the on-disk image of an executable ever change?
I'm looking at some supposedly identical CentOS5.3 systems that are behaving strangely and while grasping at straws I generated lists of the MD5 sums of all the files on the root partitions and I'm seeing differences in the on-disk images of things like /sbin/mount and /lib64/libblkid.so.1.0 that AFAIK are supposed to be entirely static. WTF? Is it ever the case that it's OK for the on-disk image of an executable to change once it's been laid down? I assume that (excluding some possible weirdo corner cases like the old Emacs trick where the binary would [yikes!] rewrite itself to save startup time on subsequent invocations) the answer is an emphatic "No" but I could be wrong. Also, since the systems in question don't have their RPMs handy I wonder if there's some simple trick that would allow me to automagically verify the various files against their corresponding RPMs in some repository out on the Net without having to explicitly drag them all onboard and execute an "rpm --verify" by hand... ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: comcast routing problems
It pains me to say anything that appears to cut ComCast any slack because I have no love for them whatsoever but, FWIW, I'm seeing essentially the same traceroute output reported by Kenta: e521:~ 395---> traceroute linuxquestions.org | lineup traceroute to linuxquestions.org (75.126.162.205), 30 hops max, 60 byte packets 1 prescott67 (192.168.1.1)1.718 ms 2.166 ms 2.612 ms 2 c-3-0-ubr03.lawrence.ma.boston.comcast.net (73.165.128.1) 18.090 ms 18.330 ms 18.541 ms 3 ge-5-41-ur01.lowell.ma.boston.comcast.net (68.85.161.121) 21.989 ms 25.375 ms 29.383 ms 4 be-21-ar01.needham.ma.boston.comcast.net (68.87.144.157) 35.297 ms 35.525 ms 35.735 ms 5 pos-0-1-0-0-ar01.chartford.ct.hartford.comcast.net (68.85.162.74) 39.328 ms 39.571 ms 39.775 ms 6 pos-2-3-0-0-cr01.newyork.ny.ibone.comcast.net (68.86.90.57)42.313 ms 40.599 ms 40.680 ms 7 pos-1-10-0-0-cr01.mclean.va.ibone.comcast.net (68.86.85.9) 45.693 ms 22.615 ms 22.519 ms 8 pos-1-11-0-0-cr01.atlanta.ga.ibone.comcast.net (68.86.85.241) 53.513 ms 56.894 ms 60.799 ms 9 pos-1-10-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.86.129) 85.758 ms 90.299 ms 90.511 ms 10 softlayer-cr01.dallas.tx.ibone.comcast.net (75.149.228.34) 92.119 ms 92.572 ms 93.221 ms 11 po2.dar02.dal01.dallas-datacenter.com (66.228.118.207) 91.142 ms 91.383 ms 92.281 ms 12 po2.fcr02.dal01.dallas-datacenter.com (66.228.118.182) 91.669 ms 92.687 ms 92.788 ms 13 www.linuxquestions.org (75.126.162.205) 91.562 ms 69.371 ms 73.092 ms ...and my /etc/resolv.conf is this: search hsd1.ma.comcast.net nameserver 68.87.71.230 nameserver 68.87.71.246 nameserver 68.87.71.226 nameserver 68.87.73.242 ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Senturion environmental monitor - usability/feature suggestions?
DTVZ wrote: >I thought you guys might have some input on this re: usability and >features... any suggestions for improvement would be appreciated. > >http://sensatronics.com/index.php/demos/senturion-demo.html ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: [GNHLUG] Doodle poll for GNHLUG party location
> The web site and phone number Google finds are both no longer > in service. http://www.lacarretamex.com/ I'll be out of town around then but I still have GNHLUG emails from mid 1995 so I'll be with y'all in spirit... ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: [OT] How To Ask Questions The Smart Way
Eric Raymond can be a PITA but in this case his recommendations (or, more to the point, the principles behind them) are refined and spot-on; they're applicable in pretty much any situation involving interactions among multiple (smart) parties, not just online mailing lists... ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: How can I retrieve the mount count for an ext3 volume?
> Modern RAID controllers usually feature something called "patrol >read", which reads all the blocks on the physical disks in the >background, when otherwise idle. > > Is there a similar feature in Linux's RAID implementation? As of 2005 when I was obliged to write scrubber code along the lines you describe, the Linux MD subsystem had no such built-in capability. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
[semi-OT] Pretty vs. Useful output
>> No need to stick it in /proc, but parsing the output of utilities with >> scripts is subject to all kinds of potential errors and inefficiencies. > > If that's your concern, the utility should have an output mode >that's more friendly to machine interpretation. :) Gr!! A long-standing source of frustration for me is that people who definitely should know better insist on writing code that utters only "pretty" outputs instead of useful, parseable info. Yes, it's darling and precious that the authors of (say) mdadm, dumpe2fs or /proc/cpuinfo spent so much time arranging for their output to be so neatly lined up, but it's a fscking PITA for scripts to pluck useful info from within that sort of dreck. If I were king I'd decree that all software be capable of uttering its output in a manner that can easily be scanned for items of interest, using a format like (say) key=value pairs or maybe (the disappointingly oversold) XML. You can always prettify info delivered in a regular format but going the other way is, as already mentioned, error-prone and inefficient. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
[OT] goofy-expensive Denon cables - spoof?
> Greg, it's obviously your Ethernet cables. I bet > they're no name. I suggest you give the Denon AK-DL1's > (http://www.usa.denon.com/ProductDetails/3429.asp) a try. "[...] Additionally, signal directional markings are provided for optimum signal transfer." I really want to believe that's a spoof site but, if so, their deadpan is very good. OMFG, do people actually order that stuff? ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: OT: Looking for degausser/magnetic tape eraser
Seriously: http://www.unitednuclear.com/magnets.htm ...and you'll have some fun, if dangerous, toys to play with, too. I don't know that they're officially represented as being appropriate for your specific purpose but some of them are so dangerously powerful you can find pictures on the WWW of smashed fingers resulting from mishandling them. Woo-hoo!! ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Enabling Virtual Machine support
> There was a study published a couple years back that showed > enabling the VT instructions can result in lower performance Heh. The x86 instruction set offers some fancy instructions that are supposed to help you implement an OS by doing (in one swell foop) some fairly involved stuff like dumping all the CPU registers into memory as is common during task switches. I don't know if it's still true but early on some of them were remarkably slower - IIRC sometimes something like an order of magnitude slower - than an equivalent series of well chosen "normal" instructions. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Enabling Virtual Machine support
> I did not want to eat up people's time with this thread. This thread is interesting and something that I've been meaning to learn more about so I was pleased to have an excuse to dig an old CPU manual out of my desk midden. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Enabling Virtual Machine support
On this busy morning I've only had time to glance at some docs for SVM (Secure Virtual Machine) support but it does appear that in some cases external hardware (in the form of a TPM - the dread Trusted Platform Module) can be involved in the prep and execution of the Secure Loader and, therefore, any subsequent use of (some? all?) VM capabilities. They (AMD Sys Prog Manual circa 2006) also show some pseudocode that seems to indicate that the BIOS (by means I don't yet understand) does have the ability to prevent later use of (some? all?) VM capabilities, with or without a TPM: 15.4 Enabling SVM The VMRUN, VMLOAD, VMSAVE, CLGI, VMMCALL, and INVLPGA instructions can be used when the EFER.SVME is set to 1; otherwise, these instructions generate a #UD exception. The SKINIT and STGI instructions can be used when either the EFER.SVME bit is set to 1 or the ECX.SKINIT bit, as returned by CPUID function 8000_0001h, is set to 1; otherwise, these instructions generate a #UD exception. Before enabling SVM, software should detect whether SVM can be enabled using the following algorithm: if (CPUID 8000_0001.ECX[SVM] == 0) return SVM_NOT_AVAIL; if (VM_CR.SVMDIS == 0) return SVM_ALLOWED; if (CPUID 8000_000A.EDX[SVM_LOCK]==0) return SVM_DISABLED_AT_BIOS_NOT_UNLOCKABLE // the user must change a BIOS setting to enable SVM else return SVM_DISABLED_WITH_KEY; // SVMLock may be unlockable; consult the BIOS or TPM to obtain the key. So I've learned something: it appears that the BIOS can indeed have the final word re: VM regardless of what any subsequent OS or would-be hypervisor might wish, but I don't yet understand the details. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Enabling Virtual Machine support
>> So if VM support is enabled by flipping some bit(s) in some CPU >> Control Register(s) I'd assume that a VM-capable OS could flip those >> bits as well as any BIOS code. I suppose it's possible that the CPU >> might first insist on seeing a certain logic level on a certain input >> pin before allowing VM support to be enabled, and only the BIOS >> authors might know how to poke the appropriate values into some secret >> I/O port to do that, but in principle the OS would still be capable of >> doing that if only those magic locations and values were known, yes? > >I believe that the vmx capabilities need to be enabled at power-up. >Once the processor gets to its "normal" state, it is too late. Not certain I understand what you're saying but processors in this family come out of their power-on Reset state in their simplest, least capable mode - interrupts disabled, MMU disabled, 20bit Real Mode addressing, etc - and each increase in capability requires a deliberate action on the part of the system code (typically the BIOS at first, then later the OS). Virtual Machine mode is like Virtual 8086 mode in that it's a capability that must be explicitly enabled once the OS has rigged itself to manage it; this as opposed to somehow being a permanent, static feature of the platform or CPU. And also, AFAIK, no external HW support is required of the platform for VM capabilities to be utilized - if the OS is coded to support it and the CPU provides it, that's all you (should!) need. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Enabling Virtual Machine support
I have fairly deep OS-level experience (including some Virtual Machine work) but I confess that I'm not up on the very latest VM technology so to further the discussion let me ask something that may also have occurred to others: What is it in the nature of VM support in these processors (or possibly in the motherboards/platforms in question) that leads to talk about the BIOS somehow having control over whether VM is enabled? I'm asking this because in my experience the typical BIOS is essentially the boot loader and although it is written by folks with detailed proprietary knowledge of the specific platform in question it is not otherwise somehow more "privileged" than any OS code that it might load. So if VM support is enabled by flipping some bit(s) in some CPU Control Register(s) I'd assume that a VM-capable OS could flip those bits as well as any BIOS code. I suppose it's possible that the CPU might first insist on seeing a certain logic level on a certain input pin before allowing VM support to be enabled, and only the BIOS authors might know how to poke the appropriate values into some secret I/O port to do that, but in principle the OS would still be capable of doing that if only those magic locations and values were known, yes? I, too, would be irritated if I discovered that my mobo designers or BIOS authors had decided that I was not entitled to enable a perfectly usable feature that my CPU supported... >-/ ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Make Q's
As an experiment, can you link a helloWorld-style object (that needs the symbols in question) against the libs in question? In other words, arrange for that memcpy_cell(void*,blah,blah) to be unresolved in your helloWorld object and then link it against the object or lib you think should be providing it. You can use readelf to provide more info than you'll ever need about the various objects&libs in question; try this: readelf --all yourObjectOrLibHere ...and then look for the symbol table info to confirm that your symbol is provided/requested where you think it should be. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: /usr/bin/ld error
What flavor are the libs in question? If you're generating x86_64 objects you can't link against i686 libs and vice versa, etc, etc... ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Packing/unpacking binary data in C - doubles, 64 bits
In just the few minutes I had to actually look at that pack2.c I found several scary sequences of code, so if you're staying your current course (instead of adopting some of the other recommendations offered here) you might want to keep on looking or else write your own from scratch. For example, in unpack() (where f is a pointer-to-float) we see code like this: case 'f': f = va_arg( ap, float * ); // WTF? pf = unpacki32( buf ); buf += 4; *f = unpack754_32( pf ); // Aai!! break; ...and in main() we see him squirt some data into buf[] and then immediately overwrite part of it "for kicks": packetsize = pack(buf, "chhlsf", 'B', 0, 37, -5, s, -3490.6677); packi16(buf+1, packetsize); // store packet size in packet for kicks These aren't the droids you're looking for... ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Packing/unpacking binary data in C - doubles, 64 bits
Ooops - I forgot about the void * ...
>> Any suggestions to look for a 2^53 type problem?
>
>Well, just for fun, how about going back to basics - what does this
>little program generate on all the systems in question?
#include "stdio.h"
main( int argc,
char *argv[] )
{
printf( "sizeof( double) %2u\n", sizeof( double)
);
printf( "sizeof( float) %2u\n", sizeof( float)
);
printf( "sizeof(long double) %2u\n", sizeof(long double)
);
printf( "sizeof(long signed long) %2u\n", sizeof(long signed long)
);
printf( "sizeof(long unsigned long) %2u\n", sizeof(long unsigned long)
);
printf( "sizeof( signed char) %2u\n", sizeof( signed char)
);
printf( "sizeof( signed long) %2u\n", sizeof( signed long)
);
printf( "sizeof( signed short) %2u\n", sizeof( signed short)
);
printf( "sizeof( unsigned char) %2u\n", sizeof( unsigned char)
);
printf( "sizeof( unsigned long) %2u\n", sizeof( unsigned long)
);
printf( "sizeof( unsigned short) %2u\n", sizeof( unsigned short)
);
printf( "sizeof( void *) %2u\n", sizeof( void *)
); /* Fprgot this one */
}
___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Packing/unpacking binary data in C - doubles, 64 bits
> Any suggestions to look for a 2^53 type problem?
Well, just for fun, how about going back to basics - what does this
little program generate on all the systems in question?
#include "stdio.h"
main( int argc,
char *argv[] )
{
printf( "sizeof( double) %2u\n", sizeof( double)
);
printf( "sizeof( float) %2u\n", sizeof( float)
);
printf( "sizeof(long double) %2u\n", sizeof(long double)
);
printf( "sizeof(long signed long) %2u\n", sizeof(long signed long)
);
printf( "sizeof(long unsigned long) %2u\n", sizeof(long unsigned long)
);
printf( "sizeof( signed char) %2u\n", sizeof( signed char)
);
printf( "sizeof( signed long) %2u\n", sizeof( signed long)
);
printf( "sizeof( signed short) %2u\n", sizeof( signed short)
);
printf( "sizeof( unsigned char) %2u\n", sizeof( unsigned char)
);
printf( "sizeof( unsigned long) %2u\n", sizeof( unsigned long)
);
printf( "sizeof( unsigned short) %2u\n", sizeof( unsigned short)
);
}
___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: [OT] Generator testing
FWIW: I work at a site where we share a building with an ISP/colo vendor with 3 big diesel generators (each in its own shipping-container sized enclosure and so powerful they require an automobile-sized resistive load to dump their juice into during testing) out front plus at least one slightly smaller unit out back and AFAICT they test those units *maybe* once every couple of months, if that. Weekly testing sounds excessive... ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Can't eject CD/DVD after warm reboot?
>> Most of our HP systems (all recent models like xw8600 and z800) refuse >> to eject their optical media when the drive button is pushed after a >> warm reboot following a rescue/install session booted from that drive. > >Have you reported this to HP as a BIOS bug? Yes, working that with them now. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Can't eject CD/DVD after warm reboot?
>> Is there some trick (maybe some kernel commandline option or some program
>> executed during shutdown) that will leave the drive willing to eject the
>> media ("unlock" it?) without us having to power-cycle these machines?
>
>Take a look at hdparm -L. Is that what you're looking for?
No, it looks like hdparm uses ioctls that aren't supported for the devices
in question, but digging into that put me onto the sg_* set of programs
and this one:
sg_prevent --allow /dev/cdrom
...appears (most of the time) to be unlocking the drive as we'd like.
Still too early to tell if it's reliable enough to be the workaround we
need, but your clue got us that much closer - thanks.
Those sg_* programs are definitely in "The Rotating Knives, yes?!"
category but since the SATA drives are presented via the SCSI midlayer
it appears they're what's required in this case. There's approx a dozen
related tools in that family (at least on the SysRescueCD) and here, for
example, is how you can force the DVD tray to open once you've unlocked
it as shown:
sg_raw /dev/cdrom 1b 00 00 00 02 00
...and we're also shipping a box of paper-clips with every system.
___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Can't eject CD/DVD after warm reboot?
>> Is there some trick (maybe some kernel commandline option or some program
>> executed during shutdown) that will leave the drive willing to eject the
>> media ("unlock" it?) without us having to power-cycle these machines?
>
>Why won't the paperclip trick (manual release) won't work?
Because that would give the customers an even worse impression than they
get from just having to power-cycle the fscking things... >-/
___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Can't eject CD/DVD after warm reboot?
Most of our HP systems (all recent models like xw8600 and z800) refuse
to eject their optical media when the drive button is pushed after a
warm reboot following a rescue/install session booted from that drive.
Other systems (eg. Dells) behave as we'd like when booted from those
same discs so this seems clearly to be something related to HP hardware
design or BIOS code. This behavior is seen after using DVDs created
using the old "Timo's Rescue CD" (Debian-based w/2.4 kernel) as well
as a fairly current SysRescueCD (Gentoo-based w/2.6 kernel) configs.
Is there some trick (maybe some kernel commandline option or some program
executed during shutdown) that will leave the drive willing to eject the
media ("unlock" it?) without us having to power-cycle these machines?
The Dell drives are IDE and the HPs are SATA - might that be relevant?
Is it the case that the HPs are working "correctly" according to some
spec and that the other systems that allow it are in fact the ones whose
behavior is b0rken?
___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
[semi-OT] CentOS named appropriately?
I wonder if the CentOS (Community ENTerprise Operating System)
founders knew about this or if it's just, like, ya know - kosmic:
e521:~/codeGen 601---> dict cento
1 definition found
From The Collaborative International Dictionary of English v.0.48 [gcide]:
Cento \Cen"to\, n.; pl. {Centos}. [L. cento a garment of several
pieces sewed together, patchwork, a poem made up of various
verses of another poem.]
A literary or a musical composition formed by selections from
different authors disposed in a new order.
[1913 Webster]
___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: wok-key: dealing with keyloggers on net-cafe computers
You could do like that character in Cryptonomicon (a good read, BTW) who was imprisoned in what he assumed was a TEMPEST-instrumented jail with his laptop, so he rigged it surreptitiously to do I/O via Morse code... ;-> ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: ComCast DNS hijacking
>>> =A0http://en.wikipedia.org/wiki/Fast_Search_&_Transfer >> >> Your second link got broken. It should have been: >> http://en.wikipedia.org/wiki/Fast_Search_%26_Transfer > > Interesting; it worked for me. I wonder if it's my mail software or >my browser that fixed it? > > Firefox 3.5.2 and Gmail. Yes, interesting. I definitely transmitted a literal ampersand in the URL in the original message (cut'n'pasted right out of Firefox's address bar) and that's how it came back to me (and how it appears in the GNHLUG Wiki); no MIME encoding or anything like that was involved. And my mailer (exmh) was able to recognize it and correctly hand it back to Firefox. Is it bad form to use literal ampersands in emailed URLs? Or for Wikipedia to use one in theirs? Are ampersands reserved as a separator when supplying parameters via CGI? ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: ComCast DNS hijacking
> At least you can opt-out now via a form presented on the page. Grumble... well the actual opt-out page is here: https://dns-opt-out.comcast.net/ ...and just for a bit of ironic fun I wondered what would happen if tried the www. version of that hostname, thus: https://www.dns-opt-out.comcast.net/ ...but all I got was a not-found error. ;-> However, when I tried this one: https://www.dns-opt-out.comcast.netJ/ ...it did redirect me back to the DNS hijack page. > Comcast.net - Domain Helper Service > > When a non-existent web address is typed into a browser, a built-in > error message is displayed. The Comcast's Domain Helper service is > designed to help guide you to a useful search page that has a list > of recommended sites that come close to matching the original web > address that did not exist. > > If you are a residential or commercial cable modem subscriber, and > you wish to opt-out of the Comcast Domain Helper service, please > complete the form below. Once you submit this information, we will > send you a confirmation so that we can authenticate the request. > We will then follow-up once you have been successfully opted-out. > > Opt-Out > > Your Confirmation Email Address: > Example: john@comcast.net > Note: A Comcast.net email address is not required. > > Why do we need this? > We will send you an email asking you to authenticate/confirm your > request. You will also be sent an email once your opt-out request > has been successfully processed. > > Cable Modem MAC Address: > Example: 00:16:46:C8:D2:DD > _: _: _: _: _: _ > Where can I find the MAC address? > Why do we need this? > We opt-out your entire household, covering all of your home computers > that access the Internet via the Comcast network. As a result, > we need this unique identifier of your cable modem / eMTA. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
ComCast DNS hijacking
I was going to write up a description of my traceroute investigations into ComCast's DNS hijacking when I found a very similar writeup here: http://slashdot.org/submission/1052907/Comcast-Hijacking-DNS-wMicrosofts-Help ...with add'l info here: http://www.microsoft.com/enterprisesearch/en/us/fast-customer.aspx http://en.wikipedia.org/wiki/Fast_Search_&_Transfer ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Listen to your log files
> oh, wait. That would be better implemented as a USB device, > wouldn't it? That way your smells would be mobile, and the > device could be of arbitrary size. Weirder people than y'all (yes, they exist) are way ahead of you... http://www.google.com/search?q=usb+aroma+therapy ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: melodrama at CentOS?
>Anybody know anything beyond what's mentioned in this open letter >to CentOS's Lance Davis signed by a number of key CentOS players? > > http://www.centos.org/ Ah. Some further info here: http://www.h-online.com/open/Growing-unrest-within-the-CentOS-project--/news/113889 ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
melodrama at CentOS?
Anybody know anything beyond what's mentioned in this open letter to CentOS's Lance Davis signed by a number of key CentOS players? http://www.centos.org/ ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: [OT] We Choose The Moon
> Yes, I'm a space junkie! :-D I've liked the Moon Machines series: http://www.youtube.com/results?search_query=moon+machines ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Phoronix test suite on CentOS5.2
Anybody have any experience with the Phoronix test suite? http://www.phoronix-test-suite.com/ I've seen some praise for it on the WWW but so far my impression is not good. I've pulled both the 2.0.0b2 and the 1.8.1 tarballs (they also offer a .deb but no RPM) onto a fairly standard CentOS5.2 box and tried to rig it up but I'm not having any fun. The core scripts (all written in PHP) generate error messages that seem to indicate they're not ready for primetime. When I said to "install-all" it seems to choke on some of the test bundles it pulls over the wire; many of them require compilation from source, most of them spew rafts of warnings during their builds and a few of the builds fail to complete. Also, I think it may have yum'd in some packages without so much as a by-your-leave, which is rather rude. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: [OT] We Choose The Moon
Another example of cool content that's only viewable if you're willing to jump through a bunch of irritating proprietary hoops: http://tierneylab.blogs.nytimes.com/2009/07/15/gates-puts-feynman-lectures-online/ ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Way to make Firefox appear to Website as IE6 ?
> YMMV with an agent switcher. If the site uses the agent to > determine what code to feed (javascript, ActiveX) like it's supposed > to, it won't work. If it uses the agent to say "we don't work on > your browser" even though it's generic HTML, it won't work. We presume you meant that last one to be, "[...]it might work." ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Way to make Firefox appear to Website as IE6 ?
I use and like the User Agent Switcher extension for Firefox but I don't think it'll help in this case. I say that because I find that Firefox on Linux can talk to my employer's Exchange server if I instruct it to ID itself truthfully, but if I tell it to lie and ID itself as Internet Exploder the server apparently tries to feed it all kinds of crap that require ActiveX and such, so I suspect he'll not find joy using that approach. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Finding *unfiltered* free WiFi?
I confess that I'm happy to use "free" wireless on occasion but I worry that if I make my own AP similarly available then somebody is going to use it to post kiddy-porn or make threats and it'll be traced to my IP address and people with guns will then make me spend a lot of time & money trying to convince them that I didn't do it. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: OpenSSH vulnerability?
>> Hey! cool - if this FUD approach is so effective maybe we can >> use it to rid the world of some other scourges. Like what if we >> very coyly insinuated that there *might* be one or two flaws in >> Microsoft Windows[...] > >It hasn't worked agains MS yet... Right - that was my (possibly too-subtle) point - how frustrating it is that a useful and robust tool like OpenSSH is thrown under the bus by those ISPs after one unsubstantiated whiff of FUD, yet despite the many documented Windows vulnerabilities they apparently never consider using anything else. And never once, BTW, in all the news accounts I've heard about the ongoing DOS attacks, have any of the talking heads mentioned that the zombie machines comprising the bot-nets are (mostly?) all running Microsoft Windows. Didn't their parents teach them that it's important to give credit where it's due... ;-> ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Mucking with a mounted filesystem?
> I am running into a disk space issue on an older server. I'd like > to do a tune2fs -m 1 (or maybe 0) to get rid of most, if not all of > the reserved block space on the partition that is close to full. > The disk is actually an iSCSI volume mounted from an EqualLogic > array, and then exported via NFS to 6 other servers. > > Has anyone ever run tune2fs on a mounted/in-use filesystem? > Is this safe to do? I don't know specifically whether that's safe to do with a mounted filesystem but if your situation allows you might be able to accomplish it by first doing an on-the-fly remount such that your filesystem is temporarily ReadOnly, then do your tune2fs thing, then restore ReadWrite mode with another on-the-fly remount: mount -oremount,ro /your/filesystem tune2fs -whatever /dev/yourDevice mount -oremount,rw /your/filesystem ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: OpenSSH vulnerability?
>> I'm not sure how widespread it is, but I know that ANHosting >> (MidPhase) is blocking it entirely. And they've got no ETA for >> when they'll put it back so far. I guess they're waiting for >> details and patches about the exploit to be released... ugh. > > HostGator has disabled OpenSSH support for now. No ETA for > restoration either. Hey! cool - if this FUD approach is so effective maybe we can use it to rid the world of some other scourges. Like what if we very coyly insinuated that there *might* be one or two flaws in Microsoft Windows that could allow millions of machines to become enslaved in botnets controlled by genuinely malicious people who rent them out to others bent on causing actual measurable harm? Ssss! we could provide details but we're not gonna, cuz it's a secret... ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: OpenSSH vulnerability?
>The best I can find is just the obvious rumor stuff at: >http://isc.sans.org/diary.html?storyid=6742 > >Anyone here have any more information? This *might* be an indication of what it's about: http://www.cpni.gov.uk/Docs/Vulnerability_Advisory_SSH.txt ...but that's based on some *very* unscientific rummaging around in on some of the full-disclosure archives, so take it FWIW... ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Tool to automatically update symlinks when moving files
I wrote: > His problem is that he's moving relative symlinks (or their > referents) around such that the symlinks no longer point at the > right thing and he wants something that detects that and recreates > those symlinks such that they still point at the right things when > the dust has settled. Oh, duh. The problem isn't limited to relative symlinks; if he moves the referent of an absolute symlink he's got the same problem. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Tool to automatically update symlinks when moving files
>> Does anyone know of a tool that can automatically update symbolic >> links when moving files around on a filesystem, so as to maintain >> symlink consistency? > >rsync has options to deal with symbolic links (and hard links) however >you'd like it to I think the complication he's dealing with is that he's not just moving self-contained (sub-)hierarchies around, which is something (as you say) that rsync handles trivially; even the humble "mv" and "cp -a" commands can often meet the need in those situations. His problem is that he's moving relative symlinks (or their referents) around such that the symlinks no longer point at the right thing and he wants something that detects that and recreates those symlinks such that they still point at the right things when the dust has settled. So he wants something that (say) generates a list of symlinks and referents prior to the move and then goes through and does the fixups afterwards. Of course, while it's easy to see when you've moved a symlink it's much more tedious to detect when something you've moved is the *referent* of a symlink - AFAIK only an exhaustive search could reveal that. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Classic running out of memory... huh? what?
I wrote: >If no joy just delete that swapFile, Yikes! I hope it was obvious but I forgot to say that you should: swapoff /someNFSdirectory/mySwapFile ...before deleting it. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Classic running out of memory... huh? what?
>> I notice that there is no swap listed. Umm, how does one add swap to a >> nfs based system? >> >> NFS swap of course ;-) > >Have any good references on NFS swap? To see if swap is even going to help you you might: # Create an empty 1Gb file dd if=/dev/zero of=/someNFSdirectory/mySwapFile bs=1G count=1 # Prepare it as a swap device mkswap /someNFSdirectory/mySwapFile # Add it to the kernel's (possibly empty) pool of swap devices swapon /someNFSdirectory/mySwapFile ...and then run your test. If no joy just delete that swapFile, else you could enshrine the whole mess in an fstab line: /someNFSdirectory/mySwapFile none swap sw 0 0 ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: scripting, no-op statements in bash function (was: SATA hot swap)
> Two possibilities come to mind: grepping for ": funcName" and > storing funcName in $_. Grepping for ": funcName" might be an easy > way to find where a function is defined if the source is spread > out among many files and none of the files contain any comments. Plausible, though that idiom isn't used consistently in the script in question. > [...] If every function begins with ": funcName", $_ would instead > hold the name of the function, as opposed to the name of the script. > Depending on what "otherStuffHere" does, this information may be > useful to the code that follows. Also plausible, though bash defines $FUNCNAME inside every function. > Also, if ":" was redefined to point to a debugging script, it > would be called, with the function name as an argument each time > a function is called. Good for tracing, maybe? Devious! Sorta like bash's "functrace" option. All your suggestions make sense considering that script mentions dates that indicate development may have begun on it before bash was widely used/available/stable. Thanks. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
ARTICLE - The First Few Milliseconds of an HTTPS Connection
[ Not Linux-specific but likely of interest to some on this channel ] A blow-by-blow description of how a secure WWW session gets setup: http://www.moserware.com/2009/06/first-few-milliseconds-of-https.html ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
scripting, no-op statements in bash function (was: SATA hot swap)
I had a look at /sbin/rescan-scsi-bus.sh - it's not the most elegant
bash script I've seen but it apparently works - cool. I've known about
the add-single-device trick but it's clunky and there have been times in
the past where it was easier to just reboot to get the kernel to notice
a new device...
One thing I noticed was that some of the functions in that script are
constructed thus:
funcName ()
{
: funcName
otherStuffHere
}
...and I wonder if those no-op constructions have some value, maybe
during development or debugging, maybe forcing the function name into
a parameter list?
___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Where are the c header files on my system?
There are several ways to get GCC to supply the info in question along
with a blizzard of other stuff:
- Ask it to be generally verbose by adding the '-v' flag to the command line.
Maybe not enough info for your purposes but often useful
nevertheless.
- Ask it to mention each header file on the fly with '-H'.
Probably what you're looking for.
- Ask it to spew the preprocessed source code (with all preprocessor
directives including the locations of all #included files) with -E.
This one can often provide insight into mysterious or bizarre
compilation puzzles when other approaches fail, but be prepared
for large volumes of, um, stuff. I often crunch the resultant
output further with a little script, thus:
#!/bin/bash
#
# A pipe that tidies up the output of a cc -E run a little bit...
#
sed -e 's/[[:space:]]*$//' -e '/^[[:space:]]*#/ { s_^_/* _ ; s_$_ */_ }' | cat
-s
___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: [OT] UNIX license plate
> http://www.facebook.com/home.php#/photo.php?pid=30037422&id=1223007473 Facebook intrusively demand that I create an account and provide contact info even if all I want to do is view the image you've invited me to see. I have no plans to create a Facebook account so I wonder if there's another place to view the image in question... ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
[OT] Re: UNIX license plate
> I'm surprised they let through HACKER with all of the criminal > rep that name has unjustly acquired. I have no idea how DMV personnel decide what's acceptable on vanity plates but I saw "455H01E" not long ago so I guess they haven't perfected their filtering techniques. My car has my official single MA plate on the back and one of those Compaq LINUX plates on the front where I suppose the casual observer might conclude it's official NH issue. I was recently parked for just a few moments in downtown Lowell and came back outside to find a meter lady writing me a ticket. I asked her what the violation was and she mumbled something incoherent about the plates being different. I pressed for an explanation about specificially what the problem was and after much additional incoherence she finally tore up the citation and wandered away muttering. For all I know there may indeed be some (interpretation of some sort of) regulation that I'm violating with my plates, and even if not she probably still had the power to tangle me up by issuing the citation out of spite, so I guess I got lucky... ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
SSH authentication forwarding
Heh. It's funny now, looking back on it, but I experienced several minutes of panic this morning as I connected to a remote system via SSH and discovered that I was unexpectedly able to connect back to the originating system at will without mentioning any password. It was definitely a WTF moment since my ~/.ssh directory on the remote system has basically nothing in it, certainly no SSH keys. I was obliged to wonder if the SSH server on the originating system had somehow been compromised such that it no longer demanded keys for inbound connections, but I now understand better what is really going on: - The originating system is rigged such that SSH connections to localhost work without passwords because ~/.ssh/id_dsa.pub is mentioned in ~/.ssh/authorized_keys - SSH on the remote system is rigged by default to forward SSH authentication agent traffic. - My SSH client config on the originating system is rigged to permit authentication agent forwarding. ...so once I'd authenticated to the remote system via password all the plumbing was in place for the originating system to pass my key to remote system which passed it back to originating system, where it was found in the authorized_keys file and used to authenticate me. I note that the SSH man page warns: "Agent forwarding should be enabled with caution" Uh-huh... ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: tar -x without clobbering directories
My Debian system's tar identifies itself as "tar (GNU tar) 1.22" and the output generated with --help includes the following excerpt where that --no-overwrite-dir option sounds like what you wanted: Overwrite control: -k, --keep-old-files don't replace existing files when extracting --keep-newer-files don't replace existing files that are newer than their archive copies --no-overwrite-dir preserve metadata of existing directories --overwriteoverwrite existing files when extracting --overwrite-diroverwrite metadata of existing directories when extracting (default) --recursive-unlink empty hierarchies prior to extracting directory --remove-files remove files after adding them to the archive -U, --unlink-first remove each file prior to extracting over it -W, --verify attempt to verify the archive after writing it ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: searching/grepping for words "near" each other
> I want to search a text file for a few (alphabetic) words which > must be "near" each other, but not necessarily on the same line. grep is pretty much "line oriented" and although it's possible to script elaborate workarounds involving transfers back and forth between the "pattern" space and the "hold" space it's icky and slow to work against the grain that way. I predict that you'll end up using something like Python or Perl. I thought agrep ( the "approximate grep" that's part of Glimpse) might do the trick as it's willing to let you specify very sloppy search terms but, alas, it too is line oriented. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
FREE: misc components
Offered are some random computer components, including: half a dozen mice (some USB and some PS/2), PCI 10/100 enet adapters & graphics adapters, a parallel printer cable, several IDE CDROM drives, etc. In North Chelmsford near Drum Hill. Please take the whole lot if interested. Thx, --M ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
[OT] Linux=evidenceOfBadIntent (was: Shifty Shell Prompts)
> Data point [...] it was asserted the girl's spotless discipline > record was not proof she was a good student, but only that she had > not been caught violating school rules. Consider the implication Considered. The implication is that the "presumed innocent" dictum was ignored in that case and might therefore be ignored in others, which is the stuff of nightmares and fodder for much discussion (all of which I hope remains duly marked [OT] !) However, I'm obliged to confirm their assertion (while repulsed by their attitudes and methods) because, strictly speaking, it is true that a "spotless discipline record" proves essentially nothing. Think of all the fscking @55h0le5 you know (or know of) who happen to have a "spotless" record, at least as far as the relevant authorities are concerned. So that was actually more of a "lack of data" point... ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: set -e (was: RHEL-CentOS conversion scripts (was Re: apache?))
> the basic echoing of commands that I know is out there some where > would make my scripts way more professional. Anyone know that? Not quite sure what you're referring to but between bash's -x and -v options you will probably get as much chatty output as you could ever want. If you remember nothing else it's worth keeping in mind that bash offers lots of good interactive help. For example, the options in question are described as part of the "set" command, so if you say: help set ...you'll probably see what you want. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: set -e (was: RHEL-CentOS conversion scripts (was Re: apache?))
> one of the things that I am enthusiastic about: set -e"
I like that one, too, and I also like the way bash allows
you to trap on error conditions, thusly:
#!/bin/bash
function errHandler() {
echo 'errHandler activated'
}
trap errHandler ERR
echo Ready for first error... errexit FALSE
false# Force error condition.
set -e # Exit on any error.
echo Ready for second error... errexit TRUE
false# Force error condition.
echo After second error. # Not reached.
___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Out of memory while booting? update
> Is there any way to stop init partway through, so I could at > least see if unreasonable amounts of memory seem to have been > used, or look for other information? I've occasionally had to engage in this sort of hackery when debugging b0rken init logic and such. In the script of your choice, I'd add something like this: # Conditionally spawn an interactive shell on /dev/tty2 in background: # if grep wait4me /proc/cmdline ; then # setup a rendezvous so you can have this script # wait until you're ready for it to proceed: # cat /dev/null > /tmp/mutexFile /bin/bash -i < /dev/tty2 > /dev/tty2 2>&1 & # Cause this script to wait around until released... # while [ -e /tmp/mutexFile ] ; do sleep 5; done fi You can then switch over to tty2 using Alt-F2 and poke around using that interactive version of bash you just spawned. When ready, release your hacked script by deleting that /tmp/mutexFile. Your bash will live on until explicitly terminated, though tty2 will suddenly become useless if init is allowed to spawn a getty on it that will compete with your bash for I/O. Of course, if you ever get that far you'll probably be happy because it means you've solved the problem... You'll need to interrupt GRUB (or LILO) before it loads your kernel and tack that wait4me token onto the kernel's boot command line to activate this rendezvous stuff. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Interrupting fsck during startup
> I don't think it was ever considered a design feature that one > could/should interrupt fsck. Indeed, I concluded after my first (shallow) investigation that it couldn't possibly work. Just for starters, IIRC, the kernel's console driver doesn't even do job control or signal delivery. It's a mystery... ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Interrupting fsck during startup
>> our customers do find themselves occasionally needing to (re)start >> systems in time-critical situations > >Or they *think* they need an emergency reboot. This isn't windows. Ahh, but I love the way Ctl-Alt-Del gives That Fresh Feeling(tm)! With few exceptions our customers are Windows users and thus many are in the habit of rebooting as a first response to *any* situation. (If you know how to get them to change their ways then maybe you also know how to convince them to unmount USB drives before yanking the connector...) Other times a system is being restarted because it's dual-boot and may be in the process of changing roles. Or it might simply have been powered off for a while. We can't (shouldn't have to) predict the circumstances in which a customer might be (re)starting a machine; all we know is that we don't want it to cause them problems. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Out of memory while booting?
> He is going to copy a disk image to another machine and see if > things work there. That'll be a good test but it'd be easier (circumstances permitting) to just move the physical drive temporarily to another machine. You don't even care if that other machine can completely boot all the way up to a multiuser, X-capable condition using your disk - you just want to see if those same weirdo problems occur. This approach might not occur to him because (in my experience) it's less likely to work with Windows, but Linux disks can often be moved from one machine to another successfully. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Interrupting fsck during startup
Thanks for the responses. Tom Buskey wrote: > Shutdown cleanly so your system doesn't have to fsck. OMG! And all this time we've been instructing our customers to just pull the AC plug from the wall when they're finished using the systems... ;-> Yes, of course, clean shutdowns are to be preferred. But the problem in question is that our customers do find themselves occasionally needing to (re)start systems in time-critical situations when, for whatever reason, fsck decides it's time to preen, even though the system was previously shutdown cleanly. This seems clearly to be tied to ext3's defaults for the "Maximum mount count" and "Check interval" values and is not a problem with power-management or the startup/shutdown logic. We are investigating changing/disabling those values and, as suggested, relying instead on journal replays and scheduled, deliberate (as opposed to these pseudo-random) fsck runs to maintain/restore filesystem health. Changing filesystem types (to, say, ZFS) is ruled out primarily because of the logistical nightmare of inflicting such changes on systems in the field. I'm still curious, though, why it's possible on some older systems (eg. RHEL3) to interrupt fsck using Ctl-C... ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Interrupting fsck during startup
In certain time-critical situations it is desirable that we be able to interrupt fsck as it tries to preen certain huge filesystems. Yes, we know that interrupting fsck is not good sysadmin hygiene and we generally discourage such behavior, but when a machine is being (re)booted in a crisis situation where seconds matter it's at least an option we'd like to have available to us. In some older distributions of Linux it was possible to interrupt fsck via Ctl-C even if it was launched from one of the init scripts, but this "feature" seems not to be available with some more recent distributions we're working with, including CentOS5.2. Does anybody know how to enable this or what was changed or why? This is apparently quite a thorny issue as it involves trying to make sense of the esoterica associated with job-control, signal handling, ttys and /dev/console, any one of which is challenging by itself and nearly impenetrable in combination... >-/ ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
ARTICLE - openwrt/dd-wrt based modem/router vulnerability?
FWIW: http://apcmag.com/new-worm-can-infect-home-modemrouters.htm ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
TAKEN - USR Sportster Vi & 3com 3CXM756 modems
Both items have been claimed. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
FREE - 3com 3CXM756 PCMCIA GSM and cellular modem card
Free - never used - box still shrinkwrapped: http://www.usr.com/support/product-template.asp?prod=3cxm756 ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
FREE - USR Sportster Vi 28.8 external fax/modem
Now, don't everybody all crowd in at once trying to be the lucky person who snags this freebie, but I'm offering a US Robotics Sportster Vi external FAX/modem unit, pretty much new in box (most items still in shrinkwrap) to the first taker... ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Labeling Multipath drives
I wrote: > The reference to that label in the fstab confuses the kernel > because of the (apparently) duplicate labels it finds in the > mirrored partitions. Come to think of it, I'm not sure it's kernel code that's getting confused. Maybe it's the mount command or some library code - whatever; somebody is scanning for labels on all candidate devices and getting confused when it finds the duplicates in the mirrored filesystem images in those RAID partitions... ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Labeling Multipath drives
This sounds similar to the problems you'd see if you did this: mdadm --create --level=1 --raid-devices=2 /dev/md0 /dev/sda1 /dev/sdb1 mkfs.ext3 -L HiMom /dev/md0 ...and you then prepared an fstab line that referenced that device by its label, thus: LABEL=HiMom / ext3 defaults 1 1 That is: you've mirrored multiple partitions by assembling them into a RAID1 (accessed via /dev/md0) and then written a filesystem with a label into /dev/md0. The reference to that label in the fstab confuses the kernel because of the (apparently) duplicate labels it finds in the mirrored partitions. Is there a way to refer to filesystems in a RAID this way by label rather than by explicit /dev node? ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Question about the ADF of a scanner.
> feed rollers on some scanners and printers. Basically, they > get glazed and cannot pull the paper. Cleaning the feed rollers > helps sometimes. Typically I use alcohol to clean them and then, > if I'm still having a problem, a very, very mild abrasive I'll second that and as an aside I'll comment (having run printing presses and mail processing equipment in a previous life) that automated paper handling is a problem that gets %0.01 of the respect it deserves. Considering the essentially infinite combination of infuriatingly subtle variables (static electricity, fiber quality, temperature, moisture [ambient as well as absorbed], friction coefficients, roller degradation, fouling by dust/grease/fibers, etc, etc) it's a fscking miracle printers work at all, never mind that most of the time you don't even have to think about them. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: find mtime not the same as ls mtime?
>> find . -mtime 60 > >Doesn't mtime's arg mean that many days ago? So you're asking find >to mention files 60 days old, I think. Is that what you intended? I actually should have said, "So you're asking find to mention files last modified 60 days ago" ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: find mtime not the same as ls mtime?
> find . -mtime 60 Doesn't mtime's arg mean that many days ago? So you're asking find to mention files 60 days old, I think. Is that what you intended? ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
[OT] Obtaining Android handsets
Anybody have a contact at Google or T-Mobile that might be useful in acquiring (purchase/loan/gift) multiple live cell-capable Android handsets for app development? I know somebody who says he's tried via the "normal" channels and gotten no love... ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
ARTICLE - Awk and Sed One-Liners Explained
In light of the occasional questions here about sed and awk this article seems worth a mention: http://www.osnews.com/story/21004/Awk_and_Sed_One-Liners_Explained ...as it in turn mentions these: http://www.pement.org/awk/awk1line.txt http://www.catonmat.net/blog/awk-one-liners-explained-part-one/ http://www.catonmat.net/blog/awk-one-liners-explained-part-two/ http://www.catonmat.net/blog/awk-one-liners-explained-part-three/ http://www.catonmat.net/blog/update-on-famous-awk-one-liners-explained/ http://student.northpark.edu/pemente/sed/sed1line.txt http://www.catonmat.net/blog/sed-one-liners-explained-part-one/ http://www.catonmat.net/blog/sed-one-liners-explained-part-two/ http://www.catonmat.net/blog/sed-one-liners-explained-part-three/ ...which are all good except that I'd point out that a slightly newer version of the list of sed one-liners appears to be available here: http://sed.sourceforge.net/sed1line.txt ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: 64 bit C question
> You will see the solution as soon as you hit "Send" Rich Hall (author of "Sniglets") defines the Onosecond as, "the interval of time after you strike the Enter key before you realize what you've just done..." ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: [GNHLUG] Reminder of "UNIX Time" event: Today, Friday 13th, 18:31:30 EST (that is about 6:30 P.M. for Microsoft users) - Marthas Please RSVP
>> http://www.1234567890day.com/ > >http://coolepochcountdown.com/ An NPR radio program (Day to Day) discussing the event was broadcast on Friday and this followup program will apparently be heard today at 3pm: Unix: An Operating System, Not A Timekeeper by Steve Proffitt "Day to Day, February 16, 2009 ยท On "1-2-3-4-5-6-7-8-9-0 Day," tech lovers all over the world celebrated the moment when the clocks in the popular Unix computer operating system struck that exact stream of numbers. But on Feb. 13, Day To Day incorrectly called Unix the timekeeper instead of an operating system. Here is why. Audio for this story will be available at approx. 3:00 p.m. ET" http://www.npr.org/templates/story/story.php?storyId=100751250 http://www.npr.org/templates/rundowns/rundown.php?prgId=17 http://www.wbur.org/ ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: [GNHLUG] Reminder of "UNIX Time" event: Today, Friday 13th, 18:31:30 EST (that is about 6:30 P.M. for Microsoft users) - Marthas Please RSVP
http://www.1234567890day.com/ ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Tutorials on VM, cacheing, etc - http://duartes.org/gustavo/blog/
Some easily digestible writeups about memory management, CPU caches, the boot process, etc: http://duartes.org/gustavo/blog/ ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Uninitialized static int counters?
> I'm not sure if kernel printfs are enabled in production kernels. > I forget how they are configured, so it is possible that no-one > will ever see the message. They're enabled - that's what drew my attention to that code in the first place. The 32bit version of libraw1394 apparently uses ioctls not supported by the x86_64 kernels... >-/ ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Uninitialized static int counters?
> The bottom line is that in the section of code you presented, > what was important was to establish a block so a variable could > be defined. Adding the do while(0) is just adding > some extraneous code that would be most probably optimized out, > but even if it is not, it is in an error condition. I suspect that whoever added that code to the kernel cribbed it from elsewhere without understanding (or maybe not caring whether they understood) it. At any rate, I wasn't concerned about that do-while(0) construct so much as the apparent randomness of allowing the past behavior of other processes to determine whether the kernel will utter a complaint about the current process's behavior. That, BTW, is what was in my head when I used the term "Uninitialized" in my Subject: line, arguably a poor choice of words. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
