On Sat, Apr 29, 2023 at 01:17:33PM +0200, Maurizio Caloro wrote:
> Hello All
>
> Meny meny Thanks again for everyone who has written to me here.
>
> please where do I go so I can unsubscribe here
>
> gently
> Maurizio
>
Hello Maurizio,
The instructions to subscribe/unsubscribe are on every em
ho has written to me here.
please where do I go so I can unsubscribe here
gently
Maurizio
-Ursprüngliche Nachricht-
Von: to...@tuxteam.de
Gesendet: Samstag, 29. April 2023 06:52
An: debian-user@lists.debian.org
Betreff: Re: why symbolic link arnt visible?
On Fri, Apr 28, 2023 at 04:09:12PM -
On Fri, Apr 28, 2023 at 04:09:12PM -0400, Greg Wooledge wrote:
> On Fri, Apr 28, 2023 at 08:20:37PM +0200, to...@tuxteam.de wrote:
> > On Fri, Apr 28, 2023 at 01:28:11PM -0400, Greg Wooledge wrote:
> > > On Fri, Apr 28, 2023 at 07:06:17PM +0200, Maurizio Caloro wrote:
> > > > f: /var/lib/rancid/rou
On Fri, Apr 28, 2023 at 08:20:37PM +0200, to...@tuxteam.de wrote:
> On Fri, Apr 28, 2023 at 01:28:11PM -0400, Greg Wooledge wrote:
> > On Fri, Apr 28, 2023 at 07:06:17PM +0200, Maurizio Caloro wrote:
> > > f: /var/lib/rancid/routers/configs
> > > drwxr-xr-x root root /
> > > drwxr-xr-x root r
On Fri, Apr 28, 2023 at 01:28:11PM -0400, Greg Wooledge wrote:
> On Fri, Apr 28, 2023 at 07:06:17PM +0200, Maurizio Caloro wrote:
> > f: /var/lib/rancid/routers/configs
> > drwxr-xr-x root root /
> > drwxr-xr-x root root var
> > drwxr-xr-x root root lib
> > drwxr-xr-x rancid rancid ranc
On Fri, Apr 28, 2023 at 07:06:17PM +0200, Maurizio Caloro wrote:
> Hello and thanks for so meny answer
>
> f: /
> drwxr-xr-x root root /
[...]
> drwxr-x--- 4 rancid rancid 4096 Apr 27 18:44 /var/lib/rancid/routers
> drwxr-x--- 2 rancid rancid 4096 Apr 27 18:44
^^^
And here is your pro
On Fri, Apr 28, 2023 at 07:06:17PM +0200, Maurizio Caloro wrote:
> f: /var/lib/rancid/routers/configs
> drwxr-xr-x root root /
> drwxr-xr-x root root var
> drwxr-xr-x root root lib
> drwxr-xr-x rancid rancid rancid
> drwxr-x--- rancid rancid routers
> drwxr-x--- rancid rancid configs
T
/configs
-Ursprüngliche Nachricht-
Von: Greg Wooledge
Gesendet: Freitag, 28. April 2023 13:55
An: debian-user@lists.debian.org
Betreff: Re: why symbolic link arnt visible?
On Fri, Apr 28, 2023 at 06:53:11AM +0200, Maurizio Caloro wrote:
> (Unattributed:)
> >Could you do ls -
On Fri, Apr 28, 2023 at 06:53:11AM +0200, Maurizio Caloro wrote:
> (Unattributed:)
> >Could you do ls -l to /var/lib/rancid, /var/lib/rancid/routers and so on
> >until .../c3560?
> Every file in this path "-R rancid:randic /var/lib/rancid"
Please actually show us. Use either of these two command
On Fri, Apr 28, 2023 at 06:20:02AM +0100, Tim Woodall wrote:
[...]
> It"s the target of the link that has a permission problem, not the
> source.
That's my bet, too.
Cheers
--
t
signature.asc
Description: PGP signature
On Fri, Apr 28, 2023 at 06:53:11AM +0200, Maurizio Caloro wrote:
> Thanks for you answer
>
> >I'm guessing what you mean by "will not appear": the web server doesn't show
> >it.
> Yes the Webserver Apache will not present the symbolic link folder
>
&g
On Fri, 28 Apr 2023, Maurizio Caloro wrote:
Thanks for you answer
I'm guessing what you mean by "will not appear": the web server doesn't show it.
Yes the Webserver Apache will not present the symbolic link folder
My first hunch would be that the web server can't
Thanks for you answer
>I'm guessing what you mean by "will not appear": the web server doesn't show
>it.
Yes the Webserver Apache will not present the symbolic link folder
>My first hunch would be that the web server can't read (or list) any of the
>com
On Thu, Apr 27, 2023 at 08:21:29PM +0200, Maurizio Caloro wrote:
> Troubling little with apache2, test1234 are visible, but the symbolic link
> folder will not appair?
>
> Thanks for possible update
>
>
>
> Deian 10 / Apache 2.4.56 (Debian)
>
>
>
> r
Troubling little with apache2, test1234 are visible, but the symbolic link
folder will not appair?
Thanks for possible update
Deian 10 / Apache 2.4.56 (Debian)
root@ovo:/var/www/html/cvsweb# ls -la
lrwxrwxrwx 1 www-data www-data 37 Apr 27 19:46 c3560 ->
/var/lib/rancid/routers/conf
lina wrote:
> $ rm -r build/
> rm: cannot remove `build/': Not a directory
> $ rm build/
> rm: cannot remove `build/': Not a directory
> $ mv build/ build.old
> mv: cannot move `build/' to `build.old': Not a directory
> ...
> lrwxrwxrwx 1 lina hpcusers 24 Dec 27 2009 build -> /scratch/lina/bui
On 07/17/2011 07:46 PM, lina wrote:
$ ls -l
total 256
lrwxrwxrwx 1 lina hpcusers 24 Dec 27 2009 build -> /scratch/lina/build/
I don't know how to remove /build.
How about:
$ rm build
That should remove the link.
HTH,
David
--
To UNSUBSCRIBE, email to debian-user-requ...@l
On Monday 18 July 2011 04:46:52 lina wrote:
> Hi,
>
> There was something called build/,
>
> when I tried to
>
> $ rm -r build/
> rm: cannot remove `build/': Not a directory
> $ rm build/
> rm: cannot remove `build/': Not a directory
> $ mv build/ build.old
> mv: cannot move `build/' to `build.o
After breaking the link first and the rm works.
Thanks with regards,
On Mon, Jul 18, 2011 at 10:46 AM, lina wrote:
> Hi,
>
> There was something called build/,
>
> when I tried to
>
> $ rm -r build/
> rm: cannot remove `build/': Not a directory
> $ rm build/
> rm: cannot remove `build/': Not a
Hi,
There was something called build/,
when I tried to
$ rm -r build/
rm: cannot remove `build/': Not a directory
$ rm build/
rm: cannot remove `build/': Not a directory
$ mv build/ build.old
mv: cannot move `build/' to `build.old': Not a directory
$ ls -l
total 256
lrwxrwxrwx 1 lina hpcusers
-window.so.1.deb3 is not a symbolic link
ldconfig: /usr/lib/libsfml-system.so.1.deb3 is not a symbolic link
Setting up boinc-dev (6.2.14-3) ...
Setting up libxmlrpc-c3 (1.06.27-1) ...
ldconfig: /usr/lib/libsfml-window.so.1.deb3 is not a symbolic link
ldconfig: /usr/lib/libsfml-system.so.1.deb3 is not a
On Sun, Aug 16, 2009 at 9:22 PM, Sven Joachim wrote:
> On 2009-08-16 22:36 +0200, Chris Bannister wrote:
>
>> I noticed that /sbin/reboot is a symbolic link to /sbin/halt. How does
>> the system "know" the difference?
>
> The program notices how it is called
On Sun, Aug 16, 2009 at 05:22:22PM -0300, Eduardo M KALINOWSKI wrote:
> Chris Bannister wrote:
> > Hi,
> >
> > I noticed that /sbin/reboot is a symbolic link to /sbin/halt. How does
> > the system "know" the difference?
> >
>
> By checking the
On 2009-08-16 22:36 +0200, Chris Bannister wrote:
> I noticed that /sbin/reboot is a symbolic link to /sbin/halt. How does
> the system "know" the difference?
The program notices how it is called and behaves accordingly. Programs
written in C can get information about thei
Chris Bannister wrote:
> Hi,
>
> I noticed that /sbin/reboot is a symbolic link to /sbin/halt. How does
> the system "know" the difference?
>
By checking the name with which the program was called. In C it's
available as the first element in the array of c
Hi,
I noticed that /sbin/reboot is a symbolic link to /sbin/halt. How does
the system "know" the difference?
--
Chris.
==
I contend that we are both atheists. I just believe in one fewer god
than you do. When you understand why you dismiss all the other
possible gods, you will
Somewhere, somehow, this item got replaced with a file rather than a symlink
to one. I might have done it myself trying to replace some errant version.
Whatever.
So ... to get rid of this repeated message, I moved the file and made it a
bonafied symlink. It works ... for a little while.
Then t
Yesterday, I have changed some symbolic links in /usr/lib32 to point to
older version libraries. For example, there was
libxml2.so.2 -> libxml2.so.2.6.30
I have changed it to libxml2.so.2.6.27 and my printer stared to work.
But after I run 'apt-get upgrade', it returns to its original state. How
Greetings;
Well, locales is installed and working, I guess. Now I
am getting screens full of messages like
> ldconfig: /usr/lib/libgnutls-openssl.so.11 is not a
symbolic link
I was installing a bunch of packages and it seemed to
repeat, but not with every program.
Anybody know how
Wait a minute Forget all this. I read the documentation for a generic
install from the blackdown site and forgot about the debian installation
process.
I deleted the manual installation I did.
I did
apt-get install java-package
I then did the fakeroot command:
[EMAIL PROTECTE
From: "Michael Fothergill" <[EMAIL PROTECTED]>
To: debian-user@lists.debian.org
Subject: RE: problem making symbolic link to blackdown (fixed) but a now a
new problem..
Date: Sat, 11 Aug 2007 15:56:12 +
From: "Michael Fothergill" <[EMAIL PROTECTED]>
From: "Michael Fothergill" <[EMAIL PROTECTED]>
To: debian-user@lists.debian.org
Subject: problem making symbolic link to blackdown amd64 java plugin
library file...
Date: Sat, 11 Aug 2007 13:17:32 +
Dear Debianists,
I use Etch 4.0 (r0) AMD64 version on a AMD64 box.
uninstall it and start
again as a user?
I then (still root) did the symbolic link assignment.
ln -s /usr/local/j2re1.4.2/plugin/amd64/mozilla/libjavaplugin_oji.so \
/usr/lib/mozilla/plugins/
I got the following error message:
localhost:/usr/local# ln -s
/usr/local/j2re1.4.2/plugin/amd64
g this error message
===
ldconfig /lib/libgtkhtml.so.6 is not a symbolic link
===
Any idea what this means and how to fix? Is it fatal? Should I
re-install Debian again?
Regards
TAC
On Wed, 15 Dec 2004 00:51:22 +, Jason Chambers wrote:
> On Tue, Dec 14, 2004 at 07:29:22PM -0500, Tong wrote:
>> On Sat, 11 Dec 2004 16:48:34 -0500, Tong wrote:
>>
>> > I remember that my previous distro can distinguish symbolic links as good
>> > or bad: good links are show as normal link co
Tong([EMAIL PROTECTED]) is reported to have said:
> On Wed, 15 Dec 2004 00:51:22 +, Jason Chambers wrote:
>
> > On Tue, Dec 14, 2004 at 07:29:22PM -0500, Tong wrote:
> >> On Sat, 11 Dec 2004 16:48:34 -0500, Tong wrote:
> >>
> >> > I remember that my previous distro can distinguish symbolic li
On Tue, Dec 14, 2004 at 07:29:22PM -0500, Tong wrote:
> On Sat, 11 Dec 2004 16:48:34 -0500, Tong wrote:
>
> > I remember that my previous distro can distinguish symbolic links as good
> > or bad: good links are show as normal link color whereas bad links are
> > shown as red.
> >
[snip]
> Ok,
On Tue, 14 Dec 2004 19:29:22 -0500, Tong <[EMAIL PROTECTED]> wrote:
> Thanks everyone for the respond... yet I'm still looking for the answer
> that I want -- the fact is I have no problem showing colors using ls. Just
> need to distinguish bad symbolic link from good on
Tong wrote:
>
Thanks everyone for the respond... yet I'm still looking for the answer
that I want -- the fact is I have no problem showing colors using ls. Just
need to distinguish bad symbolic link from good ones.
Ok, let's take a look at an example:
touch a
ln -s a l1
ln -s n
t; >
> > How can I do that in Debian? Thanks
>
> Thanks everyone for the respond... yet I'm still looking for the answer
> that I want -- the fact is I have no problem showing colors using ls. Just
> need to distinguish bad symbolic link from good ones.
>
> Ok,
respond... yet I'm still looking for the answer
that I want -- the fact is I have no problem showing colors using ls. Just
need to distinguish bad symbolic link from good ones.
Ok, let's take a look at an example:
touch a
ln -s a l1
ln -s no l2
rm no
ls --color=auto
Do l1 and l2 show
Tong wrote:
> I remember that my previous distro can distinguish symbolic links as good
> or bad: good links are show as normal link color whereas bad links are
> shown as red.
Edit your .bashrc and uncomment this line:
alias ls='ls --color=auto'
Then run:
'. .bashrc'
Adam
--
To UNSUBSCRIB
On Sat, Dec 11, 2004 at 04:48:34PM -0500, Tong wrote:
> Hi,
>
> I remember that my previous distro can distinguish symbolic links as good
> or bad: good links are show as normal link color whereas bad links are
> shown as red.
>
> How can I do that in Debian? Thanks
ls --color=auto
You can se
Hi,
I remember that my previous distro can distinguish symbolic links as good
or bad: good links are show as normal link color whereas bad links are
shown as red.
How can I do that in Debian? Thanks
tong
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Troub
On Sat, Feb 23, 2002 at 01:30:52AM +, Keith Willoughby wrote:
> Sam Varghese <[EMAIL PROTECTED]> writes:
>
> > I did this, using ln -s /etc/X11/X /usr/bin/X11/XFree86 as root.
> > I get a message stating that the file exists.
>
> You've got your parameters to ln backwards. If it helps, I do t
Sam Varghese <[EMAIL PROTECTED]> writes:
> I did this, using ln -s /etc/X11/X /usr/bin/X11/XFree86 as root.
> I get a message stating that the file exists.
You've got your parameters to ln backwards. If it helps, I do this all
the time.
--
Keith Willoughby
Our Father, who art in heaven, Harold
G'day
I upgraded one of my potato boxes to woody over the last two nights.
I have encountered problems setting up X after the upgrade.
After creating an XF86config, startx yields this error message:
X: cannot read /etc/X11/X symbolic link (Invalid argument) aborting
I looked throug
Hello:
I have a curious problem that first surfaced several months ago, but
I was unable to address until this week. Basically, 'make' refuses to
make anything, although it "knows" what has to be done. For example,
I have a small library, and a corresponding makefile for which 'make -n'
tells me
On Fri, 12 Nov 1999, Sean McIlwain wrote:
mcilwa >
mcilwa >How do make a symbolic link to a device, say if I want to make a
mcilwa >symbolic link between /dev/stylewriter and /dev/ttyS1, how would I do
it?
same way.. ln -s /dev/ttyS1 /dev/stylewri
-BEGIN PGP SIGNED MESSAGE-
On Fri, 12 Nov 1999, Sean McIlwain wrote:
>
> How do make a symbolic link to a device, say if I want to make a
> symbolic link between /dev/stylewriter and /dev/ttyS1, how would I do it?
ln -s /dev/ttyS1 /dev/stylewriter
or
ln -s t
How do make a symbolic link to a device, say if I want to make a
symbolic link between /dev/stylewriter and /dev/ttyS1, how would I do it?
"Richard E. Hawkins Esq." <[EMAIL PROTECTED]> writes:
| I don't think I've seen this one before . . .
|
| I have /boot mounted on the first partition, a single cylinder.
| /vmlinux is a symbolic link to /boot/vmlinux-2.0.33. Rather than
| following the link, "m
I don't think I've seen this one before . . .
I have /boot mounted on the first partition, a single cylinder. /vmlinux is a
symbolic link to /boot/vmlinux-2.0.33. Rather than following the link, "make
zImage zlilo" is placing a vmlinuz in /, undoing the old link, an
53 matches
Mail list logo
