[no subject]
what's the sitch on pccardd, if adaptors on, /dev/pccard* on 5.0-R? I've got an intel anypoint 2 wireless pcmcia card that is detected as pccard1 by the kernel, but where is the missing link that tells the kernel or rc that it's an ehternet adaptor? As I understand it, pccardd and pccard.conf are all old a/o 5.0. if they are, how is this supposed to work? many thanks and good fishing, -P To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
smbfs crashes
whenever I move a file from a node mounted with mount_smbfs to a local fs, the system crashes with a kernel page fault. is this a known problem? -P To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: appending files on smbfs
hello, tim. the patch you sent me did fix the problem stated, but now I've
noticed some interesting characteristics of the files that are created by a
unix machine on a share mounted by mount_smbfs, which itself resides on a
windows 200 machine.
I haven't looked into the details, but I'm using kdevelop to create a blank
c++ project with no lsm/GNU files, on that share. the problems come up in
configure with conftest and its corresponsing files. the configure script
fails with permission problems in deleteing the file. that unix machine
thinks conftest is a file, and the windows machine thinks it's a directory.
the windows machine can delete the directory, the unix machine can't delete
the file. hmm. There are also several similar errors with conftest.cc, etc.
Also, the configure script complains about not being able to find
Makefile.in, which is actually there. This could have something to do with
the conftest thing.
Copying files works fine from both directions, and I haven't seen any other
problems but this one. it probably has something to do with the way the
files are created, don't know. The symptoms are slightly worse with windows
98 machines.
The box is still a relatively clean 5.0-release, with only the patch below
applied to the smbfs source.
hope that helps, thanks!
-P
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Tim Robbins
Sent: Monday, February 03, 2003 5:59 AM
To: Patrick Stinson
Cc: freebsd-current
Subject: Re: appending files on smbfs
On Thu, Jan 30, 2003 at 07:37:04PM -, Patrick Stinson wrote:
has anyone every had problems with appending existing files on volumes
mounted by smbfs or shlight?
$ echo sdsad hey
$ echo sdsad hey
cannot create hey: Permission denied
Please try this patch and let me know whether it solves the problem.
Index: src/sys/fs/smbfs/smbfs_vnops.c
===
RCS file: /x/freebsd/src/sys/fs/smbfs/smbfs_vnops.c,v
retrieving revision 1.28
diff -u -r1.28 smbfs_vnops.c
--- src/sys/fs/smbfs/smbfs_vnops.c 29 Jan 2003 13:41:52 - 1.28
+++ src/sys/fs/smbfs/smbfs_vnops.c 3 Feb 2003 05:51:45 -
@@ -139,10 +139,9 @@
} */ *ap;
{
struct vnode *vp = ap-a_vp;
- struct ucred *cred = ap-a_cred;
- u_int mode = ap-a_mode;
+ mode_t mode = ap-a_mode;
+ mode_t smbmode;
struct smbmount *smp = VTOSMBFS(vp);
- int error = 0;
SMBVDEBUG(\n);
if ((mode VWRITE) (vp-v_mount-mnt_flag MNT_RDONLY)) {
@@ -153,15 +152,10 @@
break;
}
}
- if (cred-cr_uid == 0)
- return 0;
- if (cred-cr_uid != smp-sm_args.uid) {
- mode = 3;
- if (!groupmember(smp-sm_args.gid, cred))
- mode = 3;
- }
- error = (((vp-v_type == VREG) ? smp-sm_args.file_mode :
smp-sm_args.dir_mode) mode) == mode ? 0 : EACCES;
- return error;
+ smbmode = vp-v_type == VREG ? smp-sm_args.file_mode :
+ smp-sm_args.dir_mode;
+ return (vaccess(vp-v_type, smbmode, smp-sm_args.uid,
+ smp-sm_args.gid, ap-a_mode, ap-a_cred, NULL));
}
/* ARGSUSED */
Tim
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
appending files on smbfs
has anyone every had problems with appending existing files on volumes mounted by smbfs or shlight? $ echo sdsad hey $ echo sdsad hey cannot create hey: Permission denied hmmm thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Re[2]: appending files on smbfs
The files on the ntfs machine are owned and shared only by the user that owns them. The same username is being used from the unix side via smbfs. I've changed the privelages to everyone with full rights, and only that username with full rights, and no go. interesting. I don't see any point where there could be a security hang up. Also, do you have any idea what, at an OS-security level, the difference is between creating and appending files? -Original Message- From: Alex [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 30, 2003 10:43 PM To: Patrick Stinson Cc: Alex Subject: Re[2]: appending files on smbfs Dear/Beste Patrick, Thursday, January 30, 2003, 11:16:09 PM, you wrote: has anyone every had problems with appending existing files on volumes mounted by smbfs or shlight? $ echo sdsad hey $ echo sdsad hey cannot create hey: Permission denied You should look at permission on the windows machine if the system has NTFS. *** From Patrick oh wait, thought you were swedish. No, i'm Dutch. I meant that I looked at that. You have to log in to the filesystem with a name that works before it will let yo on. notice how I can create the file, but canat append to it. NTFS hasn't got the same security system as UFS. Just because you can logon to a filesystem doesn't mean you have any rights. Just because you can write a file doesn't mean you can append. On NTFS one can allow per person or per group to list, view, read, create or modify (append) a file. And that for multiple users and multiple groups. -- Best regards/Met vriendelijke groet, Alex P.S. Please don't top-post. It makes it hard to read, especially for others. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Sound playback problem with Maestro3.c (?)
This is a software issue. The echoing is what happens when the sound driver doesn't receive audio data fast enough from an application (ie OSS). when the driver doesn't get the data in time, it plays whatever was last in the buffer until it does get audio. this sort of thing always happens no matter what the platform. My experience with BSD, and any not-successfully preemptive kernels is that io and process sceduling never provides proper attention to the processes requiring enough power for smooth audio. I beleive 5.0 will appreciate this point, and this mailing list would be a good place to start. Disk IO has always been a big factor for me. I've moved my audio development from my FBSD/Inspiron 8000 into the ASIO/DirectX arena for performance reasons. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Michael Ferguson Sent: Tuesday, January 07, 2003 5:48 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Sound playback problem with Maestro3.c (?) Hi all, I'm experiencing a small issue with the sound output on the Maestro3 in my Dell Inspiron 8000 laptop. Every few seconds, the sound is briefly interrupted, and the last few ms of audio are looped for about a quarter of a second. I've noticed that this can happen independently on either channel; often it will pause/loop on the left channel, then shortly thereafter on the right, or visa versa. Other times it will pause/loop on both channels at the same time. I've also noticed this condition can be exaggerated by moving the mouse while moused is running; the sound pause/loops much more frequently (although not for as long), and the music becomes noticeably slower. This happens both when moving the built-in PS/2 touchpad mouse and on a USB mouse, if I plug one in. My only ignorant guess would be that this is some kind of interrupt polling issue, but since I am new to BSD and I have no clue about the driver architecture or PCM, I can only venture a guess. :/ I was experiencing this in the 4.7-release kernel also (this bug is actually why I upgraded to -current :P). Some other users appear to be having the same problems (even when porting the driver to NetBSD?). Here are some links: http://groups.google.com/groups?hl=enlr=ie=UTF-8oe=UTF8threadm=a6u7p 2%24vlc%241%40FreeBSD.csie.NCTU.edu.twrnum=1prev=/groups%3Fq%3DFreeBSD %2BMaestro3%2Bpopping%26hl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3DUTF8%26selm% 3Da6u7p2%2524vlc%25241%2540FreeBSD.csie.NCTU.edu.tw%26rnum%3D1 http://mail-index.netbsd.org/current-users/2001/08/23/0004.html I tried compiling without PNP and APM in the 4.7-release kernel, but I still saw the same issues, so I don't think they're entirely tied to that (especially since I'm running ACPI now in -current, without any apmd). My laptop is running the latest bios (A21), and the sound card has ID card=0x00a41028 chip-0x1998125d rev=0x10; my dmesg and pciconf output are also at ftp://129.110.23.84/. On a probably-unrelated side note, when I was running Linux on the same laptop (ducks), I had issues with the OS clock getting quickly out of sync with the HW clock; typically I would loose five minutes or more every hour. Although I haven't experienced the same thing with FreeBSD, I wonder if there is just something odd about interrupt handling or timing on the Inspiron 8000 line? Best regards, -- mcf To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Sound playback problem with Maestro3.c (?) -- clock issue
never noticed anything like that -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Paul A. Mayer Sent: Wednesday, January 08, 2003 11:19 AM To: Michael Ferguson Cc: [EMAIL PROTECTED] Subject: Re: Sound playback problem with Maestro3.c (?) -- clock issue Hi Michael, Regarding your linux clock issue: There was a rather lively discussion at forums.gentoo.org about drastic clock sync loss caused by KDE. I don't know if it has been resolved in the 3.1 line, but if you were running linux KDE, you might take a look at that as a cause for the linux clock sync problem. /Paul Michael Ferguson wrote: Hi all, On a probably-unrelated side note, when I was running Linux on the same laptop (ducks), I had issues with the OS clock getting quickly out of sync with the HW clock; typically I would loose five minutes or more every hour. Although I haven't experienced the same thing with FreeBSD, I wonder if there is just something odd about interrupt handling or timing on the Inspiron 8000 line? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: How can I use my kernel on DP2?
assuming you read the handbook on updating the kernel http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html , UPDATING in /usr/src ftp://ftp.freebsd.org/pub/FreeBSD/branches/-current/src/UPDATING , and completed a make and make install in your kernel compile directory, you should be able to use it. before you waste time rebooting 1000 times, check the file size of the new kernel and the old kernel to see if it changes. also, look at the make files to see what's happening when you run certain targets. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of kai ouyang Sent: Wednesday, December 04, 2002 12:56 PM To: [EMAIL PROTECTED] Subject: How can I use my kernel on DP2? Hi, everybody, I found a very strange thing about kernel on DP2. I do not know why I compiled my kernel, but I can not boot with it? Current# uname -a FreeBSD Current.wtwh.com.cn 5.0-DP2 FreeBSD 5.0-DP2 #1: Sat Nov 16 13:38:33 GMT 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 When The box reboot, I explicitly do as follow: ?unload ?load /boot/kernel/kernel ?boot But the result is the same!!! Why? Best Regards Ouyang Kai _ ÏíÓÃÊÀ½çÉÏ×î´óµÄµç×ÓÓʼþϵͳ¡ª MSN Hotmail¡£ http://www.hotmail.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Emacs errors, undefined references to osream::[*] after 4.4 - 5.0 upgd
-Original Message- From: Patrick Stinson [mailto:[EMAIL PROTECTED]] Sent: Monday, December 02, 2002 5:55 PM To: Patrick Stinson Subject: RE: Emacs errors, undefined references to osream::[*] after 4.4 - 5.0 upgd no, after a new install, I'm still getting the link errors for the undefined reference to ostream members. I've got no idea. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Patrick Stinson Sent: Sunday, December 01, 2002 3:31 PM To: Garrett Rooney Cc: freebsd-current Subject: RE: Emacs errors, undefined references to osream::[*] after 4.4 - 5.0 upgd mmm, yeah, I might try removing all of the headers and doing another installworld -Original Message- From: Garrett Rooney [mailto:[EMAIL PROTECTED]] Sent: Monday, December 02, 2002 2:48 AM To: Patrick Stinson Cc: freebsd-current Subject: Re: Emacs errors, undefined references to osream::[*] after 4.4 - 5.0 upgd On Sunday, December 1, 2002, at 09:40 AM, Patrick Stinson wrote: After doing a complete upgrade (on a clean system, no less) from 4.4 5.0, I;ve found that every now and again I get the same compiler error regarding undefined references to cerr, ostream operators, etc. I'm building the gcc33 port assuming it's a compat. issue with the libs, but has anyone else seen this? Also, all versions of emacs sparatically seg fault upon startup. thanks. i don't know about the emacs thing, but the compiler errors sound like the kind of thing you see when you try to link a c++ program with gcc instead of g++. also, there are some issues with old header files from a 4.X system that's been updated to 5.0. the details should be in UPDATING. -garrett -- garrett rooneyRemember, any design flaw you're [EMAIL PROTECTED] sufficiently snide about becomes http://electricjellyfish.net/ a feature. -- Dan Sugalski To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Emacs errors, undefined references to osream::[*] after 4.4 - 5.0 upgd
After doing a complete upgrade (on a clean system, no less) from 4.4 5.0, I;ve found that every now and again I get the same compiler error regarding undefined references to cerr, ostream operators, etc. I'm building the gcc33 port assuming it's a compat. issue with the libs, but has anyone else seen this? Also, all versions of emacs sparatically seg fault upon startup. thanks. -P patrickkidd.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Emacs errors, undefined references to osream::[*] after 4.4 - 5.0 upgd
sorry, here is one of the compiler errors: $ make c++ Main.o Temperature.o Xpm.o -o Temperature.app -L/usr/X11R6/lib -lXpm -lXext -lX11 Temperature.o: In function `catchChildExit(int)': Temperature.o(.text+0x73): undefined reference to `cerr' Temperature.o(.text+0x80): undefined reference to `ostream::operator(char const*)' Temperature.o(.text+0x90): undefined reference to `ostream::operator(char const*)' Temperature.o(.text+0x98): undefined reference to `endl(ostream)' Temperature.o: In function `Temperature::Temperature(int, char**)': Temperature.o(.text+0x540): undefined reference to `cerr' Temperature.o(.text+0x54d): undefined reference to `ostream::operator(char const*)' Temperature.o(.text+0x55d): undefined reference to `ostream::operator(char const*)' Temperature.o(.text+0x56f): undefined reference to `ostream::operator(char const*)' Temperature.o(.text+0x577): undefined reference to `endl(ostream)' Temperature.o(.text+0x58a): undefined reference to `cerr' Temperature.o(.text+0x597): undefined reference to `ostream::operator(char const*)' Temperature.o(.text+0x5a7): undefined reference to `ostream::operator(char const*)' Temperature.o(.text+0x5af): undefined reference to `endl(ostream)' Temperature.o(.text+0x66f): undefined reference to `cerr' Temperature.o(.text+0x67c): undefined reference to `ostream::operator(char const*)' Temperature.o(.text+0x68c): undefined reference to `ostream::operator(char const*)' Temperature.o(.text+0x6d4): undefined reference to `cerr' Temperature.o(.text+0x6e1): undefined reference to `ostream::operator(char const*)' Temperature.o(.text+0x6f1): undefined reference to `ostream::operator(char const*)' Temperature.o(.text+0x709): undefined reference to `ostream::operator(char const*)' Temperature.o(.text+0x719): undefined reference to `ostream::operator(char const*)' Temperature.o(.text+0x721): undefined reference to `endl(ostream)' Temperature.o(.text+0x79e): undefined reference to `cerr' Temperature.o(.text+0x7ab): undefined reference to `ostream::operator(char const*)' Temperature.o: In function `Temperature::Temperature(int, char**)': Temperature.o(.text+0xcd0): undefined reference to `cerr' Temperature.o(.text+0xcdd): undefined reference to `ostream::operator(char const*)' Temperature.o(.text+0xced): undefined reference to `ostream::operator(char const*)' Temperature.o(.text+0xcff): undefined reference to `ostream::operator(char const*)' Temperature.o(.text+0xd07): undefined reference to `endl(ostream)' Temperature.o(.text+0xd1a): undefined reference to `cerr' Temperature.o(.text+0xd27): undefined reference to `ostream::operator(char const*)' Temperature.o(.text+0xd37): undefined reference to `ostream::operator(char const*)' Temperature.o(.text+0xd3f): undefined reference to `endl(ostream)' Temperature.o(.text+0xdff): undefined reference to `cerr' Temperature.o(.text+0xe0c): undefined reference to `ostream::operator(char const*)' Temperature.o(.text+0xe1c): undefined reference to `ostream::operator(char const*)' Temperature.o(.text+0xe64): undefined reference to `cerr' Temperature.o(.text+0xe71): undefined reference to `ostream::operator(char const*)' Temperature.o(.text+0xe81): undefined reference to `ostream::operator(char const*)' Temperature.o(.text+0xe99): undefined reference to `ostream::operator(char const*)' Temperature.o(.text+0xea9): undefined reference to `ostream::operator(char const*)' Temperature.o(.text+0xeb1): undefined reference to `endl(ostream)' Temperature.o(.text+0xf2e): undefined reference to `cerr' Temperature.o(.text+0xf3b): undefined reference to `ostream::operator(char const*)' Temperature.o: In function `Temperature::tryHelp(char*)': Temperature.o(.text+0xfd9): undefined reference to `cerr' Temperature.o(.text+0xfde): undefined reference to `endl(ostream)' Temperature.o(.text+0xfee): undefined reference to `ostream::operator(char const*)' Temperature.o(.text+0xffd): undefined reference to `ostream::operator(char const*)' Temperature.o(.text+0x100d): undefined reference to `ostream::operator(char const*)' Temperature.o(.text+0x1015): undefined reference to `endl(ostream)' -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Patrick Stinson Sent: Sunday, December 01, 2002 2:40 PM To: freebsd-current Subject: Emacs errors, undefined references to osream::[*] after 4.4 - 5.0 upgd After doing a complete upgrade (on a clean system, no less) from 4.4 5.0, I;ve found that every now and again I get the same compiler error regarding undefined references to cerr, ostream operators, etc. I'm building the gcc33 port assuming it's a compat. issue with the libs, but has anyone else seen this? Also, all versions of emacs sparatically seg fault upon startup. thanks. -P patrickkidd.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Emacs errors, undefined references to osream::[*] after 4.4 - 5.0 upgd
mmm, yeah, I might try removing all of the headers and doing another installworld -Original Message- From: Garrett Rooney [mailto:[EMAIL PROTECTED]] Sent: Monday, December 02, 2002 2:48 AM To: Patrick Stinson Cc: freebsd-current Subject: Re: Emacs errors, undefined references to osream::[*] after 4.4 - 5.0 upgd On Sunday, December 1, 2002, at 09:40 AM, Patrick Stinson wrote: After doing a complete upgrade (on a clean system, no less) from 4.4 5.0, I;ve found that every now and again I get the same compiler error regarding undefined references to cerr, ostream operators, etc. I'm building the gcc33 port assuming it's a compat. issue with the libs, but has anyone else seen this? Also, all versions of emacs sparatically seg fault upon startup. thanks. i don't know about the emacs thing, but the compiler errors sound like the kind of thing you see when you try to link a c++ program with gcc instead of g++. also, there are some issues with old header files from a 4.X system that's been updated to 5.0. the details should be in UPDATING. -garrett -- garrett rooneyRemember, any design flaw you're [EMAIL PROTECTED] sufficiently snide about becomes http://electricjellyfish.net/ a feature. -- Dan Sugalski To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: [music-dsp] How do I read the Loop information from a .WAV file?
this is a great guide http://www.sonicspot.com/guide/wavefiles.html -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] Sent: Thursday, November 28, 2002 6:51 PM To: [EMAIL PROTECTED] Subject: [music-dsp] How do I read the Loop information from a .WAV file? Hy guys, please, anyone knows how do I read the Loop information from a .WAV file? I'm using fread to read the header, but how I read the rest? fread(header, 4, 3, fd) Regards, WilliamK --- Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.423 / Virus Database: 238 - Release Date: 25/11/02 dupswapdrop -- the music-dsp mailing list and website: subscription info, FAQ, source code archive, list archive, book reviews, dsp links http://shoko.calarts.edu/musicdsp/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
cyclic dependancies?
seems I've backed myself into a corner. I've got 4.4-Release installed, and have cvsup'ed src-all into a /usr prefix. make buildworld completed successfully, but now I cannot continue without libc.so.5. Unfortuantely, I can't build libc 5 without the current kernel, and vise-versa. I get a core dump (assuming that's because of my kernel version) from make in the /usr/src directory when logged in as root. config bails after asking for libc.so.5. make kernel worked at one point, but the kernel didn't seem to actually install on /. suggesstions? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
