On Sat, Jan 17, 2015 at 11:13:46PM +0100, k...@aspodata.se wrote:
> Someone mentioned [1].
>
> So I tried busybox's init. It works great, my exp. config is at [2].
>
> ///
>
> Also it would be possible to have a startup script (/etc/rcS) like:
>
> #!/bin/bash
>
> echo -n "Which init do you wan
On Sat, Jan 17, 2015 at 08:06:05PM +0100, k...@aspodata.se wrote:
> Gravis:
> > karl, what's with the hostility?
>
> Oh, maybe it come out to harsh, sorry for that.
>
> > vdev is by no means required and
> > nothing depends on it, so nobody is being forced to even install it.
> > also, since it
Could one of the venerable VUAs please do something to stop the spam being
posted to the wiki. It's starting to get out of control and no one seems to be
minding the store. It needs to be PREVENTED not just deleted (which Gravis has
been doing).
Thanks,
golinux
__
Someone mentioned [1].
So I tried busybox's init. It works great, my exp. config is at [2].
///
Also it would be possible to have a startup script (/etc/rcS) like:
#!/bin/bash
echo -n "Which init do you want to use? "
read -t 5 a # bash's read has a timeout option
if [ $? -gt 0 ]
then
echo t
Jude:
> Moreover, vdev will support the option of simply generating the device
> files for the system's current hardware configuration and promptly
> exiting. You won't have to leave it running, and if your hardware
> configuration changes, you can simply re-run it and it will add/remove the
> req
Gravis:
> karl, what's with the hostility?
Oh, maybe it come out to harsh, sorry for that.
> vdev is by no means required and
> nothing depends on it, so nobody is being forced to even install it.
> also, since it is based on FUSE, it won't actually add/remove static
> device files, so when the
Moreover, vdev will support the option of simply generating the device
files for the system's current hardware configuration and promptly
exiting. You won't have to leave it running, and if your hardware
configuration changes, you can simply re-run it and it will add/remove the
requisite device no
Dragan:
> From: "Martinx - ジェームズ"
> >> If you know how to help us with the correct solution that
> >> will immediately work correctly, you are very welcome to our
> >> community.
>
> > What about eudev?
>
> I don't know if eudev is successfully ported to debian to satisfy
> all dependencies?
karl, what's with the hostility? vdev is by no means required and
nothing depends on it, so nobody is being forced to even install it.
also, since it is based on FUSE, it won't actually add/remove static
device files, so when the program exits, it will go back to your
static device files. you can
Isaac:
> On Wed, Dec 31, 2014 at 11:29:15AM -0500, Walter Dnes wrote:
> > On Wed, Dec 31, 2014 at 03:03:50PM +0100, Enrico Weigelt, metux IT consult
> > wrote
> > > On 31.12.2014 10:59, Jude Nelson wrote:
> > >
> > > Hi,
> > >
> > > > However, future entanglements with systemd and kdbus could ma
Jude:
> I haven't read the mesa code yet, but it sounds like mesa uses udev to help
> it (1) insert the right kernel module, and (2) load the right firmware.
> udev gets its information from sysfs and/or its netlink socket, so I'd
> imagine mesa uses a similar technique with the --enable-sysfs opt
t.j.duch...@gmail.com:
> From: Hendrik Boom
> Sent: Wednesday, December 31, 2014 8:44 AM
>
> > Never mind the mechanisms for now.
> > May I ask what all this complexity is supposed to accomplish?
(please don't top post)
> The reasons for a dynamic device manger were simple:
>
> a) Ac
Katola2:
> On Thu, Jan 15, 2015 at 10:59:55PM +0700, Ста Деюс wrote:
> > Доброго времени суток, KatolaZ.
> >
> > Спасибо за ответ, Wed, 14 Jan 2015 10:52:39 +, вы писали:
> > > Well, unfortunately there is currently no clear-cut about
> > > Recommends. In most of the cases a package will work
13 matches
Mail list logo
