On 7/10/2004, at 8:16 PM, pirat sriyotha wrote:
Quoting James Pole <[EMAIL PROTECTED]>:
Heya,
To remove the old kernel just delete /kernel and rename /kernel.old to
/kernel.
sorry for interruption, am not quite sure that only replace /kernel
with
/kernel.old will solve his problem. correct me if
Hi,
I've redirected this to freebsd-stable because, as far as I
can tell from reading the script, it has nothing to do with
the networking code. This is strictly a scripting, and most
likely process creation issue.
Your script goes through each line, creat
Quoting James Pole <[EMAIL PROTECTED]>:
> Heya,
>
> To remove the old kernel just delete /kernel and rename /kernel.old to
> /kernel.
>
sorry for interruption, am not quite sure that only replace /kernel with
/kernel.old will solve his problem. correct me if am misunderstood.
> But note that y
On 7/10/2004, at 10:30 PM, pirat sriyotha wrote:
well, just my instinc that tell me that only move /kernel.old to
/kernel is not
sufficient. do we need to move /module.old to /module too ? (am not
freebsd
guru.)
Oh, that's a good point. I guess the process should be as follows:-
1. delete /kern
Quoting James Pole <[EMAIL PROTECTED]>:
>
> On 7/10/2004, at 8:16 PM, pirat sriyotha wrote:
>
> > Quoting James Pole <[EMAIL PROTECTED]>:
> >
> >> Heya,
> >>
> >> To remove the old kernel just delete /kernel and rename /kernel.old to
> >> /kernel.
> >>
> >
> > sorry for interruption, am not quite
Interestingly I just put on 5.3Beta 7 on an AMD64 based machine
and my sk0 interface hangs when I do some file transfers over to the
machine via scp
I just put an intel pci card in to fix the problem
Rong-En Fan wrote:
>[I'm not on list, so please CC me thanks]
>
>Hi,
>
>It is a 4.10-RELEASE-p2
Quoting James Pole <[EMAIL PROTECTED]>:
> On 7/10/2004, at 10:30 PM, pirat sriyotha wrote:
> >
> > well, just my instinc that tell me that only move /kernel.old to
> > /kernel is not
> > sufficient. do we need to move /module.old to /module too ? (am not
> > freebsd
> > guru.)
>
> Oh, that's a g
FreeBSD 4.10-STABLE #3: Thu Sep 30
$ id
uid=65534(nobody) gid=65534(nobody) groups=65534(nobody)
$ mkdir test
$ chmod 770 test
$ cp -Rp test test2
cp: chmod: test2: Operation not permitted
$ ls -al
drwxrwx--- 2 nobody nobody 512 Oct 7 11:29 test
drwxr-x--- 2 nobody nobody
On Thu, Oct 07, 2004 at 12:38:42PM -0400, Vlad wrote:
> FreeBSD 4.10-STABLE #3: Thu Sep 30
>
> $ id
> uid=65534(nobody) gid=65534(nobody) groups=65534(nobody)
>
> $ mkdir test
>
> $ chmod 770 test
>
> $ cp -Rp test test2
> cp: chmod: test2: Operation not permitted
>
> $ ls -al
> drwxrwx---
Alrighty so I am back up and running on my kernel.GENERIC.I started to
read through the docs for doing a build world, and I don't think I am
ready for that step yet. Mostly because this is a co-lo box that I only
have SSH access to.
Anyway now I want to make my changes to my GENERIC kernel so tha
On 8/10/2004, at 4:21 PM, Geoff Sweet wrote:
Anyway now I want to make my changes to my GENERIC kernel so that I
don't have to do the world thing. So I already CVSup'ed the /usr/src
directory to 4.10, so that is bad for me. Can I whack the /usr/src
directory and use sysinstall to load on the /usr/
Long listing, but we don't
see the code. There is a po-
ssibility that this machine
does something you are not
aware. Maybe someone else is
using it for another purpose,
hides processes via rootkit
and leaves you without clue.
It is not clear what has eaten
your cpu.
Could you make a little investi
12 matches
Mail list logo
