Re: /dev files keep no permissions
Thanks Manolis, works perfect now! FreeBSD has the safest speaker access in the universe it seems. Even the speaker-beeping user should be member of a group to do so.. Cheers herb langhans > On Wed, Sep 23, 2009 at 09:44:12AM +0300, Manolis Kiagias wrote: > > herbs wrote: > > > Hi Daemons, > > > I wonder whats wrong there: > > > > > > I need to change the permissions from > > > /dev/speaker 600 to /dev/speaker 666 > > > --all works ok. > > > > > > Then I reboot the computer and the permissions of the file is back to 600. > > > > > > How to make it permanent? Is is normal that /dev files do what they > > > want? > > > > > > > > > > Yes :) > > The /dev filesystem is dynamic, it is recreated at every boot. For your > > setting to persist, enter it in /etc/devfs.conf > > > > The examples in there will help you out, although probably this is the > > line you need: > > > > perm speaker 0666 > > ___ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Booting ZFS and GPT
2009/9/22 krad > > > 2009/9/22 Anselm Strauss > > My next question is: Is it actually the plan to use ZFS as official root >> filesystem in FreeBSD, eventually replacing UFS? Is ZFS actually designed >> for that use? >> >> Anselm >> >> >> >> On Sep 17, 2009, at 22:25 , krad wrote: >> >> 2009/9/17 Anselm Strauss >>> Hi, >>> >>> I've read and tried out that FreeBSD is able to boot from ZFS directly, >>> also with GPT partitions, through zfsboot and gptzfsboot. When I tried the >>> last time 8-CURRENT it was however not built into the release CD. Will this >>> be included in the final release image? Is there any plan to include GPT and >>> ZFS setup in sysinstall during an initial installation? >>> >>> Cheers, >>> Anselm >>> ___ >>> freebsd-questions@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >>> To unsubscribe, send any mail to " >>> freebsd-questions-unsubscr...@freebsd.org" >>> >>> To big a rewrite needed i think. I've heard of plans to potentially >>> release a graphical installer based on pc-bsd, which will do all the bells >>> an whistles. Not sure what stage its at though. >>> >>> The biggest thing we need for the release is for the loader to be >>> compiled with zfs support in. It seems to have been in and out over the past >>> few months so i try to make sure i have my own version specially compiled >>> with it in. >>> >> >> > I dont think there are any specific plans at present, as its not deemed > stable enough. Its also a complete resource hog compared to ufs, so for the > foreseeable future I can't see it happening. > > One of the good things about freebsd is the range of hardware it supports. > If you made zfs the default option you would be making most hardware over a > few years old unusable without tinkering with the default options. > > However two or three years (ish) when the average new purchase its a 16 > core system with 16 GB ram, a few ssds and 10 TB of disk and the older > systems are the hi spec systems from today then there would be a good case > for it i guess. > > > Having said that look at the bottom right http://www.freebsdnews.net/wp-content/uploads/IMG_2907-large.jpg from http://www.freebsdnews.net/2009/09/22/freebsd-9-0-feature-requests/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Booting ZFS and GPT
2009/9/22 Anselm Strauss : > My next question is: Is it actually the plan to use ZFS as official root > filesystem in FreeBSD, eventually replacing UFS? Is ZFS actually designed > for that use? zfs works fine as root on opensolaris, though it took them a while to get there. Functionally, it should do as well on FreeBSD (and note that the "experimental" appellation was removed very recently, though it has been effectively "production ready" on 8.x for a while), though I'm certain that the rather large memory needs restrict its practical use to 64bit & multiple G of RAM: not your average netbook, by any means. I hope our developers see fit to make sysinstall zfs aware, but I hope we are not pushed (I know how to kick and my screams are deafening) into using it any time soon: ufs is wonderful for us ordinary computer users. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: LDAP server gone -> impossible to login locally!
Daniel O'Connor wrote: On Wed, 23 Sep 2009, Erik Norgaard wrote: This sounds like the correct solution, AFAIK it's the same concept as for NIS, first check local files, then ldap. You don't want your root credentials possibly be leaked accross the network. On the other hand you don't want or need user accounts in the local files. Default first check local files which is fast, then fall back on ldap if the user is not found. Actually I wrote them the wrong way, how odd! I actually have.. group: cache ldap files passwd: cache ldap files I had issues with the order 'files ldap' too, that's why I choosed 'ldap files'. I think that if it fails ldap, it does so very quickly - it certainly did this morning when I rebooted uncleanly. I believe I did try it as "cache files ldap" but I had some issues, I can't recall what they were though. I had quite a bit of difficulty getting it to work acceptably so when it did I left it alone :) On a related note, why is slapd so damn fragile? It's a righteous pain in the bum the way you have to run db_recover-X.Y /var/db/openldap-data if slapd fails to start. Yes, this is a lot of pain. I have had issues the same way and never figured out what the reason was. /var/ is very often corrupted after a crash, power failure or unclean reboot. Maybe not slpad is that fragile, but db47 is. It wouldn't be so bad if it logged anything, but even with full logging it gives a very cryptic message and if you have logging disabled (which is recommended for performance!) it won't say _anything_. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Booting ZFS and GPT
2009/9/23 ill...@gmail.com > 2009/9/22 Anselm Strauss : > > My next question is: Is it actually the plan to use ZFS as official root > > filesystem in FreeBSD, eventually replacing UFS? Is ZFS actually designed > > for that use? > > zfs works fine as root on opensolaris, though it > took them a while to get there. Functionally, it > should do as well on FreeBSD (and note that > the "experimental" appellation was removed > very recently, though it has been effectively > "production ready" on 8.x for a while), though > I'm certain that the rather large memory needs > restrict its practical use to 64bit & multiple G > of RAM: not your average netbook, by any > means. > > I hope our developers see fit to make sysinstall > zfs aware, but I hope we are not pushed (I know > how to kick and my screams are deafening) into > using it any time soon: ufs is wonderful for us > ordinary computer users. > > -- > -- > I have a pure zfs system at home and i works wonderfully its really nice to be able to do a make world, and roll back seamlessly if there is an issue ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: LDAP server gone -> impossible to login locally!
> > On a related note, why is slapd so damn fragile? It's a righteous pain > > in the bum the way you have to run db_recover-X.Y /var/db/openldap-data > > if slapd fails to start. > Yes, this is a lot of pain. I have had issues the same way and never > figured out what the reason was. /var/ is very often corrupted after a > crash, power failure or unclean reboot. Maybe not slpad is that fragile, > but db47 is. Last June, we had to shutdown our openldap server every night, I noticed that a simple halt(8) would leave the bdb backend database in a corrupted state. It worked well if I /usr/local/etc/rc.d/slapd stop and sync(8) a couple of type before I halt(8). After that I wrote a small script that would take a backup of the ldap data every 2 hours and keep 5 days of backup. It seems that Berkeley DB has a lot of options that need to be configured to be working optimally with openldap. Maybe soft-update should be desactivated from the filesystem where the db files reside. Bests, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: LDAP server gone -> impossible to login locally!
On Wed, 23 Sep 2009, O. Hartmann wrote: > Daniel O'Connor wrote: > > On Wed, 23 Sep 2009, Erik Norgaard wrote: > >> This sounds like the correct solution, AFAIK it's the same concept > >> as for NIS, first check local files, then ldap. You don't want > >> your root credentials possibly be leaked accross the network. On > >> the other hand you don't want or need user accounts in the local > >> files. > >> > >> Default first check local files which is fast, then fall back on > >> ldap if the user is not found. > > > > Actually I wrote them the wrong way, how odd! > > I actually have.. > > group: cache ldap files > > passwd: cache ldap files > > I had issues with the order > > 'files ldap' > > too, that's why I choosed 'ldap files'. Can you remember any details why? I can't :) > > On a related note, why is slapd so damn fragile? It's a righteous > > pain in the bum the way you have to run db_recover-X.Y > > /var/db/openldap-data if slapd fails to start. > > Yes, this is a lot of pain. I have had issues the same way and never > figured out what the reason was. /var/ is very often corrupted after > a crash, power failure or unclean reboot. Maybe not slpad is that > fragile, but db47 is. Yes, although openldap's handling of a bad DB is quite poor IMO.. That said I haven't had the nerve to look at the code. I had a quick look to see if there was a more robust looking backend but nothing jumped out at me. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
buildkernel error with device snd_hda
Hello, I get this error when I try to make buildkernel, with device snd_hda for my sound. When I load it as module in rc.conf it works fine, but I'd rather compile it in the kernel. [FreeBSD-7.2-stable] This is my error : hdac.o(.data+0x2e8): In function `hdac_audio_undo_trace': /usr/src/sys/dev/sound/pci/hda/hdac.c:5011: undefined reference to `pcm_devclass' *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC-ROYCS. *** Error code 1 And before that there is : > hdac.o(.data+0x200): In function `hdac_channel_setformat': > /usr/src/sys/dev/sound/pci/hda/hdac.c:3359: undefined reference to > `channel_init_desc' > hdac.o(.data+0x208):/usr/src/sys/dev/sound/pci/hda/hdac.c:3360: undefined > reference to `channel_setformat_desc' > hdac.o(.data+0x210):/usr/src/sys/dev/sound/pci/hda/hdac.c:3363: undefined > reference to `channel_setspeed_desc' > hdac.o(.data+0x218):/usr/src/sys/dev/sound/pci/hda/hdac.c:3364: undefined > reference to `channel_setblocksize_desc' > hdac.o(.data+0x220):/usr/src/sys/dev/sound/pci/hda/hdac.c:3364: undefined > reference to `channel_setfragments_desc' > hdac.o(.data+0x228):/usr/src/sys/dev/sound/pci/hda/hdac.c:3365: undefined > reference to `channel_trigger_desc' > hdac.o(.data+0x230):/usr/src/sys/dev/sound/pci/hda/hdac.c:3365: undefined > reference to `channel_getptr_desc' > hdac.o(.data+0x238):/usr/src/sys/dev/sound/pci/hda/hdac.c:3363: undefined > reference to `channel_getcaps_desc' > hdac.o(.data+0x2e8): In function `hdac_audio_undo_trace': Does anyone know what would solve this? Regards, Roy Stuivenberg. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: buildkernel error with device snd_hda
On Wed, Sep 23, 2009 at 01:56:57PM +0200, Roy Stuivenberg typed: > Hello, > > I get this error when I try to make buildkernel, with device snd_hda for > my sound. > When I load it as module in rc.conf it works fine, but I'd rather > compile it in the kernel. > [FreeBSD-7.2-stable] > > This is my error : > > hdac.o(.data+0x2e8): In function `hdac_audio_undo_trace': > /usr/src/sys/dev/sound/pci/hda/hdac.c:5011: undefined reference to > `pcm_devclass' Do you have "device sound" ? Ruben > *** Error code 1 > > Stop in /usr/obj/usr/src/sys/GENERIC-ROYCS. > *** Error code 1 > > And before that there is : > > > > hdac.o(.data+0x200): In function `hdac_channel_setformat': > > /usr/src/sys/dev/sound/pci/hda/hdac.c:3359: undefined reference to > > `channel_init_desc' > > hdac.o(.data+0x208):/usr/src/sys/dev/sound/pci/hda/hdac.c:3360: undefined > > reference to `channel_setformat_desc' > > hdac.o(.data+0x210):/usr/src/sys/dev/sound/pci/hda/hdac.c:3363: undefined > > reference to `channel_setspeed_desc' > > hdac.o(.data+0x218):/usr/src/sys/dev/sound/pci/hda/hdac.c:3364: undefined > > reference to `channel_setblocksize_desc' > > hdac.o(.data+0x220):/usr/src/sys/dev/sound/pci/hda/hdac.c:3364: undefined > > reference to `channel_setfragments_desc' > > hdac.o(.data+0x228):/usr/src/sys/dev/sound/pci/hda/hdac.c:3365: undefined > > reference to `channel_trigger_desc' > > hdac.o(.data+0x230):/usr/src/sys/dev/sound/pci/hda/hdac.c:3365: undefined > > reference to `channel_getptr_desc' > > hdac.o(.data+0x238):/usr/src/sys/dev/sound/pci/hda/hdac.c:3363: undefined > > reference to `channel_getcaps_desc' > > hdac.o(.data+0x2e8): In function `hdac_audio_undo_trace': > > Does anyone know what would solve this? > > > Regards, > > Roy Stuivenberg. > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
RE: Error linking MYKERNEL
Now I see new Error linking... How I can faind all dependenciesb e f o r kernel compyling ? Arkady Tokaev From: tok...@hotmail.com To: rfar...@predatorlabs.net Subject: RE: Error linking MYKERNEL Date: Mon, 21 Sep 2009 11:40:39 +0400 Great! Thank you for your prompt reply. So, there is task for future: Create validator of config file. Arkady Tokaev > Date: Sun, 20 Sep 2009 22:09:51 -0700 > Subject: Re: Error linking MYKERNEL > From: rfar...@predatorlabs.net > To: tok...@hotmail.com; questi...@freebsd.org > > 2009/9/20 Arkady Tokaev : > > > > After hours of > > # make buildkernel KERNCONF=MYKERNEL > > > > I see this: > > ... > > linking kernel.debug > > if_ural.o(.text+0x743): In function `ural_free_tx_list': > > /usr/src/sys/dev/usb/if_ural.c:627: undefined reference to > > `ieee80211_free_node' > > > > rum and ural are wireless cards, but you have the wlan options > commented out. You need to either remove them or add the wlan section > back. Устали отбиваться от вирусов? Воспользуйтесь встроенной защитой Internet Explorer 8 _ Устали отбиваться от вирусов? Воспользуйтесь встроенной защитой Internet Explorer 8 http://www.microsoft.ru/ie8___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Error linking MYKERNEL
On Wed, 23 Sep 2009 16:20:18 +0400, Arkady Tokaev wrote: > > Now I see new Error linking... > How I can faind all dependenciesb e f o r kernel compyling ? Traditionally from the documentation. Template and example files such as GENERIC, NOTES and LINT do contain comments for the various drivers, for example "requires so and so". -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: zyd & TEW-424UB
Albert Shih wrote: So I just buy a Trendnet TEW-424UB wifi usb adapter. I find this in the man zyd but when I plug my adapter (after add if_zyd_load="YES" in my loader.conf and reboot) it's not working. According to http://linux-wless.passys.nl/query_part.php?brandname=TRENDware , there are two revisions of that device with totally different chipsets. Unfortunately, that is pretty common for wireless devices with only a few companies being exceptions. BTW: If you want to get a zyd device, be sure to get a ZD1211B version (see the source for hints which ones are). I had a ZD1211 (without B) that happened to cause kernel panics under load on FreeBSD 7. From my experience, ural or rum devices are stable. (I know nothing about uath, upgt, and urtw.) If you have that choice, cardbus or PCI tend to be better than USB, especially ath devices work well. Cheers, Jan Henrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
some issues with 9-CURRENT
hi there, i've stumbled over some issues running 9-CURRENT i386 (r197427) and would like to ask if these are in fact problems/bugs or the way things are meant to work. isssue 1: when booting into single user mode / (dev/label/rootfs) gets mounted read-only. when doing `fsck /dev/label/rootfs` problems can be solved because fsck has write access to the drive due to it being mounted read-only. however if i do `mount -r -o noatime /dev/label/usr /usr` and run `fsck /dev/label/usr` fsck isn't able to gain write access. issue 2: after issueing the following commands in single user mode: `mount -r -o noatime /dev/label/rootfs /usr` `umount /usr` `cd /usr && ls` i got the following panic: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xdeadc112 fault code = supervisor read, page not present instruction pointer = 0x20:0xc05c4301 stack pointer = 0x28:0xe7e2f82c frame pointer = 0x28:0xe7e2f854 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 = 29 (ls) panic: from debugger cpuid = 0 KDB: stack backtrace: Uptime: 1m44s Physical memory: 2034 MB Dumping 74 MB: 59 43 27 11 #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:245 #1 0xc063dc47 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:416 #2 0xc063e06c in panic (fmt=Could not find the frame base for "panic". ) at /usr/src/sys/kern/kern_shutdown.c:579 #3 0xc046e537 in db_panic (addr=Could not find the frame base for "db_panic". ) at /usr/src/sys/ddb/db_command.c:478 #4 0xc046e474 in db_command (last_cmdp=0xc093c5bc, cmd_table=0x0, dopager=1) at /usr/src/sys/ddb/db_command.c:445 #5 0xc046e5a8 in db_command_loop () at /usr/src/sys/ddb/db_command.c:498 #6 0xc0470db2 in db_trap (type=12, code=0) at /usr/src/sys/ddb/db_main.c:229 #7 0xc067583e in kdb_trap (type=12, code=0, tf=0xe7e2f7ec) at /usr/src/sys/kern/subr_kdb.c:535 #8 0xc084787f in trap_fatal (frame=0xe7e2f7ec, eva=3735929106) at /usr/src/sys/i386/i386/trap.c:929 #9 0xc0847468 in trap_pfault (frame=0xe7e2f7ec, usermode=0, eva=3735929106) at /usr/src/sys/i386/i386/trap.c:851 #10 0xc0846e2a in trap (frame=0xe7e2f7ec) at /usr/src/sys/i386/i386/trap.c:533 #11 0xc0821d8b in calltrap () at /usr/src/sys/i386/i386/exception.s:165 #12 0xc05c4301 in g_io_request (bp=0xc7e25688, cp=0xc7e2b780) at /usr/src/sys/geom/geom_io.c:425 #13 0xc05cb165 in g_vfs_strategy (bo=0xc7b37a5c, bp=0xd94eaa54) at /usr/src/sys/geom/geom_vfs.c:130 #14 0xc07c4516 in ffs_geom_strategy (bo=0xc7b37a5c, bp=0xd94eaa54) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:1954 #15 0xc07d731a in ufs_strategy (ap=0xe7e2f910) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2040 #16 0xc0858c78 in VOP_STRATEGY_APV (vop=0xc09249e0, a=0xe7e2f910) at vnode_if.c:2171 #17 0xc06d706e in VOP_STRATEGY (vp=0xc7b376b8, bp=0xd94eaa54) at vnode_if.h:940 #18 0xc06d6fff in bufstrategy (bo=0xc7b377ac, bp=0xd94eaa54) at /usr/src/sys/kern/vfs_bio.c:3926 #19 0xc06cff97 in bstrategy (bp=0xd94eaa54) at buf.h:397 #20 0xc06d00b5 in breadn (vp=0xc7b376b8, blkno=0, size=2048, rablkno=0x0, rabsize=0x0, cnt=0, cred=0x0, bpp=0xe7e2fa7c) at /usr/src/sys/kern/vfs_bio.c:813 #21 0xc06cfd4c in bread (vp=0xc7b376b8, blkno=0, size=2048, cred=0x0, bpp=0xe7e2fa7c) at /usr/src/sys/kern/vfs_bio.c:748 #22 0xc07c5449 in ffs_read (ap=0xe7e2fac4) at /usr/src/sys/ufs/ffs/ffs_vnops.c:526 #23 0xc0856a34 in VOP_READ_APV (vop=0xc09244e0, a=0xe7e2fac4) at vnode_if.c:887 #24 0xc07d70ea in VOP_READ (vp=0xc7b376b8, uio=0xe7e2fbf4, ioflag=0, cred=0xc7558480) at vnode_if.h:384 #25 0xc07d6da1 in ufs_readdir (ap=0xe7e2fbb4) at /usr/src/sys/ufs/ufs/ufs_vnops.c:1903 #26 0xc0858224 in VOP_READDIR_APV (vop=0xc09249e0, a=0xe7e2fbb4) at vnode_if.c:1737 #27 0xc06fdfe6 in VOP_READDIR (vp=0xc7b376b8, uio=0xe7e2fbf4, cred=0xc7558480, eofflag=0xe7e2fc28, ncookies=0x0, cookies=0x0) at vnode_if.h:758 #28 0xc06fde0b in kern_getdirentries (td=0xc7eff690, fd=5, buf=0x28218000 , count=4096, basep=0xe7e2fc64) at /usr/src/sys/kern/vfs_syscalls.c:4103 #29 0xc06fdbf6 in getdirentries (td=0xc7eff690, uap=0xe7e2fce8) at /usr/src/sys/kern/vfs_syscalls.c:4051 #30 0xc0847d06 in syscall (frame=0xe7e2fd38) at /usr/src/sys/i386/i386/trap.c:1078 #31 0xc0821df0 in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:261 #32 0x0033 in ?? () Previous frame inner to this frame (corrupt stack?) issue 3: is it normal that fsck in background mode is ~ 400 % slower than in foreground mode? running fsck in single user mode takes ~ 4 minutes. if however the fs is marked dirty and get's fsck'ed in the background running multi user mode fsck'ing takes ~ 20 minutes. this is of course without any hdd or cpu intensive apps running. thx for reading. alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubs
Re: /dev files keep no permissions
On Wed, Sep 23, 2009 at 09:44:12AM +0300, Manolis Kiagias wrote: > herbs wrote: > > Hi Daemons, > > I wonder whats wrong there: > > > > I need to change the permissions from > > /dev/speaker 600 to /dev/speaker 666 > > --all works ok. > > > > Then I reboot the computer and the permissions of the file is back to 600. > > > > How to make it permanent? Is is normal that /dev files do what they > > want? > > Yes :) > The /dev filesystem is dynamic, it is recreated at every boot. For your > setting to persist, enter it in /etc/devfs.conf > > The examples in there will help you out, although probably this is the > line you need: > > perm speaker 0666 One important caveat; /etc/devfs.conf works only for devices that are available at boot time. For devices that are created during runtime, like e.g. usb devices, you have to use /etc/devfs.rules instead. The format of both files is explained in their respective manual pages. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpH8n4GvoGd6.pgp Description: PGP signature
Re: zyd & TEW-424UB
Le 23/09/2009 à 15:22:30+0200, Jan Henrik Sylvester a écrit > > According to > http://linux-wless.passys.nl/query_part.php?brandname=TRENDware , there > are two revisions of that device with totally different chipsets. F**ck.20 bucks in trash > > Unfortunately, that is pretty common for wireless devices with only a > few companies being exceptions. Yes I known... > BTW: If you want to get a zyd device, be sure to get a ZD1211B version > (see the source for hints which ones are). I had a ZD1211 (without B) > that happened to cause kernel panics under load on FreeBSD 7. From my > experience, ural or rum devices are stable. (I know nothing about uath, > upgt, and urtw.) If you have that choice, cardbus or PCI tend to be > better than USB, especially ath devices work well. Yes I known but my laptop don't have carbus or PCIjust USB... Thanks for your help. I'm need to buy another . :-( :-( Regards. -- Albert SHIH SIO batiment 15 Observatoire de Paris Meudon 5 Place Jules Janssen 92195 Meudon Cedex Téléphone : 01 45 07 76 26/06 86 69 95 71 Heure local/Local time: Mer 23 sep 2009 20:02:14 CEST ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
tap dhcp
Am I doing something wrong here? kldload if_tap if_bridge sysctl net.link.tap.user_open=1 ifconfig tap0 create ifconfig bridge create ifconfig bridge0 addm tap0 addm em0 it# dhclient tap0 DHCPDISCOVER on tap0 to 255.255.255.255 port 67 interval 6 DHCPDISCOVER on tap0 to 255.255.255.255 port 67 interval 6 DHCPDISCOVER on tap0 to 255.255.255.255 port 67 interval 13 DHCPDISCOVER on tap0 to 255.255.255.255 port 67 interval 18 DHCPDISCOVER on tap0 to 255.255.255.255 port 67 interval 18 No DHCPOFFERS received. No working leases in persistent database - sleeping. Although dhclient em0 works as expected. FreeBSD it.digitecinc.net 8.0-BETA4 FreeBSD 8.0-BETA4 #2: Mon Sep 7 11:26:25 CDT 2009 vandemo...@it.digitecinc.net:/usr/obj/usr/src/sys/GENERIC i386 -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
IPFW with NAT
Hello, I am trying to add a second firewall/NAT to my network for the purpose of using NAT's address redirection to point to my webserver behind the firewall. So far I have a fresh install of FreeBSD and have recompiled the kernel with IPDIVERT and IPFIREWALL but NAT will not forward to my webserver, it will only forward to my development server. I'm not sure how this could be. I'm sure it's not an issue with the webserver because I already have an existing firewall with NAT that is functioning in a similar way. Can anyone offer any advice on why I am seeing this behavior? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
IPFW with NAT
Hello, I ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: some issues with 9-CURRENT
On Wed, 23 Sep 2009 17:02:24 +0200 (CEST), Alexander Best wrote: > however if i do `mount -r -o noatime /dev/label/usr /usr` and run `fsck > /dev/label/usr` fsck isn't able to gain write access. The fsck program should - as far as I know - only be used on unmounted (!) file systems. In order to perform fsck with the ability of file system modifications, umount the file system and run fsck (maybe with options you desire) again. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: some issues with 9-CURRENT
Polytropon schrieb am 2009-09-23: > On Wed, 23 Sep 2009 17:02:24 +0200 (CEST), Alexander Best > wrote: > > however if i do `mount -r -o noatime /dev/label/usr /usr` and run > > `fsck > > /dev/label/usr` fsck isn't able to gain write access. > The fsck program should - as far as I know - only be used on > unmounted (!) file systems. In order to perform fsck with the > ability of file system modifications, umount the file system > and run fsck (maybe with options you desire) again. thx. i thought since / gets mounted read-only and fsck is able to check it with write access this would apply to read-only mountpoints in general. alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: some issues with 9-CURRENT
On Wed, 23 Sep 2009 23:20:22 +0200 (CEST), Alexander Best wrote: > thx. i thought since / gets mounted read-only and fsck is able to check it > with write access this would apply to read-only mountpoints in general. Because fsck resides in /sbin, it is required - in SUM - that / is mounted and accessible for program execution. The best solution is to mount it ro (-r) to get minimal "interference", but generally, only unmounted partitions should be fscked. The / partition is an excelion due to a neccessary evil. :-) (If you're running fsck from a live system CD, you usually don't mount anything. Running fsck on rw-mounted partitions can cause damage to the file systems and should be avoided.) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
panic: Journal overflow
Hello, I've got a 7.2-RELEASE (i386) box that has recently experienced several panics when writing to a gjournaled partition. On this particular partition, the journal device is "mixed" in with the data provider. In both cases, I was trying to copy a 19GB file from an external USB device (da1p16.journal) to the filesystem on a 3Ware RAID-10 (da7p0.journal). This afternoon I saw... panic: Journal overflow (joffset=xxx active= inactive=zz) cpuid = 1 Uptime: Physical memory: 1011 MB Dumping 351MB Fatal trap 12: page fault while in kernel mode cpuid = 0, apic id = 00 fault virtual address= 0xea60 fault code = supervisor write, page not present instructor pointer = 0x20: 0xc04715b6 stack pointer= 0x28: 0xe6ab0320 frame pointer= 0x28: 0xe6ab03bc code segment = base 0x0, limit 0xf, type 0x1b DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, 10PL = 0 current process = 48 (gjournal da0p7) trap number = 12 Does this mean my journal is not big enough for the amount of data I'm trying to push through? Any suggestions on how to resolve this? I can provide "a lot" more data if necessary. Thanks for your help! -- Regards, Doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: panic: Journal overflow
On Wed, Sep 23, 2009 at 6:35 PM, Doug Poland wrote: > Hello, > > I've got a 7.2-RELEASE (i386) box that has recently experienced > several panics when writing to a gjournaled partition. On this > particular partition, the journal device is "mixed" in with the data > provider. In both cases, I was trying to copy a 19GB file from an > external USB device (da1p16.journal) to the filesystem on a 3Ware > RAID-10 (da7p0.journal). > > This afternoon I saw... > > panic: Journal overflow (joffset=xxx active= > inactive=zz) > cpuid = 1 > Uptime: > Physical memory: 1011 MB > Dumping 351MB > > Fatal trap 12: page fault while in kernel mode > cpuid = 0, apic id = 00 > fault virtual address= 0xea60 > fault code = supervisor write, page not present > instructor pointer = 0x20: 0xc04715b6 > stack pointer= 0x28: 0xe6ab0320 > frame pointer= 0x28: 0xe6ab03bc > code segment = base 0x0, limit 0xf, type 0x1b > DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, 10PL = 0 > current process = 48 (gjournal da0p7) > trap number = 12 > > Does this mean my journal is not big enough for the amount of data I'm > trying to push through? No, it's kinda like the journal is a is a buffer and you overflowed it. You can address this by two methods: 1) slow the rate of transfer 2) make a bigger journal > Any suggestions on how to resolve this? > http://www.freebsd.org/doc/en_US.ISO8859-1/articles/gjournal-desktop/understanding-journaling.html > > I can provide "a lot" more data if necessary. Thanks for your help! > > -- > Regards, > Doug > -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
