Re: Bad crash with if_bge when loaded as module in loader.conf
In local.freebsd-hackers, you wrote: Even more bad is that there is no escape from serial console, I can do what I like, call boot(), panic() etc. I get a endless loop. This is 4.7 STABLE from today. It panics when I try to ifconfig the bge0 interface. Wild guess: You have miibus compiled into the kernel and it gets pulled in a second time when kldloading if_bge? -- http://www-i2.informatik.rwth-aachen.de/stolz/ *** PGP *** S/MIME rage against the finite state machine To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: anoncvs.freebsd.org reachability
# [EMAIL PROTECTED] / 2003-02-10 14:40:41 -0800: In the meantime, is there an easy way to switch over my existing CVS tree to a mirror? (And is there a mirror?) If you're talking about a working copy, then it's really easy: find $wcdir -type d -name CVS | while read d; do sed -i '' s/$oldhost/$newhost/ $d/Root done -- If you cc me or remove the list(s) completely I'll most likely ignore your message.see http://www.eyrie.org./~eagle/faqs/questions.html To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Bad crash with if_bge when loaded as module in loader.conf
Hi, Wild guess: You have miibus compiled into the kernel and it gets pulled in a second time when kldloading if_bge? Correct ! I'll look if that solves the crash. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
LESBENCAM.COM
Dear Sir/Madam, LESBENCAM.COM - Euro 380 LESBENCAM.COM is now available from us for IMMEDIATE transfer. The domain name market is extremely solid at the moment and similar domains are currently selling on afternic.com, greatdomains.com (domain auction sites), and by domain name brokers, in some cases for many thousands of US dollars. Please note that transfers take just 5-15 minutes and are extremely straightforward. Absolutely NO technical knowledge is required. We use two methods of payment. You may pay via Escrow.com or PayPal. Payment to us is instant and transfers can be completed in minutes. We pay all fees connected with the transfer process. If you would like to use WWW.LESBENCAM.COM for your online business,please contact us at your earliest convenience. Please don't hesitate to contact us should you require any further assistance. We thank you for your attention and sincerely apologise if this e-mail has not been of interest to you. Yours Sincerely, Jenny. Marketing, The Portal Please visit: HTTP://WWW.Ebay.com HTTP://WWW.1stdomainbrokers.com HTTP://WWW.Afternic.com Or many of the domain NAME auction sites. We hope you will agree that we are not only offering what we believe to be a genuine investment, but you will also benefit from owning a domain of this quality. Please note that your email address can be removed from our database by replying to this e-mail with REMOVE in the subject line. You will not be contacted again. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
sis 900 10/100BaseTX
I have a laptop (i-buddy) that I have put FreeBSD on. Everything works great except for the NIC. I think the problem is that freebsd does not have any support for this sis card because it is too new. Anyone know what to do ? I have included the description of the NIC from the web site that I bought the laptop, and the chunk of dmesg that has information about the sis card. (sis discription) Communications: Onboard full duplex 10/100 Base-T ethernet, MAC: SiS? 961 built-in 56K / V.90 Conexant PCI software data/fax modem Built-in SIR transceiver module, IrDA 1.3 standard compliant up to 4.0Mbps (chunk of dmesg) ata1: at 0x170 irq 15 on atapci0 pci0: multimedia, audio at device 2.7 (no driver attached) sis0: SiS 900 10/100BaseTX port 0xd400-0xd4ff mem 0xcfff9000-0xcfff9fff irq 5 at device 3.0 on pci0 sis0: Ethernet address: 00:50:eb:0e:40:d7 sis0: MII withour any PHY! device_probe_and_attach: sis0 attach returned 6 pci0: simple comms at device 5.0 (no driver attached) pci0: serial bus, FireWire at device 7.0 (no driver attached) Thanks, Dave To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Some security questions.
[ Re-sending due to earlier failure. ] On Mon, Feb 10, 2003 at 06:03:07PM -0800, Julian Elischer wrote: Our client wants the following 'features' and we'd LIKE to be able to at least say yes we can do that, even if we can also say but we don't think it's a good idea. 1/ Command logging. We're thinking that a hacked version of the shell that logs commands may do what they want, but personally I think that if you are going to log things then you really want to PROPERLY do it, and log the EXEC commands along with the arguments. (sadmin et al. doesn't give arguments, and neither does ktrace) From a security perspective, this is usually referred to as ``indi- vidual user accountability''; i.e. the ability to hold users compl- etely accountable for any actions performed under their account. The notion of ``auditing'' typically goes hand-in-hand with accoun- tability in this sense. These are recognised terms in security pu- blications such as the Information Technology Security Evaluation Criteria (ITSEC) [1]. I've been involved in generating a security solution that allowed the software engineers in the US to remotely connect to a live, op- erational, safety-related control system in London for the purposes of fault finding and software deployment. Before our Independent Safety and Technical Assessors would even consider looking at such a proposal, we had to provide assurance that every action by any user logged in remotely would always be traceable and could be reviewed for audit purposes. We could only permit remote access to the systems running Tru64 UNIX as it was the only OS that provided a fully-featured auditing sub-system that met ITSEC requirements. Tru64 UNIX will allow you to log just about any interaction with the system you fancy, from device access to system calls to command line interaction. Take a look at Section 10 of Tru64 UNIX Security [2] for more info- rmation. If acountability and auditing was to be done properly, I believe *this* is how it should be done. I've CC'd [EMAIL PROTECTED] to this post 'cause I think this would be right up their ally. Regards, Trent. [1] Information Technology Security Evaluation Criteria Version 1.2, 28th June, 1991. (http://www.cesg.gov.uk/assurance/iacs/itsec/documents/formal-docs/media/Itsec.pdf) [2] Tru64 UNIX -- Security Version AA-RH95D-TE, June 2001. (http://www.tru64unix.compaq.com/docs/base_doc/DOCUMENTATION/V51A_PDF/ARH95DTE.PDF) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: sis 900 10/100BaseTX
sis0: MII withour any PHY! the SiS900 driver has been around for a while. According to the code if_sis.c's sis_miibus_readreg (redirected from mii.c:^mii_phy_probe) returns if the phy number is not zero and the SiS900 revision is revision 635. I'm going to guess that this might be incorrect for your chip. Why? Duno.. You could try removing the sc-sis_rev SIS_REV_635 to see if a phy is on a higher level than zero. Another option is to check the PCI values. SiS7016 is similar to the SiS900, but, has no internal PHY. Maybe FreeBSD is incorrectly seeing the chip as a 900 when its a 7016? Sometimes that happens if you have an OEM fscking the PCIDID. Don To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Filesystem Experimentation Question
Okay, so I've got an odd ball filesystem idea that I'd like to experiment with on FreeBSD. Looking at it, I can probably best implement it as a layer on top of FFS at the start, rather than adding a new filesystem driver. Does anybody have any recommendations on references to look at for implementing this? Something like CFS seems like a good starting point to me, but I'm willing to consider other options (especially ones that don't break NFS). -- - Justin Wojdacki [EMAIL PROTECTED] (408) 350-5032 Communications Processors Group -- Analog Devices To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Filesystem Experimentation Question
Looking at it, I can probably best implement it as a layer on top of FFS at the start, rather than adding a new filesystem driver. NetBSD has overlay filesystems for stackable FS layers. I'm not sure about FreeBSD, but, its a starting point. Don To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
kevent kernel expert.
I have come across several (major imo) problems with the kevent(2) and need to have contact with someone that understands the implementation, specifically how kqueues are attached to filedesc structures. This has to deal with security as well as SMP lock down issues. Please respond privately. thank you, -- -Alfred Perlstein [[EMAIL PROTECTED]] 'Instead of asking why a piece of software is using 1970s technology, start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
