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 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"
how to turn my computer into a TV
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 ___ 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 06/16/12 06:03, Andrey V. Elsukov wrote: > Hi, Eric. > > Did you try the GNU EFI toolchain? It contains a good descriptions > on how to build EFI application and we probably can use some > suggestions even without importing it. > > http://sourceforge.net/projects/gnu-efi/ > I did. It looks like what's in the base system now was adapted from that. Now that I can build OVMF, I have substantially more ability to figure out what's going wrong with the programs I build using that method. I can also compare the files and assembly coming out of EDK builds to what comes out of the GNU toolchain. I'd be willing to bet it's some sort of subtle ABI issue. There are a couple of very subtle differences between the PE (microsoft) and ELF ABIs. ___ 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 Jun 16, 2012 8:26 PM, wrote: > > > > And PLEASE DO NOT make this stupid MSDOS style slices. It is not just > > > unneeded but introduces mess and only mess. > > > > > > just have /dev/ad0a not /dev/ad0s1a > > > What FreeBSD devs have to say about this? > ;) I say we have GPT this decade :) Chris ___ 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 Sat, Jun 16, 2012 at 1:34 PM, Mike Meyer wrote: > On Sat, 16 Jun 2012 21:04:26 +0100 > Chris Rees wrote: > >> On Jun 16, 2012 8:37 PM, "Xin LI" wrote: >> > >> > On Sat, Jun 16, 2012 at 12:01 PM, Chris Rees wrote: >> > > On Jun 14, 2012 5:49 AM, "Wojciech Puchar" < >> woj...@wojtek.tensor.gdynia.pl> >> > > wrote: >> > >> > file to take 900MB or... can i call some system function to "punch" >> > holes? >> > >>> >> > >>> >> > >>> I think you can only truncate the file at this time, pretty much like >> > >>> brk() works for memory. >> > >> >> > >> >> > >> >> > >> BAD. suppose i keep windoze VM image on filesystem which takes 10GB but >> > > uses 5GB. >> > >> >> > >> i could write simple program to find out what blocks are unused and >> > > then...do nothing. >> > >> >> > > >> > > What if you cp it? >> > >> > That would be a dd(1) unless we teach cp(1) how to do sparse. I think >> > what he wanted is to tell the OS "I don't need block XX - YY anymore" >> > and the OS creates a sparse hole, which is not available at this time. >> >> Sorry, I must have misread. I take it cp would take a file with holes and >> only copy the data part? i.e. take a 10G file of which 5G is a hole, you'd >> end up with a 5G file? > > No, cp just does read()s. Reading data from a hole returns a block > full of zeros. A quick test (after writing a program to create the > file) shows this: > > bhuda% df -h . > Filesystem Size Used Avail Capacity Mounted on > /dev/md0 123M 1.2M 112M 1% /tmp > bhuda% ls -lh holey.test > -rwxr-xr-x 1 mwm wheel 953M Jun 16 16:22 holey.test > > Ok, I've got a file that's 953M on an FS with 1.2 meg used. It's got > holes. > > bhuda% cp holey.test foobar > /tmp: write failed, filesystem is full > cp: foobar: No space left on device > > And doing a cp fails. Use dd conv=sparse to get the effect you want. Our version of cp doesn't support sparsing of files, but Linux's does: http://linux.about.com/od/commands/l/blcmdl1_cp.htm Our copy of dd and rsync are the two common tools I know of that properly handle sparse files if the underlying filesystem supports it (like Xin said), apart from writing a tool to do the necessary calls to lseek to do the right thing in the file (which is possible, but you would need to potentially read the whole file in, or pieces, similar to defrag until Windows might do). Thanks, -Garrett ___ 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 Sat, 16 Jun 2012 21:04:26 +0100 Chris Rees wrote: > On Jun 16, 2012 8:37 PM, "Xin LI" wrote: > > > > On Sat, Jun 16, 2012 at 12:01 PM, Chris Rees wrote: > > > On Jun 14, 2012 5:49 AM, "Wojciech Puchar" < > woj...@wojtek.tensor.gdynia.pl> > > > wrote: > > > > file to take 900MB or... can i call some system function to "punch" > > holes? > > >>> > > >>> > > >>> I think you can only truncate the file at this time, pretty much like > > >>> brk() works for memory. > > >> > > >> > > >> > > >> BAD. suppose i keep windoze VM image on filesystem which takes 10GB but > > > uses 5GB. > > >> > > >> i could write simple program to find out what blocks are unused and > > > then...do nothing. > > >> > > > > > > What if you cp it? > > > > That would be a dd(1) unless we teach cp(1) how to do sparse. I think > > what he wanted is to tell the OS "I don't need block XX - YY anymore" > > and the OS creates a sparse hole, which is not available at this time. > > Sorry, I must have misread. I take it cp would take a file with holes and > only copy the data part? i.e. take a 10G file of which 5G is a hole, you'd > end up with a 5G file? No, cp just does read()s. Reading data from a hole returns a block full of zeros. A quick test (after writing a program to create the file) shows this: bhuda% df -h . FilesystemSizeUsed Avail Capacity Mounted on /dev/md0 123M1.2M112M 1%/tmp bhuda% ls -lh holey.test -rwxr-xr-x 1 mwm wheel 953M Jun 16 16:22 holey.test Ok, I've got a file that's 953M on an FS with 1.2 meg used. It's got holes. bhuda% cp holey.test foobar /tmp: write failed, filesystem is full cp: foobar: No space left on device And doing a cp fails. Use dd conv=sparse to get the effect you want. http://www.mired.org/ Independent Software developer/SCM consultant, email for more information. O< ascii ribbon campaign - stop html mail - www.asciiribbon.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: BIO_DELETE equivalent for file on FFS filesystem
On Jun 16, 2012 8:37 PM, "Xin LI" wrote: > > On Sat, Jun 16, 2012 at 12:01 PM, Chris Rees wrote: > > On Jun 14, 2012 5:49 AM, "Wojciech Puchar" < woj...@wojtek.tensor.gdynia.pl> > > wrote: > > file to take 900MB or... can i call some system function to "punch" > holes? > >>> > >>> > >>> I think you can only truncate the file at this time, pretty much like > >>> brk() works for memory. > >> > >> > >> > >> BAD. suppose i keep windoze VM image on filesystem which takes 10GB but > > uses 5GB. > >> > >> i could write simple program to find out what blocks are unused and > > then...do nothing. > >> > > > > What if you cp it? > > That would be a dd(1) unless we teach cp(1) how to do sparse. I think > what he wanted is to tell the OS "I don't need block XX - YY anymore" > and the OS creates a sparse hole, which is not available at this time. Sorry, I must have misread. I take it cp would take a file with holes and only copy the data part? i.e. take a 10G file of which 5G is a hole, you'd end up with a 5G file? Chris ___ 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 Sat, Jun 16, 2012 at 12:01 PM, Chris Rees wrote: > On Jun 14, 2012 5:49 AM, "Wojciech Puchar" > wrote: file to take 900MB or... can i call some system function to "punch" holes? >>> >>> >>> I think you can only truncate the file at this time, pretty much like >>> brk() works for memory. >> >> >> >> BAD. suppose i keep windoze VM image on filesystem which takes 10GB but > uses 5GB. >> >> i could write simple program to find out what blocks are unused and > then...do nothing. >> > > What if you cp it? That would be a dd(1) unless we teach cp(1) how to do sparse. I think what he wanted is to tell the OS "I don't need block XX - YY anymore" and the OS creates a sparse hole, which is not available at this time. Cheers, -- Xin LI https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die ___ 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
> > And PLEASE DO NOT make this stupid MSDOS style slices. It is not just > > unneeded but introduces mess and only mess. > > > > just have /dev/ad0a not /dev/ad0s1a What FreeBSD devs have to say about this? ;) > 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? > > matthias > -- You can encrypt ANY provider. Put HOME on i.e; 'h' bsd label and encrypt it via geli. Or encrypt whole SSD and have /boot on USB stick or optical media, or ... Domagoj Smolčić ___ 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 Jun 14, 2012 5:49 AM, "Wojciech Puchar" wrote: >>> >>> file to take 900MB or... can i call some system function to "punch" >>> holes? >> >> >> I think you can only truncate the file at this time, pretty much like >> brk() works for memory. > > > > BAD. suppose i keep windoze VM image on filesystem which takes 10GB but uses 5GB. > > i could write simple program to find out what blocks are unused and then...do nothing. > What if you cp it? Chris ___ 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
El día Wednesday, May 30, 2012 a las 07:44:37PM +0200, Wojciech Puchar escribió: > > from; one has to go (by pressing ESC) to the boot menu to pick it up as > > current boot device; any idea how this could be changed? > > boot from 4GB. just put /boot here and add > > vfs.root.mountfrom="ufs:XXX" > > where XXX is your root filesystem device name with "/dev/" stripped > > do not forget to bsdlabel -B your.4GB.SSD > > WARNING: you must have proper disklabel with a: partition containing UFS > with /boot. > > But you may have a partition equal to whole disk > >a: 117231408 04.2BSD0 0 0 >c: 117231408 0unused0 0 # "raw" part, don't > edit > > > and it is absolutely OK, UFS do not overwrite first few sectors as it is > reserved for it. > > And PLEASE DO NOT make this stupid MSDOS style slices. It is not just > unneeded but introduces mess and only mess. > > just have /dev/ad0a not /dev/ad0s1a 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? matthias -- Matthias Apitz e - w http://www.unixarea.de/ UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 ___ 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
i could write simple program to find out what blocks are unused and then...do nothing. Actually you can. Use dd if=infile of=outfile conv=sparse to convert a file to a sparse file. This obviously only works on filesystems supporting sparse files, such as UFS. of course i can by copying. not really what i want Regards, Pieter ___ 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: BIO_DELETE equivalent for file on FFS filesystem
On Thursday 14 June 2012 06:48:14 Wojciech Puchar wrote: > >> file to take 900MB or... can i call some system function to "punch" > >> holes? > > > > I think you can only truncate the file at this time, pretty much like > > brk() works for memory. > > BAD. suppose i keep windoze VM image on filesystem which takes 10GB but > uses 5GB. > > i could write simple program to find out what blocks are unused and > then...do nothing. Actually you can. Use dd if=infile of=outfile conv=sparse to convert a file to a sparse file. This obviously only works on filesystems supporting sparse files, such as UFS. Regards, Pieter ___ 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: mergemaster bug?
- Original Message - From: Doug Barton To: rank1see...@gmail.com Cc: hack...@freebsd.org Date: Fri, 15 Jun 2012 17:09:33 -0700 Subject: Re: mergemaster bug? > On 06/15/2012 11:37, rank1see...@gmail.com wrote: > >*** The following files exist in /etc/rc.d but not in > >/var/tmp/temproot/etc/rc.d/: > > > > sshd > > man src.conf, and search for SSH. You have one of those options defined > in your environment. > > Doug > > -- You were right. I had a WITHOUT_OPENSSL set, as I've tested something and forgot to remove it. Thanks. Domagoj ___ 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 16.06.2012 02:44, Eric McCorkle wrote: > I've been working on EFI support for intel platforms. I've managed to > build the EFI Development Kit (EDK II) and the IASL compiler for > FreeBSD, which raises the possibility of integrating them either as > ports, or possibly into the base system. > > Here is some background: > > Right now, there is only one EFI program that gets built in the entire > system: loader.efi (for IA64, and in the future, i386 and amd64). > This is done by building a standard ELF program with a custom linker > script which produces code at a base address of 0x1000 (This is a > trick to get the effects of compiling for position-independent code, > as required by the PE format, as the actual .text section starts at > that offset into the file). It then uses objcopy to translate to the > PE executable format. I've had some strange behavior in some of the > EFI interfaces (notably, ConOut), which smacks of some sort of subtle > ABI issue. > > EDK seems to be made for development on a windows box, with marginal > support for Darwing and some Linux distros added as an afterthought. > It takes a bit of shoehorning to get it to build and run on FreeBSD, > but I did get it to work. However, it would take a nontrivial effort > to get it in shape for importation into the base FreeBSD system. It > also relies on mingw32 binutils and gcc, as well as python (though it > only uses python for build purposes; an effort to import it into the > base system would probably remove all the python bits). Hi, Eric. Did you try the GNU EFI toolchain? It contains a good descriptions on how to build EFI application and we probably can use some suggestions even without importing it. http://sourceforge.net/projects/gnu-efi/ -- WBR, Andrey V. Elsukov ___ 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"
