On 1/24/06, John Jordan <[EMAIL PROTECTED]> wrote:
> On 23 Jan 2006, at 22:31, D. Hugh Redelmeier wrote:
> >
> > | Someone told me to create
> > | a hard link by doing this, but the syntax doesn't quite work:
> > |
> > | ln /etc/resolv.conf /chroot/breezy/32bits/etc/resolv.conf
> > |
> > | It says the file already exists. I read the man page on ln and it
> > gave | a lot of information about options, but nowhere did it say
> > exactly | what ln DOES. But don't get me started on Linux
> > documentation. :(
>
> > I like UNIX-style documentation ("man pages"). Linux has adopted
> > several conventions, partially, so the resulting mish-mash is rather
> > uneven.
> >
> > UNIX-style man pages are terse. Leaving much to the creativity of the
> > reader. This is good, if you can handle them.
> >
> > I don't know how much you know of the UNIX (Linux) file-system
> > abstraction. Here is a quick summary.
>
> <snippage of stuff I read but didn't really understand>
>
> > The command you gave would work just fine if there were not already a
> > reference /chroot/breezy/32bits/etc/resolv.conf Because the name is
> > already used, just add -f to the command.
>
> OK, doing it with the -f at the end works.
>
> However, what I am trying to figure out is if ln is permanent. In other
> words, now that I have created the hard link, will resolv.conf in the
> chroot environment always automatically be changed to whatever
> the resolv.conf in /etc becomes? I read the man page and the "info
> coreutils" thing as well, and there was not a word about whether
> the link was permanent.
When you create a hard link with ln, the two "files" are actually one
and the same file. What you have is two references that point to the
same file data. That's what Hugh was trying to relate with his *nix
filesystem overview. The problem could be that if the file is
modified in a certain way, it will update the /etc/resolv.conf
reference, but not the other one, leaving the other one useless.
Whether this is the case or not has not been determined.
> This is a laptop, so naturally it is shut down and restarted over and
> over in different locations, using ethernet-to-cable at home, and any
> of half a dozen different wifi locations while away from home. Some
> of those wifi locations (e.g., the one at the university) require me to
> log in. The procedure to log in is to open your browser and try to go
> somewhere. At that point the university's NoCat comes up and I
> enter my student ID and password, and it lets me in, and then
> proceeds to open the page I was attempting to reach. Currently I
> can do this with the Firefox installed in the 64-bit world, but I'd like
> to be able to do this using the 32-bit Firefox I installed in chroot.
> Plus, I don't want to have to open a terminal and type the ln
> command each time. I just want it all automated so it just "works."
None of this should affect whether it works. It's just a question of
how the changes to the file are written. Try it once and see what
happens. If it works, then it should always just work. If not, you
should create a script to redo the link (or at that point, just use cp
and copy it) when you want to run 32-bit Firefox. I wouldn't think
this to be a problem, since you already have some sort of script to
start it anyway.
Jonathan
_______________________________________________
LinuxR3000 mailing list
[email protected]
http://lists.pcxperience.com/cgi-bin/mailman/listinfo/linuxr3000
Wiki at http://prinsig.se/weekee/
