Mailing List archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[vdr] Re: Timeshifting pb with vdr 1.1.32 / vdr-1.1.33
Klaus Schmidinger wrote:
I justs tested this with a clean, fresh, vanilla vdr-1.1.33, only VFAT=1 is
non standard, but it happens without VFAT=1 also.
That's really odd, since I can't reproduce this...
ok, i've just did a complete reinstall of my system:
Nexus 2.1 on a Asus-Board with BX-Chipset & P3-500
RedHat9 (workstation installation)
Kernel 2.4.20 (vanilla)
driver from CVS 11:30 (with & without hw_sections=0)
vdr-1.1.33 (with & without VFAT=1)
fresh vdr-config, only remote.conf from the old system.
It works with 1.1.30 on the same system, but i could not test 1.1.31,
so the problem has been introduced in .31 or .32
Anything else i can do?
May 27 10:45:37 astra vdr: ERROR (recording.c,680): Address
already in use
Do you get this with patches only?
Hmmm, i'm sure(tm) i've seen it without the patches, but now
i can't reproduce it. Obviously i'm wrong, could be a leftover from
all the patching.
BTW: are there any downsides of VFAT=1? Or is there any reason this is
The reason why this is not "standard" is that it is just a workaround for
Windows. Linux can well handle all the characters that are mapped to
#xx for Windows. So I see no reason why the "standard" should be what's
needed by a broken OS ;-)
hrmpf. You consider Samba broken? Baaaaaad idea ;-).
(But i get the point ;-)
To unsubscribe send a mail to firstname.lastname@example.org with "unsubscribe vdr" as subject.
Main Index |