Ready for use as a router?
Do you guys think kfreebsd is ready to be used in production as an internet access router running pf and carp? -Brian -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikosto-dkkwro+ghje7ys1lfmmruphfya=tf...@mail.gmail.com
Re: Testing with VMWare Fusion... No virtual SCSI devices
On Sun, Sep 19, 2010 at 3:50 PM, Aurelien Jarno aurel...@aurel32.netwrote: On Sun, Sep 12, 2010 at 12:13:09AM -0400, Brian Gupta wrote: On Thu, Aug 5, 2010 at 11:16 PM, Aurelien Jarno aurel...@aurel32.net wrote: On Thu, Aug 05, 2010 at 11:13:35PM -0400, Brian Gupta wrote: On Thu, Aug 5, 2010 at 8:29 PM, Aurelien Jarno aurel...@aurel32.net wrote: On Wed, Aug 04, 2010 at 11:37:53PM -0400, Brian Gupta wrote: Seems that none of the SCSI options work with the AMD64 mini.iso.. I believe the device emulated is an LSI Logic SCSI adapter. (But am not 100% certain since VMWare Fusion settings are a bit more Opaque than other VMWare releases). I am using the predefined FreeBSD64 settings profile in VMWare Fusion. I did manage to get it working with a virtual ATA controller though, but got warning messages saying Warning: Could not flush cache of device /dev/ad0 - No such device. Interestingly even though the installer didn't see the SCSI devices, once I was booted off an install I did on a virtual ATA device, I did see this in dmesg.: Waiting 2 seconds for SCSI devices to settle da0 at mpt0 bus 0 target 0 lun 0 da0: VMware, VMware Virtual S 1.0 Fixed Direct Access SCSI-2 device da0: 320.000MB/s transfers (160.000MHz DT, offset 127, 16bit) da0: Command Queueing Enabled da0: 8192MB (16777216 512 byte sectors: 255H 63S/T 1044C) and /dev/da0 exists (but all the other da* devices don't), and running parted doesn't seem to see da0. On the flip side networking works.. so there is a mostly working headless config for VMWare Fusion, and most likely VMWare Workstation. One reason to get SCSI working is that VMWare ESXi does not seem to have a virtual ATA controller available and only let's virtual SCSI drives get added. (Pretty much all VMWare products provide an option to run a virtual LSI Logic SCSI controller.) I am wondering if the LSI Logic drivers that come with FreeBSD are proprietary blogs that got stripped out of kfreebsd? Please let me know if there is any more output I can provide, or if someone wants to directly interact with the VM at DC10. (I will be at DebConf for most of Thursday and alternatively can plan to meet up any evening this week.) Please note that I am currently working on getting debian-installer using the 8.1 kernel instead of the 7.3. This should probably be retested after that, as a lot of drivers are going to change. That sounds promising. Do you have an idea when it will be ready for testing? I hope next week, it will also depends on how long the ftpmasters will accept the packages. My apologies. I got busy. Did the 8.1 kernel ISO ever get cut? Since end of August, daily images are using a 8.1 kernel. You can fetch them from: http://d-i.debian.org/daily-images/ I finally got around to testing with the 8.1-1-amd64 kernel, and it works well enough. Basically I can install the base OS, boot it, and installing a few additional packages worked. Setup VMWare Fusion 3.1.1 VM OS preset: Other - FreeBSD 64-bit Other settings: SCSI disk (vs. IDE) Install method: Expert This leaves me pretty hopeful that this should work for VMWare Workstation, and ESXi which means our testing userbase is potentially pretty large. Is there anything folks would like me to test? Cheers, Brian -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net
Re: Testing with VMWare Fusion... No virtual SCSI devices
On Thu, Aug 5, 2010 at 11:16 PM, Aurelien Jarno aurel...@aurel32.netwrote: On Thu, Aug 05, 2010 at 11:13:35PM -0400, Brian Gupta wrote: On Thu, Aug 5, 2010 at 8:29 PM, Aurelien Jarno aurel...@aurel32.net wrote: On Wed, Aug 04, 2010 at 11:37:53PM -0400, Brian Gupta wrote: Seems that none of the SCSI options work with the AMD64 mini.iso.. I believe the device emulated is an LSI Logic SCSI adapter. (But am not 100% certain since VMWare Fusion settings are a bit more Opaque than other VMWare releases). I am using the predefined FreeBSD64 settings profile in VMWare Fusion. I did manage to get it working with a virtual ATA controller though, but got warning messages saying Warning: Could not flush cache of device /dev/ad0 - No such device. Interestingly even though the installer didn't see the SCSI devices, once I was booted off an install I did on a virtual ATA device, I did see this in dmesg.: Waiting 2 seconds for SCSI devices to settle da0 at mpt0 bus 0 target 0 lun 0 da0: VMware, VMware Virtual S 1.0 Fixed Direct Access SCSI-2 device da0: 320.000MB/s transfers (160.000MHz DT, offset 127, 16bit) da0: Command Queueing Enabled da0: 8192MB (16777216 512 byte sectors: 255H 63S/T 1044C) and /dev/da0 exists (but all the other da* devices don't), and running parted doesn't seem to see da0. On the flip side networking works.. so there is a mostly working headless config for VMWare Fusion, and most likely VMWare Workstation. One reason to get SCSI working is that VMWare ESXi does not seem to have a virtual ATA controller available and only let's virtual SCSI drives get added. (Pretty much all VMWare products provide an option to run a virtual LSI Logic SCSI controller.) I am wondering if the LSI Logic drivers that come with FreeBSD are proprietary blogs that got stripped out of kfreebsd? Please let me know if there is any more output I can provide, or if someone wants to directly interact with the VM at DC10. (I will be at DebConf for most of Thursday and alternatively can plan to meet up any evening this week.) Please note that I am currently working on getting debian-installer using the 8.1 kernel instead of the 7.3. This should probably be retested after that, as a lot of drivers are going to change. That sounds promising. Do you have an idea when it will be ready for testing? I hope next week, it will also depends on how long the ftpmasters will accept the packages. My apologies. I got busy. Did the 8.1 kernel ISO ever get cut? Thanks, Brian -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100806031615.gh4...@hall.aurel32.net --
Re: Testing with VMWare Fusion... No virtual SCSI devices
On Thu, Aug 5, 2010 at 8:29 PM, Aurelien Jarno aurel...@aurel32.net wrote: On Wed, Aug 04, 2010 at 11:37:53PM -0400, Brian Gupta wrote: Seems that none of the SCSI options work with the AMD64 mini.iso.. I believe the device emulated is an LSI Logic SCSI adapter. (But am not 100% certain since VMWare Fusion settings are a bit more Opaque than other VMWare releases). I am using the predefined FreeBSD64 settings profile in VMWare Fusion. I did manage to get it working with a virtual ATA controller though, but got warning messages saying Warning: Could not flush cache of device /dev/ad0 - No such device. Interestingly even though the installer didn't see the SCSI devices, once I was booted off an install I did on a virtual ATA device, I did see this in dmesg.: Waiting 2 seconds for SCSI devices to settle da0 at mpt0 bus 0 target 0 lun 0 da0: VMware, VMware Virtual S 1.0 Fixed Direct Access SCSI-2 device da0: 320.000MB/s transfers (160.000MHz DT, offset 127, 16bit) da0: Command Queueing Enabled da0: 8192MB (16777216 512 byte sectors: 255H 63S/T 1044C) and /dev/da0 exists (but all the other da* devices don't), and running parted doesn't seem to see da0. On the flip side networking works.. so there is a mostly working headless config for VMWare Fusion, and most likely VMWare Workstation. One reason to get SCSI working is that VMWare ESXi does not seem to have a virtual ATA controller available and only let's virtual SCSI drives get added. (Pretty much all VMWare products provide an option to run a virtual LSI Logic SCSI controller.) I am wondering if the LSI Logic drivers that come with FreeBSD are proprietary blogs that got stripped out of kfreebsd? Please let me know if there is any more output I can provide, or if someone wants to directly interact with the VM at DC10. (I will be at DebConf for most of Thursday and alternatively can plan to meet up any evening this week.) Please note that I am currently working on getting debian-installer using the 8.1 kernel instead of the 7.3. This should probably be retested after that, as a lot of drivers are going to change. That sounds promising. Do you have an idea when it will be ready for testing? -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktimwb42rarmno4-sbaprmixw+o-dbpyowmjcx...@mail.gmail.com
Re: Releasability of the kFreeBSD ports
Ok my suggestions below may be stating the obvious, if so my apologies. I would suggest, making a list of criteria, that we believe would constitute a stable release. (I personally don't know enough to say what that criteria is, and this email thread may be the first step in creating that list). Then, at the after the stable change-freeze, I would look and see where we are. I think the options, in my preferred order of preference, would be: 1) Fix all the release critical bugs and release as planned. (If this slightly delays things, and the overall Debian release team is ok with the delay, I'd say this should be a preference). 2) Go stable, with a caveat that stable for this port differs from standard debian stable, which has assumptions based on the development of an OS built on a Linux kernel. Much of what you are doing is unprecedented, so that some degree of flexibility on creating new policy as you go should be awarded. e.g. - changing the FreeBSD kernel during the life of a stable release *MAY* be desirable. Another caveat to announce would be that this is first stable and that as such this is the first time the port will be introduced to a widespread audience so there *MAY* be more issues than other stable ports. 3) See if we can remain in some sort of stable-candidate state after the overall squeeze goes stable, and declare it stable when we are ready. (I don't know if this is possible under current Debian policy, but again I would argue that unprecedented efforts, deserve the opportunity to create new policy). I suspect that if we can assure that we are either only touching kfreebsd packages, and/or the files that affect kfreebsd we could find support for this option. 4) Do as you have done in the past effectively skipping squeeze. I don't think this is a good idea. (If you need me to expound, I can, but I suspect my opinion here matches the majority). Cheers, Brian On Wed, Aug 4, 2010 at 11:33 AM, Julien BLACHE jbla...@debian.org wrote: Petr Salinger petr.salin...@seznam.cz wrote: Hi, * openjdk on both kfreebsd-i386/kfreebsd-amd64 man-power is missing, we use gcj similarly as hppa gcj 4.4 is currently broken on kfreebsd-amd64 per #576335. JB. -- Julien BLACHE - Debian GNU/Linux Developer - jbla...@debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/871vae75q0@sonic.technologeek.org -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktiøk49wyuayxlnfzfyj39hganefsp_e31y2...@mail.gmail.com
Testing with VMWare Fusion... No virtual SCSI devices
Seems that none of the SCSI options work with the AMD64 mini.iso.. I believe the device emulated is an LSI Logic SCSI adapter. (But am not 100% certain since VMWare Fusion settings are a bit more Opaque than other VMWare releases). I am using the predefined FreeBSD64 settings profile in VMWare Fusion. I did manage to get it working with a virtual ATA controller though, but got warning messages saying Warning: Could not flush cache of device /dev/ad0 - No such device. Interestingly even though the installer didn't see the SCSI devices, once I was booted off an install I did on a virtual ATA device, I did see this in dmesg.: Waiting 2 seconds for SCSI devices to settle da0 at mpt0 bus 0 target 0 lun 0 da0: VMware, VMware Virtual S 1.0 Fixed Direct Access SCSI-2 device da0: 320.000MB/s transfers (160.000MHz DT, offset 127, 16bit) da0: Command Queueing Enabled da0: 8192MB (16777216 512 byte sectors: 255H 63S/T 1044C) and /dev/da0 exists (but all the other da* devices don't), and running parted doesn't seem to see da0. On the flip side networking works.. so there is a mostly working headless config for VMWare Fusion, and most likely VMWare Workstation. One reason to get SCSI working is that VMWare ESXi does not seem to have a virtual ATA controller available and only let's virtual SCSI drives get added. (Pretty much all VMWare products provide an option to run a virtual LSI Logic SCSI controller.) I am wondering if the LSI Logic drivers that come with FreeBSD are proprietary blogs that got stripped out of kfreebsd? Please let me know if there is any more output I can provide, or if someone wants to directly interact with the VM at DC10. (I will be at DebConf for most of Thursday and alternatively can plan to meet up any evening this week.) Thanks, -Brian -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlkti=+yxn=gtjhupdyfmecxylhqbm+mmstpm9cz...@mail.gmail.com
Purpose driving kfreebsd?
Hey guys, I think it's awesome that you have done this, and that Debian is supporting it as official port. I was looking for FAQs and such, do you have any? Basically I want to learn about why as much as the technical what driving this port. I'd also love to see if anyone is interested in giving a techncial presentation in New York City on kfreebsd at a user group meeting in Q1 2010. If someone is available that would be great, otherwise, I plan to learn about kfreebsd and potentially give the preso myself. The target of the preso would be both Linux and BSD users. (And all interested parties). Basically I get the sense that most folks are like me, in that they know it exists, they just don't really know anyone who uses it, nor do they understand why someone would use it. (Over plain Debian or FreeBSD). Cheers, Brian -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
