Re: difference between cvsup and csup?
On 12/12/2011 7:39 πμ, Robert Huff wrote: Michael Powell writes: Csup is a rewrite of cvsup in the C language, and as such can be included as part of the base operating system. It is only linked against a few system libraries. This also means it can be built using the same tools and system compiler whenever the system itself is updated. Csup is faster, built-in, and has no third party dependencies. Theoretically it should have less potential for problems. Cvsup is a third party port, which itself depends on other third party ports. I believe there are a couple of obscure functionalities that cvsup has that csup does not. If you're asking this question, you (probably) don't have to worry about them. For the general user, csup is a drop-in replacement. My expereince - as a general user - supports this. Robert Huff It used to be (some versions ago) that csup only handled checkout mode and not CVS mode (that is, a mode of operation that allows you to mirror a complete CVS repository which in effect allows you to checkout and commit locally to your copy). This was for me the only reason to keep cvsup around. But csup has caught up with this functionality eliminating the need to install and use cvsup, esp. since csup is part of the base system. ___ 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: 9.0 install and journaling
On 10/12/2011 5:19 μμ, Warren Block wrote: On Sat, 10 Dec 2011, R Skinner wrote: So I went to the handbook. I'm still a little confused though: can one still setup the usr and var (and so forth)? It said you possibly could, but it escaped me as to how. Use the bsdinstall partition editor to manually create the partitions. I documented how to create an old-fashioned MBR layout with bsdinstall on the forums a while back: http://forums.freebsd.org/showpost.php?p=149210postcount=13 The process would be similar for GPT, which is really the way to go now. As Warren says, you can still create /usr and /var and all the other legacy partitions if you so wish - and you may even use the full journaling (gjournal) on them. But the default for bsdinstall is to use gpart, install everything on a big / and create UFS2 partitions with the new soft-updates journaling system (on by default). Compared to gjournal, soft-updates journaling only journals metadata and not everything like gjournal does. This will definitely make it faster although probably less safe than gjournal. It should be good for most purposes though and needs no additional steps after install (unlike gjournal). Since it's the default, the decision to go for one big / seems ok after all. I believe this is more or less what Linux is doing with Ext3/Ext4 filesystems (metadata journaling). ___ 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: 9.0 install and journaling
On 10/12/2011 11:41 μμ, Da Rock wrote: On 12/11/11 02:09, Manolis Kiagias wrote: On 10/12/2011 5:19 μμ, Warren Block wrote: On Sat, 10 Dec 2011, R Skinner wrote: So I went to the handbook. I'm still a little confused though: can one still setup the usr and var (and so forth)? It said you possibly could, but it escaped me as to how. Use the bsdinstall partition editor to manually create the partitions. I documented how to create an old-fashioned MBR layout with bsdinstall on the forums a while back: http://forums.freebsd.org/showpost.php?p=149210postcount=13 The process would be similar for GPT, which is really the way to go now. As Warren says, you can still create /usr and /var and all the other legacy partitions if you so wish - and you may even use the full journaling (gjournal) on them. But the default for bsdinstall is to use gpart, install everything on a big / and create UFS2 partitions with the new soft-updates journaling system (on by default). Compared to gjournal, soft-updates journaling only journals metadata and not everything like gjournal does. This will definitely make it faster although probably less safe than gjournal. It should be good for most purposes though and needs no additional steps after install (unlike gjournal). Since it's the default, the decision to go for one big / seems ok after all. I believe this is more or less what Linux is doing with Ext3/Ext4 filesystems (metadata journaling). GPT is cool - no problems there. The main thing I want to know is if I need to run fsck every time the system dies unexpectedly (which is a higher occurrence on a laptop)? GJournal helps in that it takes care of that. The growing size of drives is another concern given the time it takes to check a 500G disk (my smallest atm), although this is way down on the list for the moment. It does the fsck automatically and it seems to be fast. As with other metadata journaled filesystems you will probably have to do a full check occasionally. Can't you give you any times atm, I need to dump /repartition/restore some of my systems to use su+j. Only tested on virtual machines. As for one big / partition- linux may be using it: and its their biggest failing! I've had a system lockup due to lack of space. Never a problem with bsd as logs will only fill up var, a user won't break it with filling up usr, etc. And root always stays protected! Its saved my life a number of times... I can quickly fill TB's of data in no time, and if something goes bang the logs can be a silent killer too. My 2c's anyway... I am used to the separate partitions too, although I realize a single big / would be suitable for more than a few systems. It's nice we have a choice here. ___ 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: changing baud rate without recompiling
On 12/11/2011 1:02 μμ, saeedeh motlagh wrote: thanks for your reply it's good but includes recompiling again. i don't want to recompile in any way. is there any other solution for doing that? i don't think so:(. are you sure recompiling is the only way to change the baud rate? thanks for your attention Like you, everything else I tried simply did not work. If you do find something that works I'd be pleased to hear it. ___ 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: changing baud rate without recompiling
On 9/11/2011 11:11 πμ, saeedeh motlagh wrote: i know adding the COM_CONSOLE_SPEED=115200 to make.conf and recompile it, change the baud rate but i want to know if there is a way to change it without recompiling. please let me know if there is any way to do that. my FreeBSD is 8.0 thanks. I am using a serial console at 115200 bps. Like you, I've added comconsole_speed=115200 to /boot/loader.conf and nothing happened. After booting, the serial terminal works at 115200 - but that's because of the /etc/ttys entry (which of course is not used until the end of booting). For the actual console to work at this speed so you can see the boot messages, it seems the only way is to recompile and reinstall the boot blocks. This takes very little time however: # cd /usr/src/sys/boot # make clean # make BOOT_COMCONSOLE_SPEED=115200 # make install No need to recompile the kernel or any other part of the base system. ___ 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: X on Xterminals but not on console
On 6/10/2011 6:24 μμ, n dhert wrote: Hi, In your labserver, do you have a graphical login window at your labserver or not ? I don't want a graphical login, since I can't get anymore to the login prompt via Ctrl Alt F1 No graphical login. My lab server stops at the console login prompt. In KDM, the config directory is /usr/local/share/config/kdm for kdm window manager, there is no Xservers file, and I can't see any file .. there are Xaccess, Xwilling, Xstartup, Xreset, Xsession files and a large kdmrc file. There are no man pages for kdm, kdm-bin, Xaccess, etc... I tried setting ServerCmd= instead of ServerCmd=/usr/local/bin/X -br in the kdmrc file ... Now I only have /usr/local/bin/kdm-bin running, not /usr/local/bin/X Don't really know how KDM handles this. You could however - as a last resort - disable KDM and use xdm as your login manager. It is a bit rough (see login screens here http://www.flickr.com/photos/sonic2000gr/5033230929/in/set-72157625053818002) but it can start up any GUI using a simple .xsession file (xdm is not installed along with X but it is a very small port, x11/xdm). Am I right to believe the primary role of a local X server (local= on labserver) is to have a graphical environment on that labserver machine ? Yes, absolutely. There is no need to run a GUI on the lab server. It's a waste of CPU cycles and memory. ___ 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: building a port with very long list of build options
On 04/24/2011 11:26 AM, Carl wrote: On 2011-04-22 4:13 AM, Manolis Kiagias wrote: On 04/22/2011 10:33 AM, Manolis Kiagias wrote: On 04/22/2011 10:08 AM, Carl wrote: This form will override the Makefile present in the current directory and will use the specified make file with name your_own_make_file_name . make -f your_own_make_file_name Yes, I did see that, but I interpreted that to mean my make file *replaces* the original, in which case I would need to populate my make file not only with the list of build options I want but also a copy of everything in the original make file. If I'm correct, that doesn't seem to me to be a good idea from a maintenance perspective. I was hoping for something like the -f option that somehow inserted rather than replaced. Carl / K0802647 Assuming you have already selected some options during make config, you could try adding your own to the file /var/db/ports/portname/options ___ A probably more elegant way is to use the ports-mgmt/portconf port. This allows per port settings to be applied, which are honored by make, portupgrade and the other tools. Just install and use /usr/local/etc/ports.conf to add your options: Here is the sample supplied with the portconf: editors/openoffice.org-2: WITH_CCACHE|LOCALIZED_LANG=it print/ghostscript-* print/lpr-wrapper: A4 sysutils/fusefs-kmod*: !KERNCONF | !NOPORTDOCS www/firefox-i18n: WITHOUT_SWITCHER | FIREFOX_I18N=fr it x11/fakeport: CONFIGURE_ARGS=--with-modules=aaa bbb ccc ports-mgmt/portconf certainly does look to be a very appealing solution in general, but am I wrong in thinking that it provides me with no way to address my original problem? How do I use it when I've got an exceptionally long list of options for a particular port? You list all the options on the relevant ports.conf line, separated by '|' as shown in the example. I don't think there is any practical limit to this though admittedly I've only used it for the occasional option. As for manually customizing /var/db/ports/portname/options, the port builds in question are done in a clean chroot using a batch process, so make config doesn't happen and /var/db/ports/portname/options never exists. Carl / K0802647 You could create it manually from scratch and list all your options in there. It is just simpler if the file already exists and just needs some more entries. ___ 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: building a port with very long list of build options
On 04/22/2011 10:08 AM, Carl wrote: This form will override the Makefile present in the current directory and will use the specified make file with name your_own_make_file_name . make -f your_own_make_file_name Yes, I did see that, but I interpreted that to mean my make file *replaces* the original, in which case I would need to populate my make file not only with the list of build options I want but also a copy of everything in the original make file. If I'm correct, that doesn't seem to me to be a good idea from a maintenance perspective. I was hoping for something like the -f option that somehow inserted rather than replaced. Carl / K0802647 Assuming you have already selected some options during make config, you could try adding your own to the file /var/db/ports/portname/options ___ 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: building a port with very long list of build options
On 04/22/2011 10:33 AM, Manolis Kiagias wrote: On 04/22/2011 10:08 AM, Carl wrote: This form will override the Makefile present in the current directory and will use the specified make file with name your_own_make_file_name . make -f your_own_make_file_name Yes, I did see that, but I interpreted that to mean my make file *replaces* the original, in which case I would need to populate my make file not only with the list of build options I want but also a copy of everything in the original make file. If I'm correct, that doesn't seem to me to be a good idea from a maintenance perspective. I was hoping for something like the -f option that somehow inserted rather than replaced. Carl / K0802647 Assuming you have already selected some options during make config, you could try adding your own to the file /var/db/ports/portname/options ___ A probably more elegant way is to use the ports-mgmt/portconf port. This allows per port settings to be applied, which are honored by make, portupgrade and the other tools. Just install and use /usr/local/etc/ports.conf to add your options: Here is the sample supplied with the portconf: editors/openoffice.org-2: WITH_CCACHE|LOCALIZED_LANG=it print/ghostscript-* print/lpr-wrapper: A4 sysutils/fusefs-kmod*: !KERNCONF | !NOPORTDOCS www/firefox-i18n: WITHOUT_SWITCHER | FIREFOX_I18N=fr it x11/fakeport: CONFIGURE_ARGS=--with-modules=aaa bbb ccc ___ 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: pkg_add problem
On 04/19/2011 11:35 AM, H.Erkin ATAK wrote: I am running freebsd 8.2 on virtualbox on an ubuntu machine. I am running gnome and have network access no problem. But I can not add any packages via pkg_add. It gives can not fetch ftp address. I tried different mirrors but it did not work. Please help me. Try setting the virtual network card in vbox to bridged mode. AFAIR it defaults to NAT. ___ 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 customize login?
On 04/16/2011 09:06 AM, Alexander Lardner wrote: Hello list, I have set a banner welcoming anybody on the console. I still see the FreeBSD/i386 (Amnesiac) (ttyvX) message. How can I stop this from displaying? I'd like the banner to be the only thing displayed. Thanks to anybody helping!___ This is controlled by the im parameter in /etc/gettytab: default:\ :cb:ce:ck:lc:fd#1000:im=\r\n%s/%m (%h) (%t)\r\n\r\n:sp#1200:\ :if=/etc/issue: I guess you can remove it altogether. Have a look at man gettytab ___ 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
ANNOUNCING: FreeBSD 8.2-RELEASE Custom XFCE builds (32/64bits) released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey all, I have just completed an 8.2-RELEASE based build of the 'Custom releases' project hosted here: http://freebsd-custom.wikidot.com Both 32 and 64 bits are available for download: http://freebsd-custom.wikidot.com/downloads-page This release is based on the latest XFCE (4.8) desktop and includes a wide variety of desktop-related packages, like LibreOffice, abiword, gnumeric, firefox 4, gimp, inkscape, evince and so on. The base system is 8.2-RELEASE. A few other small window managers are included like windowmaker, fluxbox and icewm. The slim login manager is also included for people wishing to have a graphical logon screen. Make sure to read the README file before installation. This is available on the downloads page as well as on the root directory of the DVD. Also note that installing linux related packages during initial setup needs a few more steps. This is due to differences in sysinstall between 7.X and 8.X releases. A detailed explanation is provided in the README file. As always, please report any problems, success stories, comments and criticisms to mano...@freebsd.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2h2xIACgkQZ/MxGm4PtJQrBACdE9dEJfzgrEtu3iso6sVR48et ZYkAn1najLMrBljw/SOr5pU1pCy0Awus =gDeA -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: Kernel
On 01/07/2011 10:57 PM, Τάσκος Κωνσταντίνος wrote: Hello to all. I am a new user of FreeBSD-8.1 and I tried to compile a new kernel, according to the instructions given by the handbook. The command 'make buildkernel KERNCONF=MYKERNEL' failed with 'stop in /usr/obj/usr/src/sys/MYKERNEL error code 1'. I wanted to build my own kernel because i didn't have /dev/fuse (for ntfs write) and I had problems with module fuse.ko I am sending you my config file named MYKERNEL. Thanks in advance, Kostas. Looking at your MYKERNEL configuration file, just from the commit message at the top: # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.536 2010/12/31 00:21:41 yongari Exp $ it looks like you started editing a conf file that comes from FreeBSD CURRENT (what will become FreeBSD 9.0 in the future). Obviously this will not work in 8.1-RELEASE. You'll need to start by editing the GENERIC conf file that comes with 8.1-RELEASE. ___ 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: make buildworld errors
On 01/01/2011 9:54 ?.?., Mike wrote: Trying to buildworld but it keeps failing. I finally deleted /usr/src and recopyed from a cd then cvsup using standard-supfile. Tried limiting how much ram freebsd uses and only using one stick of ram. All attempts have failed at the same place. Would using the GENERIC kernel make a difference? You shouldn't have any trouble building world using a custom kernel. Try rm -rf /usr/obj/* before starting the build. This usually solves th ___ 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: XDM not showing login screen
On 31/12/2010 7:07 μ.μ., Alain G. Fabry wrote: Hi, I'm trying to get my XDMCP to work, but for some reason the XDM daemon doesn't reply to XDMCP requests. I see the XDMCP packet arriving on my xdm server harley# tcpdump port 177 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on bge0, link-type EN10MB (Ethernet), capture size 96 bytes 10:33:42.930750 IP 192.168.1.200.1291 255.255.255.255.xdmcp: UDP, length 7 All seems to be running ok harley# ps ax | grep xdm 76517 ?? Ss 0:00.41 /usr/local/bin/X :0 -auth /usr/local/lib/X11/xdm/authdir/authfiles/A:0-Z5AiCR (Xorg) 76519 ?? Is 0:00.06 xdm: :0 (xdm) 6040 2 S+ 0:00.00 grep xdm 76515 5 I+ 0:00.01 xdm -nodaemon -debug 1 The XDM daemon does not reply with a login screen. I've commented out the following in my xdm-config file ! DisplayManager.requestPort: 0 following in my Xaccess file * #any host can get a login window xdm and X are running, and I see the following in my xdm.log file, even though I don't get a login screen, the log file indicates incorrect login Add a LISTEN line at the end of your Xaccess file, with the specific IP of your server rather then relying on LISTEN * I've had the same when I was setting up my XDMCP lab. ___ 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: ANNOUNCE: Custom 64bit FreeBSD 8.1-RELEASE-p1 with XFCE packages released
On 05/10/2010 10:20 π.μ., Patrick Lamaiziere wrote: Le Sat, 02 Oct 2010 21:26:26 +0300, Manolis Kiagias son...@otenet.gr a écrit : Hello, This release is based on the latest XFCE desktop and includes a wide variety of desktop-related packages, like OpenOffice, abiword, gnumeric, firefox35, gimp, inkscape, evince and so on. The base system is 8.1-RELEASE. A few other small window managers are included like windowmaker and fluxbox. Note this release does not include editors/zim and x11-wm/icewm due to build problems. Which print system is used by the packages, cups or lpr? Regards. It is compiled with cups support. ___ 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
ANNOUNCE: Custom 64bit FreeBSD 8.1-RELEASE-p1 with XFCE packages released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey all, I have just completed an 8.1-RELEASE-p1 based build of the 'Custom releases' project hosted here: http://freebsd-custom.wikidot.com At the moment only the 64bit version is available, while a 32bit version is in the works and is expected later on this week. You may download the ISO file immediately using the downloads page: http://freebsd-custom.wikidot.com/downloads-page This release is based on the latest XFCE desktop and includes a wide variety of desktop-related packages, like OpenOffice, abiword, gnumeric, firefox35, gimp, inkscape, evince and so on. The base system is 8.1-RELEASE. A few other small window managers are included like windowmaker and fluxbox. Note this release does not include editors/zim and x11-wm/icewm due to build problems. Make sure to read the README file before installation. Also note that installing linux related packages during initial setup needs a few more steps. This is due to differences in sysinstall between 7.X and 8.X releases. A detailed explanation is provided in the README file. As always, please report any problems, success stories, comments and criticisms to mano...@freebsd.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkyneVIACgkQZ/MxGm4PtJRLyACeJ9xaFnMqmbWG1Bqg215/UZJG t3YAniiuU+JXFARW7Z94TOaA1Ujqbi6p =bs0M -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: Burning a the 8.1 release DVD iso
On 08/09/2010 9:44 μ.μ., Patrick Mahan wrote: I am wanting to burn the 8.1 DVD iso image onto a DVD-R disc. Previously, I did this on my Macbook Pro using OSX, but alas, my HD died on the Macbook so I am trying to do this on my Sony Vaio desktop system. Platform: Intel Pentium 4 @ 2.80 GHz w/512 MB memory HD: IBM DTLA-307075 (74 G) DVD writer: SONY DVD RW DW-U12A/2.0d OS: FreeBSD mycroft.adaranet.com 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:48:17 UTC 2009 r...@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 I have the following modules loaded: Id Refs Address Size Name 1 17 0xc040 b6dfe0 kernel 2 1 0xc396b000 26000 linux.ko 3 1 0xc3adc000 5e000 radeon.ko 4 1 0xc3b3d000 14000 drm.ko 5 1 0xc59dd000 4000 atapicam.ko The 'camcontrol devlist' command reports: SONY DVD RW DW-U12A 2.0d at scbus1 target 0 lun 0 (pass1,cd1) SAMSUNG CD-ROM SC-140C A101 at scbus1 target 1 lun 0 (pass0,cd0) I have built and installed dvd+rw-tools 7.1 along with cdrtools-2.01. If I try to use 'growisofs' : mycroft# growisofs -dvd-compat -Z /dev/cd1=FreeBSD-8.1-RELEASE-amd64-dvd1.iso :-( /dev/cd1: media is not recognized as recordable DVD: 0 So then I try to use 'cdrecord' and get the following: mycroft# cdrecord dev=1,0,0 speed=16 -v -eject -tao -data FreeBSD-8.1-RELEASE-amd64-dvd1.iso Cdrecord-Clone 2.01 (i386-unknown-freebsd8.0) Copyright (C) 1995-2004 Jörg Schilling TOC Type: 1 = CD-ROM scsidev: '1,0,0' scsibus: 1 target: 0 lun: 0 Using libscg version 'schily-0.8'. SCSI buffer size: 64512 atapi: 0 Device type : Removable CD-ROM Version : 0 Response Format: 2 Capabilities : Vendor_info : 'SONY ' Identifikation : 'DVD RW DW-U12A ' Revision : '2.0d' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Current: 0x Profile: 0x001B Profile: 0x001A Profile: 0x0014 Profile: 0x0013 Profile: 0x0011 Profile: 0x0010 Profile: 0x000A Profile: 0x0009 Profile: 0x0008 cdrecord: This version of cdrecord does not include DVD-R/DVD-RW support code. cdrecord: If you need DVD-R/DVD-RW support, ask the Author for cdrecord-ProDVD. cdrecord: Free test versions and free keys for personal use are at ftp://ftp.berlios.de/pub/cdrecord/ProDVD/ Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96R RAW/R96R Drive buf size : 8112896 = 7922 KB Drive DMA Speed: 5744 kB/s 32x CD 4x DVD FIFO size : 4194304 = 4096 KB Track 01: data 2199 MB Total size: 2525 MB (250:12.89) = 1125967 sectors Lout start: 2525 MB (250:14/67) = 1125967 sectors cdrecord: Input/output error. test unit ready: scsi sendcmd: retryable error CDB: 00 00 00 00 00 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 02 00 00 00 00 12 00 00 00 00 30 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x30 Qual 0x00 (incompatible medium installed) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 0.010s timeout 40s cdrecord: No disk / Wrong disk! However, I went to the ftp ftp.berlios.de and there I find a message that ProDVD has been released as of cdrtools-2.01.01a09. So obviously I am missing something. The handbook is not quite clear on this issue. And my googling has only located the issues regarding needing to load atapicam.ko module. Any help or educational experience is appreciated. Thanks, Patrick Mahan Adara Networks Nothing wrong with your growisofs line. That's what I use all the time to write DVD isos, including FreeBSD install media. It seems the drive is unable to recognize the media as a recordable one (look at the cdrecord message: incompatible medium found and growisofs: media not recognized as recordable dvd). Could you try with a different brand/type disk? Try both DVD+R and DVD-R. I've had this before: specific drives refusing to work with specific media. ___ 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: installing FreeBSD in VMWare-player
On 27/08/2010 10:24 π.μ., Matthias Apitz wrote: Is it possible that the data gets corrupt on an USB key after some time? I'm wondering why the system even is intact to be booted from... Will prepare the key again or just fill in the dumps I have... matthias I've heard of stories of data 'fading out' from USB flash drives after some period of complete inactivity. Haven't experienced this myself though. Otherwise your procedure looks fine and it shouldn't fail. ___ 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: installing FreeBSD in VMWare-player
On 27/08/2010 3:17 μ.μ., Matthias Apitz wrote: El día Friday, August 27, 2010 a las 12:06:09PM +0300, Manolis Kiagias escribió: On 27/08/2010 10:24 ??.??., Matthias Apitz wrote: Is it possible that the data gets corrupt on an USB key after some time? I'm wondering why the system even is intact to be booted from... Will prepare the key again or just fill in the dumps I have... matthias I've heard of stories of data 'fading out' from USB flash drives after some period of complete inactivity. Haven't experienced this myself though. Otherwise your procedure looks fine and it shouldn't fail. A dump of the key gives several error messages: # dump -0au -f usb8.dmp /dev/da0s1a DUMP: Date of this level 0 dump: Fri Aug 27 14:06:04 2010 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/da0s1a to usb8.dmp DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 3980686 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: 52.81% done, finished in 0:04 at Fri Aug 27 14:15:35 2010 DUMP: DUMP: read error from /dev/da0s1a: Input/output error: [block 4992928]: count=8192 read error from /dev/da0s1a: Input/output error: [block 4992870]: count=10240 DUMP: read error from /dev/da0s1a: Input/output error: [block 4992896]: count=7168 DUMP: DUMP: read error from /dev/da0s1a: Input/output error: [sector 4992928]: count=512 DUMP: read error from /dev/da0s1a: Input/output error: [sector 4992870]: count=512 read error from /dev/da0s1a: Input/output error: [sector 4992896]: count=512 DUMP: DUMP: read error from /dev/da0s1a: Input/output error: [sector 4992899]: count=512 DUMP: read error from /dev/da0s1a: Input/output error: [sector 4992931]: count=512 read error from /dev/da0s1a: Input/output error: [sector 4992873]: count=512 DUMP: DUMP: read error from /dev/da0s1a: Input/output error: [block 5032906]: count=10240 read error from /dev/da0s1a: Input/output error: [block 5032928]: count=9216 DUMP: read error from /dev/da0s1a: Input/output error: [block 5032946]: count=7168 I will re-create the key or even use another media; matthias Try recreating, preferably newfs the key first. Don't be surprised if you find out you need a new USB key. This reminds me of a recent incident I had with another key (of a respected brand as well) which failed and disappeared(!) from the bus while I was writing to it, plugged in on my freebsdgr.org server. Not only I had to umount -f, but subsequently seems the whole USB subsystem got 'stuck' and I had to reboot the server for it to work again. As I said, I have not witnessed 'data fading' in USB flash drives, but this the third one I throw away due to total hardware failure... ___ 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: running FreeBSD on Windows host
On 24/08/2010 11:42 π.μ., Matthias Apitz wrote: El día Monday, August 23, 2010 a las 02:31:08PM +0300, Manolis Kiagias escribió: Once having setup VMware (workstation), I plan to boot from FreeBSD live CD, create the slices big enough and fill in the dumps of my current system. Any objectives with this? Thx matthias This should work nicely. In fact, in one of my recent projects I did the exact opposite with great success: I installed and configured a full system on Vmware Workstation, dumped the partitions and restored on real hardware. Saved me countless hours and had the school lab running in less than a day. I have produced three dumps: from the /, /var and /usr file system. The man page of restore(8) reads about creating pristine file system, made by newfs(8). Later, in the VM environment, I'd like to have only one big file system... Is it possible to restore the tree dumps into one big file system or do I have to rebuild the same slicing as I now have? You won't have to rebuild the slicing. Just create the relevant directories in your big file system, cd into them and use restore. In the original posting I was asking for some kind of benchmark tool in the ports, to compare current and VM disk i/o... any hits? Thanks matthias Sorry I have no hard evidence on that. FWIW, virtual desktop systems running on core2duo class machines feel very fast and responsive. Definitely faster than my Atom 330 (dual core) running FreeBSD natively. There are lots of benchmarks in ports/benchmarks, some of them may be useful. I've used bonnie / bonnie++ in the past, but I am never certain I can interpret the results in a meaningful way. The base system gstat could also prove useful. ___ 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: Spontaneous Reboots (I thought it was Virtualbox Kernel Modules)
On 24/08/2010 10:58 μ.μ., Chris Maness wrote: On Tue, Aug 24, 2010 at 12:47 PM, Robert Bonomi bon...@mail.r-bonomi.com wrote: From owner-freebsd-questi...@freebsd.org Tue Aug 24 12:29:16 2010 Date: Tue, 24 Aug 2010 10:29:27 -0700 From: Chris Maness ch...@chrismaness.com To: freebsd-questions@freebsd.org Subject: Spontaneous Reboots (I thought it was Virtualbox Kernel Modules) I have commented out the lines that load kernel modules for virtualbox, and made sure they were gone with kldstat. However I am still getting VERY infrequent spontaneous reboots. So it is not the modules. I am thinking hardware. It has a temperature alarm that sounds when it is hot, but since I have cleaned it out I have not had any issues with heat. I am thinking bad processor/ram. It is behaving the same way before/after the upgraded to the latest release. What do you guys think? I think its 100% certain that it is hardware, or software. *GRIN* You can try randomly replacing things, which can be expensive, time- consuming, and not necessarily effective -- how do you *KNOW* that the parts you're putting _IN_ do not, themselves, have (as-yet undiscovered) problems? I'd try to make the box tell me something about *why* it crashed. crank up the level of logging for 'kernel' events in syslog.con, enable crash dumps, and make sure the boot process saves the dump Then you can get into the weird,wonderful, world of 'crash dump' analysis. With a few dumps in hand, you can begin to see if there is any consistency in what the machine was doing -when- it crashed. Happy hunting When I looked at the regular level kernel log, it seemed to be out of the clear blue. I am an experienced user, but I am not sure if I have the programing skills to look at debug output to find a fault. I might need a bit of hand holding on this one. I looked at backtrace to. I was thinking it was a command or something, but it looks like some debugging procedure. Regards, Chris Maness If the reboot is so abrupt and sudden that nothing is logged (like someone pressing the reset button), it is most probably hardware. As others have said the most usual culprits are RAM and power supply. If you have any spare parts at hand, it may be worth the effort to try with an other power supply. If the reboot happens when the system is stressed (lots of disk activity and/or high power consumption by the CPU, like when portupgrading) the power supply is even more suspect. Bad RAM usually causes error messages and dumps to appear rather than out of the blue reboots. Since it is unlikely that the same program will always be in the faulty area of memory each time, the dumps will not be consistent - will seem to be caused by entirely different apps. It is still worthy to at least take out the RAM modules and clean the contacts before reinstalling. Use rubbing alcohol (a pen eraser is also good for gold plated contacts). Many RAM problems on older systems are definitely caused by dust and corrosion on these contacts. ___ 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: running FreeBSD on Windows host
On 23/08/2010 10:08 π.μ., Matthias Apitz wrote: Hello, I've to re-install my laptop with some Windows version (Vista or Windows 7) with disk encryption. Of course I will go on to work in FreeBSD 9-CURRENT and KDE3 as desktop. Please, don't ask me why I have to put Windows below :-) I have some questions: From the point of view of performance in FreeBSD, what would be better, Vista or Win7? Win 7 is a lot better than Vista... Any recommendation for the virtualisation software for best performance? Vmware achieves very good performance without trouble. VirtualBox works OK most of the time (and it's free) but I had some kernel panics running FreeBSD (unless the host is also FreeBSD!) Have not tried very recent versions though, it may have improved. ___ 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: running FreeBSD on Windows host
On 23/08/2010 1:31 μ.μ., Bruce Cran wrote: On Mon, 23 Aug 2010 12:39:14 +0300 Manolis Kiagias son...@otenet.gr wrote: Vmware achieves very good performance without trouble. VirtualBox works OK most of the time (and it's free) but I had some kernel panics running FreeBSD (unless the host is also FreeBSD!) Have not tried very recent versions though, it may have improved. I presume people mean VMWare Workstation when talking about VMWare, and not other products like ESXi? Yes, I mean Workstation. I'd love to see ESXi in action but have no real server-class machines around. ___ 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: running FreeBSD on Windows host
On 23/08/2010 2:26 μ.μ., Matthias Apitz wrote: El día Monday, August 23, 2010 a las 12:39:14PM +0300, Manolis Kiagias escribió: Win 7 is a lot better than Vista... Any recommendation for the virtualisation software for best performance? Vmware achieves very good performance without trouble. VirtualBox works OK most of the time (and it's free) but I had some kernel panics running FreeBSD (unless the host is also FreeBSD!) Have not tried very recent versions though, it may have improved. Once having setup VMware (workstation), I plan to boot from FreeBSD live CD, create the slices big enough and fill in the dumps of my current system. Any objectives with this? Thx matthias This should work nicely. In fact, in one of my recent projects I did the exact opposite with great success: I installed and configured a full system on Vmware Workstation, dumped the partitions and restored on real hardware. Saved me countless hours and had the school lab running in less than a day. ___ 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
ANNOUNCE: Custom 32bit FreeBSD 8.1-RELEASE with XFCE packages released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey all, After last week's release of the first 64bit XFCE custom FreeBSD 8.1-RELEASE, I am pleased to announce the 32bit version is now also available at: http://freebsd-custom.wikidot.com You may download the ISO file immediately using the downloads page: http://freebsd-custom.wikidot.com/downloads-page This release is based on the latest XFCE desktop and includes a wide variety of desktop-related packages, like OpenOffice, abiword, gnumeric, firefox35, gimp, inkscape, evince and so on. The base system is 8.1-RELEASE. A few other small window managers are included like windowmaker, fluxbox and icewm. Make sure to read the README file before installation. Also note that installing linux related packages during initial setup needs a few more steps. This is due to differences in sysinstall between 7.X and 8.X releases. A detailed explanation is provided in the README file. As always, please report any problems, success stories, comments and criticisms to mano...@freebsd.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxdp6AACgkQZ/MxGm4PtJTraACfQ9iNNs6XRmQU/kigl79BKkQS pJIAoIFDur+hRnpo13k/roPqdzGCtZTw =KgQh -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: looking for a buildable version of OpenOffice.org
On 05/08/2010 2:25 μ.μ., Chris Whitehouse wrote: As I noted previously, there do not appear to be any packages available for 7.3, or at least portmaster doesn't find any. You could try asking here: http://freebsd-custom.wikidot.com/ or check the downloads-page Chris We don't have a recent openoffice build for 7.3-RELEASE, but could probably run a build after testing the 32bit version of the custom DVD. Do you need 32 or 64bit? ___ 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: ANNOUNCE: Custom 64bit FreeBSD 8.1-RELEASE with XFCE packages released
On 05/08/2010 5:02 ?.?., Mubeesh ali wrote: Hi Manolis, Thank You . Please advise if a GNOME version of 8.1 release will be made available or is there a different project that you are aware that makes this available. thanks. Mubeesh GNOME is available on the official DVD. I haven't built a GNOME version since 7.2 and will probably wait until 8.1-RELEASE-p1, since the version on the official DVD is probably quite recent anyway. Cheers, Manolis ___ 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
ANNOUNCE: Custom 64bit FreeBSD 8.1-RELEASE with XFCE packages released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey all, I have just completed the first 8.1-RELEASE based build of the 'Custom releases' project hosted here: http://freebsd-custom.wikidot.com At the moment only the 64bit version is available, while a 32bit version is in the works and is expected later on this week. You may download the ISO file immediately using the downloads page: http://freebsd-custom.wikidot.com/downloads-page This release is based on the latest XFCE desktop and includes a wide variety of desktop-related packages, like OpenOffice, abiword, gnumeric, firefox35, gimp, inkscape, evince and so on. The base system is 8.1-RELEASE. A few other small window managers are included like windowmaker, fluxbox and icewm. Make sure to read the README file before installation. Also note that installing linux related packages during initial setup needs a few more steps. This is due to differences in sysinstall between 7.X and 8.X releases. A detailed explanation is provided in the README file. As always, please report any problems, success stories, comments and criticisms to mano...@freebsd.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxWYlIACgkQZ/MxGm4PtJQGuQCfXv2zk1PIsQwHjXcYLYh7OAL8 FPQAn3kNgMwYzUJT/VYU/IQdiqU/xCZr =yqB+ -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: building an ISO
On 12/07/2010 9:51 μ.μ., Sam Fourman Jr. wrote: On Mon, Jul 12, 2010 at 12:51 PM, Ryan Perry rpe...@madisonip.com wrote: I need to make my own FreeBSD installer CD that installs 2 ports, and then runs some custom scripts. What are the best methods to accomplish this? I was also wondering if there is a way to make release without using a cvs tag? eg.. I want to use the /usr/src from my machine The quick answer is yes: make release CHROOTDIR=/data/release \ BUILDNAME=7.1-PRERELEASE \ CVSROOT=/data/ncvs \ EXTSRCDIR=/usr/src \ -DNODOC -DNOPORTS \ -DNO_FLOPPIES \ -DMAKE_ISOS Note the EXTSRCDIR that points to /usr/src. You still have to supply CVSROOT which need not exist, and will not be used ___ 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: screen saver
On 11/07/2010 4:00 π.μ., Giorgos Tsiapaliokas wrote: hello, i am new to the freebsd world and i am trying to put screen saver to my box. i have a freebsd 8.0-release,i386 system i have loaded to rc.conf saver=rain i have gave the command vidcontrol -t 3 in the ttyv and i am in ttyv but screen saver doesn't appear after 3 seconds. the command kldstat shows that the module rain_saver.ko is loaded. i think that i am doing everything right but screen saver doesn't appear.. thanks in advance Did you run /etc/rc.d/syscons restart (or reboot) after changing the saver= line in rc.conf? It works fine here. ___ 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: Copy a FreeBSD 8* install to larger HD
On 23/06/2010 5:52 π.μ., Al Plant wrote: Aloha, I am looking for the easiest way to copy a fresh working FreeBSD 8* HD install (Manolis version) to a bigger HD that I found. I plan to have the new HD in the same box for doing this copy. Can I use sysinstall to make the new default slices on the big HD and then move the OS and directories/files to them? What command (utility) do I use? dd or cp or some other to copy the files. Thanks Hey Al! Back to your FreeBSD adventures, heh ;) You can certainly use sysinstall to create the slice. I suggest you use the command line bsdlabel to create the partitions. On your current system, use dump/restore to dump /, /var and /usr to the new disk directly (or you can save the dumps to some external disk and use it via fixit if you don't wish to mount both drives on the same machine). It would be best to run dump/restore in single user mode, without mounting /usr and /var, or at least with the minimum number of processes running. If you do run on a live filesystem, use the -L flag in dump (I've had some problems with this on large filesystems). Email me if you need more detailed instructions, I am currently investigating this method as a quick installation system for my custom FreeBSD systems. ___ 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: pkg_version strange output
On 17/06/2010 6:27 μ.μ., Giorgos Tsiapaliokas wrote: hello, when i give the command pkg_version the following output comes up.. libxkbfile = Long list of packages snipped OpenSP = pkg_version: corrupted record (pkgdep line without argument), ignoring Terminal= pkg_version: corrupted record (pkgdep line without argument), ignoring Thunar = a2ps-a4 = what is going on??? thanks for your answers..! Are you using portmaster? Check if this applies to you: http://www.cyberciti.biz/faq/pkg_version-corrupted-record-pkgdep-line-without-argument-ignoring/ ___ 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: evince problem
On 13/06/2010 12:30 μ.μ., Istvan Galgand wrote: If you type: evince BSD_06_2010.pdf at a command prompt, do you see any error messages? Tony Hi Tony, You are absolutely right, I have tried this. Sorry for my forgetfulness... The response is: [igalg...@freebsd02 /usr/home/igalgand/Desktop/Test]$ evince BSD_06_2010.pdf ** (evince:1263): WARNING **: Error creating last_settings file: Error opening file '/home/igalgand/.gnome2/evince/last_settings': No such file or directory Being aware of this error message still I do not know how to mitigate, how to create the requested file. Istvan I think I've seen this before. It doesn't care about the file (it just creates it if it is missing) but my guess is you are missing the directory. So try something like mkdir -p ~/.gnome2/evince ___ 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: reinstall all of Xorg
On 07/06/2010 12:42 μ.μ., n dhert wrote: After an upgrade FreeBSD72 - 80, Xorg doesn't work looking in /var/log/Xorg.0.log tells Build Operating System: FreeBSD 7.2-RELEASE-p7 Current O S FreeSBD-8.0-RELEASE-p2 I have done a portupgrade -af after upgrading, but somehow if seems not to have done this for Xorg ?? How can I reinstall anything of Xorg ? Will this do the job? # cd /usr/ports/x11/xorg # make clean # make deinstall # make reinstall clean I doubt this will work. x11/xorg is a meta port, make deinstall will not really deinstall anything but the skeleton port. If you wish to go down this route, install something like ports-mgmt/pkg_rmleaves. Then select xorg from the list and follow down all the list of dependencies it will show you while it is running, until everything is uninstalled. or # portupgrade -f xorg Probably portupgrade -Rf xorg ___ 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: svgalib-1.4.3_5 is only for i386, while you are running amd64
On 08/06/2010 8:16 π.μ., Giorgos Tsiapaliokas wrote: hello, i am trying to install vlc but i came up against this error.. === vlc-1.0.6_3,3 depends on file: /usr/local/live/liveMedia/libliveMedia.a - found === vlc-1.0.6_3,3 depends on package: v4l_compat=1.0.20100321 - found === vlc-1.0.6_3,3 depends on file: /usr/local/include/X11/xpm.h - found === vlc-1.0.6_3,3 depends on executable: gmake - found === vlc-1.0.6_3,3 depends on file: /usr/local/libdata/pkgconfig/xpm.pc - found === vlc-1.0.6_3,3 depends on file: /usr/local/lib/qt4/libQtCore.so - found === vlc-1.0.6_3,3 depends on file: /usr/local/lib/qt4/libQtGui.so - found === vlc-1.0.6_3,3 depends on file: /usr/local/bin/moc-qt4 - found === vlc-1.0.6_3,3 depends on file: /usr/local/bin/rcc - found === vlc-1.0.6_3,3 depends on file: /usr/local/bin/uic-qt4 - found === vlc-1.0.6_3,3 depends on file: /usr/local/bin/sdl-config - found === vlc-1.0.6_3,3 depends on file: /usr/local/bin/perl5.10.1 - found === vlc-1.0.6_3,3 depends on file: /usr/local/bin/intltool-extract - found === vlc-1.0.6_3,3 depends on file: /usr/local/libdata/pkgconfig/gnome-mime-data-2.0.pc - found === vlc-1.0.6_3,3 depends on executable: pkg-config - found === vlc-1.0.6_3,3 depends on shared library: avcodec.1 - found === vlc-1.0.6_3,3 depends on shared library: dbus-1.3 - found === vlc-1.0.6_3,3 depends on shared library: notify.1 - found === vlc-1.0.6_3,3 depends on shared library: tar.0 - found === vlc-1.0.6_3,3 depends on shared library: zvbi.13 - found === vlc-1.0.6_3,3 depends on shared library: hal.1 - found === vlc-1.0.6_3,3 depends on shared library: avahi-common.3 - found === vlc-1.0.6_3,3 depends on shared library: vcdinfo.2 - found === vlc-1.0.6_3,3 depends on shared library: cdio.12 - found === vlc-1.0.6_3,3 depends on shared library: cdda_interface.0 - found === vlc-1.0.6_3,3 depends on shared library: dvbpsi.5 - found === vlc-1.0.6_3,3 depends on shared library: dvdnav.4 - found === vlc-1.0.6_3,3 depends on shared library: faac.0 - found === vlc-1.0.6_3,3 depends on shared library: faad.2 - found === vlc-1.0.6_3,3 depends on shared library: FLAC.10 - found === vlc-1.0.6_3,3 depends on shared library: fribidi.3 - found === vlc-1.0.6_3,3 depends on shared library: aa.1 - found === vlc-1.0.6_3,3 depends on shared library: dirac_decoder.1 - found === vlc-1.0.6_3,3 depends on shared library: x264.85 - found === vlc-1.0.6_3,3 depends on shared library: caca.0 - found === vlc-1.0.6_3,3 depends on shared library: dca.0 - found === vlc-1.0.6_3,3 depends on shared library: matroska.0 - found === vlc-1.0.6_3,3 depends on shared library: a52.0 - found === vlc-1.0.6_3,3 depends on shared library: mpeg2.0 - found === vlc-1.0.6_3,3 depends on shared library: shout.5 - found === vlc-1.0.6_3,3 depends on shared library: theora.0 - found === vlc-1.0.6_3,3 depends on shared library: tag.1 - found === vlc-1.0.6_3,3 depends on shared library: id3tag.0 - found === vlc-1.0.6_3,3 depends on shared library: mad.2 - found === vlc-1.0.6_3,3 depends on shared library: modplug.1 - found === vlc-1.0.6_3,3 depends on shared library: mpcdec.5 - found === vlc-1.0.6_3,3 depends on shared library: ogg.7 - found === vlc-1.0.6_3,3 depends on shared library: smbclient.0 - found === vlc-1.0.6_3,3 depends on shared library: gnutls.40 - found === vlc-1.0.6_3,3 depends on shared library: speex.1 - found === vlc-1.0.6_3,3 depends on shared library: vga.1 - not found ===Verifying install for vga.1 in /usr/ports/graphics/svgalib === svgalib-1.4.3_5 is only for i386, while you are running amd64. *** Error code 1 Stop in /usr/ports/graphics/svgalib. *** Error code 1 Stop in /usr/ports/multimedia/vlc. *** Error code 1 Stop in /usr/ports/multimedia/vlc. i search in the mailing list and i found that if i make a modify with make confing in /usr/ports/print/ghostscript8 these two parametres [ ] GS_lvga256 D: SVGAlib, 256-color VGA modes [ ] GS_vgalib D: SVGAlib, 16-color VGA modes that the problem will solved,but i had no luck. also i updated my ports and the i updated the packages multimedia/vlc,print/ghostscript,graphics/svgalib but still the problem wasn't solved.. any help would be appreciated.:) This does not seem to be the only place where SVGALIB is defined though. I just tried a make config-recursive in multimedia/vlc and can see SVGALIB both in the main port, the sdl port and so on. It is off by default (I am using amd64 too), so I guess you made some config changes yourself. At this point the easy way would be to: cd /usr/ports/multimedia/vlc make rmconfig-recursive make config-recursive (careful not to select SVGALIB anywhere, or even better just leave the default options) make install clean ___
Re: why so many errors with ports??
On 06/06/2010 1:39 π.μ., Giorgos Tsiapaliokas wrote: hello, i am coming from the linux world i was a gentoo user and i have install on my second machine FBSD,i have made many formats but every time i try to install a graphical enviroment (such as xfce,kde) many many errors come up. i have heard that the ports are more stable than portage but with portage i didn't have so many errors (actually i can't recall a time when portage died) am i doing sth wrong or ports comes up with many errors?? P.S.: 1 week not i haven't manage to install a graphical enviroment thanks in advance I suggest you perform just the base system install from CD, and compile everything else from an updated ports tree. If you happen to install any packages from the DVD (and esp. since i.e. FreeBSD 8.0 has been out for some time now) you will experience problems - unless you run a portupgrade first (so that all shared libraries etc. get updated to the latest versions). This is not worthy it for a new install - just proceed with the base system install, do not install any packages (doc packages are ok though) and do not even install the ports collection. After the base system is installed, run portsnap fetch extract to get an up-to date ports tree (from then on, you can update this tree with portsnap fetch update) And then go on with installing everything you wish. I usually start with the smallest console based stuff (bash, zip, unzip, rar, unrar, sudo, screen, etc) and continue with x11/xorg and WM or DE of choice. I never had this fail. Have a look at the FreeBSD Handbook's chapter 4,5,6 as well. ___ 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: why so many errors with ports??
On 06/06/2010 1:11 ?.?., Giorgos Tsiapaliokas wrote: i have FBSD 8.0 i have install the base system plus the bash shell from the CD.after the installiation of the system i install ports with portsnap and i update them with portmaster,no error came up,but now i receive errors from xfce4. @*Alejandro Imass* * * what do u mean when u say? Tip: in FBSD the word stable has a completely different meaning than in the LInux world ;-) (adding the list to the recipients) Don't install bash from CD. Bash will also install gettext, and this was recently updated. Almost every single port has a dependency on gettext and you happen to have the old version installed with bash, while the ports you are trying to install will need the new version. Start with just the base system and install bash from ports as well. ___ 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: freebsd releases?!?!?!(confused)
On 06/06/2010 1:27 μ.μ., Giorgos Tsiapaliokas wrote: hello, i was using gentoo linux and i have install FBSD 8.0 in my second machine.. i have read the handbooks but i cannot understand which version of FBSD i have. i mean i know that i have 8.0 but i have the stable or the unstable version??? and what is going on with the mirrors? Try uname -a You probably have 8.0-RELEASE, this is an officially released version suitable for servers and desktops alike. There is also 8-STABLE, this is a version in progress which is actually very stable and usable and may provide features missing from RELEASE (which you may need for some reason or other). Since you are a beginner, I suggest you stay with RELEASE for the time being. ___ 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: upgrade from FBSD from 8.0-release to stable-8
On 06/06/2010 4:37 μ.μ., Giorgos Tsiapaliokas wrote: hello, i have seach to net but i haven't find a way to update my system from 8.0-release to stable-8. can you tell me a way to do this? thanks in advance Since you are just starting with this, I would advise against it. Unless you know STABLE contains something you really need (i.e. a must have driver or fix for your particular hardware), I would say stay on RELEASE until you are more comfortable with your system. Going from RELEASE to STABLE involves recompiling the system from source. It is not really difficult, but it will save you a lot of trouble if you first get better acquainted with your system. If you would like to try it anyway, here are the instructions: http://www.freebsd.org/doc/el/books/handbook/current-stable.html (starting from 24.5.2) Since you are experimenting and don't have any data on the system, you may also wish to directly install one of the snapshots that will get you directly to a STABLE system. You can find snapshot ISOs here: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201005/ or you may even wish to try 8.1-BETA1 which is also available in local mirrors (like otenet): ftp://ftp.otenet.gr/pub/FreeBSD/releases/i386/ISO-IMAGES/8.1/ ___ 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: UPGRADE TO RELEASE 8.0-P3/SAMBA HELP REQUIRED
On 04/06/2010 12:01 π.μ., Andy Hiscock wrote: LOL - now stuck in and endless loop of: Message ─┐ │Unable to get packages/INDEX file from selected media. This is like a poorly written shareware app! Really getting pissd here! My guess is you need to do some reading first, it seems you are administering a system you don't quite understand. When doing a minor version upgrade (i.e. from 7.0 to 7.2) there is no need to touch anything in the extra programs you've installed (hint: those that come from packages or ports). Minor versions are binary compatible (few apps may need some attention but this is rare). When you do a major upgrade, you will be able to execute your 7.x installed apps on 8.x. But by the time you start installing programs to your new version, you will start replacing libraries of the 7.x system with new ones and the programs compiled for 7.x will stop functioning. My guess is you already installed some packages from the 8.0 media, so this has happened already. The recommended path for such an upgrade is to upgrade all your installed ports for your new system. Most people use ports (meaning they build the software on their own machine, it is quite straightforward and mostly automated) but it seems you are using packages. It should still be possible to do this. Please read the following section in the FreeBSD Handbook: http://www.freebsd.org/doc/en/books/handbook/updating-upgrading-freebsdupdate.html esp. 24.2.3 When upgrading from packages, change the command: portupgrade -af to portupgrade -af -PP which effectively means: Use packages only And yes, you will need a ports tree for portupgrade to work properly (although you won't be compiling anything). You don't need to keep it afterwords but it is handy to have and does not consume a lot of space. So get one: portsnap fetch extract And after finishing the upgrade, you can rm -rf /usr/ports if you don't want to keep it. You may wish to have a good read of the FreeBSD Handbook, esp. chapter 4 that deals with ports and packages. ___ 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: uname -r and patchlevel
On 01/06/2010 2:33 ?.?., n dhert wrote: Can somebody explain about the -plevel one sees in the output of the uname -r ? Under *exactly* what conditions the patch level changes to a new value after you applied a freebsd-update install ? If you are using the GENERIC kernel AND the kernel was updated as part of the freebsd-update process, the patch level is changed. You will need to reboot. If you are using the GENERIC kernel AND the kernel was not updated as part of the freebsd-update process, the patch level reported is unchanged if you are using a CUSTOM kernel, the reported patch level is not changed until you rebuild your kernel with the new sources as updated by freebsd-update. After rebuilding your kernel it always reflects the latest -p version, even if there were no actual kernel changes. The reported -p level is contained in this file: /usr/src/sys/conf/newvers.sh and this is always updated when an update comes through. If you rebuild your custom kernel (or even GENERIC) it will always report the value from this file. ___ 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: Verifying a DVD
On 24/05/2010 1:23 π.μ., Doug Hardie wrote: I am periodically backing up a bunch of files to DVD. I use mkisofs to create the original image and growisofs to write it to a real DVD. However, at that point I want to verify that the write was successful. I tried using dd to read back in the DVD to a file. Its interesting that the bs parameter must be at least 2048 or dd complains about a parameter error. However, the big issues is that the original image file is shorter than the read file. The difference is 10240 bytes. This difference is the same for bs 2048, 10240, or 102400. It appears that dd is adding one last block. Is there a way to prevent this or remove that block? Use the count= parameter in dd to read the exact count of blocks in the DVD. Use isoinfo to obtain this information from the media itself. Have a look at the instructions here: http://www.troubleshooters.com/linux/coasterless.htm ___ 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: Why is Qemu not in Handbook
On 14/04/2010 8:55 μ.μ., Adam Vande More wrote: On Wed, Apr 14, 2010 at 10:24 AM, Bob Johnson fbsdli...@gmail.com wrote: For years I used Qemu to run Windows XP under FreeBSD. It worked fine. A few months ago I saw a message that VirtualBox was now working correctly under FreeBSD. So I tried to install it and it wouldn't build. But that's not the actual topic of my question. In the process of trying to install VirtualBox I noticed that Qemu is not mentioned in the Handbook. It's not even mentioned under Other Virtualization Options. So my actual question is: Why is Qemu not mentioned in the Handbook? There is already a PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=127923 Even just a mention with a link to http://wiki.freebsd.org/qemu would be helpful. Thanks, you mean like this? http://www.freebsdgr.org/handbook-mine/virtualization-host.html I don't know why it's not on the official one, IIRC it used to be. This is not the official Handbook, but my own patch queue, and yes it has been in there for too long. Hopefully I will have a lot more free time in a few weeks, there are more patches like this that need to get reviewed and committed. ___ 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: gnome gdm diable_user_list
On 26/03/2010 3:42 ?.?., n dhert wrote: FreeBSD8.0, gnome2-2.28.2_1, using gdm to login. Gdm login screen presents a list of all users on the system to choose from. I don't want the list, just a prompt for a username and password. I tried # gconf-editor this graphical config program allows to set in apps / gdm / simple-greeter the setting 'disable_user_list' to checked (default is not checked) after setting it to checked, closing the program, rebooting I still have the user list at the gdm login window. I verified with starting the gconf-editor again: the option is still checked .. (also $ gconftool-2 -R /apps/gdm/simple-greeter shows: disable_user_list = true ) Why do I still have the user list? How to fix? gconf-editor changes the settings of the current user, the gdm settings are global (system) so should be changed by root or the user gdm is running in. I don't currently have gdm on any of my systems but AFAIR there is a gdm user created for running the greeter. You should be able to change the disable_user_list setting for this user which will have the desired effect. Something along the lines of this blog post http://lionlix.wordpress.com/2009/11/07/hack-ubuntu-9-10-disabling-userlist-in-gdm-login-screen/ should work. ___ 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: FreeBSD and vmware
On 17/03/2010 10:34 μ.μ., Erik Norgaard wrote: Hi: I have a dual boot Windows/FreeBSD which I use for work, I just tried today to create a virtual machine with vmware on windows to start up the installed FreeBSD. This works except for three problems: - The disk device is renamed, I suppose I can just dublicate the entries in the fstab, the devices not found won't be mounted, I'll get an error but problem solved? Best would probably be to label the devices and use the labels instead of device names. It will work without changes in both bare metal and vmware. (Or maybe use the ufsid labels.) Check this out: http://www.freebsd.org/doc/en/books/handbook/geom-glabel.html - I can't see the network devices from vmware The emulated network device is probably different than the one you are using. I believe most recent vmware versions emulate an Intel NIC, i.e. em0. Use ifconfig to check and add a line in rc.conf for this - I can't start xwindows, no monitor is found This is definitely fixable, make sure you install xf86-video-vmware port and create an xorg.conf by hand if needed (probably not) using the Handbook instructions. ___ 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 create a FreeBSD 8.0 boot CD without boot.flp?
On 10/02/2010 11:10 μ.μ., Pierre-Luc Drouin wrote: Hi, I would like to create a boot CD using FreeBSD 8.0 but I just noticed that there is no existing boot.flp file for 8.0. What is the alternative to get a boot image to create my CD image? Thanks! You just use the boot/cdboot file from the official CD/DVD, like this (to write to a DVD) growisofs -Z /dev/cd0 -speed 16 -J -R -no-emul-boot -b boot/cdboot -iso-level 3 path-to-your-files or use mkisofs with similar options to write an iso image, i.e. mkisofs -J -R -no-emul-boot -b boot/cdboot -iso-level 3 -o /path/to/your.iso path-to-your-files ___ 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 create a FreeBSD 8.0 boot CD without boot.flp?
On 10/02/2010 11:39 μ.μ., Pierre-Luc Drouin wrote: Great Thanks! So when I create a boot CD using the boot image, are the kernel files contained in /boot/kernel read at all during boot? How exactly are you creating your image? The basic directories in a FreeBSD install iso are 'boot' (containing the kernel that will be used for the CD boot) and a directory with the name of the release e.g. 7.2-RELEASE. If you wish to include packages they should be in a 'packages' directory on the root of the CD. If live functionality is required (FreeBSD livefs CD) there are more directories, essentially resembling the structure of an installed base system. ___ 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 create a FreeBSD 8.0 boot CD without boot.flp?
On 10/02/2010 11:56 μ.μ., Pierre-Luc Drouin wrote: I just realized that cdboot does not contain the kernel as boot.flp used to, so I guess /boot/kernel has to be there... So it does not seem to work with mkisofs. I did mkisofs -J -R -no-emul-boot -b ./cdboot -iso-level 3 -V FreeBSD_Custom -o custom_FreeBSD_8_0_i386_cd.iso custom_FreeBSD_8_0_i386_cd and it throws: mkisofs: Uh oh, I cant find the boot image './cdboot' I tried with the absolute path for cdboot and it does not help either. From the mkisofs man page it says that -no-emul-boot has to be added if the size of the image file is not 1200, 1440, or 2880 kB. I noticed that the cdboot file is only 1.2 kB, so I guess -no-emul-boot is required... Do you have an idea what could be wrong? Thanks! No need to specify an absolute path - the path you are using for the files is used. Here is another example: Assuming your files are in my_cd_files (and there is a boot/cdboot directory structure in there): mkisofs -J -R -no-emul-boot -b boot/cdboot -iso-level 3 -V FreeBSD_Custom -o custom-freebsd.iso my_cd_files or you could even do: cd my_cd_files mkisofs -J -R -no-emul-boot -b boot/cdboot -iso-level 3 -V FreeBSD_Custom -o ../custom-freebsd.iso . (note the dot at the end) ___ 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 create a FreeBSD 8.0 boot CD without boot.flp?
On 11/02/2010 12:08 π.μ., Pierre-Luc Drouin wrote: What I am trying to do is basically to install FreeBSD 8.0 on a CD. I followed these instructions to install FreeBSD on a USB stick: http://typo.submonkey.net/articles/2006/04/13/installing-freebsd-on-usb-stick-episode-2 minus the fdisk/bsdlabel/newfs part . I just set up rc.conf to configure the ethernet interface with DHCP and load sshd then I am now creating an iso image with the boot image. So at the root of the CD I will have the boot directory containing the kernel subdirectory. I figured out about the boot image error from mkisofs. I had to copy cdboot into the actual boot directory for the image and the path specified by the -b option is relative to the root directory of the CD... So should this work according to you? Thanks! It is going to be an interesting experiment. The official install CD/DVDs boot from boot/kernel on the CD but the root filesystem used is actually in an mfs (memory disk). Also it executes sysinstall instead of init at the end of the boot sequence. I suppose you can mount the root filesystem from CD as read-only but you will have to handle things like /var and /usr and you will probably need some writing capability. I am sure this can be done in more than a few ways though I've never researched this myself. ___ 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: Modules and Custom Kernels
On 07/02/2010 5:40 π.μ., James Colannino wrote: Hey everyone. Please bear with me as I'm very new to FreeBSD. I've recently started building a custom kernel after having had to apply a patch to enable support for my wireless device (Atheros 9285) in 8.0-RELEASE, and had a quick question about the process in general. According to the documentation, a line with device driver name will cause that driver to be compiled into the kernel. If one of those lines is commented out, does that mean that the driver will still be built, but that it will be installed as a module? Yes. Unless you have set some variables like WITHOUT_MODULES or MODULES_OVERRIDE in /etc/make.conf. By default all modules will be built. The modules will not be loaded automatically though. You will have to use /boot/loader.conf to specify which ones to load. I didn't see anything that told me that explicitly in the documentation, but that's the feeling I got from what I read. I just want to make sure that my assumption is correct, and if not, how to make sure that something gets built as a module rather than built directly into the kernel. You are doing just fine ;) In all, the process looks relatively painless as long as I'm careful not to make too many changes to the GENERIC config. This is true also. Using some common sense and reading the comments in GENERIC you can make your own custom kernel with little effort. Of course you may also read the Handbook on this: http://www.freebsd.org/doc/en/books/handbook/kernelconfig.html Hopefully this isn't a dumb question :) I really like FreeBSD so far, and think I'm going to enjoy my new experience quite a bit. Sure you will, FreeBSD is addictive! ___ 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: portupgrade, batch mode?
On 07/02/2010 2:14 μ.μ., Dánielisz László wrote: I think you can try this: -y --yes Answer yes to all the questions. This option implies -v and negates -n . László On 2010.02.07., at 12:59, n dhert ndh...@gmail.com wrote: When using portupgrade, from time to time, there is a package that displays an options menu and waits for a interactive response (like hitting OK to accept the defaults and continue). Is there way to specify that portupgrade should always accept the defaults and not wait for user input? And in fact, you can also use --batch ___ 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: mysql silently failing to start - suggestions?
On 01/02/2010 5:34 π.μ., John wrote: If this isn't the right list - if I should try another let me know - but since this is the mysql-server-5.4.2 package, and since you folks have been so helpful, I thought I'd give it a go. Anyway, the system is 8.0-RELEASE and that package is installed, and I can't start the server. Not only can I not start the server, but it's not giving me a clue. I can't find anything anywhere. Not in /var/log/messages, not anywhere. When I run /usr/local/etc/rc.d/mysqlserver start it says Starting mysql., pauses for several seconds (I don't see anything go by in top) and then the script exits. At that point, one would expect, there's no /tmp/mysql.sock, there's nothing in messages or anywhere else. With nothing to go on, well, I don't know where to start. Any suggestions? Maybe a long shot, but I once had a problem starting mysql because the sticky bit was not set on /tmp. I had previously dump/restored the system and forgot to chmod -R 1777 /tmp Don't remember the exact error message - if there was any - but it took me quite some time to figure out. Have a quick look at 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: VirtualBox doesn't start
On 31/01/2010 7:32 μ.μ., Frank Wißmann wrote: Glen Barber schrieb: Frank Wi?mann wrote: Glen Barber schrieb: Hi Frank, Frank Wi?mann wrote: Hi, folks! I want to launch my freshly installed VB with the run-command under KDE 3.5.10, but it won't start. All I get is Command can't be executed in german. I also tried with full pathname /usr/local/lib/virtualbox/VboxBFE, but that doesn't work either. Where should I look for a solution? Can you run this from a terminal emulator (konsole, xterm) for more verbose output? OK, here it is: VBoxBFE: supR3HardenedExecDir: couldn't read , errno=2 cchLink=-1 Is your user in the vboxusers group? OK, now he is. But either as root or as normal user I get the same result as in the message in the last mail described. Greetings Frank You probably haven't mounted the proc filesystem. See section 22.3.1 in the Handbook: http://www.freebsd.org/doc/en/books/handbook/virtualization-host.html ___ 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: xdm and xdmcp
On 21/01/2010 8:54 μ.μ., rhin...@postmail.ch wrote: Hi All, Is-it possible to run xdm with remote access through XDMCP protocol on freebsd 8 ? Yes. I have an entire lab working this way :) I have tried almost anything: commenting line about port 0 in xdm-config, This is needed. modifying Xaccess, starting xdm with parameter udpPort 177. The command netstat -a never indicates that a process is listening on that port. The notes in Xaccess seem to indicate that when a LISTEN line is not present, it works like LISTEN * I found this to be false. Please insert a LISTEN line with your IP address, i.e. LISTEN 10.14.28.10 With wdm, the listening is possible but I cannot start the X server even if the server alone is perfectly working and if it is correctly started by xdm. I don't want to use kdm or gdm since they are too heavy (almost all kde and gnome should be installed with them). Same here, I use XDM for login - I don't need anything fancy. About 15 terminals running XFCE through a core2quad machine. ___ 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: Dislike the way port conflicts are handled now
On 16/01/2010 6:57 π.μ., Greg Larkin wrote: Craig Whipp wrote: On Jan 15, 2010, at 9:44 AM, Kirk Strauser wrote: Until recently, it seems like port dependencies were handled at installation time. Lately, they're handled any time I try to do anything with a port. I absolutely detest the new behavior. Example cases: OLD WAY: $ cd /usr/ports/something/foo22 $ make $ pkg_delete foo21-2.1 $ make install NEW WAY $ cd /usr/ports/something/foo22 $ make === foo22 conflicts with installed package(s): foo21-2.1 $ make fetch === foo22 conflicts with installed package(s): foo21-2.1 $ curse --type=copious $ pkg_delete foo21-2.1 $ make install This isn't just a hypothetical pain in the butt. An example was being unable to build databases/mysql51-client because mysql-client-5.0.something was installed. I understand not being able to *install* it, but to be prevented from *building* it? In most circumstances, I want to be able to delete the old package and install the new one with minimal downtime. As another example, can you imagine not being able to even run make fetch on something huge like OpenOffice until you uninstalled the old version? In the mean time, I've been editing the port's Makefile to remove the CONFLICTS line long enough to finish building. That's not very helpful for those ports that don't actually build until you run make install, but at least I can get the distfile download out of the way. -- Kirk Strauser I agree. I've found that this can interfere with portmaster's -o option, used to replace an installed port with one of a different origin. In my case, databases/mysql41-server with databases/mysql55-server. - Craig This change was based on a recent PR (http://www.freebsd.org/cgi/query-pr.cgi?pr=137855) and made it into the tree a couple of weeks ago: http://www.freebsd.org/cgi/cvsweb.cgi/ports/Mk/bsd.port.mk.diff?r1=1.631;r2=1.632 Since some folks like the old behavior and some folks like the new behavior, what do you all think of a user-selectable make.conf option to choose where the check-conflicts target appears in the port build sequence? Regards, Greg While I build most of my personal packages using ports-mgmt/tinderbox, this option would be very useful. I routinely run make fetch on remote machines to retrieve large distfiles, and wouldn't want the installed dependencies to interfere with that. ___ 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
ANNOUNCE: New Custom XFCE isos based on 8.0-RELEASE-p2 (32 and 64 bits)
Hey all, I have just completed the second 8.0-RELEASE based build of the 'Custom releases' project hosted here: http://freebsd-custom.wikidot.com This time, both 32 and 64 bit isos are offered, both based on 8.0-RELEASE-p2 and using packages from the same ports tree. From this point on I will try to simultaneously release 32 and 64 bit images. You may download the ISO files immediately using the downloads page: http://freebsd-custom.wikidot.com/downloads-page This release is based on the latest XFCE desktop and includes a wide variety of desktop-related packages, like OpenOffice, abiword, gnumeric, firefox35, gimp, inkscape, evince and so on. The base system is 8.0-RELEASE-p2 which includes the latest security fixes. Make sure to read the README relevant to the iso you are downloading (32 or 64bit) as it contains important information on installation. In particular note: * The 'doc' set (FreeBSD documentation) is now once again included. Just select the language(s) of your choice to install. * The problem with 'libcheck-0.9.8' in the previous release has been resolved. * Installing linux related packages during initial setup needs a few more steps. This is due to differences in sysinstall between 7.X and 8.0 releases. A detailed explanation is provided in the README file. As always, please report any problems, success stories, comments and criticisms to mano...@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: FreeBSD versions
On 04/01/2010 3:33 μ.μ., Mernoz Rostangi wrote: Hi, I would like to know if the FreeBSD 8.0 IA64 can be used on 32bit cpu also ? If yes, what is the difference between IA64 and x86 versions ? :-) ./m The IA64 is intended for Intel's Itanium Processor. It is 64bit, but will not on your standard Core2Duo or AMD64 processors. You need the amd64 edition for the common 64bit CPUs (both Intel and AMD). The 64bit versions cannot be used on 32bit hardware. On the other hand, the i386 (x86) version will happily run on a Core2Duo or AMD64. ___ 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: Can't get ZFS on GPT Root to work.
On 03/01/2010 7:04 μ.μ., Randal L. Schwartz wrote: I followed the instructions on http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot precisely (annoying, because I can't cut and paste :) on both my VMWare machine locally and on a VPS from ArpNetworks.com. In both cases, when booting from the hard drive after install, I get: No ZFS pools located, can't boot Is it missing a step? Maybe the zpool should have been exported at the end too? I'm using 8.0-RELEASE-amd64-dvd1.iso on 64-bit VMs. I've tried the exact steps on vmware fusion (8.0-RELEASE amd64) and didn't notice anything. Did you get any error messages in any of the commands shown in the wiki? I found it is useful to issue sysctl kern.geom.debugflags=16 at an early stage. If you need to delete any legacy slices, go to fixit, issue the sysctl, return to syinstall and enter 'Configure' and fdisk. Delete the slice and then perform the gpart destroy ad0 command as instructed in the wiki. Otherwise it might fail (it did in my tests) ___ 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: Can't get ZFS on GPT Root to work.
On 03/01/2010 8:38 μ.μ., Randal L. Schwartz wrote: Manolis == Manolis Kiagias son...@otenet.gr writes: Manolis I've tried the exact steps on vmware fusion (8.0-RELEASE amd64) and Manolis didn't notice anything. Did you get any error messages in any of the Manolis commands shown in the wiki? No error messages at all. Of course, for vmware, I had to use da0 not ad0. But otherwise, I followed the steps *to the letter*. And when I reboot, no ZFS Pool found. :( Did you select Freebsd 64-bit for the vm type? Yes. And I used an IDE disk instead of the SCSI usually suggested by Vmware so it was ad0 for me. I doubt this makes any difference. ___ 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: Where did the handbook go?
On 01/01/2010 10:01 μ.μ., Frank Wißmann wrote: Hi all! I am wondering where my handbook is. Under /usr/share/doc/de/ where it used to be is nothing appropriate. Has anybody an idea for me? Using sysinstall to install additional docs didn't solve the problem. Or am I wrong? Greetings Frank We now got the concept of documentation packages. These are installed in /usr/local/share/doc/freebsd and are available in all languages (for which a doc project exists of course) and in a variety of formats as usual (pdf, html and so on). If you haven't installed them when installing FreeBSD, you can do so easily by reinserting your DVD and running sysinstall. Select 'Configure' and then 'Documentation Installation'. You can also install using pkg_add or build what's needed from ports. For example, the German docs port is in: misc/freebsd-doc-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: Where did the handbook go?
On 01/01/2010 11:34 μ.μ., Frank Wißmann wrote: Manolis Kiagias schrieb: On 01/01/2010 10:01 μ.μ., Frank Wißmann wrote: Hi all! I am wondering where my handbook is. Under /usr/share/doc/de/ where it used to be is nothing appropriate. Has anybody an idea for me? Using sysinstall to install additional docs didn't solve the problem. Or am I wrong? Greetings Frank We now got the concept of documentation packages. These are installed in /usr/local/share/doc/freebsd and are available in all languages (for which a doc project exists of course) and in a variety of formats as usual (pdf, html and so on). If you haven't installed them when installing FreeBSD, you can do so easily by reinserting your DVD and running sysinstall. Select 'Configure' and then 'Documentation Installation'. You can also install using pkg_add or build what's needed from ports. For example, the German docs port is in: misc/freebsd-doc-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 This was, together with Warren's answer, what I needed. The docs are building now and I hope I find what I need. But that leads me to the question: Is there no handbook anymore in the base system? And. if yes, why not? Frank Not really in the base system, although you can install them using sysinstall as said above and they are still available in the installation media. The advantage of having the documentation as ports (or packages) is they get upgraded with portupgrade. So the local docs are not now a static snapshot of what was available when the RELEASE was done, but rather an evolving set of packages that can be upgraded along with anything else. There is a continuing effort of improving (and translating) the documentation and it is good to always be able to have the latest available locally if you wish. (Please note the change in path, as these are now packages they are installed in /usr/local/share/doc) ___ 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
ANNOUNCE: 64 bit 8.0-RELEASE-p1 Custom XFCE build available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey all, I have just completed the long awaited, first 64bit build of the 'Custom releases' project hosted here: http://freebsd-custom.wikidot.com You may download the ISO file immediately using the downloads page: http://freebsd-custom.wikidot.com/downloads-page This release is based on the latest XFCE desktop and includes a wide variety of desktop-related packages, like OpenOffice, abiword, gnumeric, firefox35, gimp, inkscape, evince and so on. The base system is 8.0-RELEASE-p1 which includes the latest security fixes. Make sure to read the README file: http://freebsd.dev-urandom.com/iso/amd64/README.TXT as it contains important information on installation and esp. a few steps that are required for a successful install. In particular note: * The 'doc' set (FreeBSD documentation) is not included in this release due to problems in the related package builds. We will include them in next releases when the problem is resolved. * The 'libchek-0.9.8' will have to be selected manually in the package selection dialog. This seems to be a problem with the INDEX file. * Installing linux related packages during initial setup needs a few more steps. This is due to differences in sysinstall between 7.X and 8.0 releases. A detailed explanation is provided in the README file. As always, please report any problems, success stories, comments and criticisms to mano...@freebsd.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAks1yCYACgkQZ/MxGm4PtJT1VACdGI9nn/MFWmvanW6L5gfqIe6W sS4AnRpLq2W+49upLFWyIKEV1pgU5Dj9 =vap7 -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: freebsd-doc-en
On 23/12/2009 10:54 μ.μ., ajtiM wrote: On Wednesday 23 December 2009 01:42:32 you wrote: On 23/12/2009 2:03 π.μ., ajtiM wrote: My system: FreeBSD 8.0 Something to do with the new Ghostscript version, most of the doc package builds are broken. I was pointed to this patch http://paste.lisp.org/display/92500 and it continued for a while but it errored out again with a different message (Bounding box not found). Still, you may wish to give it a try. I didn't try a patch because there are a new version but now I have a new problem: ../../share/images/articles/building-products/freebsd-branches.png Error: no BoundingBox found. pnmtopng: bad magic number - not a ppm, pgm, or pbm file Error: no BoundingBox found. *** Error code 1 == Warning: BoundingBox not found! 1 error *** Error code 2 Same here. The patch resolves the first problem but not 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: freebsd-doc-en
On 23/12/2009 2:03 π.μ., ajtiM wrote: My system: FreeBSD 8.0 I had a problem with update freebsd-doc-en ** Error: /undefinedfilename in --file-- Operand stack: (/usr/ports/misc/freebsd-doc-en/work/doc/en_US.ISO8859-1/articles/building- products/../../../share/images/articles/building-products/freebsd- organization.eps) (r) Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- -- nostringval-- 2 %stopped_push --nostringval-- --nostringval-- -- nostringval-- false 1 %stopped_push 1862 1 3 %oparray_pop 1861 1 3 %oparray_pop 1845 1 3 %oparray_pop 1739 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- -- nostringval-- --nostringval-- Dictionary stack: --dict:1155/1684(ro)(G)-- --dict:0/20(G)-- --dict:77/200(L)-- -- dict:10/25(L)-- Current allocation mode is local Last OS error: 2 Current file position is 8177 GPL Ghostscript 8.70: Unrecoverable error, exit code 1 Error: /undefinedfilename in --file-- Operand stack: (/usr/ports/misc/freebsd-doc-en/work/doc/en_US.ISO8859-1/articles/building- products/../../../share/images/articles/building-products/freebsd- branches.eps) (r) Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- -- nostringval-- 2 %stopped_push --nostringval-- --nostringval-- -- nostringval-- false 1 %stopped_push 1862 1 3 %oparray_pop 1861 1 3 %oparray_pop 1845 1 3 %oparray_pop 1739 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- -- nostringval-- --nostringval-- Dictionary stack: --dict:1155/1684(ro)(G)-- --dict:0/20(G)-- --dict:77/200(L)-- -- dict:10/25(L)-- Current allocation mode is local Last OS error: 2 Current file position is 8177 GPL Ghostscript 8.70: Unrecoverable error, exit code 1 *** Error code 1 *** Error code 1 2 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 1 Stop in /usr/ports/misc/freebsd-doc-en. *** Error code 1 Stop in /usr/ports/misc/freebsd-doc-en. * I have checked html_split and pdf. Now I deinstall and try to install again but I got the same error. Thanks in advance. Something to do with the new Ghostscript version, most of the doc package builds are broken. I was pointed to this patch http://paste.lisp.org/display/92500 and it continued for a while but it errored out again with a different message (Bounding box not found). Still, you may wish to give it a try. ___ 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: APC Smartups 1500va sua1500
On 15/12/2009 4:58 μ.μ., Gary Kline wrote: Guys, A post I send yesterday never showed up, so I'll ask again with the following question: Do we have a driver for the APC SmartUPS 1500VA #sUA1500? gary Use sysutils/apcupsd Works great with all APC products I've tried. ___ 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: 8.0 installation doesn't contain X distributions
Ian Smith wrote: In freebsd-questions Digest, Vol 287, Issue 16, Message: 8 On Sat, 05 Dec 2009 19:39:08 +0200 Manolis Kiagias son...@otenet.gr wrote: However, I do not see any distributions listed that are prefixed with X-. The choices are All, Reset, Developer, Kern-Developer, User, Minimal and Custom. Even the Custom option has nothing related to Xorg. That's correct, these have been removed. Hi Manolis, Look, I'm sorry, but I think this is a huge regression, especially if we're still hoping that people with no prior experience of installing freeBSD, people coming from Linux and such, for essentially or including desktop use, are going to have a rewarding installation experience. Is it supposed to be like this (i.e. no distributions containing X are presented on installation), or do I need to download other media from which to install? Note that I'm not asking how to install X and I realise that I can do it post-installation, but I'm just wondering whether I've made a mistake with my download or if the documentation is out of date. You've done nothing wrong, the documentation is in need of an update. Please file a doc-bug PR. Removing X from the distributions is a right step IMO, these are just 3rd party packages and it seems confusing if they get installed along with the base system. I think this is taking base-system-only installation purity to excess. On the other hand, I feel it is confusing when you find yourself essentially selecting packages in the menus for the base-system components. The DVD *still* has the packages, and you are still asked if you wish to install any. Xorg is just one click away - select the meta-package and the entire thing goes in. Fine for people installing servers of course, and maybe it will shift more people wanting a GUI environment towards PC-BSD and such if we want to discourage these from using FreeBSD as it is (or maybe, was) but even with my 11 years experience of installing FrreeBSD versions from 2.2 till now, I kept on wondering, how would a newbie fare at this point? Having shown the FreeBSD installation to people only acquainted with Windows or Ubuntu, I always get the same reaction: Completely disheartening, confusing, complex. You need to know too many things and when everything is done right, you are just rewarded with a console login. This is a fact: FreeBSD is not for the faint of heart, and definitely not for someone who wants a desktop in five minutes. You have to get past the initial shock and devote a lot of time to learn your way around the system. This requires considerable effort and there are lots of people who have neither the time nor the inclination to dig deep into an OS - they just want a working desktop. IMHO an extra click for the Xorg is not that much important in the grand scheme of things. I think it would be best if beginners are informed beforehand that they really need to study: you will not get a working desktop FreeBSD 'by chance' or because someone else configured the defaults for you and you just restored an image to your hard drive (as I understand, this is what most desktop-oriented Linux distros do these days) Now if we delve deeper into this we are going to hit philosophical questions like Do we want ignorant users? Is our setup procedure so discouraging that even would-be-knowledgeable users abandon the system early? Should we provide an Ubuntu-like BSD install? I can live with sysinstall myself, although I don't really like it. There are numerous problems with it (and we had a long thread in the past about it, so I am not going to repeat myself) with the added fact that as the system progresses to new features (journaling, ZFS, gpart ...) sysinstall stands still and does not provide any way to use them during initial setup. I've introduced more than a few beginners to FreeBSD. I always warn them beforehand what to expect - I only continue with those who are prepared to study the handbook and a few (hundred...) pages of my introductory notes. All of them are now happy, satisfied users. But none expected to have a working desktop in five minutes. There are other distributions for that (PC-BSD, Ubuntu) If you wish to install X during initial installation you can still do it when you get to the packages stage. I believe you will need the DVD for that. I used the memstick.img (discussed in another thread) and then FTP for installing packages. I've done this before using bootonly CDs, and it has advantages and disadvantages; for me it's been mostly positive. The main advantage is access to all packages. If you know what you want, and which categories they live in, it's great; an hour or so picking and away you go (modulo failures with this FTP site or that). There still exist people with slow net connections and older, slower kit for whom building everything from source would
Re: 8.0 installation doesn't contain X distributions
Polytropon wrote:
On Thu, 10 Dec 2009 19:47:08 +1100 (EST), Ian Smith smi...@nimnet.asn.au
wrote:
In freebsd-questions Digest, Vol 287, Issue 16, Message: 8
On Sat, 05 Dec 2009 19:39:08 +0200 Manolis Kiagias son...@otenet.gr wrote:
Removing X from the distributions is a right step IMO, these are just
3rd party packages and it seems confusing if they get installed along
with the base system.
I think this is taking base-system-only installation purity to excess.
Imagine the following situation: A user wants to run Linux
applications on FreeBSD. He selects the Linux ABI service
for startup via sysinstall. The corresponding _enable setting
will be added to rc.conf, and - surprise! - a package will
be installed.
The same thing happens when a user installs X. Of course, X
is not part of the base system, but in the same way that
sysinstall (down)loads and installs packages when a specific
service is selected, it should act the same way for X.
I know that X has become a problematic and very complex
thing, not just a few packages (as it was in the past
with XFree86).
X should be installabe in a manner made easy, just like
the Linux ABI.
In the case of X,
you and I, developers and most people here know to hunt for the Xorg
meta-port.
The average user intending to run a desktop system won't
be happy with compiling stuff...
Exactly. Most desktop users want a working system in the minimum of time
(Can't blame them for that).
Even with packages, we cannot beat an image-based distro, esp. since it
will also provide all essential default settings.
But the naive or new installer knows of no such thing, and
could beat around in the huge lists of X software for ages, wondering
what's required and what's not to get a desktop going.
Therefore, I always liked the choice for X in sysinstall: It
basically installed all the components to get X up and running.
No big trouble getting the correct xorg-driver-* packages,
installing and removing them, the xorg-input-* packages with
the same story...
There is an X.org meta-package that installs everything though. It is
just a problem with the beginner not knowing what to select. This can be
tackled in two ways IMO, first is by creating a First time FreeBSD
desktop installer type article, second would be adding a menu choice in
sysinstall Install a standard X desktop {GNOME,KDE}. I must admit I
much prefer the first solution.
___
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: 8.0 installation doesn't contain X distributions
Mehmet Erol Sanliturk wrote: On Thu, Dec 10, 2009 at 9:01 AM, Reed Loefgren rloefg...@forethought.netwrote: Exactly. Most desktop users want a working system in the minimum of time (Can't blame them for that). Even with packages, we cannot beat an image-based distro, esp. since it will also provide all essential default settings. If I might butt in: If the user-to-be wants a working system in 5 minutes could there be a link on the FreeBSD homepage itself directing them to PC-BSD (or similar) .ISOs? Perhaps with an addendum that, while they can download and install FreeBSD 'straight up, no chaser' using an image from the FreeBSD page, it *isn't* going to be 5 minutes and perhaps a derivative version might be their best bet. Just a thought, r After trying installation of FreeBSD 8.0 Release ( before RCs ) without success ( Gnome : Some menu elements are not working , for example shutdown , it is becoming necessary to open a terminal and explicitly write shutdown -p now , it is not possible to every thing by terminal or GUI elements ) , You are probably missing policykit/hal settings. Have a look at: http://www.freebsd.org/gnome/docs/halfaq.html ( KDE4 : Konsole not working because after a short show of terminal window , it is disappearing , it is not possible to do every thing without Konsole ) , Haven't used KDE4 in FreeBSD for a while so I can't really say. I have built some packages but not used them yet. ( XFCE - It is becoming rock solid due to key board insensitivity , on the same computer many operating systems are working , from FreeBSD to many Linux distributions ) . After those attempts , I have installed DesktopBSD 1.7 . I can say that it is a WONDERFUL FreeBSD distribution based on FreeBSD 7.2 and KDE4 where FreeBSD 7.2 from www.FreeBSD.org can not be compared with its beatiness . You do realize of course that DesktopBSD *is* FreeBSD with many of these settings and defaults pre-applied for you? Obviously the DesktopBSD developers do a wonderful job on it, but it is also possible to build this yourself using FreeBSD and ports. It will take more time, it will be more tedious and you will learn a lot of stuff. And you will have a lot more control of what gets installed and how the final system behaves. Obviously these are less important factors, if the purpose is to have a desktop system as quickly as possible. Now , I am waiting FreeBSD 8.x from www.FreeBSD.org , where x 0 , with the hope that it will be possible to have an easily usable FreeBSD distribution . You may also want to give PC-BSD a try. ___ 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: 8.0 installation doesn't contain X distributions
Nicky Chorley wrote: Hi, I downloaded the DVD ISO for FreeBSD 8.0 (i386) and verified the MD5 checksum before burning. With regards to choosing distributions for installation, the handbook says If a graphical user interface is desired then a distribution set that is preceded by an X should be chosen and the help for the Choose Distributions section of sysinstall says An X- prefixed before a distribution set means that the Xorg base distribution, libraries, manual pages, servers and a set of default fonts will be selected in addition to the set itself... However, I do not see any distributions listed that are prefixed with X-. The choices are All, Reset, Developer, Kern-Developer, User, Minimal and Custom. Even the Custom option has nothing related to Xorg. That's correct, these have been removed. Is it supposed to be like this (i.e. no distributions containing X are presented on installation), or do I need to download other media from which to install? Note that I'm not asking how to install X and I realise that I can do it post-installation, but I'm just wondering whether I've made a mistake with my download or if the documentation is out of date. You've done nothing wrong, the documentation is in need of an update. Please file a doc-bug PR. Removing X from the distributions is a right step IMO, these are just 3rd party packages and it seems confusing if they get installed along with the base system. If you wish to install X during initial installation you can still do it when you get to the packages stage. I believe you will need the DVD for that. ___ 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: binary upgrade 6.2
Alex Huth wrote: Hi! I am trying to upgrade a 6.2-RELEASE to 6.4-RELEASE, but `freebsd-update -r 6.4-RELEASE upgrade` is not available in this version. Can i upgrade this or do i have to go the old way? Unfortunately the `pkg_add -r cvsup` does not find the package for it. Thx Alex You will have to download a version of freebsd-update for 6.2. There are instructions here: http://www.freebsd.org/releases/6.3R/announce.html under FreeBSD Update. and also more details on C. Percival's blog: http://www.daemonology.net/blog/2007-11-10-freebsd-minor-version-upgrade.html Done this for 6.2 to 6.3 back in the day, and it worked fine. I believe you will have no trouble going to 6.4 as well. Just a quick note: Make sure you have enough space under /var. There is a /var/freebsd-update directory there that holds a lot of data during the upgrade, and later releases always bring in more data. If /var is mostly full, symlink /var/freebsd-update somewhere in /usr. This has saved me once. ___ 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 do i automate building packages?
Gary Kline wrote: How do I build tarballs of packages that usually wind up in /usr/ports/packages? I thought I had something in /etc/make.conf, but nope. My build of OOo [311] recently finished on my new to-be server. Since both the new Dell and this older Dell are running 7.2, I figure I can do any builds and move the packages across. I thought I had seen foo.tgz in /usr/ports/bar/foo/; but this time, no expected tarball. --??-- A man ports isn't very clear. I usually type make install clean when I build anything. If I have to start over from scratch with openoffice would I type # make install package clean? Or what? anybody? Now that you got it installed, you may use pkg_create: pkg_create -Rb openoffice.org-3.1.1 (You can get the exact package name using pkg_info -Ix openoffice) The -R flag will also build all dependencies of openoffice. Something along the lines of the following script: #! /usr/bin/env bash mkdir -p /usr/ports/packages cd /usr/ports/packages rm -rf *.tbz echo Package creation starting `date` IFS=$'\n' for i in `pkg_info -Ea` do echo Creating $i pkg_create -b $i done echo Finished, `date` will create a package for every single port installed on your system and place it in /usr/ports/packages. You can then move these and install them on another system. Notice the script does not use -R as it is already building all packages :) ___ 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
ANNOUNCE: FreeBSD 8.0-RELEASE Custom XFCE build available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey all, After the successful release of 8.0, I am pleased to announce that I have updated my little project here: http://freebsd-custom.wikidot.com to provide an XFCE DVD based on the new release. Here are the direct download links: http://freebsd.dev-urandom.com/iso/i386/xfce-desktop/8.0-RELEASE-i386-XFCE-27112009.iso Checksum and signature files: http://freebsd.dev-urandom.com/iso/i386/xfce-desktop/8.0-RELEASE-i386-XFCE-27112009.iso.CHECKSUM.MD5 http://freebsd.dev-urandom.com/iso/i386/xfce-desktop/8.0-RELEASE-i386-XFCE-27112009.iso.CHECKSUM.SHA256 http://freebsd.dev-urandom.com/iso/i386/xfce-desktop/8.0-RELEASE-i386-XFCE-27112009.iso.asc Make sure to read the README file: http://freebsd.dev-urandom.com/iso/i386/xfce-desktop/README-8.TXT as it contains important information on installation (there are some differences in sysinstall between 7.X and 8.0) Note: While the above files are i386 only, a 64bit version is also on the works as I now have some suitable hardware available. It will become available in 7-10 days. Note this release includes the latest openoffice 3.1.1 as well as abiword / gnumeric for those who prefer them. Gnash has been dropped (linux flash plugin works very well now) and avant-window-navigator is also included (but is untested). Latest versions of well known packages (gimp, inkscape, evince, firefox35 etc) are included as well. This is the same selection of packages as the ones included in the 8.0-RC1 version of the iso, but they are of course updated to the latest versions. The documentation packages for all available languages are included on the disc. As always, please report any problems, success stories, comments and criticisms to mano...@freebsd.org Thanks and happy FreeBSDing! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksRXmEACgkQZ/MxGm4PtJQ6tQCdGuRNp9kkV0giFwB5ggx5AbJ4 KekAn1+uQesOOBF5yGxqdBAy5DtCBinJ =fBm8 -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: TeXlive2009 binaries for FreeBSD 6,7,8 (i386/AMD64)
acheron wrote: Hi, I just got the news of someone who build binaries of TeXlive 2009. http://tug.org/pipermail/tex-live/2009-November/023783.html This is great news, thanks for sharing. I was looking forward to get TexLive 2009 running on FreeBSD. ___ 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: FreeBSD 8.0 and Atheros AzureWave wireless chipset
Brett Glass wrote: However, the machine still boots. And hyperthreading is enabled, because the Atom has HTT. (I have been thinking of disabling it, because hyperthreading may not work very well on the Atom. Does anyone know how to do this properly? I tried setting machdep.hlt_logical_cpus to 1 in /boot/loader.conf and was rewarded with a system crash at boot time.) In /boot/loader.conf try: machdep.hyperthreading_allowed=0 Though it seems hyperthreading is improved on the Atom and there is no penalty for leaving it on. ___ 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: HTT on Atom (Was: FreeBSD 8.0 and Atheros AzureWave wireless chipset)
Brett Glass wrote: At 04:33 PM 11/26/2009, Manolis Kiagias wrote: Though it seems hyperthreading is improved on the Atom and there is no penalty for leaving it on. Is there really no penalty? With HZ=1000 there are double the clock interrupts to be serviced at least. And as I understand it the Atom has less redundant hardware, so there are less likely to be unused resources available to the second thread. I am seeing substantially faster compiles with the SMP option commented out of the kernel. --Brett My tests involved building a custom kernel - I never tried without SMP, just without hyperthreading and there was no appreciable difference. Using -j3 in make kernel, the kernel is built in just about 40 minutes. Without -j same procedure lasts 55 minutes. (I am using an Atom 330 which is dual core) On a Pentium 4 with HTT, -j actually results in a somewhat slower build. ___ 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: 7.2-STABLE to 8-R
John wrote: Hello list I've looked high and low for a howto/link showing how to update to 8, to no avail. Is it just a case of the regular buildworld process or are there gotchas because we are crossing major version numbers. You can go the source way or the 'freebsd-update' way. Either way, you will have to rebuild all ports. Detailed instructions are in the Handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html (see 24.2.3) ___ 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: moving an entire system
n dhert wrote: I want to move the contents of a freebsd72 system entirely to different hardware (also Intel 64-bit), using dump/restore These are the filesystems now: /dev/da0s1a 2026030650876121307235%/ /dev/da0s1e20308398652820 18030908 3%/tmp /dev/da0s1f95719170 12449998 7561164014%/usr /dev/da0s1d20308398 2960282 1572344616%/var /dev/da1p1 2175407698 168279068 1833096016 8%/home How should one proceed? I have an 286 Gb external USB disk formatted with a single slice large enough to hold all dumps of all fileystems, mounted on /seagate /dev/da2s1a 28381012612 260463064 0%/seagate a. put the original machine in single-user mode b. use dump (could L be left out if machine is in single-user mode?) yes /sbin/dump -0aL -f /seagate/dumpofroot.dmp /dev/da0s1a /sbin/dump -0aL -f /seagate/dumpoftmp.dmp /dev/da0s1e /sbin/dump -0aL -f /seagate/dumpofusr.dmp /dev/da0s1f /sbin/dump -0aL -f /seagate/dumpofvar.dmp /dev/da0s1d /sbin/dump -0aL -f /seagate/dumpofhome.dmp /dev/da1p1 so far so good. You probably don't need to dump /tmp. c. on the target machine, do a complete install of freeBSD72 from CD with same partition layout as original machine No need. Just boot using the DVD or LiveFS and select the fixit option, and the 'Use the Live CD/DVD filesystem' (On the target machine /home will be on /dev/da0s1g (no longer on /dev/da1p1)) d. target machine, plug in the external USB disk and mount it # mkdir /seagate # mount /dev/da2s1a /seagate e. restore file systems How exactly ? is this ok for /home : # umount /home # /sbin/newfs /dev/da0s1g # /sbin/mount /dev/da0s1g /mnt # cd /mnt # /sbin/restore rf /seagate/dumpofhome.dmp # umount /mnt # mount /dev/da0s1g /home for /tmp, /usr and /var? It is safe to use same procedure? or else, how to do ? And what for / file system ??? will same procedure work ? First off, use the fdisk option of sysinstall to create a slice. Press w to exit, so the slice table is immediately written to disk. You may also use sysinstall to create the individual partitions, although this can be accomplished with bsdlabel once you are at the prompt. Install the MBR and boot blocks (assuming /dev/da0 is your boot disk and /dev/da0s1 is the FreeBSD slice): fdisk -B /dev/da0 bsdlabel -B /dev/da0s1 newfs all the new partitions, using -U for soft updates where needed. Usually soft updates are used in /var /usr and /tmp newfs /dev/da0s1a newfs -U /dev/da0s1d newfs -U /dev/da0s1e newfs -U /dev/da0s1f and so on. You may also add journaling (gjournal) at this point, it is actually quite easy. You will need two temporary mount points, one for your external drive and one for the partition you will be restoring. The /mnt is available as a mount point in the LiveFS cd, create another temporary one: mkdir /seagate Now, mount your backup in /seagate: mount /dev/da2s1a /seagate Mount one of the new partitions in /mnt: mount /dev/da0s1a /mnt cd /mnt TMPDIR=/seagate restore -rvf /seagate/dumpofroot.dmp Note: restore will need some tmp space, hence the TMPDIR Before you umount /, edit at least /mnt/etc/fstab and fix your device entries with the new ones. cd / umount /mnt Repeat with all other partitions. Don't forget to newfs the /tmp partition that you will not be restoring. I hope you get the general idea, you will have to adjust this slightly for your needs. After the first normal boot: chmod -R 1777 /tmp chmod -R 1777 /var/tmp (set sticky bit on temp space) ___ 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: Wiki down?
Matias wrote: Can any of you access http://wiki.freebsd.org ? Seems down from here I'm getting a 503 error. Same here, I am sure it is probably something temporary though. ___ 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: no sshd on new server...
Polytropon wrote: On Tue, 17 Nov 2009 14:38:45 -0800, Gary Kline kl...@thought.org wrote: On Tue, Nov 17, 2009 at 07:54:14PM +0200, Manolis Kiagias wrote: Gary Kline wrote: There is a question during sysinstall: Would you like to enable ssh login? Guess you answered no there? i didn't see this question -- or don't remember seeing it. Well, it't not SUCH a question. :-) Yes, there is: http://twitpic.com/q0wxq But see note below. In the dialog Post Configuration where you can set the services that should be run on startup, there's a choice SSH which will put the correct setting in /etc/rc.conf, causing the SSH server to generate the keys at its first start. Or maybe I'm wrong and the setting was in the Networking menu... Yes, it is in Configure - Networking also as a checkbox. Regarding the question during setup, this may not appear depending on the type of installation. For me, I always select Standard and then Custom from the Select Distributions list. At the end of the install there is always this dialog: http://twitpic.com/q0xs7 with questions on networking, ftp server, ssh and so on. I am so accustomed to pressing these keys all the time I definitely don't know whether there is a difference in the other sysinstall routes :) ___ 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: no sshd on new server...
Gary Kline wrote: On Tue, Nov 17, 2009 at 04:01:17PM +0100, Polytropon wrote: On Mon, 16 Nov 2009 15:12:36 -0800, Gary Kline kl...@thought.org wrote: On Mon, Nov 16, 2009 at 08:31:49PM +0100, Polytropon wrote: By the way, it's not a problem if /etc/rc.conf is empty. In this case, defaults are used, but: % grep sshd /etc/defaults/rc.conf sshd_enable=NO# Enable sshd As you see, sshd_enable is set to NO by default. darn, but that would've been that last thing i would have expected... . i dont see any rationale... Rationale: Secure by default. Ermm... wait, that was a different OS. :-) At least, there's no telnet enabled by default with empty root password... :-) all right, all right. it might be better to default on the side of security. but it takes s much more to login remote via ssh that it seems fairly secure to me if it were enabled. ... . There is a question during sysinstall: Would you like to enable ssh login? Guess you answered no there? ___ 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: where to find libintl.so.8
Len Conrad wrote: FreeBSD 6.2-RELEASE FreeBSD 6.2-RELEASE #0 portsnap'd today running ver 1.2.8 of rdiff-backup which gets: ImportError: Shared object libintl.so.8 not found, required by librsync.so.1 thanks Len This is installed by the devel/gettext port. It is probably installed in your machine (most ports depend on it) but something may have gone wrong during a portupgrade. /usr/ports/UPDATING states the following for gettext upgrades: As a result of the upgrade to gettext-0.17, the shared library version of libintl has changed, so you will need to rebuild all ports that depend on gettext: # portupgrade -rf gettext # portmaster -r gettext I suggest you try one of these commands. (Check with 'pkg_info -Ix gettext' first to see what gettext you are running) ___ 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: Trivial questions about CNTL-ALT-DEL and CNTL-ALT-BACKSPACE
Philipp Lengemann wrote: Am Sun, 15 Nov 2009 15:19:29 -0800 schrieb Ronald F. Guilmette r...@tristatelogic.com: I _did_ go and read the Handbook section that Manolis Kiagias kindly posted a link to, and I have now tried _both_ of the two ways described there to re-enable CNTL-ALT-BACKSPACE functionality for the X server, and sadly I must report that for me, at least _neither_ of those methods worked Put the following to your xorg.conf: snip Section ServerFlags Option DontZap off Option AllowEmptyInput off Option AutoAddDevices off EndSection Section InputDevice Option XkbOptions terminate:ctrl_alt_bksp EndSection /snip This works for me very reliable (xorg-7.4_2). If you stick with HAL however (using AllowEmptyInput bypasses the autodetection), you can just use the policy file in the Handbook and just add the DontZap option in ServerFlags or ServerLayout section. In fact, I've just written a patch for the Handbook that adds this information and will be committed soon. In the meantime, you can view it here: http://www.freebsdgr.org/handbook-mine/x-config.html ___ 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: Trivial questions about CNTL-ALT-DEL and CNTL-ALT-BACKSPACE
Polytropon wrote: On Mon, 16 Nov 2009 19:35:54 +0200, Manolis Kiagias son...@otenet.gr wrote: If you stick with HAL however (using AllowEmptyInput bypasses the autodetection), you can just use the policy file in the Handbook and just add the DontZap option in ServerFlags or ServerLayout section. ^^ Or? Arbitrary locations again? :-) Hehe, both places will work actually. A default xorg.conf generated with the '-configure' option, will not have a ServerFlags section (which is entirely optional), but will certainly have a ServerLayout one. 'DontZap' (and other options) work in both places. Disclaimer: jokeXorg people will probably break this again in about 15days. Handle with care!/joke ___ 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: Trivial questions about CNTL-ALT-DEL and CNTL-ALT-BACKSPACE
Ronald F. Guilmette wrote: Many thanks to those who responded regarding my two questions. With regards to the CNTL-ALT-BACKSPACE sequence and its ability (or lack thereof) to cause an immediate shutdown of the X server... well... I _did_ go and read the Handbook section that Manolis Kiagias kindly posted a link to, and I have now tried _both_ of the two ways described there to re-enable CNTL-ALT-BACKSPACE functionality for the X server, and sadly I must report that for me, at least _neither_ of those methods worked. I did everything exactly and precisely as described. I even cut and pasted the code in the Handbook that was suggested for the /usr/local/etc/hal/fdi/policy/x11-input.fdi file, and still, CNTL-ALT-BACKSPACE is producing no effect whatsoever for me. This is on 7.2-RELEASE/amd64. What now? send-pr? Keep the x11-input.fdi section from the Handbook, and also add the following line to /etc/X11/xorg.conf, at the end of the ServerLayout section: Option DontZap false Restart your system, it should work now. (Just tried it on mine. It won't work without both of these changes). Please report back if it works for you! By the way Xorg configuration becomes more and more elusive. Initially, DontZap was enough. Then it had no effect at all and the fdi file was needed. Now seems both are needed. What's next? I'll test this in a few other systems and update the Handbook section if it seems to be the latest norm. Thanks! ___ 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: no sshd on new server...
Gary Kline wrote: ok, i have my new server-to-be underway but having problems exec'ing /usr/sbin/sshd. i can ssh out to existing computers, but cannot ssh or scp stuff in. so my question is: how do i create /etc/ssh/ssh_host_dsa_key ? checking around does no good. tia for any insights, gary Add: sshd_enable=YES to /etc/rc.conf and then execute: /etc/rc.d/sshd start (or reboot your system) The keys will be automatically created at first startup of the ssh daemon ___ 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: Trivial questions about CNTL-ALT-DEL and CNTL-ALT-BACKSPACE
Polytropon wrote: On Mon, 16 Nov 2009 01:49:04 +0200, Manolis Kiagias son...@otenet.gr wrote: By the way Xorg configuration becomes more and more elusive. Initially, DontZap was enough. Then it had no effect at all and the fdi file was needed. Now seems both are needed. What's next? If this continues, I'll run my 5.4-p8 workstation with old fashioned X (already X.org) until I die. :-) I feel your pain... No, honestly: X is going to be more and more annoying. Have you noticed the long startup time? Nearly a half minute (!!!) Don't have any startup time problems myself. I mostly run on Atom CPUs, nothing fancy. on a 1.5 GHz system! I know that there is lots of work done to make life easier for X developers, especially getting rid of many OS specific stuff, but... Finally, sliding more off-topic: Not only X gets slower with each release, the same applies for almost all X applications, except the old fashioned ones. Just the fact that I now have to edit an xml file to simply add a Greek keyboard layout is annoying enough. Combine with the fact that for some reason keyboard / mouse may or may not be detected depending on the machine, phase of the moon etc, needing AutoAddInputDevices and AllowEmptyInput hacks, I'd call it nightmare on HAL street... But that's enough ranting for tonight, I had an entire blog post complaining about it. Let's just hope we can cope with the documentation changes so we have some place to resort to! ___ 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: Remote re-installation of current FreeBSD system.
Polytropon wrote: A little sidenote: On Fri, 13 Nov 2009 15:28:04 -0500, Roger rno...@gmail.com wrote: The reason for wanting to re-install is because I only have on big slice that covers the entire harddrive and I don't want that. Primarily I would like to have /usr/local in a separate slice. In most cases, you set up one slice covering the whole disk, and then partition it, giving functional parts an own partition, such as /, /var, /tmp, /usr (including or intendedly excluding /usr/local) and /home. Those are partitions, not slices. As far as I know, there's no advantage in adding additional slices to that concept. A slice is a DOS primary partition, while a partition is just a subdivision (i. e. an own file system) inside a slice. It seems however that some dedicated servers are setup using a single slice and a single partition, i.e. having /usr /var and /tmp as subdirectories in / instead of separate filesystems. I was once administering a server setup in this way - the hosting company would only perform this kind of install (they probably had a ready image or dump and would not change it). If the OP cares to share his /etc/fstab, it will become obvious if this is the case. If there are already separate partitions inside the slice, I'd agree there is no compelling reason to move to a multiple slice system. ___ 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: libjpeg.so.9 missing from my installation of FBSD 7.2
Henry Olyer wrote: I very much appreciate the help I get here. And boy!, do I need it. Undoubtedly I did something wrong when I was putting my system together. But I just can't throw it away -- I'm trying to get some things done. So, awk! help! Where you performing an upgrade of an existing system? AFAIK libjpeg.so.* libraries get installed by the graphics/jpeg port. This was (fairly) recently upgraded, and if you did not follow the /usr/ports/UPDATING instructions carefully, you probably ended up with some dependent apps still linked to the old version of the library. See /usr/ports/UPDATING: 20090719: AFFECTS: users of graphics/jpeg AUTHOR: din...@freebsd.org The IJG jpeg library has been updated to version 7.0. Please rebuild all ports that depend on it. In short, try the following (assuming you use portupgrade): portupgrade -fr graphics/jpeg ___ 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: libjpeg.so.9 missing from my installation of FBSD 7.2
Robert Huff wrote: Manolis Kiagias writes: Where you performing an upgrade of an existing system? AFAIK libjpeg.so.* libraries get installed by the graphics/jpeg port. This was (fairly) recently upgraded, and if you did not follow the /usr/ports/UPDATING instructions carefully, you probably ended up with some dependent apps still linked to the old version of the library. In short, try the following (assuming you use portupgrade): portupgrade -fr graphics/jpeg graphics/jpeg is a dependency for a _lot_ of ports. (100+ on my system.) Were I in the OP's shoes, I'd run pkg_info -R to find out which ones and feed the (edited) results through pkg_sort. Otherwise I might find myself rebuilding something like OpenOffice at an inopportune moment Robert thirty six hours and counting, tra-la Huff I am afraid openoffice is indeed one of the packages linked to jpg.. In this case - and assuming this was caused by an improper upgrade of jpeg - maybe the OP could simply downgrade just the jpeg port to the previous version. The current version provides libjpeg.so.10 ___ 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: Trivial questions about CNTL-ALT-DEL and CNTL-ALT-BACKSPACE
Ronald F. Guilmette wrote: I've just been installing 7.2-RELEASE/amd64 on a fresh/wiped system that I plan to use as my future main workstation. Anyway, I've already noticed a couple of things that seem to be different from prior release that I need to ask about, i.e.: 1) It appears that CNTL-ALT-DEL now causes a shutdown/reboot. (I don't know what release this new feature started in... I only just noticed it now.) Anyway, I'd like to know how I can disable this particular bit of functionality. How do I do that? Add: hw.syscons.kbd_reboot=0 to /etc/sysctl.conf. Activate immediately by executing sysctl hw.syscons.kbd_reboot=0 2) Prior versions of X (Xorg?) allowed CNTL-ALT-BACKSPACE to cause an immediate shutdown of the X server, but now, that doesn't see to work anymore. How can I (re-)enable this functionality? Welcome to the new Xorg and HAL... Please read this: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html There is a note that describes how to re-enable CTRL+ALT+BKSP functionality. ___ 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: best way to install/update software and firewall choice
Guy Marcenac wrote: Hi, I am an old debian user and I am looking at freebsd for security reasons * I am very interested in the jail concept * I have to relearn iptables syntax each time I want to add a rule Don't we all :) I am testing the system in vmware virtual machine. There is a point I don't fully understand. There are several ways of updating the system, from precompiled binaries or by recompiling the system and the ports (and using csup, portsnap, portupgrade ...). To update your base system, you can use freebsd-update. This uses precompiled binaries and also updates the relevant sources (assuming you have them installed beforehand and you are using the default freebsd-update configuration - which is recommended). However if you are going to run jails, this advantage is more less defeated: you will have to run 'make buildworld' anyway to install the result in the jails. I would prefer to use the first way because it is really faster, but it seems to me that when I want to update my jails, there is no other easy way than recompiling the whole world into my jails. Yes, unless you can somehow run freebsd-update from inside a jail :) Don't know if this will work though. It will probably fail trying to patch the kernel. If you use freebsd-update you will only 'make installworld' for the jails, as the 'host' will be taken care of by freebsd-update binary patching. You still need the make buildworld step, so you don't really gain much. The other point a bit confusing is that I dont know which firewall to use. My first guess would be to use pf, because it exists also on openbsd, but it seems that the default would go to ipfw. I am using pf too. It is a matter of preference and features needed. I suggest you read the Handbook chapter and decide for yourself. ___ 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: Effing HAL
Bruce Cran wrote: On Thu, 29 Oct 2009 23:15:08 + Freminlins freminl...@gmail.com wrote: Yeah, thanks for that. I knew about that file, but don't often read it. There's even more to the saga - Xkblayout doesn't work. This whole HAL thing stinks horribly. IF X is built with HAL basically certain options specified in xorg.conf no longer work. HAL thinks it knows best. But it doesn't, cos it's broken. Xkblayout doesn't work because you need to use fdi files now. http://ubuntuforums.org/showthread.php?t=948154 has some details - essentially you need to put some XML in /usr/local/etc/hal/fdi/policy/ that tells it what layout to use. It's rather frustrating that information is scattered in forums - I couldn't see any official-looking articles on configuring it. You were not looking in the right place then: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html ___ 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: freebsd 6.4 can't load kernel after upgrade
oscar Seo wrote: I'm a beginner in freebsd. my machine consists of freebsd-6.4 + i386 bootstrap loader,+ windowmaker after upgrade freebsd-6.4 using sysinstall then reboot the system, I got an error message as follows +++ Loading /boot/defaults/loader.conf Unable to load a kernel! / can't load 'kernel' Type '?' for a list of commands, 'help' for more detailed help. OK _ +++ so I decided to reinstall freebsd-6.4 but I can't boot and re-install freebsd using CD-rom. what shall I do boot my system using installed freebsd or live-CD ? Thanks... You could try loading your old kernel. When you build a new kernel, your old kernel is preserved under /boot/kernel.old Type these commands in the loader prompt unload (probably not needed here) load kernel.old boot See section 12.3.3.3 for more examples and details http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/boot-blocks.html#BOOT-LOADER ___ 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: WD External Disc Drive
Rob Hurle wrote: Thanks for your comments too, about use of the FAT32 file system. I had thought about that, but the NTFS seemed to be a bit more universal - I'm not sure that FAT file systems are recognised by default on Macs (for example). FAT (and almost to the same extent, FAT32) are widely recognizable: FreeBSD, Windows, Linux, OS X. The most important limitation though is maximum file size (=4GB). Depending on your usage, FAT32 may or may not be appropriate because of 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: WD External Disc Drive
Rob Hurle wrote: Dear All, This may sound like a Windows problem, but please read on. I made a mistake and bought a WD My Passport external 350GB disc drive for use on several Windows machines, on some of which I don't have admin access, and a couple of FreeBSD systems. On first use on Windows the disc shows up only as a virtual CD (I assume this is the firmware), unlock.exe has to be run and the software installed (admin privileges necessary). Once it's unlocked and the software installed, the big disc appears, the software can be uninstalled, and the big disc reformatted as NTFS. From then on, the virtual CD can be ignored and the big disc used on any Windows system. Now to FreeBSD. The newly formatted (as NTFS) disc appears as two devices - /dev/cd0 (never seen this before) This is how a USB cdrom appears to FreeBSD - as a SCSI device. No problem there. and /dev/da0s1 (the normal USB disc drive device). They can be mounted as follows: freebsd [10:45] ~#mount_udf /dev/cd0 /mnt freebsd [10:45] ~#mount /usb0 (/etc/fstab describes the NTFS file system type, and the virtual CD is a UDF file system). We now have: freebsd [10:46] ~#df Filesystem 1K-blocksUsed Avail Capacity Mounted on /dev/cd0582962582962 0 100%/mnt /dev/da0s1 311877845 2332729 309545116 1%/usb0 If we look at each device, the virtual CD has the WD software, as expected: freebsd [10:45] ~#ll /mnt total 6300 drwxr-xr-x 3 501 staff 2048 12 Sep 05:32 Extras -rwxrwxrwx 1 501 staff 3680544 5 Sep 08:20 Unlock.exe drwxrwxrwx 5 501 staff2048 5 Sep 08:30 User Manuals drwxr-xr-x3 501 staff2048 12 Sep 05:28 WD SmartWare -rwxrwxrwx 1 501 staff 2770208 5 Sep 08:20 WD SmartWare.exe -rwxrwxrwx 1 501 staff 695 19 Jun03:06 What is this.html -rwxrwxrwx 1 501 staff 88 19 Jun07:12 autorun.inf No problem. Now for the FreeBSD problem. If we look at what's on the big disc (newly formatted as NTFS on a Windows system): freebsd [10:45] ~#ll /usb0 total 75200 -rwxrwxrwx 1 root wheel 2560 23 Apr 2009 $AttrDef -rwxrwxrwx 1 root wheel 0 25 Oct 14:37 $BadClus -rwxrwxrwx 1 root wheel 9746184 23 Apr 2009 $Bitmap -rwxrwxrwx 1 root wheel 8192 25 Oct 14:37 $Boot drwxrwxrwx 1 root wheel0 25 Oct 14:37 $Extend -rwxrwxrwx 1 root wheel 67108864 25 Oct 14:37 $LogFile -rwxrwxrwx 1 root wheel 4096 25 Oct 14:37 $MFTMirr -rwxrwxrwx 1 root wheel 0 23 Apr 2009 $Secure -rwxrwxrwx 1 root wheel 131072 23 Apr 2009 $UpCase -rwxrwxrwx 1 root wheel 0 25 Oct 14:37 $Volume drwxrwxrwx 1 root wheel0 25 Oct 15:54 MyStuff drwxrwxrwx 1 root wheel0 25 Oct 16:23 RECYCLER drwxrwxrwx 1 root wheel0 25 Oct 14:37 System Volume Information The only thing that shows up in Windows is the MyStuff directory, which I put there. I can copy anything from MyStuff to anywhere else on the FreeBSD system, no worries. But if I attempt to copy a new file into the MyStuff directory, I get the following: freebsd [10:46] ~#cp ~/tmp/test /usb0/MyStuff cp: /usb0/MyStuff/test: No such file or directory freebsd [11:08] ~# You are using the ntfs driver that is built-in the FreeBSD kernel. This is read only - you will be able to read from the disc, but not write to it. In order to be able to write to this disc, install sysutils/fusefs-ntfs and use the ntfs-3g command to mount your disk. If you are not going to use the disc to transfer data between Windows and FreeBSD, I would advise you to repartition the disk and create an NTFS partition for your windows data and a FreeBSD partition in UFS format. Just backup any data, and use windows disk management to create an appropriately sized NTFS partition, leaving the rest of the disk unallocated. Then use fdisk and bsdlabel (or sysinstall) in FreeBSD to create a slice and partition for FreeBSD. ___ 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: Mouse and keyboard don't work in Xorg 7.4
Andrey Zhidenkov wrote: I've installed FreeBSD 7.2 with Xorg 7.4 server, but mouse (usb) and keyboard don't work. when I start X server the only way to exit is Ctrl-Alt-F* and kill the process. I've find out that Xorg now uses hal and dbus to configure mouse and maybe this is a problem. It will probably work fine if you add the following two lines into /etc/rc.conf and reboot: dbus_enable=YES hald_enable=YES Have a look at the updated Handbook section that describes this procedure in more detail: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html ___ 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: Mouse and keyboard don't work in Xorg 7.4
Andrey Zhidenkov wrote: On Mon, Oct 19, 2009 at 10:30:27PM +0300, Manolis Kiagias wrote: Andrey Zhidenkov wrote: I've installed FreeBSD 7.2 with Xorg 7.4 server, but mouse (usb) and keyboard don't work. when I start X server the only way to exit is Ctrl-Alt-F* and kill the process. I've find out that Xorg now uses hal and dbus to configure mouse and maybe this is a problem. It will probably work fine if you add the following two lines into /etc/rc.conf and reboot: dbus_enable=YES hald_enable=YES I've added yet, but it doesn't helps ;(. And when I reboot I can't found any hald or dbus messages in dmesg. Have a look at the updated Handbook section that describes this procedure in more detail: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html Thank you, I've readed. I also noticed you have a ServerFlags section with AutoAddDevices off Could you try removing this and see if it works? You may in fact try running X without an xorg.conf at all. ___ 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: I hate to bitch but bitch I must
PJ wrote: (trimmed down) Is entirely possible that I mucked up somewhere and did not do the shutdown -r quite right... anyway, it is working fine now. I still have some minor questions, though... Can glabel be done on a dormant file system and then boot that file system to change the fstab? You mean glabel the file system but still leave it as a normal device name in fstab? Sure, no problem there. The file system can either be mounted using it's /dev/adXX (or /dev/daXX) device name, it's label, or even the ufsid (assuming it is a UFS filesystem, see the section below the glabel example) So basically you can reboot after creating the label without changing the fstab if you wish and change it later when you are certain that glabel worked as you expected. I would think that that would be about the same things ad doing it from a mounted system in SUM. Then, the last question... where does tunefs really come in? .. I ask As others have said (and as explained in Handbook section 19.6.1) tunefs can only create labels for UFS filesystems. Glabel on the other hand is not filesystem specific, you can label anything (for example, you have already labeled the swap space which clearly is not a file system). That makes glabel more suitable IMHO when the purpose is to completely replace the device names in fstab. So in short: - If you wish to create permanent labels for anything including swap space and 'alien' filesystems as well as UFS, use 'glabel label' - If you wish to create temporary labels for anything including swap space and 'alien' filesystems as well as UFS, use 'glabel create' (I doubt this is very useful, but it is an option) - If you wish to create permanent labels for UFS filesystems *only* you have the option of using tunefs. - If you do not wish to create labels yourself and you are only interested in mounting UFS filesystems without using the device names, you can use the ufsid labels that are created automatically when the filesystem is first created. From all the solutions, the only one that covers both UFS and the swap space and is permanent is the 'glabel label' command (hence the example in the Handbook) I hope this clears it up :) ___ 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: I hate to bitch but bitch I must
PJ wrote: Manolis Kiagias wrote: PJ wrote: Manolis, my state of mind is quite clear... and I'm coping with everything quite allright... I'm not about to get mad at anyone or anything... but tell me, honestly, when you see the stuff I have described above? Woldn't that confuse anyone in their right mind? I am sorry, but there is something here, either some mistake on your part or some other weird problem on your system I can not think of. I don't seem to remember glabel ever failing to store metadata, unless 1) The device is non-existing 2) The device is mounted. As a matter of fact, I did the glabel stuff on a machine a few hours ago. This was already fully installed, I rebooted single user and was done in less than 2 minutes. And yes, if you get a metadata error, it means nothing was done so you are *not* to go and change fstab! Could you please send us /etc/fstab and the results of ls /dev/ad* Here are the outputs: fstab: # DeviceMountpointFStypeOptionsDumpPass# /dev/ad12s1bnoneswapsw00 /dev/ad12s1a/ufsrw11 /dev/ad12s1h/backupsufsrw22 /dev/ad12s1g/homeufsrw22 /dev/ad12s1d/tmpufsrw22 /dev/ad12s1f/usrufsrw22 /dev/ad12s1e/varufsrw22 /dev/acd0/cdromcd9660ro,noauto00 linproc /usr/compat/linux/proc linprocfs rw 0 0 df: Filesystem 1K-blocksUsedAvail Capacity Mounted on /dev/ad12s1a 2026030 319112 154483617%/ devfs1 10 100%/dev /dev/ad12s1h 50777034 4 46714868 0%/backups /dev/ad12s1g 50777034 6276538 4043833413%/home /dev/ad12s1d 4058062 36 3733382 0%/tmp /dev/ad12s1f 50777034 5729324 4098554812%/usr /dev/ad12s1e 2026030 176070 1687878 9%/var linprocfs4 40 100%/usr/compat/linux/proc # ls /dev/ad* crw-r- 1 root operator0, 97 Oct 17 16:36 /dev/ad0 crw-r- 1 root operator0, 103 Oct 17 16:36 /dev/ad0s1 crw-r- 1 root operator0, 101 Oct 17 16:36 /dev/ad10 crw-r- 1 root operator0, 106 Oct 17 16:36 /dev/ad10s1 crw-r- 1 root operator0, 121 Oct 17 16:36 /dev/ad10s1a crw-r- 1 root operator0, 122 Oct 17 16:36 /dev/ad10s1b crw-r- 1 root operator0, 123 Oct 17 16:36 /dev/ad10s1c crw-r- 1 root operator0, 124 Oct 17 16:36 /dev/ad10s1d crw-r- 1 root operator0, 125 Oct 17 16:36 /dev/ad10s1e crw-r- 1 root operator0, 126 Oct 17 16:36 /dev/ad10s1f crw-r- 1 root operator0, 127 Oct 17 16:36 /dev/ad10s1g crw-r- 1 root operator0, 102 Oct 17 16:36 /dev/ad12 crw-r- 1 root operator0, 107 Oct 17 16:36 /dev/ad12s1 crw-r- 1 root operator0, 128 Oct 17 16:36 /dev/ad12s1a crw-r- 1 root operator0, 129 Oct 17 16:36 /dev/ad12s1b crw-r- 1 root operator0, 130 Oct 17 16:36 /dev/ad12s1c crw-r- 1 root operator0, 131 Oct 17 16:36 /dev/ad12s1d crw-r- 1 root operator0, 132 Oct 17 16:36 /dev/ad12s1e crw-r- 1 root operator0, 133 Oct 17 16:36 /dev/ad12s1f crw-r- 1 root operator0, 134 Oct 17 16:36 /dev/ad12s1g crw-r- 1 root operator0, 135 Oct 17 16:36 /dev/ad12s1h crw-r- 1 root operator0, 99 Oct 17 16:36 /dev/ad4 crw-r- 1 root operator0, 104 Oct 17 16:36 /dev/ad4s1 crw-r- 1 root operator0, 108 Oct 17 16:36 /dev/ad4s1a crw-r- 1 root operator0, 109 Oct 17 16:36 /dev/ad4s1b crw-r- 1 root operator0, 110 Oct 17 16:36 /dev/ad4s1c crw-r- 1 root operator0, 111 Oct 17 16:36 /dev/ad4s1d crw-r- 1 root operator0, 112 Oct 17 16:36 /dev/ad4s1e crw-r- 1 root operator0, 113 Oct 17 16:36 /dev/ad4s1f crw-r- 1 root operator0, 114 Oct 17 16:36 /dev/ad4s1g crw-r- 1 root operator0, 100 Oct 17 16:36 /dev/ad6 crw-r- 1 root operator0, 105 Oct 17 16:36 /dev/ad6s1 crw-r- 1 root operator0, 115 Oct 17 16:36 /dev/ad6s1a crw-r- 1 root operator0, 116 Oct 17 16:36 /dev/ad6s1b crw-r- 1 root operator0, 117 Oct 17 16:36 /dev/ad6s1c crw-r- 1 root operator0, 118 Oct 17 16:36 /dev/ad6s1d crw-r- 1 root operator0, 119 Oct 17 16:36 /dev/ad6s1e crw-r- 1 root operator0, 120 Oct 17 16:36 /dev/ad6s1f Sorry, but I don't see what this is going to tell you... ad0 is XP; ad10 is minimal FreeBSD 7.2; ad12 is 7.2 on 500gb; ad4 is 7.2 on 80gb; and ad6 is messed up FBSD I'm cheking setting up with clone of ad12 (dump/restore) Now I will try the glabel again... # shutdown now # glabel label rootfs /dev/ad12s1a glabel: Can't store metadata on /dev/ad0s1a shutdown now will get you
