Michael Schwendt wrote:
On Fri, 17 Oct 2003 08:41:57 -0700, Gordon Messmer wrote:
In either case, if
.config exists, then you'll only be asked about new configuration items
(which there should not be any of, if it uses one of the prepared configs).
Isn't "make oldconfig" non-interactive?
Not en
Michael Schwendt wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 17 Oct 2003 08:41:57 -0700, Gordon Messmer wrote:
If .config exists, "make oldconfig" will use that.
If you are copying a config file to start from, why would you do a "make
oldconfig"?
You wouldn't need to. Under
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 17 Oct 2003 11:41:07 -0700, Douglas Phillipson wrote:
> I tried make oldconfig and it looked in and took it's info from
> /usr/src/linux-2.4/config/kernel-2.4.20-i686.config, which is what I get
> with uname -r. Then it created a new ".conf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 17 Oct 2003 08:41:57 -0700, Gordon Messmer wrote:
> If .config exists, "make oldconfig" will use that.
>
> > If you are copying a config file to start from, why would you do a "make
> > oldconfig"?
>
> You wouldn't need to. Under stock ker
Michael Schwendt wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 17 Oct 2003 07:51:43 -0700, Douglas Phillipson wrote:
The easiest way is to do a make "oldconfig". That will load all of your old
configuration and then do a "make xconfig" or which ever one you use.
Forgive me for n
Thank you, that explains much!
DSP
Gordon Messmer wrote:
config-`uname -r` exactly.
If .config exists, "make oldconfig" will use that.
If you are copying a config file to start from, why would you do a
"make oldconfig"?
You wouldn't need to. Under stock kernels, "make oldconfig" will ask
yo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 17 Oct 2003 07:51:43 -0700, Douglas Phillipson wrote:
> > The easiest way is to do a make "oldconfig". That will load all of your old
> > configuration and then do a "make xconfig" or which ever one you use.
>
> Forgive me for not yet being a
Douglas Phillipson wrote:
The easiest way is to do a make "oldconfig". That will load all of
your old
configuration and then do a "make xconfig" or which ever one you use.
Forgive me for not yet being a kernel expert. Before I do this what
exactly does "make oldconfig" do?
Where does it get
On Fri, 2003-10-17 at 09:51, Douglas Phillipson wrote:
>
> >>
> >>
> >
> > The easiest way is to do a make "oldconfig". That will load all of your old
> > configuration and then do a "make xconfig" or which ever one you use.
> >
> >
> >
> Forgive me for not yet being a kernel expert. Before
The easiest way is to do a make "oldconfig". That will load all of your old
configuration and then do a "make xconfig" or which ever one you use.
Forgive me for not yet being a kernel expert. Before I do this what
exactly does "make oldconfig" do?
Where does it get the config file from?
D
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> On Behalf Of Gordon Messmer
> Sent: Thursday, October 16, 2003 6:57 PM
> To: [EMAIL PROTECTED]
> Subject: Re: How do you tell what options are compiled in your kernel
>
> Douglas Phillipso
Douglas Phillipson wrote:
I'm wanting to use Samba for a Domain Controller and was having trouble
changing permissions on files through samba from the Microsoft desktop.
IIRC, you have to have a PDC to do that, ACLs or no.
I was told you need to turn ACL's on in the Linux filesystem. How do
y
12 matches
Mail list logo