Re: *Editing* PDFs?
[EMAIL PROTECTED] wrote: in message [EMAIL PROTECTED], wrote James Leone thusly... To convert the .doc file, open it with MS Word in Cross Over Office, print it, catch the postscript file before the job finishes, rename it as whatever2.ps Being ignorant about Cross Over Office, can it not print to a file, like enscript, wordperfect (long live!), netscape, or mozilla which print to a printer by default? If you create a printer on your system that creates PDF's, Cross Over Office will use it. If you don't have one, or don't know how, you have other options. James Leone ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: *Editing* PDFs?
[EMAIL PROTECTED] wrote: On Mon, 2003-10-13 at 09:59, Bill Campbell wrote: On Mon, Oct 13, 2003, Alexander Farber wrote: I've read some where that the new OpenOffice is capable of pdf-output There's an article in this month's Linux Journal on Scribus saying that it has very good PDF capabilities. The article said that Scribus is available on a number of *ix platforms, and I think FreeBSD was on the list. The only way I have been able to edit existing PDF's is by installing Adobe Acrobat 5.0 in Linux by using Codeweaver's Cross Over Office, which is available at www.codeweavers.com. I have been able to combine PDF's and create PDF's out of anything printable just by using some basic Unix utilities. I can go into detail if someone likes. James Leone ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: *Editing* PDFs?
[EMAIL PROTECTED] wrote: On 10/13/03 19:03, James Leone wrote: The only way I have been able to edit existing PDF's is by installing Adobe Acrobat 5.0 in Linux by using Codeweaver's Cross Over Office, which is available at www.codeweavers.com. Which is the original problem :-) I would categorize PDF files in two ways: A. Indirectly editable with other programs if you have the program and data file (LyX, Scribus) B. Unencrypted postscript (PDF provided, no source editor available - See below) C. Encrypted postscript Adobe Acrobat in Wine is the only possibility I have been able to combine PDF's and create PDF's out of anything printable just by using some basic Unix utilities. I can go into detail if someone likes. Definitely! Take a look at this post, and its follow up. http://www.linuxsa.org.au/mailing-list/2002-10/1511.html http://www.linuxsa.org.au/mailing-list/2002-10/1519.html Here is an extreme example, and how much you can do depends upon the condition of the PDF file. Anyway, here is a grand tour of what can be done if everything works right.. :-) Lets just assume that I had a document, written in MS Word emailed to me and I needed to incorporate that into a PDF file as the first page, Adobe Acrobat is unavailable, but Acrobat Reader is installed. Assume I didn't have Open Office. You can save the PDF file as a postscript file with Acrobat Reader. To convert the .doc file, open it with MS Word in Cross Over Office, print it, catch the postscript file before the job finishes, rename it as whatever2.ps. You can combine the two postscript files into one with the method I describe in those emails. Now if you are somewhere else without the .doc file, you can still edit the postscript file(s). Just name the file whatever.ps, then run ps2ascii whatever.ps, it will produce a text version of the PDF file, called whatever.txt. Edit the text in whatever way you like, use whatever tool you like to print, capture the .ps file James Leone ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Request
Anna Treece wrote: I know this is a weird request, but i'm desperate here. My husband is stationed in Iraq. His access to websites is VERY limited. He can get to freebsd.org but cannot get to our home page which has pictures of his son (he last saw his son when he was 6mo old). the site is www.treece.org/sean to prove that I'm telling the truth here. I need to know if there is ANY way that you will let me send you a picture of my son to post to ANYWHERE on your site so that my husband can see what he looks like now (Sean turns 1 on the 27th). I would love to be able to keep him up to date w/pictures more so than right now. No problem. Send me an email off list. JL ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help
George Parotidis wrote: Hello my name is George Parotidis and I have a problem with FreeBSD 5.1. The problen is when I type startx in Terminal mode it beggins loading and then says:Fatal Error no screens found. Maybe some one can help me?Than you. http://www.linuxsa.org.au/mailing-list/2003-08/1397.html JL ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Netware Client for FreeBSD
/nwclient/nwfs.sh.sample,v 1.1 1999/11/03 12:06:13 bp Exp $ # # Location: /usr/local/etc/rc.d/nwfs.sh # # Simple script to mount NetWare volumes at startup. # It assumes that all mount points described in fstab file and password # entries listed in /root/.nwfsrc file. See mount_nwfs(8) for details. # mount=/sbin/mount umount=/sbin/umount HOME=/root; export HOME vols=sys if [ x$1 = x -o x$1 = xstart ]; then echo -n Mounting NetWare volumes: for vol in ${vols}; do $mount $vol echo -n $vol done echo Done elif [ x$1 = xstop ]; then echo -n Unmounting NetWare mount points: for vol in ${vols}; do $umount $vol echo -n $vol done echo Done else echo Unknown command $1 fi This seems like it should be used with $HOME/.nwfsrc, which reads: # $FreeBSD: src/share/examples/nwclient/dot.nwfsrc,v 1.2 2002/04/20 05:04:21 bp Exp $ # # Example for .nwfsrc file # # ncplib lookups configuration files in next order: #1. ~/.nwfsrc #2. /etc/nwfs.conf - if this file found it will # override values with same keys from user files. # # # This file consist of a set of sections. Each section started by section name # surrounded by square brackets: # [section_name] # # End of the section marked either by new section or by the end of file. # Each section can contain zero or more parameters: # [section_name] # key=value # # where 'key' is a represents parameter name and 'value' a value assigned # to this parameter. # # NetWare library uses next forms of section names: # [SERVER] # [SERVER:USER] # [SERVER:QUEUE] # # When user issues any ncp* command that requires create of new connection # to a NetWare server, library function lookups for parameters in the # corresponding section. First it looks in the [SERVER] section and then in # the [SERVER:USER] section. Please note that server and user names should be # in the upper case. # # Following parameters are valid for [SERVER] or [SERVER:USER] section: [BAM:james] # if you don't use password leave value empty #password=ghost # how many retries before error, default 10 retry_count=10 # timeout for request to complete timeout=5 # access mode to connection, default 0700 #access_mode=0700 # signature level, default 0 - no signatures #sig_level=0 # force bindery login, default no bindery=no # default print queue for user, default is none # print_queue=QE_BJ #[ANOTHERSERVER:PLAINUSER] # in this case user have an empty password #password= # Defaults for printer queues defined as [SERVER:QUEUE] # communication parameters taken from [SERVER:USER] section # see man ncprint(1) for queue parameters description # note: if any banner related option is specified, banner will be printed. [BAM:HP4000_Q] path_name=/nw #file_name=passwd banner_name=MY FIRST FREEBSD PRINT WITH NETWARE #job_desc=Printing from FreeBSD #lines=66 #rows=80 copies=1 tab_size=8 no_form_feed=yes #form_number=0 Here is what happens when I run /usr/local/etc/rc.d/nwfs.sh: localhost# /usr/local/etc/rc.d/nwfs.sh Mounting NetWare volumes: mount: sys: unknown special file or file system sys Done localhost# Here is what happens when I run mount_nwfs localhost# mount_nwfs usage: mount_nwfs [-Chv] -S server -U user [-connection options] -V volume [-M mode] [-c case] [-d mode] [-f mode] [-g gid] [-l locale] [-n os2] [-u uid] [-w scheme] node mount_nwfs [-options] /server:user/volume[/path] node localhost# mount_nwfs -Chv mount_nwfs: no default connection found: syserr = Bad file descriptor localhost# Note that I see no explanation of the [-Chv] portion of the command in the man page. So, what do I need to do to get this to work ? James Leone ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Images of FreeBSD
Kent Stewart wrote: Since most of the desktops on Linux are also available on FreeBSD, you can see what they look like. I can also confirm that KDE 3.1 installs very nicely in FreeBSD 5.1-Current. The trick is setting up your xconfiguration, setting up kdm so you will have a graphical login screen, and to add the .xsession and .xinitrc files to ~/. James Leone ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Possible errors in FreeBSD 5.1
Hendrik Hasenbein wrote: James Leone wrote: 2. While I am in KDE in FreeBSD, but not in KDE in Linux, if I click on the Floppy Device icon before the floppy is inserted, I will not be able to access a subsequently inserted floppy disk. When I do, I get an error that says: the device is not configured. Why do you even want to access a floppy before you insert it into the drive? No system should be able to do that. Kde tries to mount the floppy on clicking on the item. That is going to fail, because without a floppy in the drive there is no device in the device filesystem. Can't think why that should work with linux. 3. When I went to /boot/kernel and typed kldload pcm, it appeared to load up fine, no warning messages, etc. However, when I boot into KDE, KDE will not have any sound. However, if I compile PCM into the kernel and reboot, KDE's sound works just fine. Should work both ways. Perhaps the kde sound deamon is run by an script in /usr/local/etc/rc.d before your module is probed in. 4. The Real Player port does not use FreeBSD's sound system, even though sound is working in KDE. I have found a few proposed solutions, including one from the Real One Player forum, but none work. The error message says device not found. Realplayer is working fine. Perhaps your sound device is already taken and blocked by kde. 5. When configured with the tools available to sysinstall, and additionally when X -configure is run, the XF86Config file does not include the modes lines that I get in SuSE Linux 8.2. I ended up copying over and slightly modifying SuSE's XF86Config file for better screeen resolution. Modelines aren't needed any more. Just insert the parameters of your monitor and choose the desired resolution. Btw most screens show a sharper display if they aren't running at their stated max. Hendrik LIke I said, I am just providing information here. I really don't care if it gets resolved, but I did care enough to point out these REAL problems. James Leone ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Possible errors in FreeBSD 5.1
Hendrik Hasenbein wrote: James Leone wrote: LIke I said, I am just providing information here. I really don't care if it gets resolved, but I did care enough to point out these REAL problems. If you aren't interested in solutions set the reply-to to [EMAIL PROTECTED] for the problem reports. Still can't see REAL problems here. Can't see a REAL reason for your messages. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: startx fails
daniel meg wrote: I am running FreeBSD 4.8 RELEASE. Video Card: nVidia RIVA128 I run the xf86config trillion of times..read through the manual over and over..but just can't get it to works...the attached file is the XFree86.log file and mine XF86Config file..hope BSD hackers will help.. I took a look at the log, and there was a warning in it: WW) `fonts.dir' not found (or not valid) in /usr/X11R6/lib/X11/fonts/local/. Entry deleted from font path. (Run 'mkfontdir' on /usr/X11R6/lib/X11/fonts/local/). Have you tried to reinstall your fonts ? James Leone ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VT82C686/A/B AC'97 Audio Codec
Monah Baki wrote: Have you tried recompiling the kernel with device pcm This is what worked for me in FreeBSD 5.1-Current, kldload pcm from /boot/kernel did not. James Leone ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mplayer one last time :(
Monah Baki wrote: Hi, sorry for being ignorant, but I don't want to switch to another OS if freebsd can do the job. Based on the advices I installed the following on Freebsd 5.1: multimedia/openquicktime multimedia/mplayer www/mplayer-plugin www/mozilla (1.4) www/mplayer-fonts Still can't get mplayer working. I have all the required ports installed based on what the freebsd.com/ports website said, I can't think of anything else, I'm completely lost here. You are not alone., but my struggles have been in Linux... James Leone ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Possible errors in FreeBSD 5.1
I have come accross a few possible bugs or errors while using FreeBSD 5.1-Current. I wrote them down and thought I would at least pass on the information per chance it would help someone, etc. I know that some of the errors could just be me, etc. FreeBSD 5.1-Current Possible bugs: 1. When I installed FreeBSD on my machine at work, I had 10 GB of 80 GB available for it on a partitioned hard disk. I set up FreeBSD to only have two slices in the partition, one for swap, which was 300 MB, and the remaining 9700 MB was allocated for the / slice. However, when I was in FreeBSD's Fdisk utility, I could not set up a slice larger than 9499 MB, or else the creation of the slices would fail, and so would the installation. 2. While I am in KDE in FreeBSD, but not in KDE in Linux, if I click on the Floppy Device icon before the floppy is inserted, I will not be able to access a subsequently inserted floppy disk. When I do, I get an error that says: the device is not configured. 3. When I went to /boot/kernel and typed kldload pcm, it appeared to load up fine, no warning messages, etc. However, when I boot into KDE, KDE will not have any sound. However, if I compile PCM into the kernel and reboot, KDE's sound works just fine. 4. The Real Player port does not use FreeBSD's sound system, even though sound is working in KDE. I have found a few proposed solutions, including one from the Real One Player forum, but none work. The error message says device not found. 5. When configured with the tools available to sysinstall, and additionally when X -configure is run, the XF86Config file does not include the modes lines that I get in SuSE Linux 8.2. I ended up copying over and slightly modifying SuSE's XF86Config file for better screeen resolution. 6. Ymessenger, as installed through the ports, seems to be broken. It will install, but when its run, it says: /usr/libexec/ld-elf.so.1 /usr/local/lib/libglib12.so.3: Unidentified symbol getpwuid_r 7. Konqueror file permission weirdness I can access all of my FAT32 formatted partitions or disks, but when I use Konqueror to enter the directories within the mount point by clicking on them, I get an error that reads: You do not have enough permissions to read file:/storage/documents However, if I merely right click and select open in new window, it opens without a problem, and no error is shown. I do not have this problem in SuSE Linux 8.2. James Leone ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.1 WD 80.0GB SE Drive Geometry
Jim wrote: Let me start by qualifying I am extremely new to FreeBSD (I have performed a whopping two installs thus far). I am looking to fire up a machine with a single western digital special edition 80GB IDE drive for simple storage and testing. The BIOS detects the correct geometry for the drive, and both Windows 2000 and Linux (RedHat 9) correctly detect the geometry and install on the drive (each OS installed independently to verify the drive and BIOS were working - this is not a multi-boot setup). FreeBSD version 5.1 however, pops up a message stating the geometry chosen by FreeBSD during installation is incorrect. If I hit G when assigning the slices and drop in the correct geometry (as reported by the BIOS), I can assign slices (defaults) and the installation runs through, but it will fail on the next boot (won't even get to the boot manager). If I select G when assigning slices, plug in the values, then force a write using the W option, I get a warning, then everything installs and fails on reboot. Note: This same machine will accept an installation and run beautifully using a different hard drive (anything I have other than a Western Digital 80GB Special Edition), and I have tried two of the 80GB special edition drives to ensure it is not a mechanical problem with just one of the drives. Both of the special edition drives performed identically (which is to say not at all). Google is mute on the subject. Any help would be appreciated. Jim All I can say is that the same thing happened to me. James Leone ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Possible errors in FreeBSD 5.1
Jerry McAllister wrote: I have come accross a few possible bugs or errors while using FreeBSD 5.1-Current. I wrote them down and thought I would at least pass on the information per chance it would help someone, etc. I know that some of the errors could just be me, etc. FreeBSD 5.1-Current Possible bugs: 1. When I installed FreeBSD on my machine at work, I had 10 GB of 80 GB available for it on a partitioned hard disk. I set up FreeBSD to only have two slices in the partition, one for swap, which was 300 MB, and the remaining 9700 MB was allocated for the / slice. However, when I was in FreeBSD's Fdisk utility, I could not set up a slice larger than 9499 MB, or else the creation of the slices would fail, and so would the installation. First of all, your terminology is backwards. The slice is the main unit which is then divided in to partitions for such as root and /usr or whatever. eg you have a 10GB FreeBSD slice which you want to divide in to a 9700 MB root partition and a 300 MB swap partition. Second, this all may be due to different ways of expressing the math of disk units. What actual size in blocks is your 10 GB slice and how big in blocks are your 300 MB and 9700 MG partitions? Also, one virtual cylinder will be eaten for the boot records. jerry I don't know the answer to that question. If there is a problem, I hope it will be fixed. James Leone ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]