Re: Suggestions: Job boards, listings, contacts? for Senior Technical Writer

[Todd Littlefield]

A friends wife (both tech writers) was just hired by Amazon down in MA. 
I think it's their robotics division.  They may have additional openings.

Best wishes in the hunt!

- Todd
___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/

Re: Delayed mail from GNHLUG?

[Todd Littlefield]

On 12/12/2012 10:09 AM, Tom Buskey wrote:



On Tue, Dec 11, 2012 at 1:02 PM, > wrote:


True... but I always thought it was a massive faux pas for a
SysAdmin to actually admit it was his mistake.  It's never the
admin's fault, some user did something bad.  I'm sure if Ben
reviewed the logs closely enough, he could finger point.


No, a sysadmin should never cover up mistakes.  Otherwise you end up 
trying to troubleshoot and fix the wrong problem. We're all human and 
learning how these systems break (which is rarely documented, even 
internally) so mistakes happen.


Obviously Ben is a good sysadmin (from how well the site runs) and a 
great sysadmin for figuring out and exposing the root cause so it 
could be fixed.  If any of us are running the GNHLUG mailman server, 
we have shared knowledge.  Great sysadmins help create more 
sysadmins.  Good ones just keep systems running.


Thanks Ben!



Agreed... I was just making a joke.

Keeping a volunteer project running is a major (and usually thankless) 
job.  So, my most humble apologies.  I did not mean to denigrate what 
Ben has done with the full disclosure and the tireless work on behalf of 
GNHLUG.


- Todd
___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/

Sparc 20 to a good home

[Todd Littlefield]

Hello,

 Yet another cleaning of the computer room has occurred, per order 
of the Chief Spousal Officer.  Free to a good home in the Manchester - 
Nashua area is a Sparc 20 system.  It has a Ross HyperSparc processor, 
384 MB of RAM, keyboard, mouse and Monitor (including the remote).  
Right now it is booting/running Solaris 2.7.

 It is older hardware, but if someone can re-use it great!  If not, 
to the electronic recycler it goes.

 Thanks!

- Todd
___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/

Re: DHCPD and Windows question

[Todd Littlefield]

I finally got some time to sit down with Wireshark and compare the bootp 
packets between the D-Link
and the Linux box...  The first thing that jumped out as different was 
the source address on the DHCP Offer

packets.

D-Link:  192.168.1.1
Linux: 127.0.0.1

So, something wasn't right.  I began mucking around with a bunch of 
different settings based on the

dhcpd.conf(5) pages.  None seemed to work...

After looking a little closer at the server-identifier tag, it was 
misconfigured...  I was using the name instead of

IP address.  The man pages are a bit confusing though...  It states:

Theserver-identifier  statement

 *server-identifier*  hostname*;*

 The  server-identifier statement can be used to define the value that
 is sent in the DHCP Server Identifier option for a given scope.   The
 value  specified*must*  be an IP address for the DHCP server, and must
 be reachable by all clients served by a particular scope.



So, it needs to be set to the --hostname-- but they really mean --IP--  
Why they didn't just specify it as:



Theserver-identifier  statement

 *server-identifier*  *address;*


I guess we will never know...  Right below that is the server-name tag, 
which really is the name.  So, if anyone
else runs into this problem, the answer is RTFM --Carefully-- before 
adding things to the config.


Thanks to everyone for their help!

- Todd



On 1/30/2010 11:03 PM, Brian St. Pierre wrote:

On Fri, January 29, 2010 7:10 pm, Todd Littlefield wrote:
   

If I disable the daemon on the server and use the one on the router,
the Windows boxes are happy...  But that makes me unhappy.  I'm at my wits
end trying to get it figured out.
 

Can you get a wireshark capture of (a) the broken request and (b) the
working request?

Then compare the two and change whatever is needed in your config (one
thing at a time) to make (a) look more like (b).

--
Brian St. Pierre

   


___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/

DHCPD and Windows question

[Todd Littlefield]

Hello,

   I have a stupid question about how to configure the ISC DHCPD to 
work with
Vista/Win7.  At home I have XP and Linux systems running.  They all will 
broadcast

out to the network to find the server and request and address/lease.

   The DHCPD server is configured to hand out the same address, based 
on MAC
to all the machines/switches/etc. that are running internally.  The 
problem comes in when someone with a laptop running Vista or Win7 comes 
over.  According to M$ they
changed their DHCP client in Vista and 7 to rely on broadcasting to get 
address.


   From digging on the network, it seems to be that the broadcast flag 
needs
to be enabled on the server side.  Otherwise when clients beacon out to 
get an

address, the server doesn't respond to it.  (perhaps the incorrect choice of
words for the behavior)


   I've dug through the ISC docs for the daemon.  I thought the 
always-broadcast command would do it...  Unfortunately that is not the 
case.  There didn't seem to

be anything in the GNHLUG email archives about this problem.

   If I disable the daemon on the server and use the one on the router, 
the Windows
boxes are happy...  But that makes me unhappy.  I'm at my wits end 
trying to get it

figured out.


   The server in question is running CentOS 5.4 with dhcp-3.0.5-21 
running.  The running config is attached.  I'm sure I there are multiple 
things that could be set up better but it passes parsing and works, at 
least until someone visits.



   Any and all help is greatly appreciated.  Thanks in advance!


- Todd
#
# dhcpd.conf
#
server-identifier my.domain.net;
default-lease-time 86400;
ddns-update-style ad-hoc;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.1.255;
option routers 192.168.1.1;
option domain-name "my.domain.net";
option domain-name-servers 192.168.1.10,68.87.71.226,68.87.73.242;
option netbios-name-servers 192.168.1.10;
always-broadcast on;
authoritative;

# these were for setting up the comcast modem... ignore
#option domain-name-servers 68.87.64.140,68.87.66.135;

subnet 192.168.1.0 netmask 255.255.255.0 {
range dynamic-bootp 192.168.1.101 192.168.1.200;
}
 
host dd-wrt.my.domain.net {
hardware ethernet 00:1A:70:71:6E:66;
fixed-address 192.168.1.2;
}
host dgs-1224t.my.domain.net {
hardware ethernet 00:24:01:63:9a:4b;
fixed-address 192.168.1.5;
}
host chaos.my.domain.net {
hardware ethernet 00:50:DA:7D:66:42;
fixed-address 192.168.1.10;
}
host iscsi.my.domain.net {
hardware ethernet 00:0f:3d:88:2c:a3;
fixed-address 192.168.1.11;
}
host myth-backend.my.domain.net {
hardware ethernet 00:13:D3:E9:DD:0D;
fixed-address 192.168.1.12;
}
host linkstation.my.domain.net {
hardware ethernet 00:16:01:bc:3c:54;
fixed-address 192.168.1.13;
}
host epson810.my.domain.net {
hardware ethernet 00:00:48:76:b1:c9;
fixed-address 192.168.1.18;
}
host ps20fe54.my.domain.net {
hardware ethernet 00:c0:02:20:fe:54;
fixed-address 192.168.1.19;
}
host mayhem.my.domain.net {
hardware ethernet 00:a1:b0:80:37:6b;
fixed-address 192.168.1.21;
}
host entropy.my.domain.net {
hardware ethernet 00:0c:76:c0:37:90;
fixed-address 192.168.1.22;
}
host delta-s.my.domain.net {
hardware ethernet 00:0F:3D:88:2C:99;
fixed-address 192.168.1.23;
}
host mythtv.my.domain.net {
hardware ethernet 00:E0:18:BF:2A:D8;
fixed-address 192.168.1.24;
}
host myth-bedroom.my.domain.net {
hardware ethernet 00:16:44:86:72:67;
fixed-address 192.168.1.25;
}
host myth-livingroom.my.domain.net {
option broadcast-address 192.168.1.255;
hardware ethernet 00:26:2d:10:b9:5c;
fixed-address 192.168.1.26;
}
host jenlaptop.my.domain.net {
hardware ethernet 00:13:E8:87:68:97;
fixed-address 192.168.1.100;
}
___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/

Re: howto determine processor characteristics from cli

[Todd Littlefield]

Hi Bruce,

Try "more /proc/cpuinfo"  That should give you everything you want 
to know about it.

- Todd

Labitt, Bruce wrote:
> I've got a Dell Optiplex 745 that I'm trying to figure out if it is
> worth adding more memory to it.  I'd like to find out what
> processor/speed/cache it has.  Is there a simple way to get this?  I
> would imagine it is all contained in the kernel startup log?  dmesg |
> grep (something) ?  Or is there a different way?
>
> tia
>
> ___
> 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: [OT] Geek Toys

[Todd Littlefield]

There is a glaring error in their... presentation...

They forgot the nybble/nibble, depending on how you want to spell it...

Paul Lussier wrote:
> http://www.engadget.com/2007/08/08/art-lebedevs-matryoshkus-redefines-babushka-dolls/
>   

___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/

Re: encountered two fedora 6 issues - underscore in host name, :*: in passwd file prevented logins

[Todd Littlefield]

If I remember correctly, underscores are not allowed in names.  Only 
a-z, 0-9 and the

hyphen character are acceptable.  I can't quote the RFC, but someone here
probably can ;-)

Python wrote:

(For Your Information - it may save you some grief)

amanda would not backup my laptop.  There were no useful error messages
in the amanda log.  I finally ran tcpdump to monitor the chit-chat and
discovered that reverse lookup for my LAN (192.168.0.x) numbers was not
working.  


host 192.168.0.5
Host 5.0.168.192.in-addr.arpa not found: 3(NXDOMAIN)
mem.c:877: INSIST(ctx->stats[i].gets == 0U) failed.
Aborted

named-checkzone approved the zone file; named-checkconf approved the
overall configuration.

named-checkconf -t /var/named/chroot -z
(use chroot style of operation)
(load the zone files)
gave an error for a host name s_kvam in the reverse lookup file.  Once I
changed the hostname to be skvam, the reverse lookup worked.



The other issue was an inability to login as root!  This spooked me, but
there was no evidence of foul play.  My normal account and sudo worked.
The fix consisted of changing the root line:

< root:*:0:0:root:/root:/bin/bash
---
  

root:x:0:0:root:/root:/bin/bash




The problems were on a system that I upgraded from FC3 to FC6.  

  


___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/

Re: gnhlug-discuss digest, Vol 1 #1746 - 1 msg

[Todd Littlefield]

Hi Mike,

   Check your InputDevice section for the mouse.  Make sure it has a 
ZAxisMapping.

The one from my xorg.conf (formerly XF86Config I think) looks like:

Section "InputDevice"
   Identifier  "Mouse0"
   Driver  "mouse"
   Option  "Protocol" "IMPS/2"
   Option  "Device" "/dev/input/mice"
   Option  "ZAxisMapping" "4 5"
   Option  "Emulate3Buttons" "yes"
EndSection


The importnat piece is the Option "ZaxisMapping... " section.  Try 
adding that to the

config file...  Make sure you have a backup copy before trying this!!!


[EMAIL PROTECTED] wrote:


Send gnhlug-discuss mailing list submissions to
gnhlug-discuss@mail.gnhlug.org

To subscribe or unsubscribe via the World Wide Web, visit
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]

You can reach the person managing the list at
[EMAIL PROTECTED]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of gnhlug-discuss digest..."


Today's Topics:

  1. mouse wheel .. (Mike Medai)

--__--__--

Message: 1
Date: Sat, 14 Jan 2006 07:46:54 -0500
From: Mike Medai <[EMAIL PROTECTED]>
To: GNHLUG 
Subject: mouse wheel ..

I'm having problems getting my mouse wheel to work again.  I killed my 
X-server in the process of changing my monitor (I guess I picked a bad 
resolution or something), and ended up having to run XF86Config to 
rebuild and copy it resulting in a semblance of booting Kde again.  
(Major victory for me!  )


But for the time being, my wheel mouse does not respond as a wheel 
should by scrolling.  It does respond as a third key when pressed.  I've 
ran Yast (am playing with Suse 9.0 Pro with Kde 3.1), and the Kde config 
interface, and one or two other graphical interface configs that had 
something to do with a mouse .. plus the original XF86Config where I 
selected the mouse previously.


Any ideas on how I can fix this?  I've looked through my manuals/books 
but haven't been able to glean a solution.


Thanks.

 



___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss