Re: Lisp learning?

I don't know of any Lisp-specific courses in the Portland area. What
specific applications are you interested in? There are a couple of good
books on algorithmic composition that are Lisp based -- Rick Taube's
"Notes from the Meta Level" and David Cope's "The Algorithmic Composer".

Randall Lucas wrote:

> Where might I find a Portland-area course in Common Lisp?  I am an
> experienced Perl programmer, though too much a self-taught one.  I am
> also literate in Java, and conversant in OO, although I have no formal
> CS background.  Perhaps an ideal would be a CS college course that
> uses Lisp, but alas many of the local course catalogs do not specify
> language.
>
> Randall
>
>

Re: Re: Re: OT: T1 Line pricing? - 1st hop times

> On Thu, 2005-04-28 at 22:14 -0700, Steven Raymond wrote:
> > > 64 bytes from 10.139.80.1: icmp_seq=1 ttl=255 time=5.31 ms
> > > 64 bytes from 10.139.80.1: icmp_seq=2 ttl=255 time=5.77 ms
> > > 64 bytes from 10.139.80.1: icmp_seq=3 ttl=255 time=6.28 ms
> > > 64 bytes from 10.139.80.1: icmp_seq=4 ttl=255 time=4.50 ms

Wil Cooley wrote:
> Hm, my DSL-Only isn't so good:
> $ ping 63.105.18.1 
> PING 63.105.18.1 (63.105.18.1) 56(84) bytes of data.
> 64 bytes from 63.105.18.1: icmp_seq=0 ttl=63 time=51.6 ms
> 64 bytes from 63.105.18.1: icmp_seq=1 ttl=63 time=37.9 ms
> 64 bytes from 63.105.18.1: icmp_seq=2 ttl=63 time=45.1 ms

Between the two comes this Speakeasy hop:
[mikeraz <at> dawg mikeraz]$ ping -c 10 66.93.39.1
PING 66.93.39.1 (66.93.39.1) 56(84) bytes of data.
64 bytes from 66.93.39.1: icmp_seq=0 ttl=127 time=31.7 ms
64 bytes from 66.93.39.1: icmp_seq=1 ttl=127 time=34.9 ms
64 bytes from 66.93.39.1: icmp_seq=2 ttl=127 time=34.1 ms
64 bytes from 66.93.39.1: icmp_seq=3 ttl=127 time=29.6 ms

But I take some consolation in knowing the router is in 
Seattle.
[mikeraz <at> dawg mikeraz]$ host 66.93.39.1
1.39.93.66.in-addr.arpa domain name pointer er1.sea1.speakeasy.net.

Wil, where's your first hop located?

--

-- 

Re: Re: Re: OT: T1 Line pricing? - 1st hop times

Michael Rasmussen wrote:

>>On Thu, 2005-04-28 at 22:14 -0700, Steven Raymond wrote:
>>    
>>
>>>>64 bytes from 10.139.80.1: icmp_seq=1 ttl=255 time=5.31 ms
>>>>64 bytes from 10.139.80.1: icmp_seq=2 ttl=255 time=5.77 ms
>>>>64 bytes from 10.139.80.1: icmp_seq=3 ttl=255 time=6.28 ms
>>>>64 bytes from 10.139.80.1: icmp_seq=4 ttl=255 time=4.50 ms
>>>>        
>>>>
>
>Wil Cooley wrote:
>  
>
>>Hm, my DSL-Only isn't so good:
>>$ ping 63.105.18.1 
>>PING 63.105.18.1 (63.105.18.1) 56(84) bytes of data.
>>64 bytes from 63.105.18.1: icmp_seq=0 ttl=63 time=51.6 ms
>>64 bytes from 63.105.18.1: icmp_seq=1 ttl=63 time=37.9 ms
>>64 bytes from 63.105.18.1: icmp_seq=2 ttl=63 time=45.1 ms
>>    
>>
>
>Between the two comes this Speakeasy hop:
>[mikeraz <at> dawg mikeraz]$ ping -c 10 66.93.39.1
>PING 66.93.39.1 (66.93.39.1) 56(84) bytes of data.
>64 bytes from 66.93.39.1: icmp_seq=0 ttl=127 time=31.7 ms
>64 bytes from 66.93.39.1: icmp_seq=1 ttl=127 time=34.9 ms
>64 bytes from 66.93.39.1: icmp_seq=2 ttl=127 time=34.1 ms

Re: Lisp learning?

>>>>> "Randall" == Randall Lucas <rlucas <at> tercent.com> writes:

Randall> Where might I find a Portland-area course in Common Lisp?  I
Randall> am an experienced Perl programmer, though too much a
Randall> self-taught one.  I am also literate in Java, and conversant
Randall> in OO, although I have no formal CS background.  Perhaps an
Randall> ideal would be a CS college course that uses Lisp, but alas
Randall> many of the local course catalogs do not specify language.

There was a movement on comp.lang.lisp a while ago to start local
Lispnik groups.  I'd be interested.  

I went down to Powells Technical Books to look at the new _Practical
Common Lisp_, but was slightly disappointed by the typography/artistic
design of the book.  Specifically, the margins weren't generous enough
and there was excessive use of bold in the headings.  I don't buy a
lot of books these days anyway, and aesthetics are important to me in
programming.  It bothers me to buy "ugly" books.  Lot's of beautiful
Lisp books, most of which I've got already.

--

-- 
Russell Senior         ``I have nine fingers; you have ten.''
seniorr <at> aracnet.com

OT: Snip damage

On Saturday April 30 2005 7:43 pm, Adam L. Klein wrote:
> Michael Rasmussen wrote:
> >>On Thu, 2005-04-28 at 22:14 -0700, Steven Raymond wrote:
> >>>>64 bytes from 10.139.80.1: icmp_seq=1 ttl=255 time=5.31 ms
> >>>>64 bytes from 10.139.80.1: icmp_seq=2 ttl=255 time=5.77 ms
> >>>>64 bytes from 10.139.80.1: icmp_seq=3 ttl=255 time=6.28 ms
> >>>>64 bytes from 10.139.80.1: icmp_seq=4 ttl=255 time=4.50 ms

Careful on the quoting, people, somewhere along the lines someone 
stripped out two levels of quote attribution and now it looks like 
Steven Raymond got my ping times.

--

-- 
Paul Johnson
Email and Instant Messenger (Jabber): baloo <at> ursine.ca
http://ursine.ca/~baloo/

_______________________________________________
PLUG mailing list
PLUG <at> lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Re: Invisible Directory

>From: Rich Shepard <rshepard <at> appl-ecosys.com>
> On Sat, 30 Apr 2005, Rich Shepard wrote:
> >    I should have mentioned that I get the same results (or lack thereof)
> > when using the '-a' flag with ls. That is, 'ls -a', or 'ls -la' indicates the
> > directory is there but not readable/visible.
> 
>    Aha! I now know what happened, but not sure why and I certainly don't know
> how to gracefully recover.
> 
>    When I use the 'mount' command I see this:
> 
> none on /data2/winstuff type smbfs (0)
> 
> which tells me that when I was trying to get vmware to see the share I
> somehow managed to munge it from reiserfs to smbfs!
> 
>    So, my questions to you SysAdmin gurus are: 1) Can I change this filesystem
> type without losing the contained data? and B) What is the recommended
> protocol for doing so?

No, but that is not what you've got. Take a second look at that line from
`mount`. Notice the device, "none". This is characteristic of network and
pseudo filesystems. smbfs would be the SMB filesystem, like what Samba
provides. From the description though this sounds unlikely, try seeing
what the kernel says, `cat /proc/mounts`.

My first guess though would be filesystem damage, umount and run `fsck`.

--

-- 
(\___(\___(\______          --=>  EHM <=--          ______/)___/)___/)

Re: Invisible Directory

What's the content of your /proc/mounts?  What's your fstab/auto.*
look like (how are you mounting it)?

Can you unmount it safely?  If you can umount the point, and it does
disappear from the mount list I'd back up the partition if you have
space (dd if=/dev/device of=/tmp/filename bs=4096) run a read-only
fsck (reiserfsck --fix-fixable /mountpoint) on it the original and
check/fix the contents for consistency.

/eli

On 4/30/05, Rich Shepard <rshepard <at> appl-ecosys.com> wrote:
> On Sat, 30 Apr 2005, Rich Shepard wrote:
> 
> >    I should have mentioned that I get the same results (or lack thereof)
> > when using the '-a' flag with ls. That is, 'ls -a', or 'ls -la' indicates the
> > directory is there but not readable/visible.
> 
>    Aha! I now know what happened, but not sure why and I certainly don't know
> how to gracefully recover.
> 
>    When I use the 'mount' command I see this:
> 
> none on /data2/winstuff type smbfs (0)
> 
> which tells me that when I was trying to get vmware to see the share I
> somehow managed to munge it from reiserfs to smbfs!
> 
>    So, my questions to you SysAdmin gurus are: 1) Can I change this filesystem
> type without losing the contained data? and B) What is the recommended

Re: Re: Re: OT: T1 Line pricing? - 1st hop times

My speakeasy account is similar, although my gateway is 66.93.40.1:

$ ping -c 10 66.93.40.1
PING 66.93.40.1 (66.93.40.1) 56(84) bytes of data.
64 bytes from 66.93.40.1: icmp_seq=1 ttl=126 time=24.5 ms
64 bytes from 66.93.40.1: icmp_seq=2 ttl=126 time=25.1 ms
64 bytes from 66.93.40.1: icmp_seq=3 ttl=126 time=60.5 ms
64 bytes from 66.93.40.1: icmp_seq=4 ttl=126 time=20.3 ms
64 bytes from 66.93.40.1: icmp_seq=5 ttl=126 time=20.3 ms
64 bytes from 66.93.40.1: icmp_seq=6 ttl=126 time=18.8 ms
64 bytes from 66.93.40.1: icmp_seq=7 ttl=126 time=18.3 ms
64 bytes from 66.93.40.1: icmp_seq=8 ttl=126 time=19.3 ms
64 bytes from 66.93.40.1: icmp_seq=9 ttl=126 time=19.5 ms
64 bytes from 66.93.40.1: icmp_seq=10 ttl=126 time=18.9 ms

And host shows the ip returns to the same domain name as Michael's.

$ host 66.93.40.1
1.40.93.66.in-addr.arpa domain name pointer er1.sea1.speakeasy.net.

Russ

Re: Invisible Directory

On Sat, 30 Apr 2005, Elliott Mitchell wrote:

> No, but that is not what you've got. Take a second look at that line from
> `mount`. Notice the device, "none". This is characteristic of network and
> pseudo filesystems. smbfs would be the SMB filesystem, like what Samba
> provides. From the description though this sounds unlikely, try seeing what
> the kernel says, `cat /proc/mounts`.
>
> My first guess though would be filesystem damage, umount and run `fsck`.

Elliott,

   Well, I'm now thoroughly confused. Here are the pertinent lines from 'less
/proc/mounts':

/dev/hda13 /data2 reiserfs rw 0 0
none /data2/winstuff smbfs rw,nosuid,nodev,file_mode=0755,dir_mode=0755 0 0

   I can access every other directory on /dev/hda13, or /data2, other than the
winstuff/ directory. Part of what puzzles me is how that one directory was
changed from reiserfs to smbfs while in runlevel 3 and with vmware running as
a user, not as root.

Thanks,

Rich

--

-- 
Dr. Richard B. Shepard, President
Applied Ecosystem Services, Inc. (TM)

Re: Invisible Directory

# The following was supposedly scribed by
# Rich Shepard
# on Sunday 01 May 2005 07:55 am:

>/dev/hda13 /data2 reiserfs rw 0 0
>none /data2/winstuff smbfs
> rw,nosuid,nodev,file_mode=0755,dir_mode=0755 0 0
>
>   I can access every other directory on /dev/hda13, or /data2, other
> than the winstuff/ directory. Part of what puzzles me is how that one
> directory was changed from reiserfs to smbfs while in runlevel 3 and
> with vmware running as a user, not as root.

The directory was not changed.  e.g. if the /data2/winstuff directory is 
on the /dev/hda13 filesystem, then the filesystem is still reiserfs.

Did you by any chance mount the directory on top of itself as a samba 
share?

e.g.
  mount -t smbfs -o... //localhost/winstuff /data2/winstuff

While the output of 'mount' looks different for me when I do that, I 
can't say what else may have happened on your machine.  In any case, 
you are allowed to do something like this, but then you can't even list 
the contents of the mountpoint directory.

I don't think you have a filesystem problem, I think you've just gotten 
something mounted in a bad way.  If you can't umount it, you may have 
to reboot in order to kick the smbfs driver out of the kernel (looks