Re: FreeBSD 9 port XORG failed to install
Hi Савельев Владимир, El día Saturday, April 27, 2013 a las 08:59:36PM +0400, Савельев Владимир escribió: Hi, colleagues! I am trying to install FreeBSD 9 to my notebook Acer Aspire V3-571G. Ports I am trying to install: /usr/ports/x11/xorg My issue is that build fails on an unclear reason. Workflow is: 1. Install FreeBSD 2. Install system updates 3. Download and extract latest ports How do you do this exactly? From SVN? cd /usr/ports/x11/xorg make BATCH=YES install clean Please show the last hundred lines of the output of this. Without messages nobody can help you. matthias -- Sent from my FreeBSD netbook Matthias Apitz | - No system with backdoors like Apple/Android E-mail: g...@unixarea.de | - Never being an iSlave WWW: http://www.unixarea.de/ | - No proprietary attachments, no HTML/RTF in E-mail phone: +49-170-4527211 | - Respect for open standards ___ 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 9 and Windows XP
On Sat, 9 Mar 2013 12:07:41 -0800 (PST) leeoliveshackelf...@surewest.net wrote: Good afternoon, FreeBSD enthusiasts. Can FreeBSD 9.1 be installed on a computer on which Windows XP currently resides? If so, how can this installation be done? In particular, is there a way to install 9.1 so that it can be booted from the traditional master boot record? It is important that, when I am done, I can still boot to Windows XP, as I must run some applications not available on FreeBSD. If the idea I am proposing is not feasible with version 9.1, will it work with 8.3? Any comments are appreciated. If this question has already been asked many times before, please just let me know where to look to find the answer. Thanks. Newbie502 As an addon to other answers, you can install VirtualBox, create a minimal hard disk with MBR boot menu that points to the WindowsXP partition. This way you don't need to restart in WinXP. The same can be done from WinXP side, a minimal hd with MBR boot menu to startup the FreeBSD. --- --- Eduardo Morras emorr...@yahoo.es ___ 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 9 and Windows XP
On Mon, 2013-03-11 at 13:51 +0100, Eduardo Morras wrote: As an addon to other answers, you can install VirtualBox, create a minimal hard disk with MBR boot menu that points to the WindowsXP partition. This way you don't need to restart in WinXP. The same can be done from WinXP side, a minimal hd with MBR boot menu to startup the FreeBSD. This does work? I've got XP as VBox's vdi and just a folder to share content with *nix. It would be possible to install XP bootable without VBox to a ntfs partition, to boot it directly and if wanted, to use it also as guest in VBox? I only use VBox to get applications for an iPad and to copy PDFs to an iPad, since ad-hoc networks until now never worked for me, but I also would like to test hardware sometimes, impossible with VBox, so sometimes it would be nice to have a real Windows install. If this should work, will it become impossible to use snapshots made by VBox? Will there be no confusion regarding to different drivers for the XP booted as VBox guest and booted directly? Regards, Ralf ___ 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 9 and Windows XP
On Mon, 11 Mar 2013 14:14:05 +0100 Ralf Mardorf ralf.mard...@rocketmail.com wrote: On Mon, 2013-03-11 at 13:51 +0100, Eduardo Morras wrote: As an addon to other answers, you can install VirtualBox, create a minimal hard disk with MBR boot menu that points to the WindowsXP partition. This way you don't need to restart in WinXP. The same can be done from WinXP side, a minimal hd with MBR boot menu to startup the FreeBSD. This does work? I followed the instructions (only once) from this page http://geekery.amhill.net/2010/01/27/virtualbox-with-existing-windows-partition/ and it works under FreeBSD 8.3 and WinXP. I've got XP as VBox's vdi and just a folder to share content with *nix. It would be possible to install XP bootable without VBox to a ntfs partition, to boot it directly and if wanted, to use it also as guest in VBox? I use it that way, my set up is 2 primary mbr partitions, one with XP ntfs, the other with FreeBSD ufs2+su. VBox installed on both. I only use VBox to get applications for an iPad and to copy PDFs to an iPad, since ad-hoc networks until now never worked for me, but I also would like to test hardware sometimes, impossible with VBox, so sometimes it would be nice to have a real Windows install. If this should work, will it become impossible to use snapshots made by VBox? Will there be no confusion regarding to different drivers for the XP booted as VBox guest and booted directly? Don't know if VBox snapshots are usable, never tried. There's no confusion, WinXP access directly to the XP partition and FreeBSD to FreeBSD partition. If you don't play with VBox internal commands you are safe. I got a dirty fs on FreeBSD when WinXP crashed once. HTH Regards, Ralf --- --- Eduardo Morras emorr...@yahoo.es ___ 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 9 and Windows XP
On Mon, 2013-03-11 at 14:31 +0100, Eduardo Morras wrote: On Mon, 11 Mar 2013 14:14:05 +0100 Ralf Mardorf ralf.mard...@rocketmail.com wrote: On Mon, 2013-03-11 at 13:51 +0100, Eduardo Morras wrote: As an addon to other answers, you can install VirtualBox, create a minimal hard disk with MBR boot menu that points to the WindowsXP partition. This way you don't need to restart in WinXP. The same can be done from WinXP side, a minimal hd with MBR boot menu to startup the FreeBSD. This does work? I followed the instructions (only once) from this page http://geekery.amhill.net/2010/01/27/virtualbox-with-existing-windows-partition/ and it works under FreeBSD 8.3 and WinXP. I've got XP as VBox's vdi and just a folder to share content with *nix. It would be possible to install XP bootable without VBox to a ntfs partition, to boot it directly and if wanted, to use it also as guest in VBox? I use it that way, my set up is 2 primary mbr partitions, one with XP ntfs, the other with FreeBSD ufs2+su. VBox installed on both. I only use VBox to get applications for an iPad and to copy PDFs to an iPad, since ad-hoc networks until now never worked for me, but I also would like to test hardware sometimes, impossible with VBox, so sometimes it would be nice to have a real Windows install. If this should work, will it become impossible to use snapshots made by VBox? Will there be no confusion regarding to different drivers for the XP booted as VBox guest and booted directly? Don't know if VBox snapshots are usable, never tried. There's no confusion, WinXP access directly to the XP partition and FreeBSD to FreeBSD partition. If you don't play with VBox internal commands you are safe. I got a dirty fs on FreeBSD when WinXP crashed once. Thank you :) I'll flag your reply as useful information, perhaps I come back to that later. Regards, Ralf ___ 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 9 and Windows XP
Eduardo Morras emorr...@yahoo.es writes: On Sat, 9 Mar 2013 12:07:41 -0800 (PST) leeoliveshackelf...@surewest.net wrote: Good afternoon, FreeBSD enthusiasts. Can FreeBSD 9.1 be installed on a computer on which Windows XP currently resides? If so, how can this installation be done? In particular, is there a way to install 9.1 so that it can be booted from the traditional master boot record? It is important that, when I am done, I can still boot to Windows XP, as I must run some applications not available on FreeBSD. If the idea I am proposing is not feasible with version 9.1, will it work with 8.3? Any comments are appreciated. If this question has already been asked many times before, please just let me know where to look to find the answer. Thanks. Newbie502 As an addon to other answers, you can install VirtualBox, create a minimal hard disk with MBR boot menu that points to the WindowsXP partition. This way you don't need to restart in WinXP. The same can be done from WinXP side, a minimal hd with MBR boot menu to startup the FreeBSD. It is my understanding that FreeBSD doesn't allow using part of a disk, but grabs the entire disk. That means that VirtualBox can't use partitions on a disk that any other partitions are being used by anything else, including FreeBSD itself. Am I wrong about this? I use VirtualBox using vdmk for an entire disk, but I have never been able to share with anything else. -- Carl Johnsonca...@peak.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 9 and Windows XP
On Mon, 2013-03-11 at 09:05 -0700, Carl Johnson wrote:
It is my understanding that FreeBSD doesn't allow using part of a disk,
but grabs the entire disk. That means that VirtualBox can't use
partitions on a disk that any other partitions are being used by
anything else, including FreeBSD itself. Am I wrong about this? I use
VirtualBox using vdmk for an entire disk, but I have never been able to
share with anything else.
No, this is a misunderstanding. The primary below [1] is the ufs
including my FreeBSD, it's just that Linux's parted doesn't show it
(gparted does show) and I can't access BSD by my Linux installs. And no,
the ntfs isn't Windows.
FWIW my old drives have only one primary and a extended + tons of
logical partitions, but I started to partition new drives with 3 primary
and one extended including as much logical partitions as needed [2].
To have one partition that can be accessed by the BIOS I format one with
fat32, since it can't access ntfs partitions. Most Linux use ext4 by
default, I've got ext3 and ext4, because FreeBSD can share ext3
partitions without issues with Linux.
I'm using GRUB2 from Linux to boot FreeBSD [3], it's sharing a drive
with several Linux installs, more installs anybody does need ;). I'm not
maintaining all installs.
Regards,
Ralf
[1]
[rocketmouse@archlinux ~]$ sudo parted /dev/sda print
Model: ATA SAMSUNG HD321KJ (scsi)
Disk /dev/sda: 320GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End SizeType File system Flags
1 32.3kB 62.1GB 62.1GB primary boot
2 62.1GB 320GB 258GB extended
5 62.1GB 94.1GB 32.0GB logical ntfs
6 94.1GB 126GB 32.1GB logical ext3
7 126GB 158GB 32.2GB logical ext3
8 158GB 185GB 27.0GB logical ext3
9 185GB 223GB 37.7GB logical ext3
10 223GB 225GB 2328MB logical linux-swap(v1)
11 225GB 288GB 62.3GB logical ext3
12 288GB 291GB 3759MB logical ext3
13 291GB 315GB 23.7GB logical ext3
14 315GB 320GB 4927MB logical ext3
[2]
[rocketmouse@archlinux ~]$ sudo parted /dev/sdc print
Model: WD Ext HDD 1021 (scsi)
Disk /dev/sdc: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End SizeType File system Flags
1 1049kB 68.0GB 68.0GB primary ext3
2 68.0GB 138GB 69.6GB primary ext4
3 138GB 413GB 276GB primary ext4
4 413GB 2000GB 1587GB extended
[snip]
[3]
[rocketmouse@archlinux ~]$
cat /run/media/rocketmouse/q/boot/grub/grub.cfg
set timeout=8
set default='0'; if [ x$default = xsaved ]; then load_env; set
default=$saved_entry; fi
set color_normal='light-blue/black'; set
color_highlight='light-cyan/blue'
menuentry FreeBSD{
set root=(hd0,msdos1)
chainloader +1
}
menuentry 'Ubuntu Quantal,kernel 3.6.5-rt14' {
set root='(hd1,9)'; set legacy_hdbias='0'
legacy_kernel '/boot/vmlinuz-3.6.5-rt14' '/boot/vmlinuz-3.6.5-rt14'
'root=/dev/sdb9' 'ro' 'quiet' ''
legacy_initrd '/boot/initrd.img-3.6.5-rt14'
'/boot/initrd.img-3.6.5-rt14'
}
menuentry 'Ubuntu Quantal,kernel 3.5.0-18-lowlatency
threadirqs' {
set root='(hd1,9)'; set legacy_hdbias='0'
legacy_kernel '/boot/vmlinuz-3.5.0-18-lowlatency'
'/boot/vmlinuz-3.5.0-18-lowlatency' 'root=/dev/sdb9' 'ro' 'quiet'
'threadirqs'
legacy_initrd '/boot/initrd.img-3.5.0-18-lowlatency'
'/boot/initrd.img-3.5.0-18-lowlatency'
}
menuentry 'Ubuntu Quantal,kernel 3.5.0-18-lowlatency (recovery
mode)' {
set root='(hd1,9)'; set legacy_hdbias='0'
legacy_kernel '/boot/vmlinuz-3.5.0-18-lowlatency'
'/boot/vmlinuz-3.5.0-18-lowlatency' 'root=/dev/sdb9' 'ro' 'single'
legacy_initrd '/boot/initrd.img-3.5.0-18-lowlatency'
'/boot/initrd.img-3.5.0-18-lowlatency'
}
menuentry 'Ubuntu Studio Quantal, Kernel 3.6.5-rt14' {
set root='(hd1,13)'; set legacy_hdbias='0'
legacy_kernel '/boot/vmlinuz-3.6.5-rt14' '/boot/vmlinuz-3.6.5-rt14'
'root=/dev/sdb13' 'ro' 'quiet'
legacy_initrd '/boot/initrd.img-3.6.5-rt14'
'/boot/initrd.img-3.6.5-rt14'
}
menuentry 'Ubuntu Studio Quantal, Kernel 3.5.0-18-lowlatency
threadirqs' {
set root='(hd1,13)'; set legacy_hdbias='0'
legacy_kernel '/boot/vmlinuz-3.5.0-18-lowlatency'
'/boot/vmlinuz-3.5.0-18-lowlatency' 'root=/dev/sdb13' 'ro' 'quiet'
'threadirqs'
legacy_initrd '/boot/initrd.img-3.5.0-18-lowlatency'
'/boot/initrd.img-3.5.0-18-lowlatency'
}
menuentry 'Ubuntu Studio Precise, Kernel 3.0.30 threadirqs' {
set root='(hd1,1)'; set legacy_hdbias='0'
legacy_kernel '/boot/vmlinuz-3.0.30' '/boot/vmlinuz-3.0.30'
'root=UUID=338316fb-364e-4a43-8deb-738127f878ce' 'ro' 'quiet'
'threadirqs'
legacy_initrd '/boot/initrd.img-3.0.30' '/boot/initrd.img-3.0.30'
}
menuentry 'Ubuntu Studio Precise, Kernel 3.2.0-23-lowlatency
threadirqs' {
set root='(hd1,1)'; set legacy_hdbias='0'
legacy_kernel
Re: FreeBSD 9 and Windows XP
On Mon, 11 Mar 2013, Carl Johnson wrote: Eduardo Morras emorr...@yahoo.es writes: On Sat, 9 Mar 2013 12:07:41 -0800 (PST) leeoliveshackelf...@surewest.net wrote: Good afternoon, FreeBSD enthusiasts. Can FreeBSD 9.1 be installed on a computer on which Windows XP currently resides? If so, how can this installation be done? In particular, is there a way to install 9.1 so that it can be booted from the traditional master boot record? It is important that, when I am done, I can still boot to Windows XP, as I must run some applications not available on FreeBSD. If the idea I am proposing is not feasible with version 9.1, will it work with 8.3? Any comments are appreciated. If this question has already been asked many times before, please just let me know where to look to find the answer. Thanks. Newbie502 As an addon to other answers, you can install VirtualBox, create a minimal hard disk with MBR boot menu that points to the WindowsXP partition. This way you don't need to restart in WinXP. The same can be done from WinXP side, a minimal hd with MBR boot menu to startup the FreeBSD. It is my understanding that FreeBSD doesn't allow using part of a disk, but grabs the entire disk. That means that VirtualBox can't use partitions on a disk that any other partitions are being used by anything else, including FreeBSD itself. Am I wrong about this? I use VirtualBox using vdmk for an entire disk, but I have never been able to share with anything else. It's very hard to tell what situation is being described here. If the VMDK is a pointer to a whole physical disk, that would probably make the disk only usable by one VM. It should be possible to make the VMDK point to just one partition on the disk. Then other VMs or a physical machine could use those other partitions while the FreeBSD VM was running. Booting the same Windows install alternately in a VM and then on real hardware may trigger the Genuine Advantage annoyance. ___ 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 9 and Windows XP
On Mon, 2013-03-11 at 12:25 -0600, Warren Block wrote: Booting the same Windows install alternately in a VM and then on real hardware may trigger the Genuine Advantage annoyance. This is true, but for some exceptional cases perhaps untrue. I wasn't aware about this possibility, but it does sound interesting to me. I run Windows in VBox only to use an iPad I won and to transfer documents from my *nix to the iPad. So my exceptional cases is, that I've got something useful I didn't buy myself. This thing, the iPad, has a lot of disadvantages, I don't pay for apps etc., but it's useful as a reader and for some other tasks. I don't need and I don't use Windows, with this exception (to use the reader/iPad). It's a XP without admin account and service pack 2 only, I don't give a damn about the state of this Windows or the state of the reader. Ok, I made some snapshots, I use this advantage, but I could live without snapshots. I'm a *nix only user, the iPad and regarding to this, Windows XP too, fall into my lap. iPad and Windows aren't important for me, I don't need the security advantages of the virtual machine. I chose it, to avoid issues with installing Windows to a real partition, no primary was free and fixing the boot loader is work and I wish to access iTunes from my *nix ... however, since *nix tend to be problematic regarding to hardware, it can't harm to have a Windows to test hardware that does cause issues with *nix, to ensure that the hardware isn't broken. In my very exceptional, individual case it might be really interesting to share a real Windows install, directly booted and booted as guest in VBox. I'm thinking of making a backup of the virtual partition and to restore it on a real, primary ntfs partition or something similar, perhaps I can copy just the iTunes data and make a new Windows install ... OTOH I didn't use a Windows install before, disk space isn't expensive, so I'm uncertain, if I really want a real Windows install and if I should wish to have one, it's not to share it with VBox, but keep a separated version in VBox. I'm not sure that it's really easy to test hardware when booting it directly and to have completely different _virtual_ hardware by VBox. What would happen, if for the _virtual_ boot of XP, the professional audio card is missing? The setups might be that different, that it perhaps can't switch between a _real_ and a _virtual_ boot without much editing. ___ 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 9 and Windows XP
Warren Block wbl...@wonkity.com writes: On Mon, 11 Mar 2013, Carl Johnson wrote: It is my understanding that FreeBSD doesn't allow using part of a disk, but grabs the entire disk. That means that VirtualBox can't use partitions on a disk that any other partitions are being used by anything else, including FreeBSD itself. Am I wrong about this? I use VirtualBox using vdmk for an entire disk, but I have never been able to share with anything else. It's very hard to tell what situation is being described here. If the VMDK is a pointer to a whole physical disk, that would probably make the disk only usable by one VM. It should be possible to make the VMDK point to just one partition on the disk. Then other VMs or a physical machine could use those other partitions while the FreeBSD VM was running. I was thinking of the case where I tried to allow direct access by a virtual machine to a slice on the same disk that I was running FreeBSD off of. I just looked further into that and discovered that it is possible, but not allowed by geom by default. It can be done by setting 'sysctl kern.geom.debugflags=0x10'. I am sure that you are aware of the dangers, but for anybody else reading this check out the warning in the geom(4) manpage. They refer to this option as 'allow foot shooting' for a reason. -- Carl Johnsonca...@peak.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 9 and Windows XP
On Mon, 11 Mar 2013, Carl Johnson wrote: Warren Block wbl...@wonkity.com writes: On Mon, 11 Mar 2013, Carl Johnson wrote: It is my understanding that FreeBSD doesn't allow using part of a disk, but grabs the entire disk. That means that VirtualBox can't use partitions on a disk that any other partitions are being used by anything else, including FreeBSD itself. Am I wrong about this? I use VirtualBox using vdmk for an entire disk, but I have never been able to share with anything else. It's very hard to tell what situation is being described here. If the VMDK is a pointer to a whole physical disk, that would probably make the disk only usable by one VM. It should be possible to make the VMDK point to just one partition on the disk. Then other VMs or a physical machine could use those other partitions while the FreeBSD VM was running. I was thinking of the case where I tried to allow direct access by a virtual machine to a slice on the same disk that I was running FreeBSD off of. I just looked further into that and discovered that it is possible, but not allowed by geom by default. It can be done by setting 'sysctl kern.geom.debugflags=0x10'. I am sure that you are aware of the dangers, but for anybody else reading this check out the warning in the geom(4) manpage. They refer to this option as 'allow foot shooting' for a reason. That's kind of what I was saying. If you can get the VMDK to refer to just the one slice/partition that the VM needs, it won't lock the whole disk. For example, ada0s2a rather than ada0s2. Of course, it would be bad to share the same partition between more than one VM or physical machine at the same time unless it is mounted read-only by all of them. ___ 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 9 and Windows XP
On Sat, 9 Mar 2013 12:07:41 -0800 (PST) leeoliveshackelf...@surewest.net wrote: Good afternoon, FreeBSD enthusiasts. Can FreeBSD 9.1 be installed on a computer on which Windows XP currently resides? If so, how can this installation be done? In particular, is there a way to install 9.1 so that it can be booted from the traditional master boot record? It is important that, when I am done, I can still boot to Windows XP, as I must run some applications not available on FreeBSD. If the idea I am proposing is not feasible with version 9.1, will it work with 8.3? Any comments are appreciated. If this question has already been asked many times before, please just let me know where to look to find the answer. Thanks. Newbie502 When I did it, I shrunk the Windows partition and installed FreeBSD to the a new partition created on the free space of the drive. The multiboot version of the MBR stuff for FreeBSD should be able to handle it for you with out issue. I've not done it with 9.1, but when I did it with 6 way back when, it worked nicely. signature.asc Description: PGP signature
Re: FreeBSD 9 and Windows XP
On Sat, Mar 9, 2013 at 3:07 PM, leeoliveshackelf...@surewest.net wrote: Good afternoon, FreeBSD enthusiasts. Can FreeBSD 9.1 be installed on a computer on which Windows XP currently resides? As others have already answered, yes. The risks are minimal if you are careful but you will always have the risk of breaking something so make a backup of your XP before doing _anything_. Also, even before doing that, run a de-fragmenter. -- Alejandro Imass ___ 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 9 and Windows XP
On Sat, 2013-03-09 at 21:27 +0100, Polytropon wrote: Partition Magic I would avoid to use proprietary software, ntfs, fat16 and fat32 are full supported by Linux gparted, available for free as in beer at http://partedmagic.com as a live media. Perhaps you need to defragment the Windows partitions first. You need to add a primary partition for FreeBSD, an extended partition with logical partitions can't be used to install FreeBSD. I've got FreeBSD and tons of Linux installed, no Windows. However, my partition table is MBR based, as yours. Gparted can't create the FreeBSD slice, you need to do this with e.g. the FreeBSD installer. I had to use 8.3 and than to update to 9.1, I tested 9.0 first, but I couldn't create the slice, resp. the partitions in that slice. Hth, Ralf -- http://sacom.hk/mission ___ 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 9 and Windows XP
On Sat, 09 Mar 2013 21:49:29 +0100, Ralf Mardorf wrote: On Sat, 2013-03-09 at 21:27 +0100, Polytropon wrote: Partition Magic I would avoid to use proprietary software, ntfs, fat16 and fat32 are full supported by Linux gparted, available for free as in beer at http://partedmagic.com as a live media. Thanks for mentioning it - Parted Magic was the project I was actually refering to. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9 and Windows XP
On Sat, 09 Mar 2013 21:27:45 +0100, Polytropon free...@edvax.de wrote: On Sat, 9 Mar 2013 12:07:41 -0800 (PST), leeoliveshackelf...@surewest.net wrote: Good afternoon, FreeBSD enthusiasts. Can FreeBSD 9.1 be installed on a computer on which Windows XP currently resides? Yes. If so, how can this installation be done? First of all, you need a tool to make disk space available; you can do this by adding an additional hard disk, or by resizing the Windows partition. As Windows does not seem to provide native tools to do this I may misremember, but Win7 does have a functional shrink drive in the drive administration console, and I do think that was there in XP already. Michael ___ 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 9 Startx
Issue solved; I forgot to edit .xinitrc. Cheers, Hooman On Mon, Nov 19, 2012 at 6:06 AM, Polytropon free...@edvax.de wrote: On Mon, 19 Nov 2012 01:28:13 +, Hooman Oroojeni wrote: Dear All, I would like to use GUI in Freebsd 9, but I face with following error. Any idea to help is appreciated. You need to show the error message for diagnostics and suggestions better than pure guessing. :-) Meanwhile, allow me to point you do helpful resources that might be worth reading (just in case you didn't follow them yet): http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html http://wiki.freebsd.org/KDE4 http://www.freebsd.org/gnome/docs/faq2.html In case you have different trouble, please name the software you're intending to run (e. g. which window manager), what you have installed, the content of config files (such as .xinitrc or .xsession) and the commands you've entered, plus their output and error messages. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Freebsd 9 Startx
Hi, On Mon, 19 Nov 2012 01:28:13 + Hooman Oroojeni orooj...@gmail.com wrote: Dear All, I would like to use GUI in Freebsd 9, but I face with following error. I think that you have mist a paste command here. Anyway, what graphics adaptor are you using? Intel? It it is Intel, read about Intel KMS. Erich ___ 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 9 Startx
On Mon, 19 Nov 2012 01:28:13 +, Hooman Oroojeni wrote: Dear All, I would like to use GUI in Freebsd 9, but I face with following error. Any idea to help is appreciated. You need to show the error message for diagnostics and suggestions better than pure guessing. :-) Meanwhile, allow me to point you do helpful resources that might be worth reading (just in case you didn't follow them yet): http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html http://wiki.freebsd.org/KDE4 http://www.freebsd.org/gnome/docs/faq2.html In case you have different trouble, please name the software you're intending to run (e. g. which window manager), what you have installed, the content of config files (such as .xinitrc or .xsession) and the commands you've entered, plus their output and error messages. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9's SSH HPN
On Mon, Mar 19, 2012 at 8:45 PM, Mark Felder f...@feld.me wrote: Is the HPN patchset included with the base OpenSSH the full patchset? Does it include the threaded CTR patch? I can't seem to find a clear answer to this. crypto/openssh/README.hpn references it so I would assume so. -- Adam Vande More ___ 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 9-R pxeboot fails with 'Mounting root filesystem rw failed'...
Take a look at freebsd-hackers mailing list... I have suggested some change in some Makefile and sh script in order to unless at this moment to be able to have an unattended system built with sysinstall (the idea I think it was to maintain sysinstall in 9.0 unless) and using you're install.cfg At freebsd-hackers seems that people is pretty busy and can't look at this in order for committing or unless saying something about it... perhaps they're working on another thing or so, or don't know I assume they can't check this now... but like changes are not significant... I am going to do with the changes suggested and have tested and release builts fine and you can use Jumpstart without issues.. this way... So I recomend you reading last mails of mine in freebsd-hackers... Hope it helps, Bye! El Jue, 1 de Marzo de 2012, 11:24 am, Karl Pielorz escribió: Hi, I've got a 9.0-R amd64 system I'm trying to netboot / pxeboot from the network, to install other machines (and do fixups etc.) I set this up as we setup previous versions here - but setting up a tftp server, and nfs server - and 'dumping' the contents of the install CD to a directory on the dhcp server, which is exported via nfs (it's exported as read/write). The system kind of boots, but falls over with: Interface em0 IP-Address 192.168.0.47 Broadcast 192.168.0.255 Entropy harvesting: interrupts ethernet point_to_pick kickstart. Starting file system checks: mount_nfs: no host:dirpath nfs-name Mounting root filesystem rw failed, startup aborted ERROR: ABORTING BOOT (sending SIGTERM to parent)! Mar 1 118:10 init: /bin/sh on /etc/rc terminated abnormally, going to single user mode Enter full pathname of shell or RETURN for /bin/sh: It looks like it's failing to 'remount' / promote the root file system as read/write (It's definitely exported as read/write - I've tested it by mounting it on another machine). If you start a shell at this point and run mount, you get: 192.168.0.37:/usr2/netboot/os/9.0-amd64 on / (nfs, read-only) devfs on /dev (devfs, local, multilabel) Is there something I have to set (e.g. in '/etc/rc.conf') in order to fix this? Previous systems setup this way would always boot through to the sysinstall menu. Thanks, -Karl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9-R pxeboot fails with 'Mounting root filesystem rw failed'...
--On 01 March 2012 11:53 +0100 ego...@ramattack.net wrote: So I recomend you reading last mails of mine in freebsd-hackers... Hope it helps, Bye! For what it's worth - I've resolved the issue I had (which was basically the system booted, but failed trying to re-mount root as RW, and hence wouldn't go into the installer). The fix I did was to change the '/etc/fstab' on the Netboot server (i.e. the copy of FreeBSD that you're booting). It contains: /dev/iso9660/FREEBSD_INSTALL / cd9660 ro 0 0 Just commenting out that line, i.e. #/dev/iso9660/FREEBSD_INSTALL / cd9660 ro 0 0 Means the boot now completes, and I get offered the Install / Shell / Live CD prompt, instead of an error about not being able to remount root. I've yet to complete an install this way (so far we're just using a script to extract the new 9.x style '.txz' files). But that little change does let us netboot correctly now, enough for what we need. -Karl ___ 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 9-R pxeboot fails with 'Mounting root filesystem rw failed'...
In the new way of booting... you need to have the cd because the own cd is the root filesystem... and in fact is live filesystem too so unless you're booting from mfsroot... I assume you should have that line in /etc/fstab inside the iso image but if you're using mfsroot... I really even am not creating etc dir inside the iso image... because it's not needed and in previous releases and iso images when always booted from mfsroot (and where not livefs cds and so) it wasn't necessary... On Thu, 01 Mar 2012 12:43:58 +, Karl Pielorz wrote: --On 01 March 2012 11:53 +0100 ego...@ramattack.net wrote: So I recomend you reading last mails of mine in freebsd-hackers... Hope it helps, Bye! For what it's worth - I've resolved the issue I had (which was basically the system booted, but failed trying to re-mount root as RW, and hence wouldn't go into the installer). The fix I did was to change the '/etc/fstab' on the Netboot server (i.e. the copy of FreeBSD that you're booting). It contains: /dev/iso9660/FREEBSD_INSTALL / cd9660 ro 0 0 Just commenting out that line, i.e. #/dev/iso9660/FREEBSD_INSTALL / cd9660 ro 0 0 Means the boot now completes, and I get offered the Install / Shell / Live CD prompt, instead of an error about not being able to remount root. I've yet to complete an install this way (so far we're just using a script to extract the new 9.x style '.txz' files). But that little change does let us netboot correctly now, enough for what we need. -Karl ___ 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 9, GPT and gmirror
On Thu, 09 Feb 2012 07:02:29 -0800 per...@pluto.rain.com wrote: Janos Dohanics w...@3dresearch.com wrote: 1. The Guided partitioning doesn't suggest any more to create /var, /tmp, /usr, etc. file systems. Is it really the recommendation to go with just / ? Depends on who you ask :) and on your intended usage. 2. Is there a way to use the old sysinstall to install FreeBSD 9? Not using the standard distribution IIUC. You might want to look at http://druidbsd.sf.net/ [...] This may be just what I need - thank you. -- Janos Dohanics ___ 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 9, GPT and gmirror
On Thu, 09 Feb 2012 20:20:03 +0100 Michael Cardell Widerkrantz m...@hack.org wrote: Janos Dohanics w...@3dresearch.com, 2012-02-08 19:42 (+0100): 4. Also, with GPT, one has to be in single user mode to synchronize disks - correct? I think the guide you linked to: http://blather.michaelwlucas.com/archives/1071 meant that you have to be in single user mode until you have edited /etc/fstab to point to the mirror, otherwise you wouldn't boot with root on the mirror. The synchronization between the disks works fine in multi-user mode as well. I have two 2 TiB disks in gmirror set up just like that. Synchronization was done running in multi-user. You are right - just removed and then re-inserted a component in one of the mirrors and the mirror synchronized fine in multi-user mode. -- Janos Dohanics ___ 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 9, GPT and gmirror
Janos Dohanics w...@3dresearch.com wrote: 1. The Guided partitioning doesn't suggest any more to create /var, /tmp, /usr, etc. file systems. Is it really the recommendation to go with just / ? Depends on who you ask :) and on your intended usage. 2. Is there a way to use the old sysinstall to install FreeBSD 9? Not using the standard distribution IIUC. You might want to look at http://druidbsd.sf.net/ 3. It seems that setting up gmirror is more involved with GPT (http://blather.michaelwlucas.com/archives/1071); now I have a mirror for each of the filesystems /, /var, /tmp, etc. Is it OK to use gmirror in this way at all? Yes, indeed it is the only way to combine GPT and gmirror without getting into trouble of one sort or another. (The conflict between GPT and a full-disk gmirror is actually not new.) 4. Also, with GPT, one has to be in single user mode to synchronize disks - correct? Dunno about this one. 3. Assuming one has enough RAM, is zfs mirror or raidz recommended over gmirror? Same situation as with #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: FreeBSD 9, GPT and gmirror
Janos Dohanics w...@3dresearch.com, 2012-02-08 19:42 (+0100): 4. Also, with GPT, one has to be in single user mode to synchronize disks - correct? I think the guide you linked to: http://blather.michaelwlucas.com/archives/1071 meant that you have to be in single user mode until you have edited /etc/fstab to point to the mirror, otherwise you wouldn't boot with root on the mirror. The synchronization between the disks works fine in multi-user mode as well. I have two 2 TiB disks in gmirror set up just like that. Synchronization was done running in multi-user. -- http://hack.org/mc/ Warning! Plain text e-mail, please. HTML e-mail deleted unread. OpenPGP: 673B 563E 3C78 1BA0 6525 2344 B22E 2C10 E4C9 2FA5 ___ 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 9, GPT and gmirror
On Wed, 8 Feb 2012 13:42:59 -0500 Janos Dohanics w...@3dresearch.com wrote: Hello Everyone, May be I should have searched more for answers, but after installing FreeBSD 9 with gmirror, I am wondering if the experts here have some recommendations for best practices. 1. The Guided partitioning doesn't suggest any more to create /var, /tmp, /usr, etc. file systems. Is it really the recommendation to go with just / ? This is a bad recommendation I think, but you can accept guidance and the adjust to your needs. 2. Is there a way to use the old sysinstall to install FreeBSD 9? Yes, harder to use, or no the new installer should have some more sane defaults 3. It seems that setting up gmirror is more involved with GPT (http://blather.michaelwlucas.com/archives/1071); now I have a mirror for each of the filesystems /, /var, /tmp, etc. Is it OK to use gmirror in this way at all? 4. Also, with GPT, one has to be in single user mode to synchronize disks - correct? 3. Assuming one has enough RAM, is zfs mirror or raidz recommended over gmirror? gmirror, still I think Prior to FreeBSD 9, I used to take the the sysinstall defaults with some overrides as I thought appropriate and proceeded to set up gmirror - it was simple and not a lot of work, and a good way to make use of older systems... I think the new installer is quite good, but needs some shaving around the rough edges Cheers Disclaimer: http://www.ose.nl/email ___ 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 9, GPT and gmirror
3. Assuming one has enough RAM, is zfs mirror or raidz recommended over gmirror? zfs mirror but I would not recommend a raidz root on zfs. -- George Kontostanos Aicom telecoms ltd http://www.aisecure.net ___ 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 9, GPT and gmirror
I can't speak to the mirror issue, but I had difficulty trying to tweak the defaults in the install on a 128G SSD: When manually configuring the SSD, I tried to leave some extra space at the end of the SSD. Not sure that is necessary or not. In any case, I had a 128GB SSD, reported as 119GB. Auto config laid it out as ada1 119GB ada1p1 64KB freebsd-boot ada1p2 115GB freebsd-ufs / ada1p34GB freebsd-swap I then deleted the last 2 and re-created as 100GB and 4GB, at which point it showed ada1 119GB ada1p1 64KB freebsd-boot ada1p2 100GB freebsd-ufs / ada1p3 -15GB freebsd-swap (I may have the -15 wrong; main point is it was negative) After deleting and recreating in different order I managed to get it to ada1 119GB ada1p1 64KB freebsd-boot ada1p34GB freebsd-swap ada1p2 100GB freebsd-ufs / but when I tried to commit it, I got the error: Error mounting partition /mnt: mount: /dev/ada1p2: Operation not permitted The only way I could get it to actually write the distribution was to use auto and keep what it came up with. Is this problem specific to SSDs (seems unlikely)? Is there some magic sequence needed to tweak the Auto result to get it to work? Gary On 2/8/2012 12:00 PM, Bas Smeelen wrote: On Wed, 8 Feb 2012 13:42:59 -0500 Janos Dohanicsw...@3dresearch.com wrote: Hello Everyone, May be I should have searched more for answers, but after installing FreeBSD 9 with gmirror, I am wondering if the experts here have some recommendations for best practices. 1. The Guided partitioning doesn't suggest any more to create /var, /tmp, /usr, etc. file systems. Is it really the recommendation to go with just / ? This is a bad recommendation I think, but you can accept guidance and the adjust to your needs. 2. Is there a way to use the old sysinstall to install FreeBSD 9? Yes, harder to use, or no the new installer should have some more sane defaults 3. It seems that setting up gmirror is more involved with GPT (http://blather.michaelwlucas.com/archives/1071); now I have a mirror for each of the filesystems /, /var, /tmp, etc. Is it OK to use gmirror in this way at all? 4. Also, with GPT, one has to be in single user mode to synchronize disks - correct? 3. Assuming one has enough RAM, is zfs mirror or raidz recommended over gmirror? gmirror, still I think Prior to FreeBSD 9, I used to take the the sysinstall defaults with some overrides as I thought appropriate and proceeded to set up gmirror - it was simple and not a lot of work, and a good way to make use of older systems... I think the new installer is quite good, but needs some shaving around the rough edges Cheers Disclaimer: http://www.ose.nl/email ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9 buildworld with clang failure
On 02.02.2012 15:12, ill...@gmail.com wrote: Might try: Commenting out CFLAGS= Setting NO_WERROR= in /etc/make.conf Removing the CFLAGS= line made no difference, after some searching for info about the NO_WERROR=, I went ahead and added the CFLAGS line back in added NO_WERROR= WERROR= lines both in the /etc/make.conf, and it completed. Now to find out how many ports will compile, and then actually test everything, fortunately the production system I am modeling this test after only has 123 ports installed. -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ 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 9 buildworld with clang failure
On 2 February 2012 14:43, Dean E. Weimer dwei...@dweimer.net wrote:
I am trying to rebuild everything in a development machine with clang to
test for production, and ran into a problem on the buildworld process. This
machine was already rebuilt from source using gcc, here are the options I
have set in make.conf and src.conf. The lines I added to enable clang, and
the steps I took to compile.
Options in /etc/src.conf
WITHOUT_BIND_DNSSEC=YES
WITHOUT_BIND_LIBS_LWRES=YES
WITHOUT_BIND_NAMED=YES
WITHOUT_BIND_UTILS=YES
WITHOUT_NTP=YES
WITHOUT_PROFILE=YES
Options already in /etc/make.conf
WITH_OPENSSL_PORT=yes
WITHOUT_X11=yes
CFLAGS= -O -pipe
PERL_VERSION=5.12.4
Added to /etc/make.conf
.if !defined(USE_GCC)
.if !defined(CC) || ${CC} == cc
CC=clang
.endif
.if !defined(CXX) || ${CXX} == c++
CXX=clang++
.endif
.if !defined(CPP) || ${CPP} == cpp
CPP=clang-cpp
.endif
.endif
Did the cleanup process from previous build and currently installed setup.
chflags -R noschg /usr/obj/usr
rm -rf /usr/obj/usr
cd /usr/src
make cleandir
make cleandir
Then ran make buildworld, it died on libc with the following output:
=== lib/libc (obj,depend,all,install)
clang -O -pipe -I/usr/src/lib/libc/include
-I/usr/src/lib/libc/../../include -I/usr/src/lib/libc/amd64 -DNLS
-D__DBINTERFACE_PRIVATE -I/usr/src/lib/libc/../../contrib/gdtoa -DINET6
-I/usr/obj/usr/src/lib/libc -I/usr/src/lib/libc/resolv -D_ACL_PRIVATE
-DPOSIX_MISTAKE -I/usr/src/lib/libc/../../contrib/tzcode/stdtime
-I/usr/src/lib/libc/stdtime -I/usr/src/lib/libc/locale -DBROKEN_DES
-DPORTMAP -DDES_BUILTIN -I/usr/src/lib/libc/rpc -DYP -DNS_CACHING
-DSYMBOL_VERSIONING -std=gnu99 -fstack-protector -Wsystem-headers -Werror
-Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c
/usr/src/lib/libc/gen/setjmperr.c
In file included from /usr/src/lib/libc/gen/setjmperr.c:44:
/usr/src/lib/libc/../../include/setjmp.h:58:5: error: incompatible
redeclaration of library function
'sigsetjmp' [-Werror]
int sigsetjmp(sigjmp_buf, int);
^
/usr/src/lib/libc/../../include/setjmp.h:58:5: note: 'sigsetjmp' is a
builtin with type
'int (struct _jmp_buf *, int)'
1 error generated.
*** Error code 1
Stop in /usr/src/lib/libc.
*** Error code 1
Might try:
Commenting out CFLAGS=
Setting NO_WERROR= in /etc/make.conf
--
--
___
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 9 on Lenovo X200 what works?
On 01/26/2012 01:57 AM, Da Rock wrote: Despite having similar hardware, you're only real best bet is to suck it and see. Try installing and seeing what you can get to work (dmesg, pciconf -lv, usbconfig, kldload modules, questions here, etc). I've had mixed success with laptops (they're just about all I have as a desktop), and about my only problems have been with wifi- though that has mostly disappeared with Adrian's excellent work. I will have a go as Salix (which is on there now isn't cutting it and spent all night trying to get things in order but didn't :( Tested the live FBSD9 disk in the meantime and the wireless gets detected out of the box. As long as I get wifi and HD video and sound coming out of the headphone socket I will be fine I'm running 8.2 on an X200. For the most part everything works. My main complaint is that the sound is very quiet, and I haven't found the setting to fix that. Video and wifi work fine. The kernel sees the camera and the thumb reader but I haven't looked for applications that use them. Ok this sounds promising - for wifi see above! App for camera is Googletalk if supported on Firefox 9, and PAM for the figureprint reader. Just thinkin about WWAN now but there was a post floating around about 3G modems so I might just be in luck not that I've ever used WiMax before. Thanks for the replies guys :-) Regards, Kaya ___ 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 9 and 3G Modems
On Wed, Jan 25, 2012 at 18:54, Mike Tancsa m...@sentex.net wrote: On 1/25/2012 5:43 AM, Odhiambo Washington wrote: I have a Huawei E1820 I will also try RTFM. Hi, kldload u3g kldload umodem Done, although kldload u3g tells me that file already exists! Perhaps because I booted up with my Huawei dongle plugged in. kldstat | grep u3g shows me nothing though. plug in the modem Show the output of usbconfig [wash@pcbsd9] /home/wash# usbconfig ugen0.1: UHCI root HUB Intel at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen1.1: UHCI root HUB Intel at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen2.1: EHCI root HUB Intel at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen3.1: UHCI root HUB Intel at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen4.1: UHCI root HUB Intel at usbus4, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen5.1: UHCI root HUB Intel at usbus5, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen6.1: EHCI root HUB Intel at usbus6, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen6.2: HUAWEI Mobile Huawei Technologies at usbus6, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen0.2: BCM2045B Broadcom Corp at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen0.3: Biometric Coprocessor STMicroelectronics at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen3.2: Microsoft Nano Transceiver v1.0 Microsoft at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON then sysctl -a dev.u3g [wash@pcbsd9] /home/wash# sysctl -a dev.u3g dev.u3g.0.%desc: Huawei Technologies HUAWEI Mobile, class 0/0, rev 2.00/0.00, addr 2 dev.u3g.0.%driver: u3g dev.u3g.0.%location: bus=1 hubaddr=1 port=6 devaddr=2 interface=0 dev.u3g.0.%pnpinfo: vendor=0x12d1 product=0x1001 devclass=0x00 devsubclass=0x00 sernum= release=0x mode=host intclass=0xff intsubclass=0xff intprotocol=0xff ttyname=U0 ttyports=3 dev.u3g.0.%parent: uhub and ls -l /dev/cuaU* [wash@pcbsd9] /home/wash# ls -l /dev/cuaU* crw-rw 1 uucp dialer0, 117 Jan 26 18:23 /dev/cuaU0.0 crw-rw 1 uucp dialer0, 118 Jan 26 18:23 /dev/cuaU0.0.init crw-rw 1 uucp dialer0, 119 Jan 26 18:23 /dev/cuaU0.0.lock crw-rw 1 uucp dialer0, 123 Jan 26 18:23 /dev/cuaU0.1 crw-rw 1 uucp dialer0, 124 Jan 26 18:23 /dev/cuaU0.1.init crw-rw 1 uucp dialer0, 125 Jan 26 18:23 /dev/cuaU0.1.lock crw-rw 1 uucp dialer0, 129 Jan 26 18:23 /dev/cuaU0.2 crw-rw 1 uucp dialer0, 130 Jan 26 18:23 /dev/cuaU0.2.init crw-rw 1 uucp dialer0, 131 Jan 26 18:23 /dev/cuaU0.2.lock and dmesg [wash@pcbsd9] /home/wash# dmesg Copyright (c) 1992-2011 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-RELEASE #3: Tue Dec 27 14:14:29 PST 2011 r...@build9x64.pcbsd.org:/usr/obj/builds/amd64/pcbsd-build90/fbsd-source/9.0/sys/GENERIC amd64 CPU: Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz (1995.05-MHz K8-class CPU) Origin = GenuineIntel Id = 0x6fa Family = 6 Model = f Stepping = 10 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xe3bdSSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF TSC: P-state invariant, performance statistics real memory = 4294967296 (4096 MB) avail memory = 4000251904 (3814 MB) Event timer LAPIC quality 400 ACPI APIC Table: LENOVO TP-7L FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ACPI Warning: 32/64X length mismatch in Gpe1Block: 0/32 (20110527/tbfadt-556) ACPI Warning: Optional field Gpe1Block has zero address or length: 0x102C/0x0 (20110527/tbfadt-586) ioapic0: Changing APIC ID to 1 ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 cryptosoft0: software crypto on motherboard acpi0: LENOVO TP-7L on motherboard CPU0: local APIC error 0x40 acpi_ec0: Embedded Controller: GPE 0x12, ECDT port 0x62,0x66 on acpi0 acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, bff0 (3) failed Timecounter ACPI-fast frequency 3579545 Hz quality 900 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 acpi_lid0: Control Method Lid Switch on acpi0 acpi_button0: Sleep Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge irq 16 at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 vgapci0: VGA-compatible display port 0x2000-0x207f mem 0xd600-0xd6ff,0xe000-0xefff,0xd400-0xd5ff irq 16 at device 0.0 o n pci1 nvidia0: Quadro NVS 140M on vgapci0 vgapci0: child nvidia0 requested pci_enable_io
Re: FreeBSD 9 and 3G Modems
On 1/26/2012 10:58 AM, Odhiambo Washington wrote: Hi, kldload u3g kldload umodem Done, although kldload u3g tells me that file already exists! Perhaps because I booted up with my Huawei dongle plugged in. kldstat | grep u3g shows me nothing though. Looks like its already defined in the kernel! ugen6.2: HUAWEI Mobile Huawei Technologies at usbus6, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON It sees it. then sysctl -a dev.u3g [wash@pcbsd9] /home/wash# sysctl -a dev.u3g dev.u3g.0.%desc: Huawei Technologies HUAWEI Mobile, class 0/0, rev 2.00/0.00, addr 2 dev.u3g.0.%driver: u3g dev.u3g.0.%location: bus=1 hubaddr=1 port=6 devaddr=2 interface=0 dev.u3g.0.%pnpinfo: vendor=0x12d1 product=0x1001 devclass=0x00 devsubclass=0x00 sernum= release=0x mode=host intclass=0xff intsubclass=0xff intprotocol=0xff ttyname=U0 ttyports=3 dev.u3g.0.%parent: uhub More importantly, the driver sees it and has used cuaU0.* and ls -l /dev/cuaU* [wash@pcbsd9] /home/wash# ls -l /dev/cuaU* crw-rw 1 uucp dialer0, 117 Jan 26 18:23 /dev/cuaU0.0 crw-rw 1 uucp dialer0, 118 Jan 26 18:23 /dev/cuaU0.0.init crw-rw 1 uucp dialer0, 119 Jan 26 18:23 /dev/cuaU0.0.lock crw-rw 1 uucp dialer0, 123 Jan 26 18:23 /dev/cuaU0.1 crw-rw 1 uucp dialer0, 124 Jan 26 18:23 /dev/cuaU0.1.init crw-rw 1 uucp dialer0, 125 Jan 26 18:23 /dev/cuaU0.1.lock crw-rw 1 uucp dialer0, 129 Jan 26 18:23 /dev/cuaU0.2 crw-rw 1 uucp dialer0, 130 Jan 26 18:23 /dev/cuaU0.2.init crw-rw 1 uucp dialer0, 131 Jan 26 18:23 /dev/cuaU0.2.lock This is where you need to do a bit of experimenting. Some modems register these sub ports and others do not. Some are for out of band control and one will be the device you actually use in your ppp config. The init string sort of depends on your carrier. But a basic one to try in ppp.conf is below. For the set device line, you might need to change it to /dev/cuaU0.1 or /dev/cuaU0.2 invoke with ppp -ddial u3g You might need the authname and auth key, you might not. For the context you might need to change it from internet.com to something else. Again, ask your carrier for that info. Try first without the CGDCONT line as the default in the modem might do the trick. u3g: set device /dev/cuaU0.0 set server /var/run/gprs-internet 0177 set speed 921600 set timeout 0 set authname wapuser1 set authkey wap set dial ABORT BUSY TIMEOUT 2 \ \\ \ AT OK-AT-OK \ AT+CFUN=1 OK-AT-OK \ AT+CMEE=2 OK-AT-OK \ AT+CSQ OK \ AT+CGDCONT=1,\\\IP\\\,\\\internet.com\\\ OK \ ATv OK \ ATD*99# CONNECT set crtscts on disable vjcomp disable acfcomp disable deflate disable deflate24 disable pred1 disable protocomp disable mppe disable ipv6cp disable lqr disable echo #nat enable yes enable dns resolv writable set dns 8.8.8.8 set ifaddr 10.1.0.2/0 10.1.0.1/0 255.255.255.255 0.0.0.0 add default HISADDR # See ppp.link* -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ 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 9 and 3G Modems
On Thu, Jan 26, 2012 at 19:12, Mike Tancsa m...@sentex.net wrote: On 1/26/2012 10:58 AM, Odhiambo Washington wrote: Hi, kldload u3g kldload umodem Done, although kldload u3g tells me that file already exists! Perhaps because I booted up with my Huawei dongle plugged in. kldstat | grep u3g shows me nothing though. Looks like its already defined in the kernel! ugen6.2: HUAWEI Mobile Huawei Technologies at usbus6, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON It sees it. then sysctl -a dev.u3g [wash@pcbsd9] /home/wash# sysctl -a dev.u3g dev.u3g.0.%desc: Huawei Technologies HUAWEI Mobile, class 0/0, rev 2.00/0.00, addr 2 dev.u3g.0.%driver: u3g dev.u3g.0.%location: bus=1 hubaddr=1 port=6 devaddr=2 interface=0 dev.u3g.0.%pnpinfo: vendor=0x12d1 product=0x1001 devclass=0x00 devsubclass=0x00 sernum= release=0x mode=host intclass=0xff intsubclass=0xff intprotocol=0xff ttyname=U0 ttyports=3 dev.u3g.0.%parent: uhub More importantly, the driver sees it and has used cuaU0.* and ls -l /dev/cuaU* [wash@pcbsd9] /home/wash# ls -l /dev/cuaU* crw-rw 1 uucp dialer0, 117 Jan 26 18:23 /dev/cuaU0.0 crw-rw 1 uucp dialer0, 118 Jan 26 18:23 /dev/cuaU0.0.init crw-rw 1 uucp dialer0, 119 Jan 26 18:23 /dev/cuaU0.0.lock crw-rw 1 uucp dialer0, 123 Jan 26 18:23 /dev/cuaU0.1 crw-rw 1 uucp dialer0, 124 Jan 26 18:23 /dev/cuaU0.1.init crw-rw 1 uucp dialer0, 125 Jan 26 18:23 /dev/cuaU0.1.lock crw-rw 1 uucp dialer0, 129 Jan 26 18:23 /dev/cuaU0.2 crw-rw 1 uucp dialer0, 130 Jan 26 18:23 /dev/cuaU0.2.init crw-rw 1 uucp dialer0, 131 Jan 26 18:23 /dev/cuaU0.2.lock This is where you need to do a bit of experimenting. Some modems register these sub ports and others do not. Some are for out of band control and one will be the device you actually use in your ppp config. The init string sort of depends on your carrier. But a basic one to try in ppp.conf is below. For the set device line, you might need to change it to /dev/cuaU0.1 or /dev/cuaU0.2 invoke with ppp -ddial u3g You might need the authname and auth key, you might not. For the context you might need to change it from internet.com to something else. Again, ask your carrier for that info. Try first without the CGDCONT line as the default in the modem might do the trick. u3g: set device /dev/cuaU0.0 set server /var/run/gprs-internet 0177 set speed 921600 set timeout 0 set authname wapuser1 set authkey wap set dial ABORT BUSY TIMEOUT 2 \ \\ \ AT OK-AT-OK \ AT+CFUN=1 OK-AT-OK \ AT+CMEE=2 OK-AT-OK \ AT+CSQ OK \ AT+CGDCONT=1,\\\IP\\\,\\\internet.com\\\ OK \ ATv OK \ ATD*99# CONNECT set crtscts on disable vjcomp disable acfcomp disable deflate disable deflate24 disable pred1 disable protocomp disable mppe disable ipv6cp disable lqr disable echo #nat enable yes enable dns resolv writable set dns 8.8.8.8 set ifaddr 10.1.0.2/0 10.1.0.1/0 255.255.255.255 0.0.0.0 add default HISADDR # See ppp.link* Hi Mike, I guess the internet.com in AT+CGDCONT=1,\\\IP\\\,\\\internet.com\\\ OK \ refer to the APN? I know I need to read ppp.conf again soon :) ppp.log: Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: default: set timeout 180 Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: default: enable dns Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: u3g: set device /dev/cuaU0.0 Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: u3g: set server /var/run/gprs-internet 0177 Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Warning: Local: bind: Address already in use Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Warning: set server: Failed 2 Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: u3g: set speed 921600 Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: u3g: set timeout 0 Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: u3g: set authname saf Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: u3g: set authkey Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: u3g: set dial ABORT BUSY TIMEOUT 2AT OK-AT-OKAT+CFUN=1 OK-AT-OK AT+CMEE=2 OK-AT-OKAT+CSQ OK AT+CGDCONT=1,\IP\,\safaricom\ OKATv OKATD*99# CONNECT Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: u3g: set crtscts on Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: u3g: disable vjcomp Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: u3g: disable acfcomp Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: u3g: disable deflate Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: u3g: disable deflate24 Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: u3g: disable pred1 Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: u3g: disable protocomp Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: u3g: disable mppe Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command:
Re: FreeBSD 9 and 3G Modems
Odhiambo Washington odhia...@gmail.com writes: On Wed, Jan 25, 2012 at 18:54, Mike Tancsa m...@sentex.net wrote: On 1/25/2012 5:43 AM, Odhiambo Washington wrote: I have a Huawei E1820 I will also try RTFM. Hi, kldload u3g kldload umodem Done, although kldload u3g tells me that file already exists! Perhaps because I booted up with my Huawei dongle plugged in. kldstat | grep u3g shows me nothing though. The command 'kldstat -v' shows that u3g is already compiled in for the 9.0-RELEASE kernel. -- Carl Johnsonca...@peak.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 9 and 3G Modems
On 1/26/2012 12:00 PM, Odhiambo Washington wrote: Hi Mike, I guess the internet.com http://internet.com in AT+CGDCONT=1,\\\IP\\\,\\\internet.com http://internet.com/\\\ OK \ refer to the APN? I know I need to read ppp.conf again soon :) Hi, Yes, thats the APN. Your APN seems to be safaricom. Also, get rid of the line that has atv. Thats confusing your modem. ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ 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 9 and 3G Modems
On Tue, Jan 24, 2012 at 19:37, Mike Tancsa m...@sentex.net wrote: On 1/24/2012 10:56 AM, Odhiambo Washington wrote: I am Google-ing for a recent definitive HOWTO use my 3G modem with FreeBSD/PC-BSD and what I get seem rather old. Someone can point me to a recent document detailing the steps. I have PC-BSD 9 on my laptop. Most of them just come up as cuaU* devices, but not all. The method to use them has not really changed, so chances are what you have found via google will still work. Take a look at the relevant man pages. man u3g What type of modem do you have ? Hi Mike, I have a Huawei E1820 I will also try RTFM. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ I can't hear you -- I'm using the scrambler. Please consider the environment before printing this email. ___ 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 9 and 3G Modems
On Tue, Jan 24, 2012 at 21:48, Alejandro Imass a...@p2ee.org wrote: On Tue, Jan 24, 2012 at 10:56 AM, Odhiambo Washington odhia...@gmail.com wrote: I am Google-ing for a recent definitive HOWTO use my 3G modem with FreeBSD/PC-BSD and what I get seem rather old. Which one? You need to specifiy modem brand/model and network provider to see if other have got that particular one working. Also check the Linux crowd (Ubuntu in particular) and then extrapolate to FBSD. I have a Huawei E1820 and I am in KE, using Safaricom. Someone can point me to a recent document detailing the steps. I have PC-BSD 9 on my laptop. Usually it's just a question of making the kernel mount the tty and the dial using something like wvdial. If it's popular and supported it's pretty easy, if not is still possible. Supporting the modem is usually a two layer problem first solving the multi-device problem on the USB bus, that is, selecting the correct device available (i.e. selecting the modem instead of the flash that contains the windows software), and then the actual kernel or userspace driver for that specific device (ZTE, Enfora, etc.). Luckily, I already disabled the flash/virtual CD-ROM that the modem contains. I got the AT string combo to do this. I also have one ZTE dongle that I don't want to talk about because I haven't managed to find a way to disable the virtual CD-ROM it contains. Ultimately, you get a serial modem and you just have to use AT command to dial, etc. and wvdial does a great job and it's quite easy to set-up and run. You know, sometimes all this process is what makes people shy off of *BSD. I am a diehard lover of FreeBSD, but the few times I have installed Linux on my laptop, this whole process was a breeze... well, not quite, but not as difficult as it is in FreeBSD. Luckily, I use WiFi more than I use 3G, so it's never quite bothered me. Even now, I just want to see how easy it can be on PC-BSD/FreeBSD, with a GUI to boot, if there is, but I do not feel it is such a big necessity for me, because I have D-Link DIR-825 which can use this modem on it's USB port and allow me to use 3G. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ I can't hear you -- I'm using the scrambler. Please consider the environment before printing this email. ___ 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 9 and 3G Modems
On Wed, Jan 25, 2012 at 09:23, Ivan Frosty ivanfro...@gmail.com wrote:
The FreeBSD u3g driver ¶¶
Introduction ¶¶
This driver supports 3G (UMTS, HSDPA, HSUPA, HSPA) cards that provide
access to one or more serial ports through a USB interface, providing
PPP and AT command channels simultaneously. Some devices provide
access to multiple pairs of channels for integrated GPS', or other
access methods (Option HSO driver).
Transfer speeds should be above 30k on a good UMTS connection and a
fast server:
% curl -o /dev/null ftp://ftp.nl.freebsd.org/pub/FreeBSD/ls-lR.gz
% Total% Received % Xferd Average Speed TimeTime Time
Current
Dload Upload TotalSpent Left
Speed
12 19.9M 12 2486k0 0 40203 0 0:08:39 0:01:03 0:07:36
43921
Some (older) devices (from Sierra for example) provide 1 serial port
through a normal serial port or the normal serial USB drivers. They
usually support the ETSI / 3GPP 27.010 3GPPMultiplexProtocol, making
it possible to open a AT command channel and a PPP connection channel
simultaneously. A basic implementation which works on an Option
Globetrotter GPRS card is available. Contact me for details.
Verified to work ¶¶
See the man page.
Installation instructions ¶¶
The driver is available in both FreeBSD 7 and FreeBSD 8. The one in
FreeBSD 8 and up was written by Hans Petter Selasky. Consult
freebsd-usb@… for more information and bug reports.
The driver from FreeBSD 7 should be usable on FreeBSD 6, without too
many changes. You will need to patch ucom.c though with the attached
patch (see below).
Tricks ¶¶
To start your connection automatically use something like the
following snippet in your devd.conf:
attach 100 {
device-name ucom[0-9]+;
match vendor 0x12d1;
match product 0x1003;
action /usr/sbin/ppp -ddial kpn;
};
Some people have been able to get their device to successfully switch
from driver mode to modem mode using usb_modeswitch. You can compile
it on !FreeBSD with
cc -L /usr/local/lib -I/usr/local/include -lusb -o usb_modeswitch
usb_modeswitch.c
if you have libusb installed. The mass storage devices the devices
present should be available through ugen. Note that umass must not be
present in your kernel nor as a module (or it should be made to ignore
these devices).
To see signal strength for example while online:
Start ppp (See also PPPFor3GModems).
prolly that could help.
I read this, but one thing I am sure about is that those details need to be
changed to reflect what I have on my system.
But I'm trying to see if there is an easier way out.
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254733744121/+254722743223
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
I can't hear you -- I'm using the scrambler.
Please consider the environment before printing this email.
___
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 9 and 3G Modems
El día Tuesday, January 24, 2012 a las 10:23:18PM -0800, Ivan Frosty escribió: The FreeBSD u3g driver ¶¶ Introduction ¶¶ This driver supports 3G (UMTS, HSDPA, HSUPA, HSPA) cards that provide access to one or more serial ports through a USB interface, providing PPP and AT command channels simultaneously. Some devices provide access to multiple pairs of channels for integrated GPS', or other access methods (Option HSO driver). Transfer speeds should be above 30k on a good UMTS connection and a fast server: ... I'm using for years now the u3g(4) driver in 8-CURRENT, 9- and 10-CURRENT; it just works fine with ppp(8) and gives, if the provider has no bottle-nack in channels, up to 2 Mbps down- and 1 Mbps upstream; I'm using USB Huawei dongles or USB sticks. There is nearly nothing magic, it just works: you plug in the key, some devd(8) hook sends down the PIN to the created serial device, and I start ppp(8) by hand (could be done as well from a devd(8) hook); HIH matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.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: FreeBSD 9 and 3G Modems
On 1/25/2012 5:43 AM, Odhiambo Washington wrote: I have a Huawei E1820 I will also try RTFM. Hi, kldload u3g kldload umodem plug in the modem Show the output of usbconfig then sysctl -a dev.u3g and ls -l /dev/cuaU* and dmesg On some 3g sticks, you have to send a command to put them in modem mode. Typically this is done by 'ejecting the cd' camcontrol eject pass0 But the driver knows of most of the variants out there and does that automatically for you. ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ 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 9 and 3G Modems
On Wed, Jan 25, 2012 at 5:50 AM, Odhiambo Washington odhia...@gmail.com wrote: [...] You know, sometimes all this process is what makes people shy off of *BSD. I am a diehard lover of FreeBSD, but the few times I have installed Linux on my laptop, this whole process was a breeze... well, not quite, but not as difficult as it is in FreeBSD. Luckily, I use WiFi more than I use 3G, so it's never quite bothered me. Even now, I just want to see how easy it can be on PC-BSD/FreeBSD, with a GUI to boot, if there is, but I do not feel it is such a big necessity for me, because I have D-Link DIR-825 which can use this modem on it's USB port and allow me to use 3G. It used to be like that in Linux as well. It's only until recently that the netowrk manager app supports 3g modems. The problem is when these graphical apps fail you have virtually no way to see what's going on, just plug and pray. If you get the tty, using Wvdial is actuall much easier than any other dialing/ppp tool I've ever used. So even on Linuxes with NM applet and 3g modem support I would use Wvdial, and on FBSD especially! wvdial is much more robust than the nm apps, IMHO. -- Alejandro Imass ___ 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 9 on Lenovo X200 what works?
On 01/26/12 11:50, Kaya Saman wrote: Hi, I discovered this thread: http://forums.freebsd.org/showthread.php?t=25539 and am wondering what will and won't work on my Lenovo X220 I'm currently in the process in deciding between FreeBSD 9 and Fedora 15/16. I love FreeBSD on servers but unfortunately I haven't had much luck with it on client side systems. Mainly I want to use the system for running a tier 2 hypervisor - VirtualBox (not OSE version). i also want to be able to use HD graphics capabilities and wireless and the WWAN modem that comes with the system. Currently I have something called Salix on here which is Slackware based but unfortunately the hardware isn't being detected properly and that's my major concern regarding FreeBSD! Can anyone provide me with any success stories or advice in what I will be missing if I whack FreeBSD on here?? Despite having similar hardware, you're only real best bet is to suck it and see. Try installing and seeing what you can get to work (dmesg, pciconf -lv, usbconfig, kldload modules, questions here, etc). I've had mixed success with laptops (they're just about all I have as a desktop), and about my only problems have been with wifi- though that has mostly disappeared with Adrian's excellent work. I have recently had trouble with a dual video card (and ATI 4200 and a 6300 on the same machine), but that shouldn't be a problem. That has been fixed with using vesa, but that doesn't degrade performance or quality; biggest issue there is the residual image for security. But then I don't really give my video too much of workout, maybe it might affect you or not in any of the above cases. Just have a go and see how it goes I say... :) It's not too much time to find out. HTH ___ 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 9 on Lenovo X200 what works?
I'm running 8.2 on an X200. For the most part everything works. My main complaint is that the sound is very quiet, and I haven't found the setting to fix that. Video and wifi work fine. The kernel sees the camera and the thumb reader but I haven't looked for applications that use them. R's, John ___ 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 9 and 3G Modems
On 1/24/2012 10:56 AM, Odhiambo Washington wrote: I am Google-ing for a recent definitive HOWTO use my 3G modem with FreeBSD/PC-BSD and what I get seem rather old. Someone can point me to a recent document detailing the steps. I have PC-BSD 9 on my laptop. Most of them just come up as cuaU* devices, but not all. The method to use them has not really changed, so chances are what you have found via google will still work. Take a look at the relevant man pages. man u3g What type of modem do you have ? ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ 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: Horrible installer (was: Re: FreeBSD 9)
All of these complaints can go directly to /dev/null Just as you don't get to express your opinion about the government if you don't vote, you don't get to express your opinion about -RELEASE changes when you didn't run the STABLE/RC/BETAs. You had your chance to help improve FreeBSD for everyone, assuming your concerns really are valid and far-reaching. You opted out. No longer the core team's problem. Closed: WORKSFORME ___ 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: Horrible installer (was: Re: FreeBSD 9)
On Mon, 23 Jan 2012 08:27:32 -0600 Mark Felder articulated: Just as you don't get to express your opinion about the government if you don't vote, Excuse me, but are you just trying to look naive? -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ Remember to always be yourself. Unless you suck. -- Joss Whedon. ___ 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: Horrible installer (was: Re: FreeBSD 9)
On Mon, 23 Jan 2012 09:40:42 -0600, je...@seibercom.net wrote: On Mon, 23 Jan 2012 08:27:32 -0600 Mark Felder articulated: Just as you don't get to express your opinion about the government if you don't vote, Excuse me, but are you just trying to look naive? The wording wasn't exactly as clear as it should have been, and I don't feel like seeing this thread degrade into politics and conspiracy theories. I should have known better. To clarify: Don't complain about major changes in -RELEASE if you refused to participate in the release process. (and bsdinstaller was HIGHLY publicized for a solid year before 9.0-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: Horrible installer (was: Re: FreeBSD 9)
I've recently been presented with new information: namely that RC3 had sysinstall as an option (I did not know this, and I've been reading the lists) and that it was taken away for -RELEASE even though it was agreed upon that would not happen for 9.x. I'll crawl under this rock now. ___ 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: Horrible installer (was: Re: FreeBSD 9)
Allan ___ Erm, you have to realize the new installer was discussed at length here, when 9.0 was still under development/beta/prerelease. Alternatively, you could do like me and install entirely by hand: - boot an MFSBSD image (thanks mm@ ) - partition your disks from there (see http://my.gd/bsd.htm for a rough sketch on how to use gpart) - fetch the 9.0 archives in .txz (tar.xz) format - unpack archives with xz -d - untar archived to the mountpoint with your new filesystems (eg: tar xf base.tar -C /mnt) - customize configuration files (rc.conf, fstab, root's password or SSH key, sshd_config to allow root login temporarily) and almost like me installing previous release (FreeBSD 8) everywhere. i just made once bootable pendrive with system, lots of tools and whole system as .tar.gz files (made my own compiling from cvs) actually i add WITHOUT_SYSINSTALL=yes to make.conf so i don't build it at all. And IMHO sysinstall should not exist, while good documentation about installing BY HAND should be there. Someone that cannot install it him/herself will not be able to ever manage it after so why waste time. Do not forget that FreeBSD is for unix users, contrary to linux which is for windoze haters. Again i propose removing sysinstall altogether. ___ 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: Horrible installer (was: Re: FreeBSD 9)
-Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- questi...@freebsd.org] On Behalf Of Wojciech Puchar Sent: Monday, January 23, 2012 10:25 AM To: Damien Fleuriot Cc: freebsd-questions@freebsd.org Subject: Re: Horrible installer (was: Re: FreeBSD 9) Allan ___ Erm, you have to realize the new installer was discussed at length here, when 9.0 was still under development/beta/prerelease. Alternatively, you could do like me and install entirely by hand: - boot an MFSBSD image (thanks mm@ ) - partition your disks from there (see http://my.gd/bsd.htm for a rough sketch on how to use gpart) - fetch the 9.0 archives in .txz (tar.xz) format - unpack archives with xz -d - untar archived to the mountpoint with your new filesystems (eg: tar xf base.tar -C /mnt) - customize configuration files (rc.conf, fstab, root's password or SSH key, sshd_config to allow root login temporarily) and almost like me installing previous release (FreeBSD 8) everywhere. i just made once bootable pendrive with system, lots of tools and whole system as .tar.gz files (made my own compiling from cvs) actually i add WITHOUT_SYSINSTALL=yes to make.conf so i don't build it at all. And IMHO sysinstall should not exist, while good documentation about installing BY HAND should be there. Someone that cannot install it him/herself will not be able to ever manage it after so why waste time. Disagree. For example, field engineers which may not be expected to know how to manage FreeBSD _ARE_ expected to know how to install it. A manual install process is more prone to errors than one that is guided by something/anything. Do not forget that FreeBSD is for unix users, Not all users are people. A corporation can be considered a unix user which changes the perspective quite a bit. contrary to linux which is for windoze haters. Again i propose removing sysinstall altogether. And you'll have your wish... over time! The community has agreed to phase out sysinstall(8) gradually over the next 2 or three releases (producing either a 10.0 or 11.0 that is free of sysinstall depending on how things progress with respect to replacement utilities such as bsdinstall and the proposed bsdconfig). -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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: Horrible installer (was: Re: FreeBSD 9)
On Mon, Jan 23, 2012 at 07:25:03PM +0100, Wojciech Puchar wrote: And IMHO sysinstall should not exist, while good documentation about installing BY HAND should be there. I agree with the part of that sentence following the comma. That is all. Someone that cannot install it him/herself will not be able to ever manage it after so why waste time. Do not forget that FreeBSD is for unix users, contrary to linux which is for windoze haters. Again i propose removing sysinstall altogether. Automation is good, provided it does not eliminate useful options and flexibility. You seem unaware of this fact in the general case, for some reason. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.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: Horrible installer (was: Re: FreeBSD 9)
On Mon, Jan 23, 2012 at 09:52:17AM -0600, Mark Felder wrote: On Mon, 23 Jan 2012 09:40:42 -0600, je...@seibercom.net wrote: On Mon, 23 Jan 2012 08:27:32 -0600 Mark Felder articulated: Just as you don't get to express your opinion about the government if you don't vote, Excuse me, but are you just trying to look naive? The wording wasn't exactly as clear as it should have been, and I don't feel like seeing this thread degrade into politics and conspiracy theories. I should have known better. To clarify: Don't complain about major changes in -RELEASE if you refused to participate in the release process. (and bsdinstaller was HIGHLY publicized for a solid year before 9.0-RELEASE.) I understand the theory, but in reality, not everyone has the resources to frequently try out CURRENT or even STABLE as sort of Beta tests. It is good for those who can. In spite of that, it is good - a part of the development process - that people do post their complaints and concerns. Of course, the sendpr process is the canonical method, but really, many of these comments need some discussion before they are ready for prime time - eg to be posted by sendpr. Frankly, many of the comments are rather half baked and many are really just personal preferences that are not actually technical failings. That does not make them unvaluable. It ends up being sort of an Email BOF session like one might get into in a FreeBSD or USENIX conference. That hashing out is where many new ideas and features start and get vetted and may eventually get worked on by people able to do it. The one failing I frequently see in the complaint posts and the responses by other complainers is too frequently a lack of civility and respect for people who are doing the work of creating and maintaining this system and for those who are making complaints and stating personal preferences (true on other similar lists such as CentOS, etc too). It is not necessary or helpful to ascribe all sorts of negative attributes and motives to those doing the work or to those making comments and complaints. Just state your bit, then shut your digital mouth. jerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Horrible installer (was: Re: FreeBSD 9)
I'm very new to FreeBSD but it seems to me that the installer is pretty much ok. My only wish is that there might be a little more info upfront somewhere, preferably in the installer somewhere, about setting up for a dual boot. I couldn't find in the handbook, (that may be my fault, don't know, but i finally googled the info i needed, after thinking that I had inadvertently committed my Windows slice into the abyss. maybe that was a good thing, but IMO though, the installer should be as lightweight and spare as possible, that is, if the engineering dudes are writing it. I would rather see them doing their fantastic work on the OS, not on the installer anyway. Seems to me that a full-featured GUI installer would be a good project for the community? (ok, yeah they could have left sysinstall alone, but so what???) If you had to depend on sysinstall on a daily basis, i could see having issues with the change, but then again, if you are using it that often a custom install scriptsomething... would be better anyway. from my point of view, I would rather learn how to do this by hand, because then i would come out learning a lot more, and knowing more about my own system. Probably be next on my agenda. since this is my first contact with the community, I would like to thank the development folks properly for the awesome work that they do, and to those who contribute to this list. Kyle Adkins Sent from my iPad On Jan 23, 2012, at 9:27 AM, Mark Felder f...@feld.me wrote: All of these complaints can go directly to /dev/null Just as you don't get to express your opinion about the government if you don't vote, you don't get to express your opinion about -RELEASE changes when you didn't run the STABLE/RC/BETAs. You had your chance to help improve FreeBSD for everyone, assuming your concerns really are valid and far-reaching. You opted out. No longer the core team's problem. Closed: WORKSFORME ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Horrible installer (was: Re: FreeBSD 9)
On Monday 23 January 2012 05:18:01 pm B. Kyle Adkins wrote: I'm very new to FreeBSD but it seems to me that the installer is pretty much ok. My only wish is that there might be a little more info upfront somewhere, preferably in the installer somewhere, about setting up for a dual boot. I couldn't find in the handbook, (that may be my fault, don't know, but i finally googled the info i needed, after thinking that I had inadvertently committed my Windows slice into the abyss. maybe that was a good thing, but Heh, I remember back in the day when I FIRST got to use FreeBSD for the very first time; I bought the BSD PowerPak, complete with FreeBSD 4.0, the 4 CD-ROM set, and a 6 CD toolkit, and The Complete FreeBSD book 3rd edition, Which is one of the best books ever written on BSD, or any OS period. Back then, I was running my Computer, it had Windows 98 SE, dual booting with a Linux distro (I used a few and formatted a lot to try new things so it could have been any of them) and then I decided to tri-boot Windows 98 SE, Linux, and FreeBSD... To put it mildly; The BSD installer overwrote my MBR even though I said not to, and wouldn't boot Windows. So it only booted Linux and FreeBSD. I was TOTALLY new to Computers in general still, but even back then, I knew I'd stumbled upon something special. I've also had installs go bad and I couldn't boot Windows anymore either, so I know how you feel. Right now, My Wife and I have 11 computers, and all of mine are running some form of BSD (ONLY FreeBSD and PC-BSD, which is FreeBSD with a pretty pain job and some custom apps that I like) and then a Slackware 12.0 FTP Server which is just my first Computer I ever bought because it still works, and then, I have my main desktop dual booting Windows 7 and Slackware as well. Every other machine is now running some form of FreeBSD. I like that. BSD has come a long way in terms of desktop usability over the years. I mean you could use FreeBSD as a Desktop or Workstation easily, but it COULD be a little but of a pain in the butt now and then for that, as it really is aimed at Servers. These days; It's much easier I think. And I LOVE FreeBSD. I have downloaded and tried out NetBSD but I didn't ever like it. I refuse to try OpenBSD, because I hate that damned talking turnip Theo, and, if anyone remembers unixpunx back in the day, I still have the Live CD they made based on FreeBSD :) IMO though, the installer should be as lightweight and spare as possible, that is, if the engineering dudes are writing it. I would rather see them doing their fantastic work on the OS, not on the installer anyway. Seems to me that a full-featured GUI installer would be a good project for the community? Actually, you could try out PC-BSD :) I'm installing 9.0 on my Laptop right now. I predict in the near future, with the rate at which PC-BSD is going, it's going to become MAJOR MAJOR COMPETITION to Linux, and even the Idiotic Ubuntu. I don't like Ubuntu... I do like Slackware and SUSE, but Ubuntu just. I like Debian, and it's retarded cousin Ubuntu is NOT for me. I use the installation media I have for it, for the SAME purpose I use my Windows NT and Windows Server 2003 Enterprise Edition CDs; Coffee Coasters. from my point of view, I would rather learn how to do this by hand, because then i would come out learning a lot more, and knowing more about my own system. Probably be next on my agenda. I personally would like to learn that part too. However, I don't think it should EVER be a requirement. I mean, when it comes down to it, I think we could all admit, FreeBSD is the most popular BSD because it was the first one to actually try and get something out there that was installable without being a guru. NetBSD and OpenBSD are barely catching up, and I don't care; FreeBSD and PC-BSD, are becoming very quickly my main OSs these days. I used to use SUSE Debian and Slackware for most of my stuff, but anymore, I don't. BSD has, FINALLY, got something called PC-BSD where I can use the stability of FreeBSD, but, with then fast and easy set up of something like RedHat. I hate RedHat so I'm VERY happy Pc-BSD has come along so far. I've got versions of it going back pretty far heh. I actually have a CD / DVD case that is dedicated JUST to BSD. and it's LOADED. FreeBSD going back to 4.0, and other BSD stuff I have. All in there. And For Christmas, I got a new FreeBSD tee, hoody, and a FreeBSD CD/DVD Case. I LOVE it. I also got stickers and stuff, and ANOTHER FreeBSD PC Case thingy, and I love it. since this is my first contact with the community, I would like to thank the development folks properly for the awesome work that they do, and to those who contribute to this list. If you want to thank them properly, I'd HIGHLY recommend buying some of the books! Look into The FreeBSD Mall and on the left hand side, you'll see a section called Books and Magazines. Look
Re: Horrible installer (was: Re: FreeBSD 9)
On Monday 23 January 2012 12:17:33 pm Mark Felder wrote: I've recently been presented with new information: namely that RC3 had sysinstall as an option (I did not know this, and I've been reading the lists) and that it was taken away for -RELEASE even though it was agreed upon that would not happen for 9.x. I'll crawl under this rock now. Instead of crawling under a Rock, how about everyone here, ALL of the people I've seen in this thread trashing each other; ALL of you, just take 60 seconds, take a DEEP breath, and realize we ARE a Community, which is a lot like a family in some ways. That means we aren't always going to agree with each other, and that we may even want to punch one another in the head from time to time, but, at the least, can all of you who ARE getting pissed off like that, at LEAST be respectfulof one another? God, it's like being on an Ubuntu mailing list with this thread and I WILL NOT stand for that! If I wanted to use shoddy shitty software that some asshole Billionaire ripped off from another OS I'd go buy Windows and pretend I was being bent over. I don't personally care if everyone here gets along or anything, but I DO care when you start insulting each other over OPINIONS. I'm not going to say that stupid cliche about how everyone has one, because I think it's cheezy, but damn it this is FreeBSD! The most Stable OS on Earth. (If you take into account that you don't need a 40 millon dollar cluster to run it and all that). I've been watching this thread from the start, and I've replied to a few posts myself, but it's like, seriously? You have to insult EVERY person you don't agree with? I don't have an issue with insulting morons. I'd make it a sport if I could and I LOVE being a condescending jerk sometimes. But, on a list such as this, it's making us ALL look bad! So, to all of you taking part in this thread; Can we turn the bashing off for a while? We're FreeBSD users, and I sort of expect... No, I EXPECT that we all can act professional! So, PLEASE, if you have an issue with someone on here, and you want to bash them for it... Why not just reply to their email address instead of the list itself? work it out! Man up! If your pooter hurts; the Vagisil is in the same isle as the Depends. Suck it up! (Yes, I'm trying to add humor I'm one of those people who can't deal with certain high stress situations so I try and crack jokes and stuff. But yea, I'm a playful person right now because the Oxy kicked in, but yea, can we not bash each other over opinions?). Anyway, I fully understand BOTH sides of what everyone is saying. I really do for the most part. I know that bsdinstall has it's issues, but don't you think that the FreeBSD team is watching this? You know they WILL get it going and fix it up, so just be professional. Make a list of EVERYTHING that EVERYONE doesn't like about bsdinstall, and get the list to the right people who can do something about it. I mean come on You HAVE the source Write something better, or, at least, get the stuff that bugs you to the people in charge. It will be OK! I've been working with BSD since 4.0, do you really think this is the first time something happened where people were upset? Jeez guys They'll work it out and we'll be fine, OK? -Allen -- BSD user ___ 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 9
On Thu, Jan 19, 2012 at 05:31:00PM -0800, Devin Teske wrote:
-Original Message- From: 'Frank Shute'
[mailto:fr...@shute.org.uk] Sent: Thursday, January 19, 2012 4:52
PM To: Devin Teske Cc: 'Chad Perrin';
freebsd-questions@freebsd.org; Dave Robison Subject: Re: FreeBSD 9
On Thu, Jan 19, 2012 at 02:36:29PM -0800, Devin Teske wrote:
I believe the difficulty in maintenance stems primarily
from the fact that the existing partition editor MAY have to
be entirely rewritten to accommodate other root filesystem
types (but even that's not entirely true -- if done right).
Other than that, it's most likely just FUD and misperception
that sysinstall(8) is either (a) hard to maintain or (b)
hard to extend. -- Devin
To quote the manpage for sysinstall:
BUGS
snip
This utility is a prototype which lasted several years
past its expira- tion date and is greatly in need of
death.
There are a (great) number of undocumented variables.
UTSL.
Perspective.
Let's take a look at the commit history for this manual.
Let's not. Let us discuss the merit of what the manpage says.
There are a (great) number of undocumented variables.
From my reading of postings to this list and stable@,
yet not -sysinstall@ (?!)
Didn't know it existed until now!
it was felt that sysinstall couldn't be extended without a total
re-write, that seems to suggest that the manpage is right and is
not FUD.
I disagree. Just because you document something doesn't make it
true.
I've already discussed the fact that the first line you quoted (in
need of death) is 15+ years old and we have no way of tracking its
origin and thus can't extrapolate why on-Earth it was put into a
release-quality product in the first place.
The second line you quote (which was added 2 years 10 months ago via
SVN r189754 by grog@) has everything to do with highlighting the
fact that sysinstall(8) is highly scriptable through a large number
of under-documented dispatch keywords and nothing to do with the
total re-write issue you're discussing.
Plus, the keywords are a lot more documented than you think. If a
dispatch word is not documented, there's probably good cause (a
great number of the dispatch keywords are meant for internal use
only and their documentation would merely invite strangeness only
reserved for people that know what they're doing -- i.e. they can
read the code to learn what their function is).
However, I will concede to the fact that the number of dispatch
keywords that are documented versus ones that CAN be used is only
about 33%.
Here's how I generated that number...
awk '/VAR_/{sub(/[^]*/,);sub(/$/,);print}'
/usr/src/usr.sbin/sysinstall/sysinstall.h | sh -c 'while read var;do
zgrep -q \$var\ /usr/share/man/man8/sysinstall.8.gz
varcount=$((${varcount:-0}+1));done;echo $varcount'
This returns the number of variables -- as-defined-as a dispatch
keyword in sysinstall.h -- are present in the manual.
In 9.0-RELEASE, it returns 33 for me.
In contrast with the number of dispatch keywords, obtainable by:
awk '/VAR_/{print}' | wc -l
which returns 105 for me ... minus the markedly internal keywords
which begin with _...
awk '/VAR_/{print}' | grep -vc '_'
We see 101 supposedly-usable dispatch keywords which brings us to
about 33% documentation.
However, I will re-iterate...
The first quote you pulled from the man-page was made 15+ years ago,
the second quote you pulled was from 2+ years ago and the two are
not related. The first declares some inferred quality about the code
itself and the second simply states that the variable keywords are
under-documented. One not-necessarily imply the other or vice-versa.
-- Devin
Devin, damn you with your logic, sensible arguments
*statistics*[spit] ;)
You've obviously got more invested in sysinstall than I have. It was
always a thing that I just muddled through to get a minimal system up
running.
But if you're using the scripting interface then I can see that you
would want something of equivalent functionality in the replacement,
bsdinstall.
Regards,
--
Frank
Contact info: http://www.shute.org.uk/misc/contact.html
pgp0xdjiNi6hm.pgp
Description: PGP signature
Re: FreeBSD 9
Allan McKinnon mckinnon at live.com writes: ... I really enjoyed the old installer because then I had complete control over how I tweaked my computer during and after the install. I agree. The new installer got rid of dependencies and is scriptable - very good ! But the new installer looks primitive now. There were e.g. error messages that were incomprehensive, or did not return user to the beginning of a particular step or allow to continue, instead just interrupted the installation - a sign of untested software. That's not good for an introduction to OS which every installer is to a user. Perhaps the dev should take a look at PC-BSD installer for an inspiration. Please make changes soon, for 9.1 release if possible. inquiz ___ 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 9
At 10:05 19/01/2012, you wrote: Allan McKinnon mckinnon at live.com writes: ... I really enjoyed the old installer because then I had complete control over how I tweaked my computer during and after the install. I agree. The new installer got rid of dependencies and is scriptable - very good ! But the new installer looks primitive now. There were e.g. error messages that were incomprehensive, or did not return user to the beginning of a particular step or allow to continue, instead just interrupted the installation - a sign of untested software. That's not good for an introduction to OS which every installer is to a user. I think that a full/complete update of the old installer to add it support GEOM, ZFS, scripting and more newer features will consume more manpower and resources than create a new one from scratch, where the devs aren't chained by old code, backwards compatibility, old restrictions and old point of views. This way, is easier correct bugs, new features, simplify the installation and even automate it to this new installer than try to add them to the old one. As always, i suppose that any ideas and help are welcome. Perhaps the dev should take a look at PC-BSD installer for an inspiration. Please make changes soon, for 9.1 release if possible. Or 8.3 ;) inquiz ___ 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 9
Eduardo Morras nec556 at retena.com writes: ... I think that a full/complete update of the old installer to add it support GEOM, ZFS, scripting and more newer features will consume more manpower and resources than create a new one from scratch, where the devs aren't chained by old code, backwards compatibility, old restrictions and old point of views. This way, is easier correct bugs, new features, simplify the installation and even automate it to this new installer than try to add them to the old one. As always, i suppose that any ideas and help are welcome. ... If devs decided that there are good technical and other reasons to retire the old installer, then that's fair enough. But then the new installer has to be at least equal in features, functionality, and overall quality. Take a look at: http://distrowatch.com/weekly.php?issue=20100308#feature Installation, etc. Very impressive. inquiz ___ 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 9
On Jan 18, 2012 9:37 PM, Allan McKinnon mckin...@live.com wrote: I finally got to install FreeBSD 9 onto my computer and noticed that the installer is now different. It seems to me that it forces you into doing extra steps that I was comfortable doing on my own. I really enjoyed the old installer because then I had complete control over how I tweaked my computer during and after the install. I am surprised that there is no gui present while installing FreeBSD because it feels more like Ubuntu or a windows install (somewhat). Please, please, please take this nightmare away and bring the beloved installer that was before FreeBSD 9. Thank you for listening. Allan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org I am going to have to agree. The new installer is terrible ___ 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
Horrible installer (was: Re: FreeBSD 9)
On 1/19/12 3:25 AM, Allan McKinnon wrote: I finally got to install FreeBSD 9 onto my computer and noticed that the installer is now different. It seems to me that it forces you into doing extra steps that I was comfortable doing on my own. I really enjoyed the old installer because then I had complete control over how I tweaked my computer during and after the install. I am surprised that there is no gui present while installing FreeBSD because it feels more like Ubuntu or a windows install (somewhat). Please, please, please take this nightmare away and bring the beloved installer that was before FreeBSD 9. Thank you for listening. Allan ___ Erm, you have to realize the new installer was discussed at length here, when 9.0 was still under development/beta/prerelease. Then would have been the best time to voice your frustration over the new scheme. Alternatively, you could do like me and install entirely by hand: - boot an MFSBSD image (thanks mm@ ) - partition your disks from there (see http://my.gd/bsd.htm for a rough sketch on how to use gpart) - fetch the 9.0 archives in .txz (tar.xz) format - unpack archives with xz -d - untar archived to the mountpoint with your new filesystems (eg: tar xf base.tar -C /mnt) - customize configuration files (rc.conf, fstab, root's password or SSH key, sshd_config to allow root login temporarily) And then most of all, profit ;) I've been doing installs this way first with 8.x (using the install scripts on the CDROM) then now with 9.x unpacking the .txz archives. I'm quite happy with it, the process is simple enough to document and reproduce, and offers suitable customization options. We've developed a tiny web interface here that lets us customize the size, type and label of our GPT partitions, hostname, IP address, root password and SSH accounts/keys to deploy on such newly installed machines. The interface spits the whole wall of commands to paste once logged in to the MFSBSD image to install the new OS and configure it. Works like a charm really. ___ 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 9
On Jan 19, 2012, at 1:05 AM, inquiz inq...@gmx.com wrote: Allan McKinnon mckinnon at live.com writes: ... I really enjoyed the old installer because then I had complete control over how I tweaked my computer during and after the install. I agree. The new installer got rid of dependencies and is scriptable - very good ! ??? *cough* Old installer _is_ scriptable and had less external dependencies as it was written in C not sh(1) *cough* -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: * Re: FreeBSD 9
Devin Teske devin.teske at fisglobal.com writes: ... The new installer got rid of dependencies and is scriptable - very good ! ??? *cough* Old installer _is_ scriptable and had less external dependencies as it was written in C not sh(1) *cough* Well, here it is: http://wiki.freebsd.org/BSDInstall inquiz ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: * Re: FreeBSD 9
On Jan 19, 2012, at 7:20 AM, inquiz wrote: Devin Teske devin.teske at fisglobal.com writes: ... The new installer got rid of dependencies and is scriptable - very good ! ??? *cough* Old installer _is_ scriptable and had less external dependencies as it was written in C not sh(1) *cough* Well, here it is: http://wiki.freebsd.org/BSDInstall Right, but those claims (1 - being scriptable and 2 - not requiring utilities outside the base) are *both* not unique to bsdinstall and its predecessor (sysinstall) exhibited both those features long before bsdinstall. We've been scripting sysinstall since 2006. Successfully, I might add (and yes, we plan to release a 9.0 scripted sysinstall image to share the love). -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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 9
On Thu, Jan 19, 2012 at 11:15:08AM +0100, Eduardo Morras wrote: I think that a full/complete update of the old installer to add it support GEOM, ZFS, scripting and more newer features will consume more manpower and resources than create a new one from scratch, where the devs aren't chained by old code, backwards compatibility, old restrictions and old point of views. This way, is easier correct bugs, new features, simplify the installation and even automate it to this new installer than try to add them to the old one. I'm curious: Is this just speculation, or have you determined this by reading the source of the old installer? Old code means *tested* code, and when it is well-maintained it often means easily extensible code. Is that the case for the old installer, or is the older installer a crufty mess of temporary fixes that became permanent, as your statements seem to imply? -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.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 9
On Thu, Jan 19, 2012 at 10:41:37AM +, inquiz wrote: Eduardo Morras nec556 at retena.com writes: ... I think that a full/complete update of the old installer to add it support GEOM, ZFS, scripting and more newer features will consume more manpower and resources than create a new one from scratch, where the devs aren't chained by old code, backwards compatibility, old restrictions and old point of views. This way, is easier correct bugs, new features, simplify the installation and even automate it to this new installer than try to add them to the old one. As always, i suppose that any ideas and help are welcome. ... If devs decided that there are good technical and other reasons to retire the old installer, then that's fair enough. But then the new installer has to be at least equal in features, functionality, and overall quality. . . . or provide the ability to select the old installer at boot time, perhaps. Let's not turn this into a false dilemma; I don't see why we can't have our cake and eat it too for a while. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.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 9
On Jan 19, 2012, at 8:46 AM, Chad Perrin wrote: On Thu, Jan 19, 2012 at 10:41:37AM +, inquiz wrote: Eduardo Morras nec556 at retena.com writes: ... I think that a full/complete update of the old installer to add it support GEOM, ZFS, scripting and more newer features will consume more manpower and resources than create a new one from scratch, where the devs aren't chained by old code, backwards compatibility, old restrictions and old point of views. This way, is easier correct bugs, new features, simplify the installation and even automate it to this new installer than try to add them to the old one. As always, i suppose that any ideas and help are welcome. ... If devs decided that there are good technical and other reasons to retire the old installer, then that's fair enough. But then the new installer has to be at least equal in features, functionality, and overall quality. . . . or provide the ability to select the old installer at boot time, perhaps. Let's not turn this into a false dilemma; I don't see why we can't have our cake and eat it too for a while. Before sysinstall is simply made available as an option, it first needs to be taught how to handle a monolithic txz file because the structure of the system has changed. Also... sysinstall expects to boot into a RW filesystem, and I don't know yet whether the architecture has changed in this respect. If bsdinstall doesn't boot into an MFS, then having the boot loader set vfs.root.mountfrom.options to rw is of little effect (for example, if you're booting directly into an ISO 9660 filesystem which can't be made writable -- unionfs aside). So, whatever prompt the user is given to choose between sysinstall and bsdinstall... said prompt best be pretty early in the game (if we're going to fork to two different operating environments: MFS versus ISO 9660). -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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 9
2012/1/19 Jonathan Vomacka juvi...@gmail.com: On Jan 18, 2012 9:37 PM, Allan McKinnon mckin...@live.com wrote: I finally got to install FreeBSD 9 onto my computer and noticed that the installer is now different. It seems to me that it forces you into doing extra steps that I was comfortable doing on my own. I really enjoyed the old installer because then I had complete control over how I tweaked my computer during and after the install. I am surprised that there is no gui present while installing FreeBSD because it feels more like Ubuntu or a windows install (somewhat). Please, please, please take this nightmare away and bring the beloved installer that was before FreeBSD 9. Thank you for listening. Allan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org I am going to have to agree. The new installer is terrible Actually, I like the new installer, it's great, simple, fast and straight forward; only uncompress 4 files and you're done, still let you enable the services you need. I think it can be improved a little more though, for instance the manual partition utility could show the total available free space in units that will actually fill the disk/partition (It recommended me to create a 40G partition and let 800Mb unpartitioned hole at the end) and could also show a resume of the steps to be performed. Other than that, I think is a good improvement. Cheers Ismael ___ 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 -- Do not let me induce you to satisfy my curiosity, from an expectation, that I shall gratify yours. What I may judge proper to conceal, does not concern myself alone. ___ 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 9
-Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- questi...@freebsd.org] On Behalf Of Chad Perrin Sent: Thursday, January 19, 2012 8:43 AM To: freebsd-questions@freebsd.org Subject: Re: FreeBSD 9 On Thu, Jan 19, 2012 at 11:15:08AM +0100, Eduardo Morras wrote: I think that a full/complete update of the old installer to add it support GEOM, ZFS, scripting and more newer features will consume more manpower and resources than create a new one from scratch, where the devs aren't chained by old code, backwards compatibility, old restrictions and old point of views. This way, is easier correct bugs, new features, simplify the installation and even automate it to this new installer than try to add them to the old one. I'm curious: Is this just speculation, or have you determined this by reading the source of the old installer? Old code means *tested* code, and when it is well- maintained it often means easily extensible code. Is that the case for the old installer, or is the older installer a crufty mess of temporary fixes that became permanent, as your statements seem to imply? I believe the difficulty in maintenance stems primarily from the fact that the existing partition editor MAY have to be entirely rewritten to accommodate other root filesystem types (but even that's not entirely true -- if done right). Other than that, it's most likely just FUD and misperception that sysinstall(8) is either (a) hard to maintain or (b) hard to extend. -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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 9
On Thu, Jan 19, 2012 at 11:22:14AM -0800, Devin Teske wrote: On Thu, Jan 19, 2012 at 11:15:08AM +0100, Eduardo Morras wrote: I think that a full/complete update of the old installer to add it support GEOM, ZFS, scripting and more newer features will consume more manpower and resources than create a new one from scratch, where the devs aren't chained by old code, backwards compatibility, old restrictions and old point of views. This way, is easier correct bugs, new features, simplify the installation and even automate it to this new installer than try to add them to the old one. I'm curious: Is this just speculation, or have you determined this by reading the source of the old installer? Old code means *tested* code, and when it is well- maintained it often means easily extensible code. Is that the case for the old installer, or is the older installer a crufty mess of temporary fixes that became permanent, as your statements seem to imply? I believe the difficulty in maintenance stems primarily from the fact that the existing partition editor MAY have to be entirely rewritten to accommodate other root filesystem types (but even that's not entirely true -- if done right). Other than that, it's most likely just FUD and misperception that sysinstall(8) is either (a) hard to maintain or (b) hard to extend. -- Devin To quote the manpage for sysinstall: BUGS snip This utility is a prototype which lasted several years past its expira- tion date and is greatly in need of death. There are a (great) number of undocumented variables. UTSL. I welcome the new installer. sysinstall was a piece of buggy garbage that gave a pretty poor first impression of FreeBSD. The new installer will get better with time. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html pgpqyW22oYPpS.pgp Description: PGP signature
RE: FreeBSD 9
-Original Message- From: Frank Shute [mailto:fr...@shute.org.uk] Sent: Thursday, January 19, 2012 12:01 PM To: Devin Teske Cc: 'Chad Perrin'; freebsd-questions@freebsd.org Subject: Re: FreeBSD 9 On Thu, Jan 19, 2012 at 11:22:14AM -0800, Devin Teske wrote: On Thu, Jan 19, 2012 at 11:15:08AM +0100, Eduardo Morras wrote: I think that a full/complete update of the old installer to add it support GEOM, ZFS, scripting and more newer features will consume more manpower and resources than create a new one from scratch, where the devs aren't chained by old code, backwards compatibility, old restrictions and old point of views. This way, is easier correct bugs, new features, simplify the installation and even automate it to this new installer than try to add them to the old one. I'm curious: Is this just speculation, or have you determined this by reading the source of the old installer? Old code means *tested* code, and when it is well- maintained it often means easily extensible code. Is that the case for the old installer, or is the older installer a crufty mess of temporary fixes that became permanent, as your statements seem to imply? I believe the difficulty in maintenance stems primarily from the fact that the existing partition editor MAY have to be entirely rewritten to accommodate other root filesystem types (but even that's not entirely true -- if done right). Other than that, it's most likely just FUD and misperception that sysinstall(8) is either (a) hard to maintain or (b) hard to extend. -- Devin To quote the manpage for sysinstall: BUGS snip This utility is a prototype which lasted several years past its expira- tion date and is greatly in need of death. There are a (great) number of undocumented variables. UTSL. Perspective. Let's take a look at the commit history for this manual. Try as you might, you can't go back far-enough to find when that message was even added. However, you can see where the message was tweaked slightly by a couple people: SVN r49961 by mpp@ addressing PR docs/13148 and docs/13144 Prior to-which the message said 3 years past (s/3/several/) SVN r40275 by jkh@ (no PR mentioned) Prior to-which the message said 2 years past (s/2/3/) So, literally for the past 15+ years, the man-page has said essentially the same thing prototype ... in need of death. I raise the hypothesis that: a. The prototype ... in need of death message in the man-page was added by the original author, whom... b. ...had self-esteem issues on that particular day (hence the self-denigrating remark about one's code). I further pontificate that once the original author relinquished control of sysinstall(8) (whomever that may be -- since commit logs don't go back that far) that one of the 2-dozen-plus committers should have removed that message to quell evident propagation of FUD against sysinstall(8)). Afterall, who's to say that sysinstall(8) was still a prototype when it was being used for several major releases in production and enterprise environments. But instead, this entry in the man-page was not removed, year-after-year, but instead maintained (with no apparent rhyme or reason). The situation is the exact opposite of what we're seeing with bsdinstall. sysinstall(8) was added to the tree as a prototype yet was stable. Now we see bsdinstall added to the tree as a NON-prototype yet is NOT-stable or free of show-stoppers! I welcome the new installer. sysinstall was a piece of buggy garbage that gave a pretty poor first impression of FreeBSD. I think we have some very different opinions of what buggy is. The new installer will get better with time. The new installer is buggy, and the above maxim is something I'd rather not have to deal with when downloading RELEASE software. RELEASE software shouldn't be released under the statement it will get better with time. Releasing feature-INcomplete software that is known to be broken hurts the FreeBSD impression far more than sysinstall ever could/did. I feel your argument is an attempt to justify the egregious offense of foisting premature software on the community when in-fact it does NOT replicate even a fraction of the abilities of sysinstall. IMHO. -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions
Re: FreeBSD 9
On Thu, Jan 19, 2012 at 02:36:29PM -0800, Devin Teske wrote: From: Frank Shute The new installer will get better with time. The new installer is buggy, and the above maxim is something I'd rather not have to deal with when downloading RELEASE software. I do not dispute that the new installer is buggy, nor do I agree that it is buggy. I have used it twice, without any bugs biting me. That may just be good luck. I have, however, discovered that usability is no better than sysinstall; it's just *different*. In fact, in some respects, it feels more limiting. I suspect some of my issues with it will be resolved by simple familiarity -- but then, some of those issues are not due solely to differences between bsdinstall and sysinstall; they are also due to differences between bsdinstall and *every* console-based piece of software with that general curses-style appearance. Maybe I'll never get to quite *that* level of familiarity with bsdinstall, considering I use a lot of other console-based applications, too. I do not recall running into any bugs in sysinstall, either, by the way. Considering how many more times I have used it, I think it is far less likely that I was just lucky. Perhaps it has bugs, but it must have bugs primarily with features for which I have (so far) had no use. If the fact sysinstall does not support some functionality needed for installation of new versions of FreeBSD (I believe someone has suggested this is the case) while bsdinstall does is a result of sysinstall's architecture being insufficiently well organized for the addition of this functionality to be a reasonable alternative to writing a new installer instead, I can understand the desire to create and propagate the use of bsdinstall. In that case, great: I'm glad we're moving forward. If it is functionality that not everyone needs, I think it might be nice to offer both installers as options (perhaps bsdinstall as the default, if we must). As someone who has never really looked into the code used to handle starting the installation process, I do not know how feasiable that is, and would appreciate someone who knows from first-hand experience enlightening me as to whether it's a good idea. It is likely that many people will not need the new functionality that bsdinstall would support, if it relates to things like ZFS support, after all. If the reason it was decided to create bsdinstall and replace sysinstall was simply to do something new, without particular interest in maintaining the benefits provided by sysinstall, and without any actual technical requirement for the new installer, I have a somewhat different opinion -- one normally reserved for ludicrous exercises of neophilia like those rampant in the Ubuntu community in particular and the Linux community in general, breaking all the old ways of doing things just because someone decided to write some code one day. Did you know that ifconfig is no longer guaranteed to work as a tool for restarting networking on Linux-based systems? Are you aware of the Cthulhoid tentacular horror of the Linux sound architecture, especially with PulseAudio thrown into the mix? Have you seen the filesystem and shell environment clutter that is the XDG Base Directory Specification? Please, let the reasons behind bsdinstall be better than for all of those messes. I'm inclined to believe that the motives for bsdinstall are good motives, knowing what I do of the FreeBSD developers' philosophy (maybe not a lot, but enough to know it tends to eschew such radical changes for change's sake, in my experience). It may have moved slightly too quickly, but it may be a movement in the right direction nonetheless, and I hope it is. I'd just like to know more about the whys and wherefores than statements (from people who have not indicated where I can see it that they actually know anything about it first-hand) that sysinstall is buggy because the manpage says so and bsdinstall is not because it's not sysinstall. RELEASE software shouldn't be released under the statement it will get better with time. Releasing feature-INcomplete software that is known to be broken hurts the FreeBSD impression far more than sysinstall ever could/did. I feel your argument is an attempt to justify the egregious offense of foisting premature software on the community when in-fact it does NOT replicate even a fraction of the abilities of sysinstall. I also think it's worthwhile to give people the benefit of the doubt, at least at first. Perhaps the rhetoric can be scaled back a little bit in this case. Has there been some response to your complaints that I have not seen that justifies this level of heat? -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to
RE: FreeBSD 9
-Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- questi...@freebsd.org] On Behalf Of Chad Perrin Sent: Thursday, January 19, 2012 3:15 PM To: freebsd-questions@freebsd.org Subject: Re: FreeBSD 9 On Thu, Jan 19, 2012 at 02:36:29PM -0800, Devin Teske wrote: From: Frank Shute The new installer will get better with time. The new installer is buggy, and the above maxim is something I'd rather not have to deal with when downloading RELEASE software. I do not dispute that the new installer is buggy, nor do I agree that it is buggy. It surely has numerous usability problems. a. SHIFT+TAB is interpreted as ESC causing a dialog to be dismissed with no easy way to return to said dialog b. TAB does not move the cursor to the next field in a multi-field dialog such as IPv4 manual configuration (usability issue arises when you press TAB, nothing happens, you next try ENTER and are surprised null fields are accepted/not-validated and you're then whisked off to the next screen; again, no easy way to return to said dialog despite the fact that clearly bad-values were given for netmask/etc.) c. stderr is sent to the same console as stdout, making it impossible to read errors as they get printed and then subsequently wiped from screen by the next dialog (this ties into the above... the bad values provided cause errors which can't be seen; you only see them fly by for a micro-second and can't use Scroll-lock to view them as dialog wiped the buffer). d. Almost no user-provided values are taint-checked. A hostname for example does not need to conform to any of the given RFCs that dictate the format of a multi-label FQHN. e. bsdinstall provides no easy way of discovering which arguments it supports (other than looking in /usr/libexec/bsdinstall -- which if you don't know this, you're in the dark). That is to say that it has no -h, no --help, no list, and no exploration mode. This usability issue is fueling threads that propose we remove any/all post-installation procedures from bsdinstall and move them to a new utility called bsdconfig which provides a master-list of all sub-modules that can be invoked (as this closer matches how config utilities are utilized versus install utilities). It really is a serious usability issue that bsdinstall without arguments does not have an execution path that can lead to re-obtaining the network configuration dialog (which you've presumably bombed-out-of due to one of the previously-mentioned usability issues). -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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 9
-Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- questi...@freebsd.org] On Behalf Of Chad Perrin Sent: Thursday, January 19, 2012 3:15 PM To: freebsd-questions@freebsd.org Subject: Re: FreeBSD 9 On Thu, Jan 19, 2012 at 02:36:29PM -0800, Devin Teske wrote: From: Frank Shute The new installer will get better with time. The new installer is buggy, and the above maxim is something I'd rather not have to deal with when downloading RELEASE software. [snip] If the reason it was decided to create bsdinstall and replace sysinstall was simply to do something new The way we view the timeline of events is: 1. FreeBSD in the beginning had one official filesystem -- UFS1 -- for the root filesystem. 2. FreeBSD gets a new filesystem -- UFS2. sysinstall(8) is updated to support this as the new ONLY offering (though you can still get a UFS1 partition by pressing Z to set a custom value for newfs arguments, if you're in-the-know). 3. Enterprise FreeBSD community then desperately wants journaling filesystem, but ZFS is the only offering with built-in journaling (gjournal does not qualify here) as McKusick's SU+J is not ready yet. 4. Community recognizes that sysinstall(8) needs to be updated but can't envision a successful re-work of the C-code that provides the FDISK Partition Editor screen to the point where it can handle both the UFS options as well as ZFS, etc. 5. Nathan Whitehorn envisions bsdinstall to solve the problem. However, we feel that something went wrong along the way. If FreeBSD had decided that there is no need to offer ZFS-on-root and instead put their eggs in the SU+J basket, then modifying sysinstall(8) to meet the needs of supporting SU+J would have been trivial at-best as all options would be UFS based. Hypothetically, once you landed in the FDISK Partition Editor of sysinstall(8), the auto partitioning would default to UFS2 SU+J and you could toggle any combination of SU+J, SU-J, and no-SU/J. In fact, this is still a possibility. sysinstall(8) could be enhanced to support SU+J and the people that don't care about ZFS-on-root can be happy with the sysinstall(8) route as it still leads to a journaled filesystem. Meanwhile, if they want ZFS-on-root, they'll have to go to the bsdinstall route. -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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 9
-Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- questi...@freebsd.org] On Behalf Of Devin Teske Sent: Thursday, January 19, 2012 4:33 PM To: 'Chad Perrin'; freebsd-questions@freebsd.org Cc: Dave Robison Subject: RE: FreeBSD 9 [snip] If FreeBSD had decided that there is no need to offer ZFS-on-root and instead put their eggs in the SU+J basket, then modifying sysinstall(8) to meet the needs of supporting SU+J would have been trivial at-best as all options would be UFS based. Well, not entirely true. sysinstall(8) would need to be re-worked to support GPT versus MBR. Otherwise system is limited to 2TB on root filesystem (lol; as if that were a limit we were concerned with -- I've not seen a whole lot of setups that required 2TB for the root filesystem). -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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 9
On Thu, Jan 19, 2012 at 02:36:29PM -0800, Devin Teske wrote: I believe the difficulty in maintenance stems primarily from the fact that the existing partition editor MAY have to be entirely rewritten to accommodate other root filesystem types (but even that's not entirely true -- if done right). Other than that, it's most likely just FUD and misperception that sysinstall(8) is either (a) hard to maintain or (b) hard to extend. -- Devin To quote the manpage for sysinstall: BUGS snip This utility is a prototype which lasted several years past its expira- tion date and is greatly in need of death. There are a (great) number of undocumented variables. UTSL. Perspective. Let's take a look at the commit history for this manual. Let's not. Let us discuss the merit of what the manpage says. There are a (great) number of undocumented variables. From my reading of postings to this list and stable@, it was felt that sysinstall couldn't be extended without a total re-write, that seems to suggest that the manpage is right and is not FUD. Try as you might, you can't go back far-enough to find when that message was even added. However, you can see where the message was tweaked slightly by a couple people: SVN r49961 by mpp@ addressing PR docs/13148 and docs/13144 Prior to-which the message said 3 years past (s/3/several/) SVN r40275 by jkh@ (no PR mentioned) Prior to-which the message said 2 years past (s/2/3/) So, literally for the past 15+ years, the man-page has said essentially the same thing prototype ... in need of death. I raise the hypothesis that: a. The prototype ... in need of death message in the man-page was added by the original author, whom... b. ...had self-esteem issues on that particular day (hence the self-denigrating remark about one's code). I further pontificate that once the original author relinquished control of sysinstall(8) (whomever that may be -- since commit logs don't go back that far) that one of the 2-dozen-plus committers should have removed that message to quell evident propagation of FUD against sysinstall(8)). Afterall, who's to say that sysinstall(8) was still a prototype when it was being used for several major releases in production and enterprise environments. But instead, this entry in the man-page was not removed, year-after-year, but instead maintained (with no apparent rhyme or reason). The situation is the exact opposite of what we're seeing with bsdinstall. sysinstall(8) was added to the tree as a prototype yet was stable. Now we see bsdinstall added to the tree as a NON-prototype yet is NOT-stable or free of show-stoppers! I welcome the new installer. sysinstall was a piece of buggy garbage that gave a pretty poor first impression of FreeBSD. I think we have some very different opinions of what buggy is. It didn't do what you asked it to do on occasion. It violated pola wholesale. That didn't bother me much. I'd become familiarised with it and could work round all that to get a minimal system installed but it was a pretty poor experience for newbies. The new installer will get better with time. The new installer is buggy, and the above maxim is something I'd rather not have to deal with when downloading RELEASE software. I don't doubt that the new installer may be buggy in parts but so was sysinstall and nobody was tempted to fix it. At least with bsdinstall people are actively developing it. RELEASE software shouldn't be released under the statement it will get better with time. Releasing feature-INcomplete software that is known to be broken hurts the FreeBSD impression far more than sysinstall ever could/did. I feel your argument is an attempt to justify the egregious offense of foisting premature software on the community when in-fact it does NOT replicate even a fraction of the abilities of sysinstall. IMHO. -- Devin It's a chicken/egg situation. Eventually you have to release software that is possibly buggy/feature incomplete or nobody tests it and files pr's. Arguments can be had about whether it was released too soon but I'm not tempted to get into them. It's odd that sysinstall should get support now, it got bugger all support when it was alive. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html pgpCzji05GI3y.pgp Description: PGP signature
RE: FreeBSD 9
-Original Message-
From: 'Frank Shute' [mailto:fr...@shute.org.uk]
Sent: Thursday, January 19, 2012 4:52 PM
To: Devin Teske
Cc: 'Chad Perrin'; freebsd-questions@freebsd.org; Dave Robison
Subject: Re: FreeBSD 9
On Thu, Jan 19, 2012 at 02:36:29PM -0800, Devin Teske wrote:
I believe the difficulty in maintenance stems primarily from the
fact that the existing partition editor MAY have to be entirely
rewritten to accommodate other root filesystem types (but even
that's not entirely true -- if done right).
Other than that, it's most likely just FUD and misperception that
sysinstall(8) is either (a) hard to maintain or (b) hard to
extend. -- Devin
To quote the manpage for sysinstall:
BUGS
snip
This utility is a prototype which lasted several years past
its expira- tion date and is greatly in need of death.
There are a (great) number of undocumented variables. UTSL.
Perspective.
Let's take a look at the commit history for this manual.
Let's not. Let us discuss the merit of what the manpage says.
There are a (great) number of undocumented variables.
From my reading of postings to this list and stable@,
yet not -sysinstall@ (?!)
it was felt that sysinstall
couldn't be extended without a total re-write, that seems to suggest that the
manpage is right and is not FUD.
I disagree. Just because you document something doesn't make it true.
I've already discussed the fact that the first line you quoted (in need of
death) is 15+ years old and we have no way of tracking its origin and thus
can't extrapolate why on-Earth it was put into a release-quality product in
the first place.
The second line you quote (which was added 2 years 10 months ago via SVN r189754
by grog@) has everything to do with highlighting the fact that sysinstall(8) is
highly scriptable through a large number of under-documented dispatch keywords
and nothing to do with the total re-write issue you're discussing.
Plus, the keywords are a lot more documented than you think. If a dispatch word
is not documented, there's probably good cause (a great number of the dispatch
keywords are meant for internal use only and their documentation would merely
invite strangeness only reserved for people that know what they're doing -- i.e.
they can read the code to learn what their function is).
However, I will concede to the fact that the number of dispatch keywords that
are documented versus ones that CAN be used is only about 33%.
Here's how I generated that number...
awk '/VAR_/{sub(/[^]*/,);sub(/$/,);print}'
/usr/src/usr.sbin/sysinstall/sysinstall.h | sh -c 'while read var;do zgrep -q
\$var\ /usr/share/man/man8/sysinstall.8.gz
varcount=$((${varcount:-0}+1));done;echo $varcount'
This returns the number of variables -- as-defined-as a dispatch keyword in
sysinstall.h -- are present in the manual.
In 9.0-RELEASE, it returns 33 for me.
In contrast with the number of dispatch keywords, obtainable by:
awk '/VAR_/{print}' | wc -l
which returns 105 for me ... minus the markedly internal keywords which begin
with _...
awk '/VAR_/{print}' | grep -vc '_'
We see 101 supposedly-usable dispatch keywords which brings us to about 33%
documentation.
However, I will re-iterate...
The first quote you pulled from the man-page was made 15+ years ago, the second
quote you pulled was from 2+ years ago and the two are not related. The first
declares some inferred quality about the code itself and the second simply
states that the variable keywords are under-documented. One not-necessarily
imply the other or vice-versa.
--
Devin
Try as you might, you can't go back far-enough to find when that
message was even added. However, you can see where the message was
tweaked slightly by a couple people:
SVN r49961 by mpp@ addressing PR docs/13148 and docs/13144
Prior to-which the message said 3 years past (s/3/several/)
SVN r40275 by jkh@ (no PR mentioned)
Prior to-which the message said 2 years past (s/2/3/)
So, literally for the past 15+ years, the man-page has said
essentially the same thing prototype ... in need of death.
I raise the hypothesis that:
a. The prototype ... in need of death message in the man-page was
added by the original author, whom...
b. ...had self-esteem issues on that particular day (hence the
self-denigrating remark about one's code).
I further pontificate that once the original author relinquished
control of sysinstall(8) (whomever that may be -- since commit logs
don't go back that far) that one of the 2-dozen-plus committers should
have removed that message to quell evident propagation of FUD against
sysinstall(8)).
Afterall, who's to say that sysinstall(8) was still a prototype when
it was being used for several major releases in production and
enterprise environments.
But instead, this entry in the man-page was not removed,
year
Re: FreeBSD 9 on an AMD64 with an LSI SAS controller
On 10/2/11 11:48 AM, Jukka A. Ukkonen wrote: Greetings all, Roughly a week ago I sent to this mailing list a question about problems with installing FreeBSD 9 on an AMD64 system. It seems that I now know the reason why booting from the install CD failed. When buying the system I had not paid enough attention to the fact that the SAS controller on the motherboard is a new LSI SAS2008-IR which would need the mps driver. I had been assuming that since there is an LSI controller on the motherboard the older mpt driver should work. The mps driver, which would be needed for the SAS2008 series is still relatively new work in progress, is apparently not part of the GENERIC kernel used for the install kits. The next obvious question in my mind is: Are these new SAS2008 series controllers now becoming common as the default SAS chips on motherboards? If so, until the mps driver matures enough it might be better for everybody to check before selecting a motherboard that the SAS controller on it will work with the older mpt driver. mps has been backported to the 8.x branch from 9.x several months ago. AFAIK, it's included in GENERIC, there is no reason it wouldn't be. ___ 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 9-Beta3 and FlashPlayer
Hi, this mail is from Japan. My name is Hiroshi Saeki, a hobby user of FreeBSD. I think that this issue is invoked by kernel of FreeBSD 9.0-BETA3. /usr/src/sys/kern/uipc_usrreq.c 1.244.2.2 may have problem. I recommend you to revert older kernel. For example, downgrade to FreeBSD 9.0-BETA2, BETA1. ftp://ftp2.jp.freebsd.org/pub/FreeBSD/ISO-IMAGES-amd64/9.0/FreeBSD-9.0-BETA1-amd64-disc1.iso may of your help. With warm regards. On Thu, 29 Sep 2011 15:40:37 +0200 crsnet.pl crs...@crsnet.pl wrote: On Thu, 29 Sep 2011 08:22:56 -0500, Edgar Rodolfo cybernaut...@gmail.com wrote: 2011/9/29, crsnet.pl crs...@crsnet.pl: Hello. I make update yesterday with csup. And i have build new firefox 7 from src. And today i see my flashplayer dont work (under Opera/Firefox). i had flash player on freebsd 8.2, but the major result is with ports, try install it, but using port check handbook. I can try, but that configuration works to yesterday and im now confuse. I see im not alone that flash stop to work after buidling firefox from sources (or one of its dependencies). Regards. Regards. ___ 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 9-Beta3 and FlashPlayer
On Fri, 30 Sep 2011 16:10:29 +0900, Hiroshi Saeki hsa...@wmail.plala.or.jp wrote: Hi, this mail is from Japan. My name is Hiroshi Saeki, a hobby user of FreeBSD. I think that this issue is invoked by kernel of FreeBSD 9.0-BETA3. /usr/src/sys/kern/uipc_usrreq.c 1.244.2.2 may have problem. I recommend you to revert older kernel. For example, downgrade to FreeBSD 9.0-BETA2, BETA1. ftp://ftp2.jp.freebsd.org/pub/FreeBSD/ISO-IMAGES-amd64/9.0/FreeBSD-9.0-BETA1-amd64-disc1.iso may of your help. With warm regards. Hello. True, i boot today from my old kernel, and flash works fine. I can say in 100% that is problem with uipc, but i realy belive that Hiroshi have right. Realy 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: FreeBSD 9-Beta3 and FlashPlayer
Now flash plugin and skype 2.0 doesn't work after applying the lastest security patch to 8.2-RELEASE $ uname -srm FreeBSD 8.2-RELEASE-p3 amd64 launching skype doesn't show any output in console, it's just silently hangs. there is nothing in logs either. Opera, firefox and nspluginwrapper are able to detect flash plugin, but there is just black square instead of flash content on web page. ___ 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 9-Beta3 and FlashPlayer
On Fri, 30 Sep 2011 09:58:48 +0200 crsnet.pl crs...@crsnet.pl wrote: On Fri, 30 Sep 2011 16:10:29 +0900, Hiroshi Saeki hsa...@wmail.plala.or.jp wrote: I think that this issue is invoked by kernel of FreeBSD 9.0-BETA3. /usr/src/sys/kern/uipc_usrreq.c 1.244.2.2 may have problem. I recommend you to revert older kernel. For example, downgrade to FreeBSD 9.0-BETA2, BETA1. ftp://ftp2.jp.freebsd.org/pub/FreeBSD/ISO-IMAGES-amd64/9.0/FreeBSD-9.0-BETA1-amd64-disc1.iso may of your help. With warm regards. Hello. True, i boot today from my old kernel, and flash works fine. I can say in 100% that is problem with uipc, but i realy belive that Hiroshi have right. Strange, flash works fine for me under 9.0-BETA3. Go figure. -- Conrad J. Sabatier conr...@cox.net ___ 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 9-Beta3 and FlashPlayer
On Fri, 30 Sep 2011 19:07:26 -0500, Conrad J. Sabatier conr...@cox.net wrote: On Fri, 30 Sep 2011 09:58:48 +0200 crsnet.pl crs...@crsnet.pl wrote: On Fri, 30 Sep 2011 16:10:29 +0900, Hiroshi Saeki hsa...@wmail.plala.or.jp wrote: I think that this issue is invoked by kernel of FreeBSD 9.0-BETA3. /usr/src/sys/kern/uipc_usrreq.c 1.244.2.2 may have problem. I recommend you to revert older kernel. For example, downgrade to FreeBSD 9.0-BETA2, BETA1. ftp://ftp2.jp.freebsd.org/pub/FreeBSD/ISO-IMAGES-amd64/9.0/FreeBSD-9.0-BETA1-amd64-disc1.iso may of your help. With warm regards. Hello. True, i boot today from my old kernel, and flash works fine. I can say in 100% that is problem with uipc, but i realy belive that Hiroshi have right. Strange, flash works fine for me under 9.0-BETA3. Go figure. [cr4sh@x300 ~]$ uname -a FreeBSD x300 9.0-BETA3 FreeBSD 9.0-BETA3 #3: Tue Sep 27 10:47:57 CEST 2011 cr4sh@x300:/sys/amd64/compile/GENERIC amd64 For me too. But i make csup yesterday, and when i build it. I get BETA3 but with damaged flash. Regards. ___ 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 9-Beta3 and FlashPlayer
On Sat, 01 Oct 2011 02:31:24 +0200
crsnet.pl crs...@crsnet.pl wrote:
On Fri, 30 Sep 2011 19:07:26 -0500, Conrad J. Sabatier
conr...@cox.net wrote:
Strange, flash works fine for me under 9.0-BETA3. Go figure.
[cr4sh@x300 ~]$ uname -a
FreeBSD x300 9.0-BETA3 FreeBSD 9.0-BETA3 #3: Tue Sep 27 10:47:57
CEST 2011 cr4sh@x300:/sys/amd64/compile/GENERIC amd64
For me too. But i make csup yesterday, and when i build it. I get
BETA3 but with damaged flash.
Hmmm, most peculiar. My last update was Wed Sep 28 04:37:01 CDT.
Was your last kernel/world build a clean build? You may want to try
updating your sources, nuking /usr/obj, and rebuilding/installing,
just in case there's a bit of incompatible cruft lying about somewhere
(not likely, I know, but it doesn't hurt to make sure).
Also, I have my plugins setup in a local, rather than a system-wide
fashion. I did do a normal install from ports of all of the relevant
packages, but then I either copied or symlinked the needed stuff under
${HOME}/.mozilla. I remember when I first went about setting up the
flash plugin and the plugin wrapper, I couldn't get it to work properly
until I did this.
Honestly, I don't know exactly why I've been spared from this recent
round of complaints I've seen from people re: flash, acroread, etc. and
the linux emulator in general. I'm just glad that I have! Must be
living right. :-)
--
Conrad J. Sabatier
conr...@cox.net
___
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 9-Beta3 and FlashPlayer
2011/9/29, crsnet.pl crs...@crsnet.pl: Hello. I make update yesterday with csup. And i have build new firefox 7 from src. And today i see my flashplayer dont work (under Opera/Firefox). Opera about:plugins Opis: Shockwave Flash 10.3 r183 /usr/local/lib/npapi/symlinks/linux-opera/libflashplayer.soapplication/futuresplash FutureSplash Player spl application/x-shockwave-flashShockwave Flash swf,swt,null,flash Firefox about:plugins File: npwrapper.libflashplayer.so Version: Shockwave Flash 10.3 r183 MIME TypeDescription Suffixes application/x-shockwave-flashShockwave Flash swf application/futuresplash FutureSplash Player spl [cr4sh@x300 ~]$ pkg_info | grep flash linux-f10-flashplugin-10.3r183.10 Adobe Flash Player NPAPI Plugin [cr4sh@x300 ~]$ pkg_info | grep nsplugi nspluginwrapper-1.4.4 A compatibility plugin for Mozilla NPAPI plugins [cr4sh@x300 ~]$ nspluginwrapper -v -i $( find / -name libflashplayer.so ) Install plugin /usr/local/lib/npapi/linux-f10-flashplugin/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/local/lib/npapi/symlinks/linux-firefox/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/local/lib/npapi/symlinks/linux-firefox-devel/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/local/lib/npapi/symlinks/linux-flock/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/local/lib/npapi/symlinks/linux-flock-devel/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/local/lib/npapi/symlinks/linux-mozilla/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/local/lib/npapi/symlinks/linux-netscape-messenger/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/local/lib/npapi/symlinks/linux-netscape-navigator/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/local/lib/npapi/symlinks/linux-nvu/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/local/lib/npapi/symlinks/linux-opera/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/local/lib/npapi/symlinks/linux-opera-devel/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/local/lib/npapi/symlinks/linux-seamonkey/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/local/lib/npapi/symlinks/linux-seamonkey-devel/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/local/lib/npapi/symlinks/linux-sunbird/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/local/lib/npapi/symlinks/linux-sunbird-devel/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/local/lib/browser_plugins/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/ports/www/linux-f10-flashplugin10/work/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/home/cr4sh/.mozilla/plugins/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so When i try to play youtube movie i get only black rectangle. I try to pkg_delete pkg_add -r nspluginwrapper, opera-linuxplugins and make linux-f10-flashplugin. But this doesn't work ;/ i had flash player on freebsd 8.2, but the major result is with ports, try install it, but using port check handbook. Regards. ___ 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 -- Edguitar ;) http://cybernautape.blogspot.com ___ 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 9-Beta3 and FlashPlayer
On Thu, 29 Sep 2011 08:22:56 -0500, Edgar Rodolfo cybernaut...@gmail.com wrote: 2011/9/29, crsnet.pl crs...@crsnet.pl: Hello. I make update yesterday with csup. And i have build new firefox 7 from src. And today i see my flashplayer dont work (under Opera/Firefox). Opera about:plugins Opis: Shockwave Flash 10.3 r183 /usr/local/lib/npapi/symlinks/linux-opera/libflashplayer.soapplication/futuresplash FutureSplash Player spl application/x-shockwave-flash Shockwave Flash swf,swt,null,flash Firefox about:plugins File: npwrapper.libflashplayer.so Version: Shockwave Flash 10.3 r183 MIME Type Description Suffixes application/x-shockwave-flash Shockwave Flash swf application/futuresplash FutureSplash Player spl [cr4sh@x300 ~]$ pkg_info | grep flash linux-f10-flashplugin-10.3r183.10 Adobe Flash Player NPAPI Plugin [cr4sh@x300 ~]$ pkg_info | grep nsplugi nspluginwrapper-1.4.4 A compatibility plugin for Mozilla NPAPI plugins [cr4sh@x300 ~]$ nspluginwrapper -v -i $( find / -name libflashplayer.so ) Install plugin /usr/local/lib/npapi/linux-f10-flashplugin/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/local/lib/npapi/symlinks/linux-firefox/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/local/lib/npapi/symlinks/linux-firefox-devel/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/local/lib/npapi/symlinks/linux-flock/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/local/lib/npapi/symlinks/linux-flock-devel/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/local/lib/npapi/symlinks/linux-mozilla/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/local/lib/npapi/symlinks/linux-netscape-messenger/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/local/lib/npapi/symlinks/linux-netscape-navigator/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/local/lib/npapi/symlinks/linux-nvu/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/local/lib/npapi/symlinks/linux-opera/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/local/lib/npapi/symlinks/linux-opera-devel/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/local/lib/npapi/symlinks/linux-seamonkey/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/local/lib/npapi/symlinks/linux-seamonkey-devel/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/local/lib/npapi/symlinks/linux-sunbird/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/local/lib/npapi/symlinks/linux-sunbird-devel/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/local/lib/browser_plugins/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/ports/www/linux-f10-flashplugin10/work/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so Install plugin /usr/home/cr4sh/.mozilla/plugins/libflashplayer.so into /home/cr4sh/.mozilla/plugins/npwrapper.libflashplayer.so When i try to play youtube movie i get only black rectangle. I try to pkg_delete pkg_add -r nspluginwrapper, opera-linuxplugins and make linux-f10-flashplugin. But this doesn't work ;/ i had flash player on freebsd 8.2, but the major result is with ports, try install it, but using port check handbook. I can try, but that configuration works to yesterday and im now confuse. I see im not alone that flash stop to work after buidling firefox from sources (or one of its dependencies). Regards. Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9-Beta3 on X300 2 problems
2011/9/27 crsnet.pl crs...@crsnet.pl: Hi, Hello, thanks for reply. Please try to do this without wlan loaded at all (not just down, but build your wifi support as a module.) Then try without X, see whether it's related to that or not. First i make kldunload if_iwn. When i try to suspend from X, Xorg close, i see console and laptop suspend. When i resume it, i get console (any key dosent work), when i try to ALT+F9 i get black screen and beep;/ But when i try to suspen from console. I get : pci0: failed to set ACPI power state D2 \_SB_.PCI0_EXP0: AE_BAD_PARAMETER pci0: failed to set ACPI power state D2 \_SB_.PCI0_EXP1: AE_BAD_PARAMETER pci0: failed to set ACPI power state D2 \_SB_.PCI0_EXP2: AE_BAD_PARAMETER And laptop suspend, when i resume it. He hangs when i press any buttons it does nothing. And than i see on console that info : ugen0.2: Broadcom Corp ... disconnected ugen4.2: Sierra Wireless ... disconnected ubt0: at uhub0 ... disconnected then i see this presed lethers and acpi0: suspend request ignored (not ready yet) and laptops langs and beep ;/ (And you haven't told us what your hardware is.) #dmesg (+WITNESS) Copyright (c) 1992-2011 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-BETA3 #3: Tue Sep 27 10:47:57 CEST 2011 cr4sh@x300:/sys/amd64/compile/GENERIC amd64 WARNING: WITNESS option enabled, expect reduced performance. CPU: Intel(R) Core(TM)2 Duo CPU L7100 @ 1.20GHz (1197.03-MHz K8-class CPU) Origin = GenuineIntel Id = 0x6fb Family = 6 Model = f Stepping = 11 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,P BE Features2=0xe3bdSSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF TSC: P-state invariant, performance statistics real memory = 2147483648 (2048 MB) avail memory = 2019139584 (1925 MB) Event timer LAPIC quality 400 ACPI APIC Table: LENOVO TP-7T FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ACPI Warning: 32/64X length mismatch in Gpe1Block: 0/32 (20110527/tbfadt-556) ACPI Warning: Optional field Gpe1Block has zero address or length: 0x102C/0x0 (20110527/tbfadt-586) ioapic0: Changing APIC ID to 1 ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: LENOVO TP-7T on motherboard CPU0: local APIC error 0x40 acpi_ec0: Embedded Controller: GPE 0x12, ECDT port 0x62,0x66 on acpi0 acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 7ef0 (3) failed Timecounter ACPI-fast frequency 3579545 Hz quality 900 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 acpi_lid0: Control Method Lid Switch on acpi0 acpi_button0: Sleep Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 vgapci0: VGA-compatible display port 0x1800-0x1807 mem 0xfa00-0xfa0f,0xe000-0xefff irq 16 at device 2.0 on pci0 agp0: Intel GM965 SVGA controller on vgapci0 agp0: aperture size is 256M, detected 7676k stolen memory vgapci1: VGA-compatible display mem 0xfa10-0xfa1f at device 2.1 on pci0 pci0: simple comms at device 3.0 (no driver attached) atapci0: Intel ATA controller port 0x1828-0x182f,0x180c-0x180f,0x1820-0x1827,0x1808-0x180b,0x1810-0x181f irq 18 at device 3.2 on pci0 ata2: ATA channel 0 on atapci0 ata3: ATA channel 1 on atapci0 pci0: simple comms, UART at device 3.3 (no driver attached) em0: Intel(R) PRO/1000 Network Connection 7.2.3 port 0x1840-0x185f mem 0xfa20-0xfa21,0xfa225000-0xfa225fff irq 20 at device 25.0 o n pci0 em0: Using an MSI interrupt acquiring duplicate lock of same type: network driver 1st dev_spec-swflag_mutex @ dev/e1000/e1000_ich8lan.c:785 2nd dev_spec-nvm_mutex @ dev/e1000/e1000_ich8lan.c:751 I think that MTX_NETWORK_LOCK is not suitable for this case as you will have 2 different locks with the same name in softc. I think that this patch should be good to go (and fixes the WITNESS warning): http://www.freebsd.org/~attilio/e1000_mutex_init.patch Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein ___ freebsd-sta...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to
Re: FreeBSD 9-Beta3 on X300 2 problems
Hi, Hello, thanks for reply. Please try to do this without wlan loaded at all (not just down, but build your wifi support as a module.) Then try without X, see whether it's related to that or not. First i make kldunload if_iwn. When i try to suspend from X, Xorg close, i see console and laptop suspend. When i resume it, i get console (any key dosent work), when i try to ALT+F9 i get black screen and beep;/ But when i try to suspen from console. I get : pci0: failed to set ACPI power state D2 \_SB_.PCI0_EXP0: AE_BAD_PARAMETER pci0: failed to set ACPI power state D2 \_SB_.PCI0_EXP1: AE_BAD_PARAMETER pci0: failed to set ACPI power state D2 \_SB_.PCI0_EXP2: AE_BAD_PARAMETER And laptop suspend, when i resume it. He hangs when i press any buttons it does nothing. And than i see on console that info : ugen0.2: Broadcom Corp ... disconnected ugen4.2: Sierra Wireless ... disconnected ubt0: at uhub0 ... disconnected then i see this presed lethers and acpi0: suspend request ignored (not ready yet) and laptops langs and beep ;/ (And you haven't told us what your hardware is.) #dmesg (+WITNESS) Copyright (c) 1992-2011 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-BETA3 #3: Tue Sep 27 10:47:57 CEST 2011 cr4sh@x300:/sys/amd64/compile/GENERIC amd64 WARNING: WITNESS option enabled, expect reduced performance. CPU: Intel(R) Core(TM)2 Duo CPU L7100 @ 1.20GHz (1197.03-MHz K8-class CPU) Origin = GenuineIntel Id = 0x6fb Family = 6 Model = f Stepping = 11 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,P BE Features2=0xe3bdSSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF TSC: P-state invariant, performance statistics real memory = 2147483648 (2048 MB) avail memory = 2019139584 (1925 MB) Event timer LAPIC quality 400 ACPI APIC Table: LENOVO TP-7T FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ACPI Warning: 32/64X length mismatch in Gpe1Block: 0/32 (20110527/tbfadt-556) ACPI Warning: Optional field Gpe1Block has zero address or length: 0x102C/0x0 (20110527/tbfadt-586) ioapic0: Changing APIC ID to 1 ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: LENOVO TP-7T on motherboard CPU0: local APIC error 0x40 acpi_ec0: Embedded Controller: GPE 0x12, ECDT port 0x62,0x66 on acpi0 acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 7ef0 (3) failed Timecounter ACPI-fast frequency 3579545 Hz quality 900 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 acpi_lid0: Control Method Lid Switch on acpi0 acpi_button0: Sleep Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 vgapci0: VGA-compatible display port 0x1800-0x1807 mem 0xfa00-0xfa0f,0xe000-0xefff irq 16 at device 2.0 on pci0 agp0: Intel GM965 SVGA controller on vgapci0 agp0: aperture size is 256M, detected 7676k stolen memory vgapci1: VGA-compatible display mem 0xfa10-0xfa1f at device 2.1 on pci0 pci0: simple comms at device 3.0 (no driver attached) atapci0: Intel ATA controller port 0x1828-0x182f,0x180c-0x180f,0x1820-0x1827,0x1808-0x180b,0x1810-0x181f irq 18 at device 3.2 on pci0 ata2: ATA channel 0 on atapci0 ata3: ATA channel 1 on atapci0 pci0: simple comms, UART at device 3.3 (no driver attached) em0: Intel(R) PRO/1000 Network Connection 7.2.3 port 0x1840-0x185f mem 0xfa20-0xfa21,0xfa225000-0xfa225fff irq 20 at device 25.0 o n pci0 em0: Using an MSI interrupt acquiring duplicate lock of same type: network driver 1st dev_spec-swflag_mutex @ dev/e1000/e1000_ich8lan.c:785 2nd dev_spec-nvm_mutex @ dev/e1000/e1000_ich8lan.c:751 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a kdb_backtrace() at kdb_backtrace+0x37 _witness_debugger() at _witness_debugger+0x2e witness_checkorder() at witness_checkorder+0x8de _mtx_lock_flags() at _mtx_lock_flags+0x79 e1000_acquire_nvm_ich8lan() at e1000_acquire_nvm_ich8lan+0x1e e1000_read_nvm_ich8lan() at e1000_read_nvm_ich8lan+0x76 e1000_post_phy_reset_ich8lan() at e1000_post_phy_reset_ich8lan+0x1b1 e1000_reset_hw_ich8lan() at e1000_reset_hw_ich8lan+0x4c1 em_attach() at em_attach+0x11bd device_attach() at device_attach+0x69 bus_generic_attach() at bus_generic_attach+0x1a acpi_pci_attach() at acpi_pci_attach+0x14f
Re: FreeBSD 9-Beta3 on X300 problems.
2. Kadu/Gnu Gadu. I dont know why, but when i run kadu / gnu gadu and try to connect to Gadu-Gadu network software segments ;/ Kadu with signal 6, GnuGadu with signal 11. I try to use old gadulib, or recompie it. But this doesn't help ;/ I run portmaster -y --no-confirm --packages-if-newer -m 'BATCH=yes' -d -a And... its works;) [cr4sh@x300 ~]$ uname -a FreeBSD x300 9.0-BETA3 FreeBSD 9.0-BETA3 #2: Mon Sep 26 00:25:30 CEST 2011 cr4sh@x300:/sys/amd64/compile/GENERIC amd64 Regards. ___ 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 9-Beta3 on X300 2 problems
Hi, Please try to do this without wlan loaded at all (not just down, but build your wifi support as a module.) Then try without X, see whether it's related to that or not. (And you haven't told us what your hardware is.) Adrian ___ 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 9-Beta3 on X300 problems.
On 09/26/2011 16:02, crsnet.pl wrote: 2. Kadu/Gnu Gadu. I dont know why, but when i run kadu / gnu gadu and try to connect to Gadu-Gadu network software segments ;/ Kadu with signal 6, GnuGadu with signal 11. I try to use old gadulib, or recompie it. But this doesn't help ;/ I run portmaster -y --no-confirm --packages-if-newer -m 'BATCH=yes' -d -a The -y option is meaningless in that context, FYI. And... its works;) I'm glad to hear that at least. :) -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ 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 9/ZFS: Striped Pool (2 disks) migrating to mirror (onto additional disk)
On Wed, Jan 26, 2011 at 9:42 AM, O. Hartmann ohart...@mail.zedat.fu-berlin.de wrote: My question is: is it possible to migrate the two-disk pool without data loss into a mirrored pool by adding the one 2TB-disk? No, you cant create a two-way mirror of three disks with ZFS. The only way of doing what you want by creating a gmirror (or by hardware raid) of the two 1TB disks. -- chs, ___ 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 9/ZFS: Striped Pool (2 disks) migrating to mirror (onto additional disk)
On 26 January 2011 09:21, Christer Solskogen christer.solsko...@gmail.com wrote: On Wed, Jan 26, 2011 at 9:42 AM, O. Hartmann ohart...@mail.zedat.fu-berlin.de wrote: My question is: is it possible to migrate the two-disk pool without data loss into a mirrored pool by adding the one 2TB-disk? No, you cant create a two-way mirror of three disks with ZFS. The only way of doing what you want by creating a gmirror (or by hardware raid) of the two 1TB disks. -- chs, ___ 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 ive not tried it but wouldn't you want to gstripe the two disks together and then add the geom device to the pool? It sounds a bit horrible to me and with the price of 2TB disks being ~ £65-70 here in the uk I wouldn't bother. Remember you will get a speed boost for reads on a mirror. WIth regards to the backup, the most efficient way would probably to use zfs send and receive between the pools ___ 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 9/ZFS: Striped Pool (2 disks) migrating to mirror (onto additional disk)
In the last episode (Jan 26), Christer Solskogen said: On Wed, Jan 26, 2011 at 9:42 AM, O. Hartmann wrote: My question is: is it possible to migrate the two-disk pool without data loss into a mirrored pool by adding the one 2TB-disk? No, you cant create a two-way mirror of three disks with ZFS. The only way of doing what you want by creating a gmirror (or by hardware raid) of the two 1TB disks. You can, if you partition the 2tb disk into two smaller volumes, each the same size as one of the 1tb disks, then add one of those as a mirror of each original disk. You'll end up with two mirrored vdevs in the pool. Performance probably won't be as good as a real mirror, though, since zfs doesn't know that two of its physical disks share a spindle. Original: pool1 da0 da1 New: pool1 mirror da0 da2p1 mirror da1 da2p2 -- Dan Nelson dnel...@allantgroup.com ___ 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 9/ZFS: Striped Pool (2 disks) migrating to mirror (onto additional disk)
On Wed, Jan 26, 2011 at 8:58 PM, Dan Nelson dnel...@allantgroup.com wrote: In the last episode (Jan 26), Christer Solskogen said: On Wed, Jan 26, 2011 at 9:42 AM, O. Hartmann wrote: My question is: is it possible to migrate the two-disk pool without data loss into a mirrored pool by adding the one 2TB-disk? No, you cant create a two-way mirror of three disks with ZFS. The only way of doing what you want by creating a gmirror (or by hardware raid) of the two 1TB disks. You can, if you partition the 2tb disk into two smaller volumes, each the same size as one of the 1tb disks, then add one of those as a mirror of each original disk. You'll end up with two mirrored vdevs in the pool. Performance probably won't be as good as a real mirror, though, since zfs doesn't know that two of its physical disks share a spindle. Rememer that he also asked to do this without data loss. As far as I know you cant remove devices from a vdev. If he is willing to accept data loss there are a lots of ways of doing it. -- chs, ___ 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 9/ZFS: Striped Pool (2 disks) migrating to mirror (onto additional disk)
In the last episode (Jan 26), Christer Solskogen said: On Wed, Jan 26, 2011 at 8:58 PM, Dan Nelson dnel...@allantgroup.com wrote: In the last episode (Jan 26), Christer Solskogen said: On Wed, Jan 26, 2011 at 9:42 AM, O. Hartmann wrote: My question is: is it possible to migrate the two-disk pool without data loss into a mirrored pool by adding the one 2TB-disk? No, you cant create a two-way mirror of three disks with ZFS. The only way of doing what you want by creating a gmirror (or by hardware raid) of the two 1TB disks. You can, if you partition the 2tb disk into two smaller volumes, each the same size as one of the 1tb disks, then add one of those as a mirror of each original disk. You'll end up with two mirrored vdevs in the pool. Performance probably won't be as good as a real mirror, though, since zfs doesn't know that two of its physical disks share a spindle. Rememer that he also asked to do this without data loss. As far as I know you cant remove devices from a vdev. If he is willing to accept data loss there are a lots of ways of doing it. ZFS lets you add and detach mirrors on the fly, since you're not changing the capacity of the pool itself. Sure, you're going to lose the contents of the large 2TB drive, but that's sort of assumed. You can't convert 4TB of non-mirrored disks into 2TB of mirrored disks without losing 2TB of space. Just make sure you have less than 2TB total used data on all volumes, and copy the data off the 2TB filessytem onto the striped 1+1TB one before repartitioning and adding the mirrors. zpool attach [-f] pool device new_device Attaches new_device to an existing zpool device. The existing device cannot be part of a raidz configuration. If _device_ is not currently part of a mirrored configuration, _device_ automatically transforms into a two-way mirror of _device_ and _new_device_. If _device_ is part of a two-way mirror, attaching _new_device_ creates a three-way mirror, and so on. In either case, _new_device_ begins to resilver immediately. (Do not confuse with zpool add, which adds a whole new vdev to the pool. vdevs cannot be removed once added) -- Dan Nelson dnel...@allantgroup.com ___ 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 9/ZFS: Striped Pool (2 disks) migrating to mirror (onto additional disk)
On Wed, Jan 26, 2011 at 9:42 PM, Dan Nelson dnel...@allantgroup.com wrote: ZFS lets you add and detach mirrors on the fly, since you're not changing the capacity of the pool itself. Sure, you're going to lose the contents of the large 2TB drive, but that's sort of assumed. You can't convert 4TB of non-mirrored disks into 2TB of mirrored disks without losing 2TB of space. Just make sure you have less than 2TB total used data on all volumes, and copy the data off the 2TB filessytem onto the striped 1+1TB one before repartitioning and adding the mirrors. zpool attach [-f] pool device new_device The problem is that you cant attach a drive to a vdev that consists of two striped disks. -- chs, ___ 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
