Hi!
Yes it is confusing, but I remember that when I was a gentoo-geek they
used a program/script called coldplug for loading modules and such and
hotplug was what you just said, I guess they "changed" the name of the
daemon to stop the confusion...
don't know if that is hard to do? becuase th
Hi
yes it's a bit confusing, the "hotplug" daemon does only coldplugging, which
means it loads modules for things it thinks it's there, nothing more.
hotplug daemon is a bunch of script that are executed and not a real daemon at
all.
hwdetect does the same but is faster and far more precise in d
Scott Weisman schrieb:
> Does this mean I can now do "pacman -R hotplug"? It doesn't look like
> it, because it is still used to process hotplug events, even if the
> hotplug daemon is not run on startup.
>
> Does the hotplug daemon only run at startup then exit?
>
> How are hotplug events proces
Le Tuesday 22 November 2005 01:19, Aaron Griffin a écrit :
| On Tue, Nov 22, 2005 at 12:51:50AM +0100, Damir Perisa wrote:
| > may i ask you and all people who learn this things to start working
| > on archwiki pages (wiki.archlinux.org)
|
| Hah, for this topic, I'm one step ahead of you:
|
On Tue, Nov 22, 2005 at 12:51:50AM +0100, Damir Perisa wrote:
> may i ask you and all people who learn this things to start working on
> archwiki pages (wiki.archlinux.org)
Hah, for this topic, I'm one step ahead of you:
http://wiki.archlinux.org/index.php/HotPlug
- phrak
__
Hi Scott W.,
i'm happy that you bring up this questions. i cannot provide detailed
answers, because my knowledge on this subject is not that good to reason
and argue on it with confidence, but i hope that you will get competent
answers from others.
Le Tuesday 22 November 2005 00:27, Scott Weis
On 11/22/05, Scott Weisman <[EMAIL PROTECTED]> wrote:
> Hi there,
>
> I've been reading about the ongoing development of hotplug
> alternatives with interest, but I am confused.
>
> I see that it is possible, and now it seems even preferable, to remove
> hotplug from the DAEMONS line in rc.conf.
D
Hi there,
I've been reading about the ongoing development of hotplug
alternatives with interest, but I am confused.
I see that it is possible, and now it seems even preferable, to remove
hotplug from the DAEMONS line in rc.conf.
Does this mean I can now do "pacman -R hotplug"? It doesn't look li
On Monday 21 November 2005 14:17, z4ziggy wrote:
> oops... previous mail was a private message to dibble... well, im guessing
> its not private anymore ;)
>
> you may ignore it. PLEASE...
OOohhh.. Now you have done it. The cats out of the bag... You forgot how to
commit sources back to the cvs.
oops... previous mail was a private message to dibble... well, im guessing its
not private anymore ;)
you may ignore it. PLEASE...
--
regards,
Elia Yehuda, aka z4ziggy
Archie project, http://archie.dotsrc.org
___
arch mailing list
arch@archlinux.org
heya man,
i finished recoding mkliveiso and its now modular as i wanted it to be. i also
added --verbose (default is quiet mode) and fixed some minor issues regarding
the code structure. i shamefully admit i dont remember how to commit sources
back to the cvs with approp message (for the change
Your description is basically what i do.
I have like 3 machines that basically do NAT and transparent proxying
(ala SQUID) on three client networks. I ignorepkg = iptables, squid,
kernel26 on all three of them.
Since my laptop also runz Arch, i always upgrade my laptop first... and
find out if
Thanks again for all the thoughts. It occurs to me that one never
really *HAS* to update. There's no-one holding a gun to your
head. So, I'm thinking that maybe *A* way to proceed is to
maintain a test server that has all of the packages installed that we
would normally install on a production s
Hi I gave you the answer already:
MODULES=
is now only needed for modules that are not detected by hwdetect.
greetings
tpowa
--
Tobias Powalowski
Archlinux Package Maintainer (tpowa)
http://www.archlinux.org
[EMAIL PROTECTED]
pgp8fwqo6RHv6.pgp
Description: PGP signature
Rosenstrauch, David schrieb:
> What does this mean for the MODULES section in the rc.conf, Tobias? If we're
> going to use autoload, should we comment out MODULES?
You probably still want to load some modules that hwdetect cannot
"guess" for you. For example (this is for my custom kernel, some o
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Behalf Of Tobias Powalowski
> Sent: Monday, November 21, 2005 4:09 AM
> To: arch@archlinux.org
> Subject: [arch] Initscripts update
>
> Hi,
> finally i think hwdetect comes to final stage :)
> it does now module o
2005/11/21, j l <[EMAIL PROTECTED]>:
>
>
> --- Mikkel Poulsen <[EMAIL PROTECTED]> wrote:
>
> > Hi
> >
> > Reasently I have been up to *BSD, and I find it vere
> > interesting.
> > Though I have this problem that I am using my
> > onboard card for Arch.
> > *BSD don't like it, and Arch doesn't like
On Fri, Nov 18, 2005 at 01:23:42PM +0100, Thomas Bächler wrote:
>Magnus Therning schrieb:
>>>Our release structure isn't like that at all. We just take a snapshot
>>>of the state of current and that's a release. The rolling part means
>>>that the difference between releases is all the updates we'
Hi,
finally i think hwdetect comes to final stage :)
it does now module ordering with priority to internal devices, this is
important for network or scsi.
added a load_modules=off option to rc.sysinit, that means if you run into
trouble with module loading just add this option to your boot prompt
19 matches
Mail list logo
