Re: MFC of r180753: ABI problems?
In message: [EMAIL PROTECTED] Max Laier [EMAIL PROTECTED] writes: : Hi, : : I'm wondering how to merge r180753 to stable/7 as luoqi@ has indicated that he : doesn't have time to take care of it right now. : : It seems that changing the size of pcicfgregs (aka struct pcicfg) which is : part of struct pci_devinfo is out of the question, right? Ideas where to : store the HT related state or how to avoid storing the state are welcome. : : The merge result is attached for reference. This fix is essential for many : nforce based boards from ASUS which are rather common, I'm afraid. So it : would be good to have this in 7.1/6.4, I think. I think this is OK. pcicfgregs is an internal to pci implementation detail. You've added it at the end, so any leakage of the offsets won't matter. All subclasses of pci would be affected. Internal to the kernel isn't all that interesting, since they are all compiled at the same time. This would only matter for modules. Cardbus and acpi would be the only modules affected. That would mean you couldn't boot a 7.0 kernel with a 7.1 set of modules or vice versa. I'm not sure that is actually going to work anyway... Warner ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Driver accessing other drivers/devices ?
In message: [EMAIL PROTECTED] Alex Hornung [EMAIL PROTECTED] writes: : Hello, : : I need to access the hard disk from within a driver that is not a FS. : I would also need to get a list of PCI devices connected. Is there a : way I can access these devices directly, at least in the first case, : issuing directly ATA/IDE commands to the hard disk? There's always ata_if.m... : In the case of PCI it would be even nicer to be able to communicate : with the pci driver... but if that's not possible, it's also ok if I : can access the PCI bus controller directly. The driver I'm writing is : not a PCI or PCI device driver either. : : Hope someone can help me out on this one, it's important that there's : no user-space code... Generally, you don't want to scan the PCI bus to look for drivers to talk to. That's bad kharma and likely begging to be abused. Having said that, I've had cooperative drivers in the kernel before. They usually look for each other and send messages to each other with kobj. It is better to look for friend0 that you know can receive messages. kobj adds a layer of protection since it will gracefully give an error when you can't do it. Hey, wait, ata_if is kobj... You could likely expand it to allow queueing of commands and such. Warner ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sun4v arch
In message: [EMAIL PROTECTED] Pietro Cerutti [EMAIL PROTECTED] writes: : -BEGIN PGP SIGNED MESSAGE- : Hash: SHA512 : : Kris Kennaway wrote: : | Just so everyone is on the same page, what is needed to keep sun4v : | viable are people with experience with (or intention to learn about) low : | level architectural and implementation details of the FreeBSD kernel and : | the sun4v hardware platform, who know their way around things like : | pmap.c and other MD places where the kernel interfaces with the bare : | metal, and who are willing to make a long term (multi-year) commitment : | to supporting the platform. : : If we had docs... There's a bunch of sun4v docs available. See http://www.sun.com/processors/documentation.html for example. Warner ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
What is difference between /etc/rc called programs and ones called after login prompt shows up
What is difference between /etc/rc.d called programs and ones called after login prompt shows up? The reason for asking is sysutils/fusefs-kmod gives an error if any mounts are attempted in /etc/rc but if the exactly the same command is issued by a user's .login/.xsession/etc. it works without problem (assuming proper permissions of course). a) Can anyone think of a reason why this would happen (the maintainer is non-responive) b) Is it possible to force something to run after /etc/rc exits but before init calls getty? ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What is difference between /etc/rc called programs and ones called after login prompt shows up
On Sat, 23 Aug 2008 06:34:23 -0400 Aryeh Friedman [EMAIL PROTECTED] wrote: What is difference between /etc/rc.d called programs and ones called after login prompt shows up? The reason for asking is sysutils/fusefs-kmod gives an error if any mounts are attempted in /etc/rc but if the exactly the same command is issued by a user's .login/.xsession/etc. it works without problem (assuming proper permissions of course). a) Can anyone think of a reason why this would happen (the maintainer is non-responive) I suspect that fuse.ko is loaded by one of the scripts under /etc/rc.d since it seems to be installed under $PREFIX/modules where PREFIX is normally /usr/local. Until that happens you can't use mount_fusefs. b) Is it possible to force something to run after /etc/rc exits but before init calls getty? Well, there are ways to force dependencies in the rc.d scripts, but I don't know the setup well enough to be helpful. I have no idea which script handles modules installed by ports and when it is invoked. You could try moving fuse.ko to /boot/modules and modify loader.conf to load fuse.ko at boot time. --- Gary Jennejohn ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What is difference between /etc/rc called programs and ones called after login prompt shows up
On Sat, 23 Aug 2008 15:33:54 +0200 Gary Jennejohn [EMAIL PROTECTED] wrote: On Sat, 23 Aug 2008 06:34:23 -0400 Aryeh Friedman [EMAIL PROTECTED] wrote: What is difference between /etc/rc.d called programs and ones called after login prompt shows up? The reason for asking is sysutils/fusefs-kmod gives an error if any mounts are attempted in /etc/rc but if the exactly the same command is issued by a user's .login/.xsession/etc. it works without problem (assuming proper permissions of course). a) Can anyone think of a reason why this would happen (the maintainer is non-responive) Well, there are ways to force dependencies in the rc.d scripts, but I don't know the setup well enough to be helpful. I have no idea which script handles modules installed by ports and when it is invoked. You could try moving fuse.ko to /boot/modules and modify loader.conf to load fuse.ko at boot time. There's no need for that, it's already handled by the rc.d scripts. Fuse-based filesystems should be mounted with the late option, so they get mounted after the kernel module is loaded. You might also need a patch so the mount can find the correct mount_* executable.I think it's needed in 7.0, I'm not sure about 7-stable and current. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: MFC of r180753: ABI problems?
On Saturday 23 August 2008 02:42:09 am M. Warner Losh wrote: In message: [EMAIL PROTECTED] Max Laier [EMAIL PROTECTED] writes: : Hi, : : I'm wondering how to merge r180753 to stable/7 as luoqi@ has indicated : that he doesn't have time to take care of it right now. : : It seems that changing the size of pcicfgregs (aka struct pcicfg) which : is part of struct pci_devinfo is out of the question, right? Ideas where : to store the HT related state or how to avoid storing the state are : welcome. : : The merge result is attached for reference. This fix is essential for : many nforce based boards from ASUS which are rather common, I'm afraid. : So it would be good to have this in 7.1/6.4, I think. I think this is OK. pcicfgregs is an internal to pci implementation detail. You've added it at the end, so any leakage of the offsets won't matter. All subclasses of pci would be affected. Internal to the kernel isn't all that interesting, since they are all compiled at the same time. This would only matter for modules. Cardbus and acpi would be the only modules affected. That would mean you couldn't boot a 7.0 kernel with a 7.1 set of modules or vice versa. I'm not sure that is actually going to work anyway... ACPI (and OFW's) PCI bus code isn't going to care, and I doubt cardbus is either. Hmm, actually, cardbus doesn't, but ACPI actually does (acpi_pci uses its own extended ivars for PCI devices to cache ACPI handles). That said, this particular ABI was actually broken earlier by MSI (though I didn't realize it at the time. :( ). -- John Baldwin ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What is difference between /etc/rc called programs and ones called after login prompt shows up
On Sat, Aug 23, 2008 at 8:27 AM, Garrett Cooper [EMAIL PROTECTED] wrote: On Sat, Aug 23, 2008 at 3:34 AM, Aryeh Friedman [EMAIL PROTECTED] wrote: What is difference between /etc/rc.d called programs and ones called after login prompt shows up? The reason for asking is sysutils/fusefs-kmod gives an error if any mounts are attempted in /etc/rc but if the exactly the same command is issued by a user's .login/.xsession/etc. it works without problem (assuming proper permissions of course). a) Can anyone think of a reason why this would happen (the maintainer is non-responive) b) Is it possible to force something to run after /etc/rc exits but before init calls getty? a) Bad credentials? Dependencies not started (yet)? b) You can enforce ordering, if that's what you want. See: http://www.freebsd.org/doc/en/articles/rc-scripting/ a) I use a custom /etc/rc thus I can place the mount command anywhere I want. No matter where I place I get the same error it is *ONLY* after /etc/rc terminates I am b) I load fuse.ko in /boot/loader.con (copied it from /usr/local/modules to /boot/modules) here is dmesg proof it is loaded: dmesg|grep fuse fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8 fuse4bsd: compiled against kernel config /usr/obj/usr/src/sys/MONSTER c) See a additionally to prove all the above here is my /etc/rc (the last 2 lines where added just to prove the point): #!/bin/sh PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin swapon -a fsck -p mount -rw / mount -a hostname flosoft.no-ip.biz ifconfig re0 192.168.2.2 ifconfig lo0 127.0.0.1 route add default 192.168.2.1 named cupsd noip2 ntpdate pool.ntp.org sendmail -bd -q1m apachectl start moused -t auto -p /dev/ums0 vidcontrol -m on mount /mnt/win_c mount /mnt/win_d Here is /etc/fstab (set up as recommended in the docs for sysutils/fusefs-ntfs [which I am the co-maintainer of]): # DeviceMountpoint FStype Options DumpPass# /dev/ad8s2b noneswapsw 0 0 /dev/ad8s2a / ufs rw 1 1 /dev/ad8s2e /tmpufs rw 2 2 /dev/ad8s2f /usrufs rw 2 2 /dev/ad8s2d /varufs rw 2 2 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 proc/proc procfs rw 0 0 linproc /compat/linux/proc linprocfs rw 0 0 /dev/ad8s1 /mnt/win_cntfs-3g rw,late 0 0 /dev/da0s1 /mnt/win_dntfs-3g rw,late 0 0 The patch to mount recommended in the fusefs-ntfs docs has been applied. In order to show that the mount commands work post call to getty but not before: When the above /etc/rc is run: swapon: adding /dev/ad8s2b as swap device /dev/ad8s2a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad8s2a: clean, 164555 free (3603 frags, 20119 blocks, 1.4% fragmentation) /dev/ad8s2e: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad8s2e: clean, 253254 free (54 frags, 31650 blocks, 0.0% fragmentation) /dev/ad8s2f: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad8s2f: clean, 210848941 free (53253 frags, 26349461 blocks, 0.0% fragmenta tion) /dev/ad8s2d: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad8s2d: clean, 1970559 free (551 frags, 246251 blocks, 0.0% fragmentation) re0: link state changed to DOWN add net default: gateway 192.168.2.1 re0: link state changed to UP 23 Aug 09:02:00 ntpdate[48]: step time server 216.184.20.83 offset 0.794898 sec pid 54 (limits), uid 0: exited on signal 11 (core dumped) [Sat Aug 23 09:02:01 2008] [warn] (2)No such file or directory: Failed to enable the 'httpready' Accept Filter fuse: failed to exec mount program: No such file or directory fuse: failed to mount file system: Unknown error: 0 fuse: failed to exec mount program: No such file or directory fuse: failed to mount file system: Unknown error: 0 FreeBSD/i386 (flosoft.no-ip.biz) (ttyv0) login: Here is the .login for root and the .xsession for my main user account (I use xdm): more ~root/.login # $FreeBSD: src/etc/root/dot.login,v 1.22 2000/07/15 03:25:14 rwatson Exp $ # # .login - csh login script, read by login shell, after `.cshrc' at login. # # see also csh(1), environ(7). # # Uncomment to display a random cookie each login: # [ -x /usr/games/fortune ] /usr/games/fortune -s echo Mounting C: mount /mnt/win_c echo Mounting D: mount /mnt/win_d more ~aryeh/.xsession sudo mount /mnt/win_c sudo mount /mnt/win_d mixer 100 mixer pcm 100 xfce4-session Sudo is configured to allow 'aryeh' to no password access. And finally proof that the two methods do in fact work: df -k Filesystem 1024-blocks Used Avail Capacity Mounted on /dev/ad8s2a 507630 17852028850038%/ devfs 11 0 100%/dev /dev/ad8s2e 507630 1124465896 0%/tmp /dev/ad8s2f
Re: MFC of r180753: ABI problems?
In message: [EMAIL PROTECTED] John Baldwin [EMAIL PROTECTED] writes: : On Saturday 23 August 2008 02:42:09 am M. Warner Losh wrote: : In message: [EMAIL PROTECTED] : : Max Laier [EMAIL PROTECTED] writes: : : Hi, : : : : I'm wondering how to merge r180753 to stable/7 as luoqi@ has indicated : : that he doesn't have time to take care of it right now. : : : : It seems that changing the size of pcicfgregs (aka struct pcicfg) which : : is part of struct pci_devinfo is out of the question, right? Ideas where : : to store the HT related state or how to avoid storing the state are : : welcome. : : : : The merge result is attached for reference. This fix is essential for : : many nforce based boards from ASUS which are rather common, I'm afraid. : : So it would be good to have this in 7.1/6.4, I think. : : I think this is OK. : : pcicfgregs is an internal to pci implementation detail. You've added : it at the end, so any leakage of the offsets won't matter. All : subclasses of pci would be affected. Internal to the kernel isn't all : that interesting, since they are all compiled at the same time. This : would only matter for modules. Cardbus and acpi would be the only : modules affected. That would mean you couldn't boot a 7.0 kernel with : a 7.1 set of modules or vice versa. I'm not sure that is actually : going to work anyway... : : ACPI (and OFW's) PCI bus code isn't going to care, and I doubt cardbus is : either. Hmm, actually, cardbus doesn't, but ACPI actually does (acpi_pci CardBus' does because it creates a slightly larger pcicfgreg per device... : uses its own extended ivars for PCI devices to cache ACPI handles). That : said, this particular ABI was actually broken earlier by MSI (though I didn't : realize it at the time. :( ). Warner ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What is difference between /etc/rc called programs and ones called after login prompt shows up
On Sat, 23 Aug 2008 16:38:13 -0400 Aryeh Friedman [EMAIL PROTECTED] wrote: c) See a additionally to prove all the above here is my /etc/rc (the last 2 lines where added just to prove the point): #!/bin/sh PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin swapon -a fsck -p ... fuse: failed to exec mount program: No such file or directory Thus it is clear that the *ONLY* difference between the /etc/rc calls and the post getty calls is when they are made. There's another difference: your /etc/rc script doesn't export PATH. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What is difference between /etc/rc called programs and ones called after login prompt shows up
On Sat, 23 Aug 2008 23:13:49 +0100 RW [EMAIL PROTECTED] wrote: On Sat, 23 Aug 2008 16:38:13 -0400 Aryeh Friedman [EMAIL PROTECTED] wrote: c) See a additionally to prove all the above here is my /etc/rc (the last 2 lines where added just to prove the point): #!/bin/sh PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin swapon -a fsck -p ... fuse: failed to exec mount program: No such file or directory Thus it is clear that the *ONLY* difference between the /etc/rc calls and the post getty calls is when they are made. There's another difference: your /etc/rc script doesn't export PATH. That does seem to be the answer. I was curious as to why it only fails on ntfs, so I had a look at the source. It seems that mount and fsck find mount_* and fsck_* through a hard-coded path of /rescue:/sbin:/usr/sbin, but mount_ntfs-3g then additionally has to find mount_fusefs through the environment path. Perhaps sysutils/fusefs-libs should be patched to make the whole thing more self-consistent. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What is difference between /etc/rc called programs and ones called after login prompt shows up
RW wrote: There's another difference: your /etc/rc script doesn't export PATH. And TERM. signature.asc Description: OpenPGP digital signature
Re: What is difference between /etc/rc called programs and ones called after login prompt shows up
On Sat, Aug 23, 2008 at 7:39 PM, RW [EMAIL PROTECTED] wrote: On Sat, 23 Aug 2008 23:13:49 +0100 RW [EMAIL PROTECTED] wrote: On Sat, 23 Aug 2008 16:38:13 -0400 Aryeh Friedman [EMAIL PROTECTED] wrote: c) See a additionally to prove all the above here is my /etc/rc (the last 2 lines where added just to prove the point): #!/bin/sh PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin swapon -a fsck -p ... fuse: failed to exec mount program: No such file or directory Thus it is clear that the *ONLY* difference between the /etc/rc calls and the post getty calls is when they are made. There's another difference: your /etc/rc script doesn't export PATH. That does seem to be the answer. I was curious as to why it only fails on ntfs, so I had a look at the source. It seems that mount and fsck find mount_* and fsck_* through a hard-coded path of /rescue:/sbin:/usr/sbin, but mount_ntfs-3g then additionally has to find mount_fusefs through the environment path. Perhaps sysutils/fusefs-libs should be patched to make the whole thing more self-consistent. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] Thanks that did it... but you're incorrect in saying it is only ntfs it is all fuse based fs's I had a the same error when doing a fuse-ssh mount to my machine at work ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What is difference between /etc/rc called programs and ones called after login prompt shows up
On Sat, Aug 23, 2008 at 9:06 PM, Ivan Voras [EMAIL PROTECTED] wrote: RW wrote: There's another difference: your /etc/rc script doesn't export PATH. And TERM. Since I never set TERM why export it? ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sun4v arch
Peter Jeremy wrote: Is there a summary of the open issues somewhere? There are no sun4v PRs open. http://wiki.freebsd.org/FreeBSD/sun4v effectively hasn't been touched since November 2006 and suggests that the only critical issue is lack of serial port support. There is a better interpretation, which is that the only critical issue is lack of real users for this port, not lack of serial port support :). -Maxim ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What is difference between /etc/rc called programs and ones called after login prompt shows up
On Sat, Aug 23, 2008 at 7:02 PM, Aryeh Friedman [EMAIL PROTECTED] wrote: On Sat, Aug 23, 2008 at 7:39 PM, RW [EMAIL PROTECTED] wrote: On Sat, 23 Aug 2008 23:13:49 +0100 RW [EMAIL PROTECTED] wrote: On Sat, 23 Aug 2008 16:38:13 -0400 Aryeh Friedman [EMAIL PROTECTED] wrote: c) See a additionally to prove all the above here is my /etc/rc (the last 2 lines where added just to prove the point): #!/bin/sh PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin swapon -a fsck -p ... fuse: failed to exec mount program: No such file or directory Thus it is clear that the *ONLY* difference between the /etc/rc calls and the post getty calls is when they are made. There's another difference: your /etc/rc script doesn't export PATH. That does seem to be the answer. I was curious as to why it only fails on ntfs, so I had a look at the source. It seems that mount and fsck find mount_* and fsck_* through a hard-coded path of /rescue:/sbin:/usr/sbin, but mount_ntfs-3g then additionally has to find mount_fusefs through the environment path. Perhaps sysutils/fusefs-libs should be patched to make the whole thing more self-consistent. Isn't the typical use-case for fuse-based FS'es to be executed in userland though by non-root users? -Garrett ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sun4v arch
On Sat, Aug 23, 2008 at 6:52 PM, Maxim Sobolev [EMAIL PROTECTED] wrote: Peter Jeremy wrote: Is there a summary of the open issues somewhere? There are no sun4v PRs open. http://wiki.freebsd.org/FreeBSD/sun4v effectively hasn't been touched since November 2006 and suggests that the only critical issue is lack of serial port support. There is a better interpretation, which is that the only critical issue is lack of real users for this port, not lack of serial port support :). -Maxim Maybe some time should be spent looking at stuff from NetBSD to see whether or not they've solved some already critical porting pieces that FreeBSD lacks in this architecture? -Garrett ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sun4v arch
On Sat, Aug 23, 2008 at 06:52:07PM -0700, Maxim Sobolev wrote: There is a better interpretation, which is that the only critical issue is lack of real users for this port, not lack of serial port support :). My understanding is the the port is in a pre-alpha state due to unfinished work in the kernel, so expecting there to be any userbase is premature. All of our 'new' architectures which are in this state have so few non- developer users that there is hardly any reason to submit PRs. AFAICT the active developers already know what's missing :-) Our implementation of GNATS barely serves us as a problem report system; it fails almost completely as a system for listing missing features. We would need to have something like that to track the status of the non- Tier-1 ports. (I used to maintain a table of how feature-complete the various ports are, but it is now way out of date.) mcl ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sun4v arch
On 2008-Aug-23 22:40:55 -0500, Mark Linimon [EMAIL PROTECTED] wrote: My understanding is the the port is in a pre-alpha state due to unfinished work in the kernel, so expecting there to be any userbase is premature. Except that the wiki gives a far more optimistic picture. All of our 'new' architectures which are in this state have so few non- developer users that there is hardly any reason to submit PRs. AFAICT the active developers already know what's missing :-) That makes it very difficult for someone outside that group to come up to speed. I can't find anything in the freebsd-sun4v archvies. I was hoping that there would be a list somewhere of what state various subsystems were in and what remained to be done. wiki.freebsd.org sounds like the ideal place for this. On 2008-Aug-23 20:39:29 -0700, Garrett Cooper [EMAIL PROTECTED] wrote: Maybe some time should be spent looking at stuff from NetBSD to see whether or not they've solved some already critical porting pieces that FreeBSD lacks in this architecture? I can't find anything that suggests NetBSD runs on sun4v. Their sparc64 port only covers the US-I/II families and there's no mention of sun4v. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. pgp5YmG2dn3qK.pgp Description: PGP signature
Re: sun4v arch
Hi Peter, There really isn't any magic to bringing up a port. You compile it, install it, and then run it until it breaks. Once it breaks you spend a lot of time instrumenting the code to track down what went wrong. Then, depending on the amount of technical insight you have in to the issue, you go through a number of iterations until it is fixed. Fixing the pmap issue is just (notice the quotes) a matter of tracking down the missing TLB shootdowns. For anyone who chooses pick this up it will be very educational. It will also be very time consuming. -Kip On Sat, Aug 23, 2008 at 9:23 PM, Peter Jeremy [EMAIL PROTECTED] wrote: On 2008-Aug-23 22:40:55 -0500, Mark Linimon [EMAIL PROTECTED] wrote: My understanding is the the port is in a pre-alpha state due to unfinished work in the kernel, so expecting there to be any userbase is premature. Except that the wiki gives a far more optimistic picture. All of our 'new' architectures which are in this state have so few non- developer users that there is hardly any reason to submit PRs. AFAICT the active developers already know what's missing :-) That makes it very difficult for someone outside that group to come up to speed. I can't find anything in the freebsd-sun4v archvies. I was hoping that there would be a list somewhere of what state various subsystems were in and what remained to be done. wiki.freebsd.org sounds like the ideal place for this. On 2008-Aug-23 20:39:29 -0700, Garrett Cooper [EMAIL PROTECTED] wrote: Maybe some time should be spent looking at stuff from NetBSD to see whether or not they've solved some already critical porting pieces that FreeBSD lacks in this architecture? I can't find anything that suggests NetBSD runs on sun4v. Their sparc64 port only covers the US-I/II families and there's no mention of sun4v. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sun4v arch
On Sat, Aug 23, 2008 at 9:34 PM, Sevan / Venture37 [EMAIL PROTECTED] wrote: I can't find anything that suggests NetBSD runs on sun4v. Their sparc64 port only covers the US-I/II families and there's no mention of sun4v. OpenBSD/sparc64 supports the sun4v architecture has done for a while. Heh. The bugs that FreeBSD exhibits on sun4v won't be hit on UP and are much less prevalent without preemption. -Kip ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What is difference between /etc/rc called programs and ones called after login prompt shows up
On Sat, 23 Aug 2008 22:02:14 -0400 Aryeh Friedman [EMAIL PROTECTED] wrote: Thanks that did it... but you're incorrect in saying it is only ntfs it is all fuse based fs's I had a the same error when doing a fuse-ssh mount to my machine at work I meant only ntfs out of all the other entries in your fstab. If PATH isn't exported then the question became: why are any of the mounts or fscks succeeding? Presumably all the fuse filesystems are mounted in the same way mount -t foo -- mount_foo -- mount_fusefs as opposed to mount -t foo -- mount_foo for native filesystems. Since it turns out that only the mount_foo -- mount_fusefs call needs a PATH variable, all fuse filesystems will fail if PATH isn't exported, but no native filesystem will be affected. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
