Re: Boston Linux Meeting Wednesday, October 20, 2010 Hardware Hacking: Atomic Clock Building
On 10/14/2010 3:02 PM, Joshua Judson Rosen wrote: > Bruce Labitt writes: >> On 10/14/2010 8:34 PM, John Abreau wrote: >>> On Thu, Oct 14, 2010 at 5:07 PM, Bruce Labitt >>>wrote: > Federico builds an atomic clock out of a pocket-sized Sheevaplug device > [...] >>> Given that the event is still in the future (Oct 20), I don't think >>> anyone went to it yet. >> :-[ >> >> OK, I jumped the gun :) I guess I'm relly ahead of >> everyone on this! >> >> That being said, are there any good primary sources that are >> affordable? > This guy may know: > > http://leapsecond.com/pages/atomic-bill/ > > Look at http://www.itwire.com/business-it-news/open-source/40246-radclock-delivers-atomic-clock-accuracy-through-software ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
How Linux Saved A Fast Food Giant.
this should be of interest http://therealedwin.com/2010/05/17/how-linux-saved-a-fast-food-giant/ ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
opensource.com
I do not think I have seen this posted. There is a new community web page. opensource.com "A Red Hat community service" . It is worth taking a look at. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Linus at Windows 7 booth in Japan
http://picasaweb.google.com/cschlaeger/JapanLinuxSymposium#539540458161906 ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Linus at the Windows 7 booth in Japan
http://picasaweb.google.com/cschlaeger/JapanLinuxSymposium#539540458161906 ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Blackduck Software and IP
I think that calling them a scam is a thoughtless remark. They presented at Pierce Law along with Richard Stallman , Dan Ravisher ( Free Software Foundation) and others on Law and Technology. They said today you can no longer blindly ship software hoping you actually own everything in the software. There are tools to allow the software to be validated. A management policy which forbids this regrettably does not work. This can result in expensive legal costs. Don ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
GPLV3 webcast
BlackDuck software recently did a webcast on GPLV3. It can be found on their web page at http://blackducksoftware.com/resources/presentations . This was done by a Lawyer and should be of interest. It runs 55 min. Don ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Problem with wrt54gl router
Keeping power off on the cable modem fixed the problem. I had recycled it before but only for a short time. When it was working /etc/resolv.conf had an entry to search and 3 name servers. Don ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Problem with wrt54gl router
Ben Scott wrote: > On 9/17/07, Don Leslie <[EMAIL PROTECTED]> wrote: > >> When I bring up the network /etc/resolv.conf has the following: >> >> search >> nameserver 192.168.1.1 >> >> This is true for both hardwired and wireless. >> > > What were you expecting instead? Have you tried actually running a > lookup with that IP address as the "nameserver"? > > 192.168.1.1 may actually be correct. As I recall, the stock LinkSys > firmware runs a DNS proxy on the router. That means machines inside > your LAN can just send their DNS queries to the router, and the router > will handle forwarding the request out to whatever the ISP nameservers > are today. > > Assuming that is *not* the situation: Have you tried rebooting the > router? Have you tried updating to the latest firmware on the router? > (These are standard procedures, yes, but they're standard because > they often work. :) ) > > Assuming *that* does not fix anything: What OS/distribution/release > are you running on your DHCP client? > > -- Ben > > I do not remember what it looked like when things worked. If I try to ping the Roadrunner name server I get from 192.16.1.1 Destination Unreachable dig fails to find a server I am running SuSE 10.2 . I rebooted the router which made no difference. I could look into new firmware but it has been running fine for months. Don ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Problem with wrt54gl router
I have a Linksys WRT54GL router with the original firmware. It worked fine until yesterday. When I bring up the network /etc/resolv.conf has the following: search nameserver 192.168.1.1 This is true for both hardwired and wireless. If I run dhclient it acts as if everything is working but I get no nameservers. If I connect directly to the external network everything works fine. Don ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: High Latency Survival Tactics (Was: Re: Thunderbird stupid about X traffic?)
I have not used FreeNX but I did use their commercial product NX. It made a huge improvement. Don ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: As a world traveler this would be my greatest nightmare....
Public blue screens are a fertile territory: www.miguelcarrasco.net/miguelcarrasco/2006/10/blue_screen_of_.html api.flickr.com/services/feeds/[EMAIL PROTECTED]&format=rss_200 ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Entertaining DEC stuff
http://cwflyris.computerworld.com/t/1932927/66622678/74698/2/ This points to a Computer World article which has links to a 12 minute DEC marketing video "Educating Peter" and the very funny mock Ad "DEC Wash" plus more links. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Entertaining DEC stuff
http://cwflyris.computerworld.com/t/1932927/66622678/74698/2/ This points to a Computer World article which has links to a 12 minute DEC marketing video "Educating Peter" and the very funny mock Ad "DEC Wash" plus more links. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
a song about Perl on YouTube by Pudge
http://www.youtube.com/watch?v=Mxk5RMQF6Js ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Nashua to offer "free" WiFi
Michael ODonnell wrote: > "The Chamber intends to launch this new service in June of 2007" > >http://www.nashuachamber.com/Services/wifi.htm > > ...no technical details are provided. I wonder if we'll > be able to stream the GNHLUG meetings from Martha's live... ;-> > > ___ > gnhlug-discuss mailing list > gnhlug-discuss@mail.gnhlug.org > http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/ > > You may want to look at http://www.avivadirectory.com/blogger-law/ . ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Problem build initrd file
Thomas Charron wrote: You're misunderstanding what I'm asking. Is the initrd that works IN the root of the drive, in /, or is it in /boot? On 3/23/07, Don Leslie <[EMAIL PROTECTED]> wrote: Thomas Charron wrote: > > But is that where the files are physically located? in / vs /boot? > /boot is on /dev/sda1 original grub entry root (hd0,0) kernel /vmlinux-2.4.21-27-mpt_scsi ro root=LABEL=/ hda=ide-scsi I tried kernel /vmlinux-2.4.21-27-mpt_scsi ro root=LABEL=/dev/sda1 hda=ide-scsi & kernel /vmlinux-2.4.21-27-mpt_scsi ro root=LABEL=/dev/hda1 hda=ide-scsi I get the same error . ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/ initrd is in /boot for the working system ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Problem build initrd file
Thomas Charron wrote: But is that where the files are physically located? in / vs /boot? /boot is on /dev/sda1 original grub entry root (hd0,0) kernel /vmlinux-2.4.21-27-mpt_scsi ro root=LABEL=/ hda=ide-scsi I tried kernel /vmlinux-2.4.21-27-mpt_scsi ro root=LABEL=/dev/sda1 hda=ide-scsi & kernel /vmlinux-2.4.21-27-mpt_scsi ro root=LABEL=/dev/hda1 hda=ide-scsi I get the same error . ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Problem build initrd file
Thomas Charron wrote: On 3/22/07, Don Leslie <[EMAIL PROTECTED]> wrote: I have a RHEL3 system which boots from scsi disk . # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/sda2 # initrd /initrd-version.img #boot=/dev/sda default=0 timeout=10 splashimage=(hd0,0)/grub/splash.xpm.gz title Red Hat Enterprise Linux WS (2.4.21-27.EL_SNARE096) root (hd0,0) kernel /vmlinuz-2.4.21-27.EL_SNARE096 ro root=LABEL=/ hda=ide-scsi initrd /initrd-2.4.21-27.EL_SNARE096.img title Red Hat Enterprise Linux WS (2.4.21-27.EL) root (hd0,0) kernel /vmlinuz-2.4.21-27.EL ro root=LABEL=/ hda=ide-scsi initrd /initrd-2.4.21-27.EL.img title Red Hat Enterprise Linux WS (2.4.21-27.EL mpt scsi) root (hd0,0) kernel /vmlinux-2.4.21-27-mpt_scsi ro root=LABEL=/ hda=ide-scsi initrd /initrd-2.4.21-27-mpt_scsi.EL_SNARE096.img Wait, are your files in /boot, or in the root? Sorry, I haven't fudged with grub for a while, but if their in /boot, wouldnt they need to full path? The other boots in menu.lst work and they use root=/ ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Problem build initrd file
[SHIFT]+[PAGE UP] This does not work . On the boot messages . I get : IP routing cache ... TCP: Hash table ... NET4: Unix domain sockets ... then ds: no socket drivers on the working boot at this point I get RAMDISK compressed image found at block 0 ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Problem build initrd file
1) The older grub entry works just fine 2) I did also run the following: make mrproper make xconfig Again from LSI: Look for the new top-level "Fusion-MPT device support" entry: Fusion-MPT device support ---> and select it to access the Fusion-MPT drivers submenu entries: Fusion-MPT (base + ScsiHost) drivers Enhanced SCSI error reporting < > Fusion-MPT misc device (ioctl) driver < > Fusion-MPT LAN driver On the submenu, select the "Fusion-MPT (base + ScsiHost) drivers" line, and then enter "m" to configure for building this support as a module. 3) I logged the output from make modules_install . I believe the only updates were to the fusion modules. 4) The boot info scrolls off the screen but I do see a line with HDA . ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Problem build initrd file
I have a RHEL3 system which boots from scsi disk . There is also LSI 1030 scsi controller for a HP Ultrium tape drive . I did the following to add the new drivers ( per Lsi web page ). cd /usr/src/linux-2.4.21-27.EL tar zxvf /home/urdge/LSIdriver/fusion-2.05.16.tgz tar tzvf /home/urdge/LSIdriver/fusion-2.05.16.tgz drwxr-xr-x root/root 0 2004-04-26 15:17:22 fusion/ drwxr-xr-x root/root 0 2004-04-26 15:19:24 fusion/lsi/ -rw--- root/root 32113 2004-04-26 15:19:24 fusion/lsi/mpi.h -rw--- root/root104949 2004-04-26 15:19:24 fusion/lsi/mpi_cnfg.h -rw--- root/root 17696 2004-04-26 15:19:24 fusion/lsi/mpi_fc.h -rw--- root/root 9422 2004-04-26 15:19:24 fusion/lsi/mpi_inb.h -rw--- root/root 17578 2004-04-26 15:19:24 fusion/lsi/mpi_init.h -rw--- root/root 37524 2004-04-26 15:19:24 fusion/lsi/mpi_ioc.h -rw--- root/root 9706 2004-04-26 15:19:24 fusion/lsi/mpi_lan.h -rw--- root/root 10259 2004-04-26 15:19:24 fusion/lsi/mpi_raid.h -rw--- root/root 8419 2004-04-26 15:19:24 fusion/lsi/mpi_sas.h -rw--- root/root 22672 2004-04-26 15:19:24 fusion/lsi/mpi_targ.h -rw--- root/root 15262 2004-04-26 15:19:24 fusion/lsi/mpi_tool.h -rw--- root/root 2284 2004-04-26 15:19:24 fusion/lsi/mpi_type.h -rw--- root/root 5997 2004-04-26 15:19:24 fusion/lsi/fc_log.h -rw--- root/root 15679 2004-04-26 15:19:24 fusion/lsi/mpi_history.txt -rw-r- root/root 1237 2004-02-04 20:53:06 fusion/Config.in -rw-r--r-- root/root 9178 2004-03-15 01:15:17 fusion/linux_compat.h -rw-r--r-- root/root 2203 2004-03-16 13:00:16 fusion/Makefile -rw-r--r-- root/root 45398 2004-03-15 01:15:17 fusion/ascq_tbl.c -rwxr-x--- root/root 3080 2004-02-04 20:53:06 fusion/ascq_tbl.sh -rw-r--r-- root/root 4703 2004-03-15 01:15:17 fusion/isense.c -rw-r--r-- root/root 2803 2004-03-15 01:15:17 fusion/isense.h -rw-r--r-- root/root 89064 2004-03-16 11:08:12 fusion/mptctl.c -rw-r--r-- root/root 13501 2004-03-15 01:15:17 fusion/mptctl.h -rw-r--r-- root/root 49451 2004-03-15 01:15:17 fusion/mptlan.c -rw-r--r-- root/root 2417 2004-03-15 01:15:17 fusion/mptlan.h -rw-r--r-- root/root216324 2004-03-16 11:02:00 fusion/mptscsih.c -rw-r--r-- root/root 10181 2004-03-15 01:15:17 fusion/mptscsih.h -rw-r--r-- root/root 21887 2004-03-15 01:15:17 fusion/scsi3.h -rw-r--r-- root/root 9267 2004-03-15 01:15:17 fusion/scsiops.c -rw-r--r-- root/root 34580 2004-03-16 13:00:16 fusion/mptbase.h -rw-r--r-- root/root170805 2004-03-15 01:36:28 fusion/mptbase.c cp fusion/Config.in drivers/message/fusion cp fusion/Makefile drivers/message/fusion make dep make clean make bzImage make modules make modules_install mkinitrd initrd-2.4.21-27-mpt_scsi.EL_SNARE096.img 2.4.21-27.EL cp initrd-2.4.21-27-mpt_scsi.EL_SNARE096.img /boot/ cp arch/i386/boot/bzImage /boot/vmlinux-2.4.21-27-mpt_scsi Updated grub # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/sda2 # initrd /initrd-version.img #boot=/dev/sda default=0 timeout=10 splashimage=(hd0,0)/grub/splash.xpm.gz title Red Hat Enterprise Linux WS (2.4.21-27.EL_SNARE096) root (hd0,0) kernel /vmlinuz-2.4.21-27.EL_SNARE096 ro root=LABEL=/ hda=ide-scsi initrd /initrd-2.4.21-27.EL_SNARE096.img title Red Hat Enterprise Linux WS (2.4.21-27.EL) root (hd0,0) kernel /vmlinuz-2.4.21-27.EL ro root=LABEL=/ hda=ide-scsi initrd /initrd-2.4.21-27.EL.img title Red Hat Enterprise Linux WS (2.4.21-27.EL mpt scsi) root (hd0,0) kernel /vmlinux-2.4.21-27-mpt_scsi ro root=LABEL=/ hda=ide-scsi initrd /initrd-2.4.21-27-mpt_scsi.EL_SNARE096.img At boot I get : Cannot open root device LABEL=/ or 00:00 Please append a correct "root=" boot option Unable to mount root fs on 00:00 Any suggestions? ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
linux on Itanium
I believe that HP initially used Debian as its Linux. The link to debian ports is : http://www.debian.org/ports/index#released Look at http://www.gag.com/~bdale. Bdale Garbee is HP's chief Linux Technology Person and is active in the Debian community. He may be of help. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
