Using multiply kernels with reserved GENERIC
I compile my own kernel: # make buildkernel KERNCONF=MYKERN make installkernel KERNCONF=MYKERN After this, the new kernel is into /boot/kernel , and old one is into /boot/kernel.old After first kernel rebuilding, kernel.old is GENERIC. But after second one it seems that I'm unable to boot GENERIC without compiling and installing it again. Is it possible to have GENERIC for system crash restoring purposes somewhere like /boot/kernel.generic ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Using multiply kernels with reserved GENERIC
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 14/03/2010 08:05:37, Антон Клесс wrote: I compile my own kernel: # make buildkernel KERNCONF=MYKERN make installkernel KERNCONF=MYKERN After this, the new kernel is into /boot/kernel , and old one is into /boot/kernel.old After first kernel rebuilding, kernel.old is GENERIC. But after second one it seems that I'm unable to boot GENERIC without compiling and installing it again. Is it possible to have GENERIC for system crash restoring purposes somewhere like /boot/kernel.generic ? Yes. Just mv /boot/kernel.old /boot/kernel.generic If you want to update your copy of the GENERIC kernel: # cd /usr/src # make buildkernel KERNCONF=GENERIC # make installkernel KERNCONF=GENERIC KODIR=/boot/kernel.generic Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkucoEEACgkQ8Mjk52CukIzmwACfeTkSfNc/s86EkYvBABCWGRa5 VQAAmQFH2QQUnVOA16FJGFuoSHsgJ5+l =O0/G -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to use cdrecord
On Sun, Mar 14, 2010 at 11:47:35AM +0800, Aiza wrote: Chris Hill wrote: On Sun, 14 Mar 2010, Aiza wrote: [snip] tried cdrecord -v speed=2 dev=acd0 blank=fast gives this error Open by devname not supported on this OS. What device am i to use? cdrecord wants to see your ATA burner as a SCSI device, so you'd use cdrecord dev=1,0,0 ... The numbers after dev= depend on where your burner is; find it using cdrecord -scanbus HTH. -- Chris Hill ch...@monochrome.org cdrecord -scanbus gives a error. Invalid argument. Camiocommand ioctl failed, can not open scsi driver Do you have that atapicam(4) kernel module loaded? If not load it. -- Insert your favourite quote here. Erik Trulsson ertr1...@student.uu.se ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to use cdrecord
On Sun, Mar 14, 2010 at 11:47:35AM +0800, Aiza wrote: Chris Hill wrote: On Sun, 14 Mar 2010, Aiza wrote: [snip] tried cdrecord -v speed=2 dev=acd0 blank=fast gives this error Open by devname not supported on this OS. What device am i to use? cdrecord wants to see your ATA burner as a SCSI device, so you'd use cdrecord dev=1,0,0 ... The numbers after dev= depend on where your burner is; find it using cdrecord -scanbus HTH. cdrecord -scanbus gives a error. Invalid argument. Camiocommand ioctl failed, can not open scsi driver You need SCSI emulation for your burner in your kernel. Specifically, you need to recompile your kernel with the following devices in its configuration file: device atapicam# emulate ATAPI devices as SCSI ditto via CAM # needs CAM to be present (scbus pass) # SCSI peripherals device scbus # SCSI bus (required for SCSI) device da # Direct Access (disks) device cd # CD device pass# Passthrough device (direct SCSI access) See the manual pages atapicam(4), scbus(4), cd(4) and pass(4). It could be that these devices are also available as modules, but I've always build a custom kernel, so I don't know about that. The manual pages don't say that they are available as modules, so I'm inclined to say they are not. After rebuilding the kernel, which you'll find documented in Chapter 8 of the Handbook, you also need to give your user-id write access to the right devices. I have done that by creating a group cdrom, to which I've added my user-id (with 'pw groupmod -m'). Then I've put the following lines in my /etc/devfs.conf: # Give members of group cdrom access to the CD/DVD-ROM and DVD+RW via the # SCSI interface own xpt0root:cdrom permxpt00660 own cd0 root:cdrom permcd0 0660 own cd1 root:cdrom permcd1 0660 linkcd1 cdrom linkcd1 dvd Since I've got both a burner and a regular DVD player in my machine, you see two cd devices but only one xpt device. Additionally, the following has been added to my standard ruleset in /etc/devfs.rules: [slackbox=10] add path 'pass*' mode 0660 group cdrom And in /etc/rc.conf the following is added; devfs_system_ruleset=slackbox I've put the pass device in devfs.rules because it will attach to every SCSI device that attaches to the system, _even if they are added after booting_ like e.g. USB disks used with the da(4) driver. Hope this helps. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgp4cC4eT6Q5D.pgp Description: PGP signature
Re: Compose key and xterm vs. UTF-8
On Sun, Mar 14, 2010 at 12:16:45AM +, Christian Weisgerber wrote: Short: -- Why do compose key sequences fail to work in a UTF-8 xterm? The port x11/rxvt-unicode is lighter on resources then xterm, and works fine with utf-8. (with LANG=en_US.UTF-8 and LC_ALL=en_US.UTF-8 set) Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpUG8w69Czzd.pgp Description: PGP signature
Re : building from source after freebsd-update
Please read the handbook section related to the FreeBSD update tool http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html freebsd-update is a binary update tool, so you haven't got anything to rebuild, except your custom kernel (if you are using one). --- En date de : Dim 14.3.10, johnea m...@johnea.net a écrit : De: johnea m...@johnea.net Objet: building from source after freebsd-update À: FreeBSD Questions freebsd-questions@freebsd.org Date: Dimanche 14 mars 2010, 3h37 Hello, I have been using freebsd-update to update several 7.1 systems. The default freebsd-update.conf contains: Components src world kernel Recently while trying to build sendmail to enable SASL I ran into errors: host# cd /usr/src/usr.sbin/sendmail host# make depend make: don't know how to make alias.c. Stop How can I build the source updated by freebsd-update? Thank You! johnea p.s. I have replaced sendmail with ssmtp and have the necessary SASL authentication working. However I have always maintained these servers via freebsd-update and I would like to learn the process of building the system from source. Thanks for any help! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to use cdrecord
Erik Trulsson wrote: On Sun, Mar 14, 2010 at 11:47:35AM +0800, Aiza wrote: Chris Hill wrote: On Sun, 14 Mar 2010, Aiza wrote: [snip] tried cdrecord -v speed=2 dev=acd0 blank=fast gives this error Open by devname not supported on this OS. What device am i to use? cdrecord wants to see your ATA burner as a SCSI device, so you'd use cdrecord dev=1,0,0 ... The numbers after dev= depend on where your burner is; find it using cdrecord -scanbus HTH. -- Chris Hill ch...@monochrome.org cdrecord -scanbus gives a error. Invalid argument. Camiocommand ioctl failed, can not open scsi driver Do you have that atapicam(4) kernel module loaded? If not load it. No I do not. how do i do this? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to use cdrecord
On Sun, 14 Mar 2010 20:48:22 +0800, Aiza aiz...@comclark.com wrote: No I do not. how do i do this? If you don't want to compile it into your kernel, load it manually: # kldload atapicam You can automate it using the appropriate line in /boot/loader.conf, I think it's atapicam_load=YES Then you get something like this: % camcontrol devlist SCANNER 2.02at scbus0 target 6 lun 0 (pass0) HL-DT-ST DVD-RAM GSA-H58N 1.01 at scbus2 target 0 lun 0 (cd0,pass1) The scanner is a real SCSI scanner, the DVD recorder is an ATAPI drive. You see it's device number is 2,0,0, and the device node is /dev/cd0. You need access to /dev/pass1, too. (If the scanner wouldn't be present, it would be /dev/pass0.) If you want to burn a data CD, use something like this: % cdrecord dev=2,0,0 speed=16 -v -eject -tao -data iso-file For a music CD: % cdrecord dev=2,0,0 speed=16 -v -eject -dao -audio track1 track2 ... If you want to combine the mkisofs step with the burning step (instead of first creating the ISO, then burnin it), you can do something like this: % mkisofs -r files | cdrecord dev=2,0,0 speed=16 -v -eject -tao -data - It works similar with DVDs, just you use growisofs from the port dvd+rw-tools here: % growisofs -dvd-compat -Z /dev/dvd=$1 The /dev/dvd is a symling that points to /dev/cd0 - again, the ATAPICAM cd driver is used instead of ATAPI's acd. To make this symlink, I have linkacd0cdrom linkcd0 dvd in /etc/devfs.conf. This makes refering to the example in man growisofs more easy. :-) If you don't have this symlink, you must use /dev/cd0 (or the correct device name for the SCSI drive) in the command. You can check this with camcontrol devlist where both numerical and device node are displayed. Additionally, you can do the same with growisofs as I have shown you with cdrecord - combine the building of the ISO with the burning: % growisofs -dvd-compat -Z /dev/dvd -r files This should give you a good summary of how to use these tools. You already have gotten useful advices on how to set the correct device permissions - this is important. Additionally, see man cdrecord on how to construct a simple config file so you don't have to put speed= and dev= whenever you want to use the program - it makes things more comfortable. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Compose key and xterm vs. UTF-8
On Sun, Mar 14, 2010 at 12:45:24PM +0100, Roland Smith wrote: On Sun, Mar 14, 2010 at 12:16:45AM +, Christian Weisgerber wrote: Short: -- Why do compose key sequences fail to work in a UTF-8 xterm? The port x11/rxvt-unicode is lighter on resources then xterm, and works fine with utf-8. (with LANG=en_US.UTF-8 and LC_ALL=en_US.UTF-8 set) That doesn't appear to answer his question. awai -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net pgpkGv4Pzen2O.pgp Description: PGP signature
Re: Compose key and xterm vs. UTF-8
Roland Smith: Why do compose key sequences fail to work in a UTF-8 xterm? The port x11/rxvt-unicode is lighter on resources then xterm, and works fine with utf-8. (with LANG=en_US.UTF-8 and LC_ALL=en_US.UTF-8 set) You didn't bother to read and understand my question, did you? urxvt shows the same poor composing behavior for UTF-8 as xterm does. -- Christian naddy Weisgerber na...@mips.inka.de ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to use cdrecord
On Sun, 14 Mar 2010 20:48:22 +0800 Aiza Aiza aiz...@comclark.com articulated: Erik Trulsson wrote: On Sun, Mar 14, 2010 at 11:47:35AM +0800, Aiza wrote: Chris Hill wrote: On Sun, 14 Mar 2010, Aiza wrote: tried cdrecord -v speed=2 dev=acd0 blank=fast gives this error Open by devname not supported on this OS. What device am i to use? cdrecord wants to see your ATA burner as a SCSI device, so you'd use cdrecord dev=1,0,0 ... The numbers after dev= depend on where your burner is; find it using cdrecord -scanbus cdrecord -scanbus gives a error. Invalid argument. Camiocommand ioctl failed, can not open scsi driver Do you have that atapicam(4) kernel module loaded? If not load it. No I do not. how do i do this? Add this to your /usr/src/sys/i386/conf/GENERIC file: (or what ever you have named it) device atapicam You then have to rebuild your kernel. You would probably be best served by reading up on how to update FreeBSD. Starting at this URL would be a good idea: http://www.freebsd.org/doc/handbook/makeworld.html Post back here if you need further information. -- Jerry ges...@yahoo.com |=== |=== |=== |=== | All the evidence concerning the universe has not yet been collected, so there's still hope. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Compose key and xterm vs. UTF-8
On Sun, Mar 14, 2010 at 01:43:27PM +0100, Christian Weisgerber wrote: Roland Smith: Why do compose key sequences fail to work in a UTF-8 xterm? The port x11/rxvt-unicode is lighter on resources then xterm, and works fine with utf-8. (with LANG=en_US.UTF-8 and LC_ALL=en_US.UTF-8 set) You didn't bother to read and understand my question, did you? urxvt shows the same poor composing behavior for UTF-8 as xterm does. Make sure that the key you designated as the multi-key really does return that keysym! My ~/.Xmodmap contains: ! Use the right windows key as the Multi-key. keycode 0xffec = Multi_key Multi_key ! Use the left windows key as the Meta toets keycode 0xffe7 = Meta_L Use xev(1) to check what symbols the different keys really generate. Then edit ~/.Xmodmap to suite your taste and call 'xmodmap ~/.Xmodmap' to apply the changes. Make your X startup repeat that to make the changes permanent. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpvpCcAAPhdH.pgp Description: PGP signature
Re: how to use cdrecord
On 03/14/10 08:17, Jerry wrote: snip Add this to your /usr/src/sys/i386/conf/GENERIC file: (or what ever you have named it) device atapicam You then have to rebuild your kernel. You would probably be best served by reading up on how to update FreeBSD. Starting at this URL would be a good idea: http://www.freebsd.org/doc/handbook/makeworld.html Post back here if you need further information. Rebuilding the kernel is not always an option, and it seems to me the OP and I are at the same point of knowledge about FreeBSD (not far enough along to be comfortable building/rebuilding the kernel). kldload atapicam works just fine for me (as I'm sure it does the OP), it even gives me info about my internal ZIP 100 drive. Problem solved, at least for me, no kernel rebuild necessary. -- Yours In Christ, PIT Emails are not formal business letters, whatever businesses may want. Original content copyright under the OWL http://owl.apotheon.org Please do not CC me. If I'm posting to a list it is because I am subscribed. signature.asc Description: OpenPGP digital signature
tunefs -L issue
I'm seeing this in my dmesg: GEOM: ad0s1: geometry does not match label (255h,63s != 16h,63s). I'm guessing I screwed up tunefs -L, but it sure looked straightforward. Anyway, my /dev/ufs is empty, and I kind of thought there should be stuff in it. I called tunefs -L from single-user mode, so usr, var, and tmp should have been unmounted as per instructions. If I start playing with the geomerty, am I going to wipe my system inadvertently? Also, I kind of think the ufsid is really what I'm looking for, and /dev/ufsid is empty too! Isn't this the class of things that should just work? I mean, the disk is pretty fundamental. I swap disks in and out alot, and I've got one of those motherboards that likes to reorder them, making booting reliably under 8-RELEASE a real pain in the neck... Best, Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: tunefs -L issue
On Sun, Mar 14, 2010 at 09:31:50AM -0700, Steve Franks wrote: I'm seeing this in my dmesg: GEOM: ad0s1: geometry does not match label (255h,63s != 16h,63s). AFAICT, you can ignore this. There have been previous discussions of this on the mailing list. I'm guessing I screwed up tunefs -L, but it sure looked straightforward. Anyway, my /dev/ufs is empty, and I kind of thought The labels in /dev/ufsid are removed if the partition in question is mounted. If you look in your logs you'll see messages like: 'GEOM_LABEL: Label ufsid/482b3a7c20b36d8c removed.' If I start playing with the geomerty, am I going to wipe my system inadvertently? Possibly. My advice would be not to go there. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpXKHhHjs837.pgp Description: PGP signature
Wow! ixsystems.....
Folks,
Late last night i finally surfed into the ixsystems pages.
WHile I haven't had a chance to check out the
price/performance ration and compare it to other sites [[or
maybe I'll do yet another roll-my-own]], I did happen on the
PCBSD link. It really does look like FreeBSD people who do
*not* wish to invest 101% of their lives getting
thing-to-work on the most stable OS ever. My one question
is: does at least everything that works under Ubuntu work
under PC BSD? I mean, things like setting my text fonts to
international? and being able to stream what streams {say,
FRONTLINE or NOVA} that PBS has.
Can i drop in a CD or DVD that I got from my pvblic library
and have it play without mucking around creating mount-points
like /media/dvd/0 and /media/cd/0? This is the latest thing
to break with my 7.3RC.2. The sound-juicer doesn't recognize
my music CD whereas my Ubuntu does. In other words, is
PCBSD closer to the Just-Works{TM} side of things?
tia, y'all!
gary
--
Gary Kline kl...@thought.org http://www.thought.org Public Service Unix
http://jottings.thought.org http://transfinite.thought.org
The 7.79a release of Jottings: http://jottings.thought.org/index.php
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Re : building from source after freebsd-update
On 2010-03-14 05:39, Alexandre L. wrote: Please read the handbook section related to the FreeBSD update tool http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html freebsd-update is a binary update tool, so you haven't got anything to rebuild, except your custom kernel (if you are using one). That handbook section is where I read: The default is to update the source code, the entire base system, and the kernel. And in fact much of the /usr/src/ does contain source code. /usr/src/sys/ subdirectories seem populated, and some directories under /usr/src/usr.bin/ and /usr/src/usr.sbin/ contain source, while others only contain the Makefile. /usr/src/usr.sbin/sendmail/ contains only the Makefile. Which lead to the make depend error I experienced. It seems like I could build the kernel, and parts of the non-kernel base, but not other parts. After RTFMing, scroogling for days, and going through UPDATINGs and READMEs I'm still not clear on how to mix freebsd-update and building all or parts of the base source. I'm interested in being able to build system apps in the base, custom kernel modules, and eventually the entire kernel. freebsd-update is _extremely_ painless for tracking the security patches. It would be nice to be able to mix this with a certain amount of building source. Any insight is greatly appreciated... johnea ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
I'd like you to join me on Swom...
Hi I'd like to add you to my professional network on Swom. You can use Swom to connect with new contacts and promote your existing businesses. Swom even has an affiliate program that pays you. - N'GUESSAN p.s. Here is the link:br http://swom.com/r/51774-nguessan--koffi-ezai -- This e-mail was sent on behalf of N'guessan Koffi Ezai by Swom. If you do not wish to receive future commercial mailings from Swom, please use the link below. Swom's registered offices are located at The Courtyard, Goldsmith Way, Eliot Business Park, Nuneaton, CV10 7RJ http://swom.com/blacklists/new?uuid=49d0c3ee73b9f11fc5eb0523f7666938cb72b61c___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
jpeg2swf segfaults
Ever since I updated from jpeg-7 to jpeg-8 and recompiled swftools to link against it (FreeBSD-8.0-RELEASE-p2), jpeg2swf segfaults with jpeg2swf -q 100 -o test.swf *.jpg (at most 12 jpegs). Running gdb jpeg2swf jpeg2swf.core reveals the following: GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd...(no debugging symbols found)... Core was generated by `jpeg2swf'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/local/lib/libmp3lame.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libmp3lame.so.0 Reading symbols from /usr/local/lib/libglut.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libglut.so.3 Reading symbols from /usr/local/lib/libGLU.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libGLU.so.1 Reading symbols from /usr/local/lib/libGL.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libGL.so.1 Reading symbols from /usr/local/lib/libungif.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libungif.so.5 Reading symbols from /usr/local/lib/libjpeg.so.11...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libjpeg.so.11 Reading symbols from /lib/libz.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libz.so.5 Reading symbols from /lib/libm.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libm.so.5 Reading symbols from /usr/local/lib/libfontconfig.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libfontconfig.so.1 Reading symbols from /usr/local/lib/libfreetype.so.9...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libfreetype.so.9 Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /usr/local/lib/libXmu.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libXmu.so.6 Reading symbols from /usr/local/lib/libXt.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libXt.so.6 Reading symbols from /usr/local/lib/libX11.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libX11.so.6 Reading symbols from /usr/local/lib/libSM.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libSM.so.6 Reading symbols from /usr/local/lib/libICE.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libICE.so.6 Reading symbols from /usr/local/lib/libXi.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libXi.so.6 Reading symbols from /usr/lib/libstdc++.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libstdc++.so.6 Reading symbols from /lib/libgcc_s.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/libgcc_s.so.1 Reading symbols from /usr/local/lib/libXext.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libXext.so.6 Reading symbols from /usr/local/lib/libXxf86vm.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libXxf86vm.so.1 Reading symbols from /usr/local/lib/libXdamage.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libXdamage.so.1 Reading symbols from /usr/local/lib/libXfixes.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libXfixes.so.3 Reading symbols from /usr/local/lib/libX11-xcb.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libX11-xcb.so.1 Reading symbols from /usr/local/lib/libxcb-glx.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libxcb-glx.so.0 Reading symbols from /usr/local/lib/libxcb.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libxcb.so.2 Reading symbols from /usr/local/lib/libdrm.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libdrm.so.2 Reading symbols from /lib/libthr.so.3...(no debugging symbols found)...done. Loaded symbols for /lib/libthr.so.3 Reading symbols from /usr/local/lib/libXau.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libXau.so.6 Reading symbols from /usr/local/lib/libXdmcp.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libXdmcp.so.6 Reading symbols from /usr/local/lib/libpthread-stubs.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libpthread-stubs.so.0 Reading symbols from /usr/lib/librpcsvc.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/lib/librpcsvc.so.5
Re: how to use cdrecord
Polytropon wrote: On Sun, 14 Mar 2010 20:48:22 +0800, Aiza aiz...@comclark.com wrote: No I do not. how do i do this? If you don't want to compile it into your kernel, load it manually: # kldload atapicam You can automate it using the appropriate line in /boot/loader.conf, I think it's atapicam_load=YES Then you get something like this: % camcontrol devlist SCANNER 2.02at scbus0 target 6 lun 0 (pass0) HL-DT-ST DVD-RAM GSA-H58N 1.01 at scbus2 target 0 lun 0 (cd0,pass1) The scanner is a real SCSI scanner, the DVD recorder is an ATAPI drive. You see it's device number is 2,0,0, and the device node is /dev/cd0. You need access to /dev/pass1, too. (If the scanner wouldn't be present, it would be /dev/pass0.) If you want to burn a data CD, use something like this: % cdrecord dev=2,0,0 speed=16 -v -eject -tao -data iso-file For a music CD: % cdrecord dev=2,0,0 speed=16 -v -eject -dao -audio track1 track2 ... If you want to combine the mkisofs step with the burning step (instead of first creating the ISO, then burnin it), you can do something like this: % mkisofs -r files | cdrecord dev=2,0,0 speed=16 -v -eject -tao -data - It works similar with DVDs, just you use growisofs from the port dvd+rw-tools here: % growisofs -dvd-compat -Z /dev/dvd=$1 The /dev/dvd is a symling that points to /dev/cd0 - again, the ATAPICAM cd driver is used instead of ATAPI's acd. To make this symlink, I have linkacd0cdrom linkcd0 dvd in /etc/devfs.conf. This makes refering to the example in man growisofs more easy. :-) If you don't have this symlink, you must use /dev/cd0 (or the correct device name for the SCSI drive) in the command. You can check this with camcontrol devlist where both numerical and device node are displayed. Additionally, you can do the same with growisofs as I have shown you with cdrecord - combine the building of the ISO with the burning: % growisofs -dvd-compat -Z /dev/dvd -r files This should give you a good summary of how to use these tools. You already have gotten useful advices on how to set the correct device permissions - this is important. Additionally, see man cdrecord on how to construct a simple config file so you don't have to put speed= and dev= whenever you want to use the program - it makes things more comfortable. :-) Aloha... Poly is right. I use in #/boot/bootloader the line: atapicam_load=YES # For DVD/CD Burner to work. ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 7.2 - 8.0 - 9* + email: n...@hdk5.net All that's really worth doing is what we do for others.- Lewis Carrol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to use cdrecord
An addition: On Sat, 13 Mar 2010 21:46:17 -0600, Programmer In Training p...@joseph-a-nagy-jr.us wrote: [r...@heaven]dmesg -a | grep acd acd0: DMA limited to UDMA33, controller found non-ATA66 cable acd0: DVDR HP DVD Writer 1040r/MH21 at ata1-master UDMA33 Thoughts? You're using a 40-pin ATA cable. Replace it with an 80-pin (every 2nd wire is shield, still only 40 pins on the connector) cable which is finer. This way the drive can be accessed faster than UDMA33. Looks like this: % dmesg | grep acd acd0: DVDR HL-DT-STDVD-RAM GSA-H58N/1.01 at ata1-master UDMA66 -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: jpeg2swf segfaults
Programmer In Training p...@joseph-a-nagy-jr.us writes: Ever since I updated from jpeg-7 to jpeg-8 and recompiled swftools to link against it (FreeBSD-8.0-RELEASE-p2), jpeg2swf segfaults with jpeg2swf -q 100 -o test.swf *.jpg (at most 12 jpegs). Doesn't crash for me. My guess is that you failed to update some other library that also links to jpeg. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Compose key and xterm vs. UTF-8
Nothing of susbtance here ... in message 20100314114524.gb25...@slackbox.erewhon.net, wrote Roland Smith thusly... On Sun, Mar 14, 2010 at 12:16:45AM +, Christian Weisgerber wrote: Short: -- Why do compose key sequences fail to work in a UTF-8 xterm? The port x11/rxvt-unicode is lighter on resources then xterm, and works fine with utf-8. (with LANG=en_US.UTF-8 and LC_ALL=en_US.UTF-8 set) I tried to open a genunine xterm window but a kterm-like window was opened. Tried it again; got another non-xterm window. The experience was rather annoying. After waking up I realized what had happened, and life went on as it was before. - parv -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: jpeg2swf segfaults
On 03/14/10 19:19, Lowell Gilbert wrote: Programmer In Training p...@joseph-a-nagy-jr.us writes: Ever since I updated from jpeg-7 to jpeg-8 and recompiled swftools to link against it (FreeBSD-8.0-RELEASE-p2), jpeg2swf segfaults with jpeg2swf -q 100 -o test.swf *.jpg (at most 12 jpegs). Doesn't crash for me. My guess is that you failed to update some other library that also links to jpeg. Possibly. I've been tracking this problem (with other apps) forever. -- Yours In Christ, PIT Emails are not formal business letters, whatever businesses may want. Original content copyright under the OWL http://owl.apotheon.org Please do not CC me. If I'm posting to a list it is because I am subscribed. signature.asc Description: OpenPGP digital signature
What is the path of knowledge from Novice to committer, In FreeBSD?
Respected Sir, *I am MCA(Master Of Computer Application) Student from India,Asia *and much intrested about UNIX or UNIX-like OS. As per my knowledge, in FreeBSD; there are *Volunteers(For Questioning) -- Contributers -- Committers* * 1] To be VOLUNTEER 2] After That; To Be Contributer 3] After That; To Be a Committer. * So, please guide me sir, about the above path (iff, it is correct) i.e. how could i cover above path? I mean to say, how could I develop my Knowlwdge in FreeBSD to follow above path. Please, guide me with any thing you think better for me(books,web links,any thing). I've average knowledge of UNIX. And, right now; I am studying FreeBSD on Vmware Workstation. -- Thanks And Regards, Vishal Kashyap. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
