[vox-tech] Fwd: Re: Directory name changed out from underneath me.

[Bill Kendrick]

I think it's moot, but here's a note from Orson from this thread.
(Posted from a non-sub'd email addr, so got discarded by Mailman.
Please remember to post from the addr with which you're subscribed to the
list!)

-bill!

----- Forwarded message from vox-tech-bounces at lists.lugod.org -----

Date: Mon, 01 Aug 2011 23:17:32 -0700
From: vox-tech-bounces at lists.lugod.org
Subject: Auto-discard notification
To: vox-tech-owner at lists.lugod.org

The attached message has been automatically discarded.
Date: Tue, 02 Aug 2011 00:12:18 -0600
From: Orson Jones <orson at afriskito.net>
Subject: Re: [vox-tech] Directory name changed out from underneath me.
To: lugod's technical discussion forum <vox-tech at lists.lugod.org>

Try: pwd | hexdump -C
Maybe there are special characters in your filename.

Orson

Nick Schmalenberger <nick at schmalenberger.us> wrote:

>On Mon, Aug 01, 2011 at 11:25:36PM -0500, Ken Bloom wrote:
>> On Mon, 2011-08-01 at 19:43 -0700, Nick Schmalenberger wrote:
>> > On Mon, Aug 01, 2011 at 08:59:58PM -0500, Chanoch (Ken) Bloom wrote:
>> > > I was just navigating around on one of the machines in my lab, when I
>> > > noticed something wierd: bash is getting the name of one of my
>> > > directories wrong when it tries to print it in the prompt.
>> > > 
>> > > [bloom at zuni ~]$ cd /
>> > > [bloom at zuni /]$ ls
>> > > bin/   etc/         lib/         media/        proc/     srv/  var/
>> > > boot/  home/        lib32/       mnt/          root/     sys/  vmlinuz@
>> > > data/  home-raid/   lib64@       nonexistent/  sbin/     tmp/
>> > > dev/   initrd.img@  lost+found/  opt/          selinux/  usr/
>> > > [bloom at zuni /]$ cd data
>> > > [bloom at zuni dtaa]$ pwd
>> > > /data
>> > > [bloom at zuni dtaa]$ echo ~+
>> > > /data
>> > > [bloom at zuni dtaa]$ mount
>> > > /dev/sda1 on / type ext3 (rw,errors=remount-ro)
>> > > tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
>> > > proc on /proc type proc (rw,noexec,nosuid,nodev)
>> > > sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
>> > > udev on /dev type tmpfs (rw,mode=0755)
>> > > tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
>> > > devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
>> > > fusectl on /sys/fs/fuse/connections type fusectl (rw)
>> > > binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
>> > > nas.lingcog.iit.edu:/home2 on /home-raid type nfs (rw,nosuid,noatime,addr=216.47.152.22)
>> > > nas.lingcog.iit.edu:/data on /data type nfs (rw,nosuid,noatime,addr=216.47.152.22)
>> > > 
>> > > It's correctly spelled in the pwd command, and bash's ~+ expansion, and
>> > > also in the mount command (/data happens to be a mountpoint), so
>> > > basically it's correctly spelled everywhere except for the prompt. Any
>> > > ideas why?
>> > >
>> > What do echo $PWD and echo $PS1 say? $PS1 seems like the next
>> > place to look, and particularly the \w part.
>> 
>> [bloom at zuni dtaa]$ echo $PS1
>> [\u@\h \W]\$
>> [bloom at zuni dtaa]$ echo $PWD
>> /data
>>
>What if you try setting PS1 with \w instead of \W? Maybe there is
>some weirdness with getting the basename from the full pathname.
>Nick
>_______________________________________________
>vox-tech mailing list
>vox-tech at lists.lugod.org
>http://lists.lugod.org/mailman/listinfo/vox-tech


----- End forwarded message -----

-- 
-bill!
Sent from my computer