[EMAIL PROTECTED] said:
> using group read and write is not an option.
Why not? The obvious thing is to chgrp file foo to group foo_group and anyone
who's allowed to modify foo is a member of foo_group.
Jeff
___
tec
[EMAIL PROTECTED] said:
> Then we upgraded the kernel to 2.2.14, and the behaviour changed: now
> it suddenly started to announce the name/IP on the last virtual
> interface on eth0 as its name, fex. when being used for irc or when
> NFS-mounting directories.
There was a complaint about this on t
[EMAIL PROTECTED] said:
> Unfortunately this is a different problem from mine.
Sorry about that. I think I understand the problem now.
I can't reproduce this on either 2.2.5 or 2.2.14 in the simplest case (add a
virtual interface, ssh out to another machine, look at where it thinks I came
fro
[EMAIL PROTECTED] said:
> It just hangs the box when trying to boot into the newly compiled
> kernel.
You're going to need to be a lot more informative if anyone's going to help.
What manages to appear on the console would be a good start. Also what makes
it into the log if that's not on the
[EMAIL PROTECTED] said:
> so far i know parent and child process should have separate address
> space. but here the addresses are same in both the processes. r they
> sharing the same address space?
They are in different address spaces, which is why those addresses can be the
same without them i
[EMAIL PROTECTED] said:
> Well I think Linux kernel is declared stable when there are no
> *showstoppers* - I don't know about no *bugs*.
There will be bugs. They will be squashed in succeeding 2.4 releases, as is
happening with 2.2 right now. The thing with a new stable series is that the
us
[EMAIL PROTECTED] said:
> Well I think Linux kernel is declared stable when there are no
> *showstoppers* - I don't know about no *bugs*.
I forgot to mention one thing. The current kernel bug list is maintained by
Ted T'so at http://linux24.sourceforge.net/. The ones that have to be fixed
bef
> I'd say free of all known bugs - who would willingly, knowingly, release
> buggy software as anything other than an alpha or a beta release?
That would be stupid, not to mention impossible.
If you're going to try to do right by your users, you want to release
something as soon as the benefits
[EMAIL PROTECTED] said:
> But is 2.4 going to be release with any of the bugs they know about
> now, say?
Yes, it will. As of test10, Linus was only taking critical bug fixed.
The CRITICAL bugs on Ted's list will be fixed. Most of the rest will be in
2.4.0 and be fixed later. Most of them a
[EMAIL PROTECTED] said:
> Not computer geek library is complete with Donald Knuth's seminal
> series on the Art of Programming.
Yup. That series isn't going out of date any time soon.
> Another one of my all time
> favorites is Barb Liskov's "Abstraction and Specification in Software
> Develo
Have you read Documentation/oops-tracing.txt in your kernel tree? If not,
that would be a good place to start.
> Do i need to run the ksymoops from the same computer which barfed?
It needs access to your System.map, which ought to be in /boot.
> from what i've been able to tell, the output f
> free_one_pmd: bad directory entry 0020
> Is this a kernel error and how severe is it? Should I worry?
This looks like a NULL which has had a one-bit error in it. If so, you have
some flaky memory.
It could crash your system if it happens in the right place. The error above
happened in
[EMAIL PROTECTED] said:
> i've traced the command using strace, and found that it hangs right
> on the the mount() system call.
If the mount syscall is hanging, then DNS can't have anything to do with it (I
don't think even in the case of NFS, because the kernel doesn't know about
resolv.co
[EMAIL PROTECTED] said:
> (see the "Found the Culprit!" section) http://www.linuxcentral.com/
> linux/lg/issue43/tag/4.html
Oh, the automounter was getting in the way on that one. That's something I
don't know much about.
So, do you have an amd in state 'D'? If so, disabling it or fixing mig
[EMAIL PROTECTED] said:
> You were right on that the automount process' stat was D... once I
> removed that process from the startup and it was no longer running, my
> disks mounted fine.
So, it turned out to be exactly the same problem.
So much for my "mount can't possibly care about the netw
[EMAIL PROTECTED] said:
> echo 1 > /proc/sys/net/ipv4/tcp_syncookies
> for which I am getting the following error message.
> /proc/sys/net/ipv4/tcp_syncookies: No such file or directory
What Angela said.
To explain that error above, /proc is special. It is not a normal filesystem
in which yo
[EMAIL PROTECTED] said:
> A!
> Any day in which you learn something is a good day.
Any day you manage to teach someone something ain't so bad either :-)
> Thanks, Jeff, for making this a good day for me. :)
Jeff
___
[EMAIL PROTECTED] said:
> the directory (/usr/src/linux) is correct
/usr/src/linux is WRONG.
Don't build new kernels in it. The reason is that the headers in
/usr/src/linux/asm have to match the system (i.e. libc), because
/usr/include/asm is a link to /usr/src/linux/include/asm. Dumping a n
[EMAIL PROTECTED] said:
> Unfortunately, there isn't any directory notification on Unix.
It's not clear whether you're including Linux as Unix, but Linux (2.4) does
have directory notification. See Documentation/dnotify.txt in the kernel pool.
It has some limitations. Updating a multiply-link
[EMAIL PROTECTED] said:
> man: can't create index cache /var/qmail/man/index.bt: Permission
> denied
> I've checked permissions on /var, /var/qmail, and /var/qmail/man, and
> they all the same as another system where this error doesn't happen. I
> can also touch a file in /var/qmail/man.
Try ru
[EMAIL PROTECTED] said:
> I 'make bzImage'd, replaced /vmlinuz (which appears to have been a
> symlink to something in /boot) with /usr/src/linux/arch/i386/boot/
> bzImage0 and ran lilo, then tried to reboot.
Someone else said it, but it bears repeating. If you have a booting kernel,
DO NOT TOU
[EMAIL PROTECTED] said:
> However, I can't upgrade glibc using rpm, because I need a higher
> version of rpm.
> I tried installing rpm 4.0.2 from source, but it immediately barfed
> and told me I needed a higher glibc.
Have you tried rpm --nodeps in one of these strategic places? The new rpm
I think we're being trolled here, and reasonably well, too.
To support this, we have have our troll making inflammatory claims, completely
ignoring any kind of logic, and tossing in extras like comparisons to Windows.
Also, cute female physicists tend not to go advertising that fact on the net.
[EMAIL PROTECTED] said:
>From memory there is a Linux specific one:
I probably am not going to be the only person to post a pointer to the whole
thing, but maybe I'll be first :-)
http://lark.cc.ukans.edu/~pauljohn/linux/airline.txt
Jeff
[EMAIL PROTECTED] said:
> Anyway, pouring through the strace info did the trick. That's a new
> one for me - I haven't used that tool, but I see it is incredibly
> useful. The output is amazing - a bit too much, but very informative.
You can use the -e switch to filter strace output. Also logg
> /usr/include/linux/param.h:4: asm/param.h: No such file or directory
Looks like you don't have the kernel headers installed. I'd go looking for a
package that says kernel-headers or something in the name and install it.
Also make sure that /usr/include/asm either doesn't exist or points at
101 - 126 of 126 matches
Mail list logo
