Re: FreeBSD kernel as a replacement for Linux kernel
On the other hand, the FreeBSD kernel is superior than that of Linux. Yes, and FreeBSD is also superior to every Linux distribution I have seen. Although SuSE is pretty good. And my penis is _SO_ much larger than yours. Large penises are _ALWAYS_ better, of course. -MB To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSD kernel as a replacement for Linux kernel
Perhaps we should go just a bit further with that approach and make things _write_ into that hierarchy first as well, e.g. if you run /compat/linux/bin/bash and then install something with rpm, it will install (as far as it's concerned) into /usr/bin, /usr/lib, etc. but really be chrooted into the /compat/linux hierarchy and only affect things there. Actually, I'm pretty sure that this does work as has since the 3.2 tree, when I thought to try it and see if it would. You actually have 2 options. 1. You can run /compat/linux/bin/bash and then you in a sort of Linux/FreeBSD directory mix. The root directory looks just like your FreeBSD root, but changing to a directory that is in /compat/linux, like /bin, will put in the linux tree of this directory, but changing to a directory that doesn't exist, like /home, will keep you in the FreeBSD structure. This is very close to being able to run FreeBSD and Linux at the same time (/bin/csh in one xterm and /compat/linux/bin/bash in another). Within this, you can do an rpm or any linux command and you will be operating on the Linux/FreeBSD mix directory structure. 2. Just run /compat/linux/bin/rpm (or any other command in /compat/linux) and you will be operating on the Linux directory structure as described above. I've found the Linux emulation on FreeBSD to be one of the best, most integrated emulation I've ever seen of anything. I've messed around with it quite a bit and discovered quite a few nifty tricks you can do. I've never actually tried it, but I think you could probably compile Linux binaries under FreeBSD by installing the Linux version of gcc and using it. Very cool stuff. Keep up the excellent work! --- Preston Wiley GoTo.Com, Inc. Systems Administrator 1820 Gateway Drive, Suite 300 [EMAIL PROTECTED] San Mateo, CA 94404 650/403-2227 http://www.cadabra.com --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSD kernel as a replacement for Linux kernel
1. You can run /compat/linux/bin/bash and then you in a sort of Linux/FreeBSD directory mix. The root directory looks just like your FreeBSD root, but changing to a directory that is in /compat/linux, like /bin, will put in the linux tree of this directory, but changing to a directory that doesn't exist, like /home, will keep you in the FreeBSD Well, what do you know - you're right! :) I learn something new every day. I've found the Linux emulation on FreeBSD to be one of the best, most integrated emulation I've ever seen of anything. I've messed around with it quite a bit and discovered quite a few nifty tricks you can do. I've never actually tried it, but I think you could probably compile Linux binaries under FreeBSD by installing the Linux version of gcc and using it. There used to be a linux-devel port which did exactly this. Don't know what became of it, however.. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSD kernel as a replacement for Linux kernel
On Wed, May 24, 2000 at 12:07:06AM -0700, Jordan K. Hubbard wrote: There used to be a linux-devel port which did exactly this. Don't know what became of it, however.. [hawk-billf] /home/billf cat /usr/ports/devel/linux_devtools/pkg/COMMENT Packages needed for doing development in Linux mode -- Bill Fumerola - Network Architect / Computer Horizons Corp - CVM e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
error in usr.bin/ftp/main.c ?
Hi,
in usr.bin/ftp/main.c at line 407; instead of
if (line[--num] == '\n') {
it should probably be
if (buf[--num] == '\n') {
looks like a copy-paste error to me.
greets
thomas
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
MAD16 in FreeBSD 4.0
Hi! I'm using FreeBSD-4.0-RELEASE and I'm not able to get my sound card work. my soundcard is "Monte Carlo 929" by "Turtle Beach". AFAIK there is MAD16 (OPTi 82C929) and is compatible w/ mss, sb (i guess sb pro), midi (YM 3812/OPL3) and have MPU 401 interface. I only need mss to work. There are some documents about configuring it but now... I found out this: using device snd is obsolete, I tried it and there is much more nois than real sounds device pcm doesnt find the card device pcm0 irq 10 ... etc then this if found: pcm0: CS4231A at port 0x530-0x537 irq 10 drq 1 flags 0xa100 on isa0 but at boot time and at any time I want to use it, it seems to wait for some time-out... nothing there's nothing to be heared. $ cat /dev/sndstat FreeBSD Audio Driver (newpcm) May 23 2000 11:08:18 Installed devices: pcm0: CS4231A at io 0x530 irq 10 drq 1 (1p/1r channels) I had the similar (or the same) problem in linux, it seems that it found mss (CS4231A) but do not use MAD16 which is really needed to be used to make sound (AFAIK - but maybe I'm wrong). The problem was solved w/ Linux 2.2.x. I have found some information in list-archives - there was some options MAD16_PORT but it doesn't seem to work. And handbook is about kernel 3.x :( - am I missing the newest one? Any help? Zeno To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-multimedia" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Need help debugging a crash (PR kern/18685)
Hi,
I'm trying to assist in debugging the crash reported as kern/18685--
apparently Greg is unable to reproduce the problem on his machine.
The error
| Fatal trap 12: page fault while in kernel mode
| fault virtual address = 0x69666f27
| fault code= supervisor read, page not present
| instruction pointer = 0x8:0xc0158c14
| stack pointer = 0x10:0xc3dd7bf8
| frame pointer = 0x10:0xc3dd7c0c
| code segment = base 0x0, limit 0xf, type 0x1b
| = DPL 0, pres 1, def32 1, gran 1
| processor eflags = interrupt enabled, resume, IOPL = 0
| current process = 974 (make)
| interrupt mask= none
| kernel: type 12 trap, code=0
| Stopped at dscheck+0x104: movl0xb8(%esi),%edx
|
| db trace
| dscheck(c1413728,c08c6900) at dscheck+0x104
| diskstrategy(c1413728,c0845e80,c1413728,0,c3dd7c4c) at diskstrategy+0xad
| spec_strategy(c3dd7c70,c3dd7c58,c0208f7d,c3dd7c70,c3dd7c8c) at spec_strategy+0x8c
| spec_vnoperate(c3dd7c70,c3dd7c8c,c02089e5,c3dd7c70,c3dd7ce4) at spec_vnoperate+0x15
| ufs_vnoperatespec(c3dd7c70,c3dd7ce4,c1413728,0,c028ae80) at ufs_vnoperatespec+0x15
| ...
occurs at line 198 ("labelsect = lp-d_partitions[LABEL_PART].p_offset;")
of /sys/kern/subr_diskslice.c due to a bogus "struct diskslices" pointer
(the second argument of dscheck(), "ssp").
I can't do a crash dump, since ddb refuses to step past the instruction
that triggered the trap (saying "panic" just repeats the above message).
I can't catch the "ssp" pointer when it gets corrupted either, since
watchpoints don't seem to work in ddb (at least not on kernel memory).
What can I do to help getting this fixed? Suggestions?
Thomas
--
Thomas Faehnle, Am Sommerrain 12, D-71522 Backnang | MIME mail welcome
mail: [EMAIL PROTECTED] * phone: +49 7191 954671 | PGP key available
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: xxx_stop and ifq-if_snd in NIC drivers
In message [EMAIL PROTECTED] Duncan Barclay writes: : In a wireless NIC driver should one drain the output queue when the interface is : stopped? I've been perusing /sys/dev/awi.c and the output queue is drained in : that driver. It depends on how the interface is stopped. If it is being stopped a few milliseconds before it loses power, I don't think it would make sense to drain anything... If it is just ifconfig down, then it likely makes sense. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
shutdownhook_establish()
I see references to this routing (apparently replacing at_shutdown() in v4.0) but compiling it into a driver results in an unresolved reference. I also dont see it in any of the include files. How can this be used, and where does it live? Dennis To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSD kernel as a replacement for Linux kernel
On Wed, 24 May 2000, Daniel O'Connor wrote: On 24-May-00 Mohit Aron wrote: Yes, that looks promising. That'll possibly enable one to install rpms easily on FreeBSD. You can try this too.. rpm --ignoreos --root /compat/linux --dbbath /var/lib/rpm --nodeps --replacepkgs foo.rpm Or: /compat/linux/bin/bash rpm Running Linux-based installers directly in the FreeBSD environment can Cause Problems(tm), particularly if they're shells scripts that make assumptions. Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSD kernel as a replacement for Linux kernel
:Or: : :/compat/linux/bin/bash :rpm : :Running Linux-based installers directly in the FreeBSD environment can :Cause Problems(tm), particularly if they're shells scripts that make :assumptions. : :Doug White| FreeBSD: The Power to Serve :[EMAIL PROTECTED] | www.FreeBSD.org That should be mostly fixed now, actually, insofar as you have the correct linux utilities installed in /compat/linux (so the scripts don't break-out of the linux emulation by running freebsd utilities which then turn around and try to run other scripts). -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: shutdownhook_establish()
I see references to this routing (apparently replacing at_shutdown() in v4.0) but compiling it into a driver results in an unresolved reference. I also dont see it in any of the include files. How can this be used, and where does it live? Use EVENTHANDLER_REGISTER; see sys/kern/kern_shutdown.c for examples. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Needed: suid library calls (was Re: cvs commit: src/crypto/openssh sshd_config)
"Jeroen C. van Gelderen" wrote: [...] Since user authentication is needed by more than one program it should live in it's own process. Right now there is code duplication and it is impossible to change the authentication policy without messing with sshd. What we _really_ need is some mechanism to recognize the difference between a user program and a system library, with an eye towards granting privileges to trusted libraries without letting those privileges leak past the library in question. I don't claim that this is an _easy_ thing to do, nor that it is a particularly standard thing to do. But the mechanism of having some sort of daemon or service whose job it is to just do !strcmp(pw-pw_passwd,crypt(foo,pw-pw_passwd)) is, I think, kind of overkill. Perhaps some sort of syscall to change the euid that only works in privileged libraries would work. User authentication is only one example. There are many things that only root can do where letting non-root do the job is not dangerous, but granting non-root permission in a general way is. Another good example is daemons that must bind listening sockets 1024, but don't need root otherwise. The entire binary must be suid up to the bind, at which point the program may renounce the suid bit (setreuid(getuid(),getuid());). Wouldn't it be more secure if a library could selectively grant low ports to _selected_ non-suid programs (perhaps with a config file)? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
hack.c in kernel
On Fri, 19 May 2000 17:35:34 PDT, "Manny Obrey" [EMAIL PROTECTED] wrote: I saw the following near the end of running "make depend;make" during a kernel re-config ... seriously, is this something to be concerned about? ... cc -elf -shared -nostdlib hack.c -o hack.So To expand somewhat on Kris's answer: hack.So is a dummy shared object whose sole purpose is to make the linker mark the kernel as a `dynamic', rather than `static' executable. This allows it to use the dynamic loader (ie load kernel modules at run time). This is probably an RTFM, but I'm not sure which FM to suggest you R. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: file creation times ?
On Thu, 18 May 2000 10:35:11 -0700, Arun Sharma [EMAIL PROTECTED] wrote: On Thu, May 18, 2000 at 09:04:52PM +0400, Aleksandr A.Babaylov wrote: Arun Sharma writes: Is there any reason why FreeBSD doesn't store file creation times on the disk (apart from historical reasons) ? To put it another way, why _should_ FreeBSD store a file creation time? in adddition to atime, ctime and mtime? struct timespec st_atimespec; /* time of last access */ struct timespec st_mtimespec; /* time of last data modification */ struct timespec st_ctimespec; /* time of last file status change */ None of them tell me when the file was created. That's all Unix has ever offered (both the original ATT FS and FFS/UFS). If you really need a file creation time, you'll need a different filesystem. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: boot/kernel debugging
Nick Hibma writes: In general it is well possible to single step anything in the kernel. You might find occasions where things stop working, and odd cases were things all of a sudden start working, but normally, apart from hardware things, most things are not time critical, or create problems through spin locks. You can single step at boot time, by setting the flags in the loader. set boot_ddb# jump to debugger set boot_gdb# use remote gdb for debugging by default Also don't for get 'sysctl -w debug.enter_debugger=ddb' (or gdb) to enter the debugger from the command line. -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Need help debugging a crash (PR kern/18685)
Thomas Faehnle writes: I'm trying to assist in debugging the crash reported as kern/18685-- apparently Greg is unable to reproduce the problem on his machine. Have you tried hooking up another machine via serial console and using gdb? -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Driver for Aureal Vortex* based soundcards is available
[Please, remove hackers from Cc: list when replying] Finally took the time to put this stuff together. I am releasing the newpcm driver for Aureal Vortex1, Vortex2, Vortex Advantage based soundcards (au8830, au8820, au8810 chipsets). This is not a "true" driver, it needs to be linked with Aureal's Linux Vortex binary core which provides the interface to the Vortex hardware. Detailed information can be found on: http://www.cis.ohio-state.edu/~matey/au88x0/ Driver supports 4 playback channels at sampling rates 4 though 48kHz. Recording is also supported to some extent. The only soundcard I had the chance to test it with was my Diamond Monster MX-300 (Vortex2, au8830 based card). If your soundcard is based on au8820 or au8810 chipsets please give it a try. I'd like to know if it works for other chipsets as well. I tested it on 5.0-CURRENT although I believe it should compile and run on 4.0-STABLE as well. This my first driver, any comments are appreciated. :) -- lx To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: file creation times ?
On Thu, May 25, 2000 at 11:03:38AM +1000, Peter Jeremy wrote: On Thu, 18 May 2000 10:35:11 -0700, Arun Sharma [EMAIL PROTECTED] wrote: On Thu, May 18, 2000 at 09:04:52PM +0400, Aleksandr A.Babaylov wrote: Arun Sharma writes: Is there any reason why FreeBSD doesn't store file creation times on the disk (apart from historical reasons) ? To put it another way, why _should_ FreeBSD store a file creation time? 0. I'm tired of seeing people putting "Created: mm/dd/yy" in their documents. 1. NTFS does it. It's a part of SMB. I suspect that Samba just uses the last modified time. 2. An average computer user would expect it. I didn't know that UNIX didn't keep track of file creation times 5-6 years after I started using it. That's all Unix has ever offered (both the original ATT FS and FFS/UFS). If you really need a file creation time, you'll need a different filesystem. I know. That's why I ask. So if someone designs a ext3fs killer journalling filesystem for BSD, would they consider adding it :) ? -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Needed: suid library calls (was Re: cvs commit: src/crypto/openssh sshd_config)
:"Jeroen C. van Gelderen" wrote: : : [...] : : Since user authentication is needed by more than one program it : should live in it's own process. Right now there is code : duplication and it is impossible to change the authentication : policy without messing with sshd. : : :What we _really_ need is some mechanism to recognize the difference :between a user program and a system library, with an eye towards :granting privileges to trusted libraries without letting those privileges :leak past the library in question. Oh god, its MULTICS! Run! Run! Run for the hills! -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: hack.c in kernel
tks for the clarifcation! From: Peter Jeremy [EMAIL PROTECTED] To: Manny Obrey [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Subject: hack.c in kernel Date: Thu, 25 May 2000 11:03:37 +1000 On Fri, 19 May 2000 17:35:34 PDT, "Manny Obrey" [EMAIL PROTECTED] wrote: I saw the following near the end of running "make depend;make" during a kernel re-config ... seriously, is this something to be concerned about? ... cc -elf -shared -nostdlib hack.c -o hack.So To expand somewhat on Kris's answer: hack.So is a dummy shared object whose sole purpose is to make the linker mark the kernel as a `dynamic', rather than `static' executable. This allows it to use the dynamic loader (ie load kernel modules at run time). This is probably an RTFM, but I'm not sure which FM to suggest you R. Peter Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Needed: suid library calls (was Re: cvs commit: src/crypto/openssh sshd_config)
Matthew Dillon wrote: [lost attribution. Nick wrote this] : :What we _really_ need is some mechanism to recognize the difference :between a user program and a system library, with an eye towards :granting privileges to trusted libraries without letting those privileges :leak past the library in question. Oh god, its MULTICS! Run! Run! Run for the hills! See? Final proof that those who don't know history are bound to repeat it. :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: file creation times ?
On 2000-May-25 11:59:41 +1000, Arun Sharma [EMAIL PROTECTED] wrote: On Thu, May 25, 2000 at 11:03:38AM +1000, Peter Jeremy wrote: To put it another way, why _should_ FreeBSD store a file creation time? 0. I'm tired of seeing people putting "Created: mm/dd/yy" in their documents. - UFS stores a UID for each file, but that doesn't stop "Author: J. Bloggs" in documents. Why would storing a creation timestamp be any different? - How do you determine the creation time of a file when it's printed? - If I make a copy of an existing file, was the new file created when the original file was created or when I did the copy? 1. NTFS does it. It's a part of SMB. That's not justification for putting a creation time into the UFS. Different filesystems store different information - depending on what the FS developers saw as important. You could just as easily point out the deficiencies of NTFS based on it's inability to support all the metadata in NFS. I suspect that Samba just uses the last modified time. According to the SAMBA documentation, it uses the earliest of the 3 timestamps that are available. (Or can be told to fake a creation time of 1980-JAN-01 on directories). Transferring file metadata between systems is always problematic. Generally the metadata translation layer does the best it can and fakes the rest. For example, NTFS access and modification timestamps can't be translated to Unix timestamps without knowing the location (timezone) where the NTFS file was last modified/accessed. 2. An average computer user would expect it. I didn't know that UNIX didn't keep track of file creation times 5-6 years after I started using it. If it took you 5-6 years to notice that the creation time _wasn't_ stored, the creation time can't have been that important to you. (And I haven't previously run into anyone else who wanted a creation time, so the expectation can't be that widespread). So if someone designs a ext3fs killer journalling filesystem for BSD, would they consider adding it :) ? Adding a creation timestamp would add 4 or 8 bytes of metadata to each file, as well as requiring additional code (and CPU time) to manage it. A 6th Edition inode was 32 bytes (and only stored access and modify times). A FreeBSD inode is already 4 times as big. It's necessary to strike a balance between storing every possible piece of information about a file and the amount of space/time used to store/manage this metadata. A modification timestamp is essential to support incremental backups. Splitting it into separate data and metadata timestamps meets POLA (users generally want 'modification' to mean that the content changed, not that the file was renamed). Access timestamps are important for filespace management (knowing what files aren't used and can therefore be archived or deleted). As far as I'm concerned, you still haven't demonstrated any real need or justification for a creation timestamp. That said, there's nothing stopping you adding a creation timestamp to the UFS and providing patches. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
NFS, permissions and 4.0-RELEASE
I have several partitions from a 3.2-RELEASE machine mounted via NFS on a 4.0-RELEASE machine. On the 4.0 machine, I am unable to append to a world writable file (622, for example) that resides on the 3.2 machine. This did not happen with 3.3. Using cat /nfspath/file results in "cat: stdout: Permission denied" as soon as the first line of text tries to get appended. I double-checked the mount point permissions on the 4.0 box and they are the same as on a 3.3 box that does the above with no problem. The mount point is set to 755. Am I missing something very obvious, or have things changed a bit in this situation with 4.0? -- Scott M. Drassinower [EMAIL PROTECTED] Cloud 9 InternetWhite Plains, NY +1 914 696-4000 / 800 356-5683 http://www.cloud9.net To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Needed: suid library calls (was Re: cvs commit: src/crypto/openssh sshd_config)
Matthew Dillon wrote: :"Jeroen C. van Gelderen" wrote: : : [...] : : Since user authentication is needed by more than one program it : should live in it's own process. Right now there is code : duplication and it is impossible to change the authentication : policy without messing with sshd. : : :What we _really_ need is some mechanism to recognize the difference :between a user program and a system library, with an eye towards :granting privileges to trusted libraries without letting those privileges :leak past the library in question. Oh god, its MULTICS! Run! Run! Run for the hills! Hold on! I only spoke the first part, mind your quoting pleaz! Cheers, Jeroen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
