Re: TeXLive merge into FreeBSD ports tree - FreeBSD project idea
On Wed, May 30, 2012, Aldis Berjoza wrote: On Sat, 26 May 2012 22:45:37 +1200 Sam Lin sam.lin...@gmail.com wrote: Hi FreeBSD fellows, Those who are using LaTeX on FreeBSD must know that tetex has been discontinued years ago and that TeXLive is now recommended, however TeXLive has never been merged in the ports tree on FreeBSD and that tetex is still used on FreeBSD ports. Although there have been some customized work so that FreeBSD users can install and use TeXLive on FreeBSD machine (for example, http://code.google.com/p/freebsd-texlive/wiki/Installing), this is quite confusing and may still cause conflict on the system side when using or maintaining it. There has also been years of gossips that a Japanese developer Hiroki Sato (hrs@freebsd) has been working on this matter for the last years and therefore the FreeBSD admin panel don't want anyone else to work on this and merge it into the ports tree. I actually contacted Hiroki Sato in the beginning of last year (2011) regarding this, and in his reply he said that there had been several technical issues but most of them had been solved and almost ready to merge into the port tree, and that he was planning to go forward after the 8.2/7.4 releases (one or two weeks later from that time stage) are out. However, more than a year has passed since then and still nothing happened. I tried to contact him several times after that (email, tweet, etc) but haven't heard anything back from him at all. Is TeXLive really going to be merged into the FreeBSD ports tree as Hiroki Sato mentioned previously? Or is this just a myth?? I am now thinking that this should be put into the FreeBSD Project ideas List [http://wiki.freebsd.org/IdeasPage]. Regards, Sam Hey, Sam! I which TeXLive would be merged in FreeBSD ports. Romain is doing great job maintaining it. And it work, And it work now. In fact it works for more than a year. I have used his TeXLive ports through portshaker for a while. They work pretty well, but there are some issues due to the fact that the TeXLive folks have some strange ideas. For one, TeXLive is split into over 2000 packages, many of which are tiny; the FreeBSD package system doesn't handle that very well. For another, TeXLive now has its own (dubious) package manager, tlmgr, which doesn't play well with other package management systems. I'm not a ports committer, but perhaps a good first step to getting TeXLive working better in FreeBSD is to introduce a TeTeX vs TeXLive knob in the ports tree so that people don't wind up accidentally clobber their TeXLive install when TeTex gets pulled in as a dependency. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: TeXLive merge into FreeBSD ports tree - FreeBSD project idea
On 06/17/2012 08:01, David Schultz wrote: On Wed, May 30, 2012, Aldis Berjoza wrote: I which TeXLive would be merged in FreeBSD ports. Romain is doing great job maintaining it. And it work, And it work now. In fact it works for more than a year. I have used his TeXLive ports through portshaker for a while. They work pretty well, but there are some issues due to the fact that the TeXLive folks have some strange ideas. For one, TeXLive is split into over 2000 packages, many of which are tiny; the FreeBSD package system doesn't handle that very well. For another, TeXLive now has its own (dubious) package manager, tlmgr, which doesn't play well with other package management systems. I'm not a ports committer, but perhaps a good first step to getting TeXLive working better in FreeBSD is to introduce a TeTeX vs TeXLive knob in the ports tree so that people don't wind up accidentally clobber their TeXLive install when TeTex gets pulled in as a dependency. I have been using Romain's TeXLive for almost a year, too. It is great, Romain does a good job and is very helpful, but it is definitely not ready for ports, yet. On machines not older than two years, the 500 to 600 ports that texlive-scheme-tetex is bearable, although it considerably slows down testing if all ports are up to date etc. Though it would like to have texlive-scheme-full, I have stopped using it for that reason. On older machines, even texlive-scheme-tetex adds a lot to port upgrading operations. The last time I checked, there still have been many broken links installed into bin. It is pretty easy to fix after installing the ports, but of course it should be done in the port, which at least does not seem to be trivial. Some other ports do not build because of this, for example with epstopdf missing. Quite a few conflicts and changes in dependencies are needed for TeXLive. TeXLive does not just replace teTeX, but also ports like freetype-tools, t1utils, jadetex, etc. I have patches for all ports I use, which has been working for me for half a year. If TeXLive and teTeX were supposed to exist in ports in parallel for some time, something like bsd.tex.mk would be needed with a generic way to specify tex related dependencies. Maybe this would be useful for the transition period, since we probably would not want texlive-scheme-tetex to replace all teTeX dependencies, but many people disagree that having both TeX at the same time in ports would be a good idea. There are ports that I could not get to build with TeXLive at all: misc/freebsd-doc-* There are too many error messages I do not understand. Someone with a lot more insight will have to look at these, before TeXLive can replace teTeX in ports. I have posted to texlive-free...@googlegroups.com about this, but there were no answers. I guess the biggest problem for people to put more effort into fixing TeXLive in FreeBSD ports is the huge disagreement about how a final solution should look like. OT: FreeBSD might be more behind than others, but others have trouble with TeXLive in their native packaging system, too: Nothing never than TeXLive 2009 made it into Ubuntu 12.04 LTS. Cheers, Jan Henrik ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: how to turn my computer into a TV
On 06/17/12 04:14, Aryeh Friedman wrote: I just moved into a very cramped apartment and we only have room for one monitor so it is the computer then I heard it is possible to make it so you can watch TV on your computer I know about some this for windows but I am dedicated FreeBSD person... how do I go about doing all the research I need to make sure that the following is true: 1. FreeBSD supports all hardware (and the needed functionality) to watch full screen tv on my computer (extra points of a remote can be used)... NOTE: This hardware must be currently fairly mass market 2. What ports to install (right now my desktop is x11-wm/xfce4) make this happen 3. Any tips on making it optimal This is perhaps not the solution you are looking for, but many modern TV screens has a VGA and a DVI input connector, as well as many fairly modern computers has HDMI output. DVI is also compatible with HDMI, at least to an extent. Perhaps you can find a monitor and use it as a dual-purpose monitor instead? Regards! -- Niclas Zeising ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: how to turn my computer into a TV
On Sun, Jun 17, 2012 at 9:38 AM, Niclas Zeising zeis...@daemonic.se wrote: On 06/17/12 04:14, Aryeh Friedman wrote: I just moved into a very cramped apartment and we only have room for one monitor so it is the computer then I heard it is possible to make it so you can watch TV on your computer I know about some this for windows but I am dedicated FreeBSD person... how do I go about doing all the research I need to make sure that the following is true: 1. FreeBSD supports all hardware (and the needed functionality) to watch full screen tv on my computer (extra points of a remote can be used)... NOTE: This hardware must be currently fairly mass market 2. What ports to install (right now my desktop is x11-wm/xfce4) make this happen 3. Any tips on making it optimal This is perhaps not the solution you are looking for, but many modern TV screens has a VGA and a DVI input connector, as well as many fairly modern computers has HDMI output. DVI is also compatible with HDMI, at least to an extent. Perhaps you can find a monitor and use it as a dual-purpose monitor instead? Regards! -- Niclas Zeising I think hes maybe looking for a tv tuner card to plug into his computer so he can watch TV on the PC also... Haupauge makes a few and are compatible with FreeBSD. See Setting Up TV Cards and a good list is freebsd-multimedia http://www.freebsd.org/doc/handbook/tvcard.html ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: TeXLive merge into FreeBSD ports tree - FreeBSD project idea
On Sun, Jun 17, 2012, Jan Henrik Sylvester wrote: Quite a few conflicts and changes in dependencies are needed for TeXLive. TeXLive does not just replace teTeX, but also ports like freetype-tools, t1utils, jadetex, etc. I have patches for all ports I use, which has been working for me for half a year. If TeXLive and teTeX were supposed to exist in ports in parallel for some time, something like bsd.tex.mk would be needed with a generic way to specify tex related dependencies. Maybe this would be useful for the transition period, since we probably would not want texlive-scheme-tetex to replace all teTeX dependencies, but many people disagree that having both TeX at the same time in ports would be a good idea. Right, so like I said, having the knob in the tree would be a useful first step, even if TeXLive isn't ready for inclusion. (I'd be surprised if there's a good reason to have multiple versions of things like t1utils, but that's a separate issue.) I guess the biggest problem for people to put more effort into fixing TeXLive in FreeBSD ports is the huge disagreement about how a final solution should look like. OT: FreeBSD might be more behind than others, but others have trouble with TeXLive in their native packaging system, too: Nothing never than TeXLive 2009 made it into Ubuntu 12.04 LTS. Yep, it's a giant mess. IIRC Ubuntu ships the most popular TeXLive schemas as separate packages. Doing anything more fine-grained than that seems unmanageable, especially since dependencies among TeXLive packages aren't tracked properly. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: how to turn my computer into a TV
Just a small notes on requirements we *DO NOT* have cable or any other
non-broadcast service (we are using a broadcast signal only [current
US {NYC} standards])
On Sun, Jun 17, 2012 at 1:02 PM, Juergen Lock n...@jelal.kn-bremen.de wrote:
In article
cakyr3zwqqyihzcomyuobobou-svqylmgk36qdnebvcvgbhj...@mail.gmail.com you
write:
On Sun, Jun 17, 2012 at 9:38 AM, Niclas Zeising zeis...@daemonic.se wrote:
On 06/17/12 04:14, Aryeh Friedman wrote:
I just moved into a very cramped apartment and we only have room for
one monitor so it is the computer then I heard it is possible to make
it so you can watch TV on your computer I know about some this for
windows but I am dedicated FreeBSD person... how do I go about doing
all the research I need to make sure that the following is true:
1. FreeBSD supports all hardware (and the needed functionality) to
watch full screen tv on my computer (extra points of a remote can be
used)... NOTE: This hardware must be currently fairly mass market
2. What ports to install (right now my desktop is x11-wm/xfce4) make this
happen
3. Any tips on making it optimal
This is perhaps not the solution you are looking for, but many modern TV
screens has a VGA and a DVI input connector, as well as many fairly modern
computers has HDMI output. DVI is also compatible with HDMI, at least to an
extent. Perhaps you can find a monitor and use it as a dual-purpose monitor
instead?
Regards!
--
Niclas Zeising
I think hes maybe looking for a tv tuner card to plug into his
computer so he can watch TV on the PC also...
Haupauge makes a few and are compatible with FreeBSD. See Setting Up TV Cards
and a good list is freebsd-multimedia
http://www.freebsd.org/doc/handbook/tvcard.html
That handbook chapter only mentions analog bktr(4) tuner cards so
it's a bit outdated. Nowadays you can also use cx88-based analog
and dvb-t/atsc(?) pci(e) tuner cards driven by the multimedia/cx88
port, as well as a greater variety of usb tuners supported by
multimedia/webcamd which runs the Linux v4l/dvb driver code in
FreeBSD userland. See
http://wiki.freebsd.org/WebcamCompat
for some tuners people have reported as working. Another usb
atsc tuner that has good chances of working is this one:
http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-950Q
(at least it seems pretty popular on Linux.)
And about tv apps that you can control using a remote (usually via
comms/lirc), the most popular ones are multimedia/mythtv and
multimedia/vdr, see these pages:
http://wiki.freebsd.org/HTPC
http://wiki.freebsd.org/MythTV
and
http://wiki.freebsd.org/VDR
as well as multimedia/xbmc-pvr that you can use with vdr as backend
as also described in the above vdr wiki page.
HTH, :)
Juergen
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: how to turn my computer into a TV
In article cakyr3zwqqyihzcomyuobobou-svqylmgk36qdnebvcvgbhj...@mail.gmail.com you write: On Sun, Jun 17, 2012 at 9:38 AM, Niclas Zeising zeis...@daemonic.se wrote: On 06/17/12 04:14, Aryeh Friedman wrote: I just moved into a very cramped apartment and we only have room for one monitor so it is the computer then I heard it is possible to make it so you can watch TV on your computer I know about some this for windows but I am dedicated FreeBSD person... how do I go about doing all the research I need to make sure that the following is true: 1. FreeBSD supports all hardware (and the needed functionality) to watch full screen tv on my computer (extra points of a remote can be used)... NOTE: This hardware must be currently fairly mass market 2. What ports to install (right now my desktop is x11-wm/xfce4) make this happen 3. Any tips on making it optimal This is perhaps not the solution you are looking for, but many modern TV screens has a VGA and a DVI input connector, as well as many fairly modern computers has HDMI output. DVI is also compatible with HDMI, at least to an extent. Perhaps you can find a monitor and use it as a dual-purpose monitor instead? Regards! -- Niclas Zeising I think hes maybe looking for a tv tuner card to plug into his computer so he can watch TV on the PC also... Haupauge makes a few and are compatible with FreeBSD. See Setting Up TV Cards and a good list is freebsd-multimedia http://www.freebsd.org/doc/handbook/tvcard.html That handbook chapter only mentions analog bktr(4) tuner cards so it's a bit outdated. Nowadays you can also use cx88-based analog and dvb-t/atsc(?) pci(e) tuner cards driven by the multimedia/cx88 port, as well as a greater variety of usb tuners supported by multimedia/webcamd which runs the Linux v4l/dvb driver code in FreeBSD userland. See http://wiki.freebsd.org/WebcamCompat for some tuners people have reported as working. Another usb atsc tuner that has good chances of working is this one: http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-950Q (at least it seems pretty popular on Linux.) And about tv apps that you can control using a remote (usually via comms/lirc), the most popular ones are multimedia/mythtv and multimedia/vdr, see these pages: http://wiki.freebsd.org/HTPC http://wiki.freebsd.org/MythTV and http://wiki.freebsd.org/VDR as well as multimedia/xbmc-pvr that you can use with vdr as backend as also described in the above vdr wiki page. HTH, :) Juergen ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: TeXLive merge into FreeBSD ports tree - FreeBSD project idea
On 06/17/2012 18:32, David Schultz wrote:
On Sun, Jun 17, 2012, Jan Henrik Sylvester wrote:
Quite a few conflicts and changes in dependencies are needed for
TeXLive. TeXLive does not just replace teTeX, but also ports like
freetype-tools, t1utils, jadetex, etc. I have patches for all ports I
use, which has been working for me for half a year. If TeXLive and teTeX
were supposed to exist in ports in parallel for some time, something
like bsd.tex.mk would be needed with a generic way to specify tex
related dependencies. Maybe this would be useful for the transition
period, since we probably would not want texlive-scheme-tetex to replace
all teTeX dependencies, but many people disagree that having both TeX at
the same time in ports would be a good idea.
Right, so like I said, having the knob in the tree would be a
useful first step, even if TeXLive isn't ready for inclusion.
(I'd be surprised if there's a good reason to have multiple
versions of things like t1utils, but that's a separate issue.)
I do not understand what you precisely mean with a knob as a useful
first step.
If we do not create a generic way to specify tex related dependencies
(USE_TEX=core t1utils tocloft), we need to decide that TeXLive will
eventually go into the tree the way Romain created the ports to be able
to depend on print/texlive-core, print/texlive-tocloft, etc.
Or what other way to introduce dependencies are you thinking about?
It is not possible to simply use print/texlive-core instead of
print/teTeX, not even print/texlive-scheme-tetex is enough as teTeX
includes more than that scheme currently gives. At the same time,
print/texlive-core replaces more than just print/teTeX: I have a list of
about 10 ports I had previously installed, which conflict with TeXLive
but have their functionality provided mostly by print/texlive-core as
far as I need it (except for building misc/freebsd-doc-*, which I cannot
fix).
For the ports I use, I have patches that introduce dependencies like
this one in devel/doxygen:
.if exists(${LOCALBASE}/share/texmf/scripts/texlive/tlmgr.pl)
BUILD_DEPENDS+=
texlive-scheme-tetex=0:${PORTSDIR}/print/texlive-scheme-tetex \
${LOCALBASE}/share/texmf-dist/tex/latex/tocloft/tocloft.sty:${PORTSDIR}/print/texlive-tocloft
.else
BUILD_DEPENDS+=dvips:${PORTSDIR}/print/dvipsk-tetex \
latex:${PORTSDIR}/print/teTeX
.endif
Even with a knob instead of checking if print/texlive-core is installed,
it would put a lot of mess into the ports tree. Some maintainers will
not agree to introduce these conditions, if there is no general
agreement that we want to transition to TeXLive that way.
As far as I remember, both romain@ and hrs@ have stated that they do not
want both teTeX and TeXLive in the tree concurrently.
Cheers,
Jan Henrik
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: TeXLive merge into FreeBSD ports tree - FreeBSD project idea
On Sun, Jun 17, 2012, Jan Henrik Sylvester wrote: Even with a knob instead of checking if print/texlive-core is installed, it would put a lot of mess into the ports tree. Some maintainers will not agree to introduce these conditions, if there is no general agreement that we want to transition to TeXLive that way. As far as I remember, both romain@ and hrs@ have stated that they do not want both teTeX and TeXLive in the tree concurrently. In that case, it sounds like using TeXLive in FreeBSD will be a bit tricky until someone steps in and does all the work required for integration. Unfortunately I'm a bit time-constrained for the next few months, but I do use TeXLive and would be happy to test any proposed patches. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: TeXLive merge into FreeBSD ports tree - FreeBSD project idea
Enviat des del meu iTotxo (disculpeu la brevetat) Sent from my iBrick (excuse me for the brief message) Quite a few conflicts and changes in dependencies are needed for TeXLive. TeXLive does not just replace teTeX, but also ports like freetype-tools, t1utils, jadetex, etc. I have patches for all ports I use, which has been working for me for half a year. If TeXLive and teTeX were supposed to exist in ports in parallel for some time, something like bsd.tex.mk would be needed with a generic way to specify tex related dependencies. Maybe this would be useful for the transition period, since we probably would not want texlive-scheme-tetex to replace all teTeX dependencies, but many people disagree that having both TeX at the same time in ports would be a good idea. There are ports that I could not get to build with TeXLive at all: misc/freebsd-doc-* There are too many error messages I do not understand. Someone with a lot more insight will have to look at these, before TeXLive can replace teTeX in ports. I have posted to texlive-free...@googlegroups.com about this, but there were no answers. I guess the biggest problem for people to put more effort into fixing TeXLive in FreeBSD ports is the huge disagreement about how a final solution should look like. OT: FreeBSD might be more behind than others, but others have trouble with TeXLive in their native packaging system, too: Nothing never than TeXLive 2009 made it into Ubuntu 12.04 LTS. Cheers, Jan Henrik ___ One (among others) problems is the TL nanescheme. They don't release packages with version number. Because of that maintaining the distinfo of thousands of packages is quite difficult. Then I'd vote for keeping an old version of the TL tarballs (like ubuntu does) in the FreeBSD FTP distfiles dir and proceed with fixing the ports needing teTeX. I did for gnome2 sometime ago and wasn't that for most of the gnome2 packages. I would like to help if this patch is taken. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: BIO_DELETE equivalent for file on FFS filesystem
On 16 June 2012 13:46, Garrett Cooper yaneg...@gmail.com wrote: What if you cp it? Our version of cp doesn't support sparsing of files, but Linux's does: http://linux.about.com/od/commands/l/blcmdl1_cp.htm Is this intentional that we don't support sparse files or just no one wrote the code? -- Eitan Adler ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: EFI development tools
On 6/15/12 6:44 PM, Eric McCorkle wrote:
However, the EFI programs I produce using the EDK system work
properly, and don't have the same issues as the ones I produce using
what's in the base system.
Okay, after a whole lot of slogging, I figured out the root of the
problems I've been seeing, and it needs to be addressed ASAP.
When I compile the following program:
#include stdlib.h
#include efi.h
#include efiapi.h
#include stdio.h
int main() {
printf(%d\n, UINT64);
return 0;
}
as follows:
gcc -o test -O2 -m32 -I${HEAD}/sys/boot/efi/include
-I${HEAD}/sys/boot/efi/include/i386 -I${HEAD}/sys/boot/common test.c
and run it, the output is 4, not 8 as it should be. You can replace
UINT64 with uint64_t and see the same (erroneous) behavior. The -m32
flag seems to be the culprit; removing it fixes the problem.
This is why I was having problems, as the offsets in EFI_SYSTEM_TABLE
were wrong.
In any case, this is a pretty serious error, and someone should try to
reproduce it and take a look at it.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: EFI development tools
On 6/17/12 6:45 PM, Eric McCorkle wrote:
On 6/15/12 6:44 PM, Eric McCorkle wrote:
int main() {
printf(%d\n, UINT64);
return 0;
}
Correction: it should be sizeof(UINT64)
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: EFI development tools
Hiya,
don't suppose you could file a PR for this?
Adrian
On 17 June 2012 16:10, Eric McCorkle e...@shadowsun.net wrote:
On 6/17/12 6:45 PM, Eric McCorkle wrote:
On 6/15/12 6:44 PM, Eric McCorkle wrote:
int main() {
printf(%d\n, UINT64);
return 0;
}
Correction: it should be sizeof(UINT64)
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: EFI development tools
On 6/17/12 8:26 PM, Adrian Chadd wrote: Hiya, don't suppose you could file a PR for this? Typing one up just now, after figuring out the root cause. The short version is this: __uint64_t gets defined in machine/_types.h as unsigned long. This breaks when you use -m32, in which case sizeof(unsigned long) == 4. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: EFI development tools
Eric McCorkle e...@shadowsun.net wrote: The -m32 flag seems to be the culprit; removing it fixes the problem. This is why I was having problems, as the offsets in EFI_SYSTEM_TABLE were wrong. In any case, this is a pretty serious error, and someone should try to reproduce it and take a look at it. This is a known issue, and had been around for a long time. You can't reliably build 32 bit binaries (what the -m32 flag specifies) on a 64 bit system. The header files (and possibly other things) are wrong. Doesn't look like anyone has opened a PR for it. -- Sent from my Android tablet. Please excuse my swyping. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: EFI development tools
On 6/17/12 8:43 PM, Mike Meyer wrote: Eric McCorkle e...@shadowsun.net wrote: The -m32 flag seems to be the culprit; removing it fixes the problem. This is why I was having problems, as the offsets in EFI_SYSTEM_TABLE were wrong. In any case, this is a pretty serious error, and someone should try to reproduce it and take a look at it. This is a known issue, and had been around for a long time. You can't reliably build 32 bit binaries (what the -m32 flag specifies) on a 64 bit system. The header files (and possibly other things) are wrong. Doesn't look like anyone has opened a PR for it. I just did. I'll keep that in mind, as I'm working on the 32-bit EFI implementation on a 64-bit machine. In the short term, I'll edit efibind.h (or wherever UINT64 is defined in the efi hierarchy) in my checkout and add a workaround. That should, in theory, hold. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: how to turn my computer into a TV
[ Added multimedia@ as that is a more appropriate list than hackers ]
I just moved into a very cramped apartment
we are using a broadcast signal only [current US {NYC} standards]
You'll need to know if you have any NTSC (analog) stations you
care about or if everything is ATSC (digital). Hopefully your
building has a good antenna system.
Next, select your tuner(s). You have a choice of tuners that connect
via Ethernet (HDHomeRun, pros: small external box, doesn't need a slot,
works with any OS, better diagnostic info than others. cons: I've seen
a *lot* of postings with people saying that various other tuners get better
reception, digital only no NTSC analog), Firewire (if they are still
available?), USB, PCIe cards (needs a slot), PCI cards (needs a slot).
Some cards also do FM radio.
2. What ports to install
Depends on what tuner(s) you select.
Cards based on cx88 need multimedia/cx88 and multimedia/libtuner
http://corona.homeunix.net/cx88wiki
has a list of supported cards.
Some cards are supported by bktr(4).
Make sure the tuner you select is supported by FreeBSD.
Recording ATSC takes very little CPU. Recording NTSC takes either
a lot of CPU or hardware compression. Decoding either takes a lot of CPU
(or hardware decoding which AFAIK FreeBSD doesn't have). You can use
at(1) for automated recordings. A full ATSC channel is 19.3 Mbps.
Some tuners allow filtering by PID, which saves disk space.
For playback you can use mplayer or any of several similar programs.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: proper newfs options for SSD disk
On Sat, 16 Jun 2012, Matthias Apitz wrote: OK, but I wanted to have most of the space of the 4 GB SSD encrypted with geli(8); so I should make there some slice containing /boot (unencrypted) and a second slice which later will contain my HOME and encrypted; wrong? That's correct: http://forums.freebsd.org/showthread.php?t=29652 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
