Hello,
Does xineliboutput support this?
The Problem: the Kids shouldn't be able to view or modify anything in
the system.
E. G.
/media should contain all content and
it shouldn't be possible to change to /.
Any ideas how to do this?
Regards
Halim
___
v
I think the rotor plugin is a bit of a mess now and the latest version (1.5)
is a step backwards with no transponder scan facility.
A clever friend of mine has doctored the previous version to work with
vdr-1.7.9, to still scan transponders and better still to scan C-band
transponders. Rotor sw
hi,
On Thu, 12 Nov 2009, Halim Sahin wrote:
Hello,
Does xineliboutput support this?
The Problem: the Kids shouldn't be able to view or modify anything in
the system.
E. G.
/media should contain all content and
it shouldn't be possible to change to /.
do you mean a chroot env?
that would be nic
Yes, i have signal, as my LNB cable is coming from the Kathrein's
loopthrough, and channels are fine on Kathrein's Enigma2.
I also tried to connect my LNB directly to TT3200, with same results.
I compared Engima2's lamedb channels list to vdr's channels.conf, and I
can see only one difference.
Simon,
Pay attention that /boot can be installed only on a single disk or RAID-1
where every disk can actually work as a stand alone disk.
I personally decided to use RAID-5 on 3 disks with RAID-1 on 3xsmall
partitions for /boot and RAID-5 on the rest.
RAID-5 also allows easier expansion in the f
Hi,
On Do, Nov 12, 2009 at 12:33:42 +0100, Marco Skambraks wrote:
> hi,
> On Thu, 12 Nov 2009, Halim Sahin wrote:
>
> > Hello,
> > Does xineliboutput support this?
> > The Problem: the Kids shouldn't be able to view or modify anything in
> > the system.
> > E. G.
> > /media should contain all cont
On 12/11/2009, Halim Sahin wrote:
> Hi,
>
> On Do, Nov 12, 2009 at 12:33:42 +0100, Marco Skambraks wrote:
> > hi,
> > On Thu, 12 Nov 2009, Halim Sahin wrote:
> >
> > > Hello,
> > > Does xineliboutput support this?
> > > The Problem: the Kids shouldn't be able to view or modify anything in
>
Hi,
On Do, Nov 12, 2009 at 02:41:53 +0200, Theunis Potgieter wrote:
> command: chroot /my/chroot/area /usr/bin/vdr-sxfe
>
> Create the chroot with the help of the tool ldd, ldd vdr-sxfe will
> tell you what shared objects vdr-sxfe requires to start. This is an
> interim solution until xineliboutpu
> I think the rotor plugin is a bit of a mess now and the latest version (1.5)
> is a step backwards with no transponder scan facility.
>
> A clever friend of mine has doctored the previous version to work with
> vdr-1.7.9, to still scan transponders and better still to scan C-band
> transponde
I couldn't apply a patch
/usr/src/vdr/PLUGINS/src/rotor-0.1.5# cat patch1 | patch -p0 --dry-run
patching file rotor.c
patch: malformed patch at line 6:
(diseqc=Diseqcs.Get(source->Code(),12000,'v')) ||
any clue ?
> Is it just me or the newly released rotor plugin for vdr 1.7.9 needs the
On 12/11/2009, Halim Sahin wrote:
> Hi,
>
> On Do, Nov 12, 2009 at 02:41:53 +0200, Theunis Potgieter wrote:
> > command: chroot /my/chroot/area /usr/bin/vdr-sxfe
> >
> > Create the chroot with the help of the tool ldd, ldd vdr-sxfe will
> > tell you what shared objects vdr-sxfe requires to sta
Goga777 wrote:
I couldn't apply a patch
/usr/src/vdr/PLUGINS/src/rotor-0.1.5# cat patch1 | patch -p0 --dry-run
patching file rotor.c
patch: malformed patch at line 6:
(diseqc=Diseqcs.Get(source->Code(),12000,'v')) ||
if ((diseqc=Diseqcs.Get(source->Code(),12000,'h')) ||
(diseqc=D
Just insert the 3 lines with a + and remove the 2 with a -
works fine then
>
>
> Message: 8
> Date: Thu, 12 Nov 2009 17:56:28 +0300
> From: Goga777
> Subject: Re: [vdr] rotor plugin puzzling question
> To: vdr@linuxtv.org
> Message-ID: <20091112175628.2ad3b...@bk.ru>
> Content-Type: text/plain
On 12/11/2009, Theunis Potgieter wrote:
> what is your output device?
Hi,
I use vdr-xine-0.9.3. on a nvidia card. I have the same problem with and
without vdpau with 180.51 and 190.42 nvidia modules.
Regards
Senufo
___
vdr mailing list
vdr@linuxt
Hi,
I just found an error when I use the keys 4 or 7 for me to move in the
mpeg2 stream (vdr-17.9 with vdr-xine 0.9.3).
Clear(1785)!
StillPicture: 0x191da2a0, 0
FIXME: xineDevice.c:1321
FIXME: xineDevice.c:2075
Clear(1786)!
StillPicture: 0x19179110, 0
FIXME: xineDevice.c:1321
FIXME: xineDevice.c:2
Thanks Alex. I think I've decided to go RAID 1+0 rather than RAID 5 as
I'm worried about the write speed.
I often record 3 or 4 channels at once and do see some "slow down" on OSD
responsiveness during this.
What's your experience with RAID5?
- Original Message -
From: Alex Betis
To: V
In general good experience.
I don't record much, so I don't worry about speed.
There are many web pages about raid5 speed optimizations.
The slowdown in raid5 writes mostly happen when a part of a strip (chunk of
data) has to be written,
so the driver has to read the strip, and write it back. The o
I too have only good experiences with md raid5 and have used it for years on
my vdr server. Its not uncommon that I record 7-8 programs simultaneously,
including HD channels, and I have never had any problems with that. On the
other hand, this is just a VDR/NFS server serving two diskless VDR/XBMC
18 matches
Mail list logo
