Re: possible NIS/ACL bug?
On 03 Nov 2003, Robert Watson wrote: revision 1.11 date: 2003/07/24 23:33:25; author: rwatson; state: Exp; lines: +3 -2 Print group name in getfacl output when calculating an effective permission set based on a more restrictive mask. Duh. I need to add cvsweb to my list of things to check first. I just had to update yppasswdd_server.c from cvs for similar reasons. Thanks for pointing this out! :) -- Mark Nippere-contacts: Computing and Information Services [EMAIL PROTECTED] Texas AM Universityhttp://ops.tamu.edu/nipsy/ College Station, TX 77843-3142 AIM/Yahoo: texasnipsy ICQ: 66971617 (979)575-3193 MSN: [EMAIL PROTECTED] -BEGIN GEEK CODE BLOCK- GG/IT d- s++:+ a- C++$ UBL+++$ P---+++ L+++$ E--- W++ N+ o K++ w(---) O++ M V(--) PS+++(+) PE(--) Y+ PGP++(+) t 5 X R tv b+++ DI+(++) D+ G e h r++ y+(**) --END GEEK CODE BLOCK-- ---begin random quote of the moment--- There are 10 kinds of people in the world; those who know binary and those who don't. end random quote of the moment ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
possible NIS/ACL bug?
I think I might have found a bug in ACL's under UFS2 with 5.1-RELEASE-p10. I have been using ACL's successfully for awhile now, but I'd never played with default ACL's for directories and files you create underneath said directories until I came across the daemon news article at: --- http://ezine.daemonnews.org/200310/acl.html Anyway, while playing and following the examples, I think I may have found a bug in ACL's when using NIS maps. Here's my example (extra newline between prompts): --- [EMAIL PROTECTED]/p0:~/test getfacl .. | setfacl -M - . [EMAIL PROTECTED]/p0:~/test getfacl . #file:. #owner:1019 #group:1019 user::rwx group::r-x group:nes:r-x group:loki:r-x mask::r-x other::r-x [EMAIL PROTECTED]/p0:~/test getfacl .. | setfacl -dM - . [EMAIL PROTECTED]/p0:~/test getfacl -d . #file:. #owner:1019 #group:1019 user::rwx group::r-x group:nes:r-x group:loki:r-x mask::r-x other::r-x [EMAIL PROTECTED]/p0:~/test touch something [EMAIL PROTECTED]/p0:~/test getfacl something #file:something #owner:1019 #group:1019 user::rw- group::r-x # effective: r-- group::r-x # effective: r-- group::r-x # effective: r-- mask::r-- other::r-- --- Uh oh! It's that last part where there are the two extra entries for the two ACL added groups, but no GID seems to have been stored with each entry, whereas the example in the daemon news article does actually show GID's in these places. So I assume this is an NIS/ACL bug of some kind? Both my uid and gid as well as both the gid's above (nes and loki) are mapped via NIS. If anyone needs me to do anything else, let me know. I don't feel nearly competent enough to start debugging the source for get/setfacl to try to grok any of this. :) -- Mark Nippere-contacts: Computing and Information Services [EMAIL PROTECTED] Texas AM Universityhttp://ops.tamu.edu/nipsy/ College Station, TX 77843-3142 AIM/Yahoo: texasnipsy ICQ: 66971617 (979)575-3193 MSN: [EMAIL PROTECTED] -BEGIN GEEK CODE BLOCK- GG/IT d- s++:+ a- C++$ UBL+++$ P---+++ L+++$ E--- W++ N+ o K++ w(---) O++ M V(--) PS+++(+) PE(--) Y+ PGP++(+) t 5 X R tv b+++ DI+(++) D+ G e h r++ y+(**) --END GEEK CODE BLOCK-- ---begin random quote of the moment--- Well, if we told you how we did it, then it very well wouldn't be unbreakable, would it? You need to trust us with your data. These are not the backdoors you are looking for. -- random /. quote end random quote of the moment ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: possible NIS/ACL bug?
On 03 Nov 2003, Mark Nipper wrote: Uh oh! It's that last part where there are the two extra entries for the two ACL added groups, but no GID seems to have been stored with each entry, whereas the example in the daemon news article does actually show GID's in these places. Of course, looking at the example right after I sent the message, I see that the file inherited default UID's from the directory, not GID's, but blah, I assume it should still work the same either way? Or maybe it's a feature and not a bug. :) -- Mark Nippere-contacts: Computing and Information Services [EMAIL PROTECTED] Texas AM Universityhttp://ops.tamu.edu/nipsy/ College Station, TX 77843-3142 AIM/Yahoo: texasnipsy ICQ: 66971617 (979)575-3193 MSN: [EMAIL PROTECTED] -BEGIN GEEK CODE BLOCK- GG/IT d- s++:+ a- C++$ UBL+++$ P---+++ L+++$ E--- W++ N+ o K++ w(---) O++ M V(--) PS+++(+) PE(--) Y+ PGP++(+) t 5 X R tv b+++ DI+(++) D+ G e h r++ y+(**) --END GEEK CODE BLOCK-- ---begin random quote of the moment--- If you're not part of the solution, you're part of the precipitate. end random quote of the moment ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sysinstall's fdisk/disklabel should be improved
On 28 Oct 2003, David O'Brien wrote: It is NOT useless. Why do you think it is? Perhaps you don't relize that some BIOS's wont boot from a hard disk that isn't partitioned to agree with the specifications of the PeeCee. If you want to treat your PC as a Sun, don't -- buy a Sun, FreeBSD runs on that too. This is true. And while I disagree with some of the initial complaints, I do think that fdisk/disklabel in sysinstall need to be improved upon. They do not handle multi-terabyte disk arrays properly at all (unless something has changed since 5.1-RELEASE) and as array sizes increase, it seems like this would be an issue to address lest people think that FreeBSD is not geared toward middle range server duties, which it most obviously handles exceptionally well. :) Having said that, I had to reflect a few seconds myself to figure out how to actually tell fdisk to go into dangerously dedicated mode, but it wasn't entirely impossible. It just wasn't entirely intuitive (although at the moment I cannot imagine why it wouldn't have been!). It's been awhile since I used it admittedly. If you want truly user unfriendly, try using fdisk/disklabel post installation, which both DO handle large slice/partition sizes properly, and through which I finally realized my 1638492118Kb RAID-5 partition. :) -- Mark Nippere-contacts: Computing and Information Services [EMAIL PROTECTED] Texas AM Universityhttp://ops.tamu.edu/nipsy/ College Station, TX 77843-3142 AIM/Yahoo: texasnipsy ICQ: 66971617 (979)575-3193 MSN: [EMAIL PROTECTED] -BEGIN GEEK CODE BLOCK- GG/IT d- s++:+ a- C++$ UBL+++$ P---+++ L+++$ E--- W++ N+ o K++ w(---) O++ M V(--) PS+++(+) PE(--) Y+ PGP++(+) t 5 X R tv b+++ DI+(++) D+ G e h r++ y+(**) --END GEEK CODE BLOCK-- ---begin random quote of the moment--- If the fool would persist in his folly he would become wise. -- one of the Proverbs of Hell from William Blake's _The Marraige of Heaven and Hell_, 1789-1790 end random quote of the moment ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Postfix locks 5.1-servers?
On 29 Oct 2003, Niklas Saers Mailinglistaccount wrote: are anyone familiar with conditions where postfix may bring a 5.1-p10 server to a halt, making the server accept incoming ports (such as 22) but serve nothing, making getty(8) become non-respondent (pressing enter doesn't give any feedback) and making the server ignore ctrl-alt-del etc? I've only been running 5.1-RELEASE-p10 for a couple of days now with postfix-2.0.14-20030812,1, but so far no lock ups. I'll certainly keep an eye out for it though! :) Maybe it's the Java process... ;) -- Mark Nippere-contacts: Computing and Information Services [EMAIL PROTECTED] Texas AM Universityhttp://ops.tamu.edu/nipsy/ College Station, TX 77843-3142 AIM/Yahoo: texasnipsy ICQ: 66971617 (979)575-3193 MSN: [EMAIL PROTECTED] -BEGIN GEEK CODE BLOCK- GG/IT d- s++:+ a- C++$ UBL+++$ P---+++ L+++$ E--- W++ N+ o K++ w(---) O++ M V(--) PS+++(+) PE(--) Y+ PGP++(+) t 5 X R tv b+++ DI+(++) D+ G e h r++ y+(**) --END GEEK CODE BLOCK-- ---begin random quote of the moment--- In theory there is no difference between theory and practice. In practice there is. end random quote of the moment ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sysinstall's fdisk/disklabel should be improved
On 29 Oct 2003, Garrett Wollman wrote: On Wed, 29 Oct 2003 08:12:17 -0600, Mark Nipper [EMAIL PROTECTED] said: initial complaints, I do think that fdisk/disklabel in sysinstall need to be improved upon. They do not handle multi-terabyte disk arrays properly at all You should probably use GPT on multi-terabyte disk arrays. At first, I didn't even know what you were saying. :) Then, I remember seeing something about this when I was having my problems, and upon refreshing my memory a second ago, I'm now on the same page! :) But, I don't know too much about the new partitioning scheme you mention (GUID Partition Table, right?), especially with regards to the normal PC BIOS actually recognizing it, etc. I assume you could just use the MBR and do whatever you want with the rest of the drive. Anyway, do you you know of any good links describing the reasons to use it and generally how to use it as well as compatibility issues? I see a few things on google about patches and the like, but know real thorough description of all of this, even just under FreeBSD. -- Mark Nippere-contacts: Computing and Information Services [EMAIL PROTECTED] Texas AM Universityhttp://ops.tamu.edu/nipsy/ College Station, TX 77843-3142 AIM/Yahoo: texasnipsy ICQ: 66971617 (979)575-3193 MSN: [EMAIL PROTECTED] -BEGIN GEEK CODE BLOCK- GG/IT d- s++:+ a- C++$ UBL+++$ P---+++ L+++$ E--- W++ N+ o K++ w(---) O++ M V(--) PS+++(+) PE(--) Y+ PGP++(+) t 5 X R tv b+++ DI+(++) D+ G e h r++ y+(**) --END GEEK CODE BLOCK-- ---begin random quote of the moment--- Whose woods these are I think I know. His house is in the village though; He will not see me stopping here To watch his woods fill up with snow. My little horse must think it queer To stop without a farmhouse near Between the woods and frozen lake The darkest evening of the year. He gives his harness bells a shake To ask if there is some mistake. The only other sound's the sweep Of easy wind and downy flake. The woods are lovely, dark and deep. But I have promises to keep, And miles to go before I sleep, And miles to go before I sleep. -- Robert Frost, _New Hampshire: A Poem with Notes and Grace Notes_, 1923 end random quote of the moment ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI on Tyan Motherboard
On 19 Aug 2003, Stephen Montgomery-Smith wrote: Alexander Leidinger wrote: Stephen Montgomery-Smith schrieb: Actually the power-off button doesn't work at all under FreeBSD-current. (It is a soft power-off button that dmesg shows is detected by the OS.) Have you tried to hold the power-button a little bit longer? My power-button turn the system off when I pres it for ~4secs (but I haven't a Tyan board). I tried pressing the power button for a longer time. It does actually do something. After about 4 seconds, it has the same effect as shutdown -p now or halt -p, that is, the video card stops working, the fans keep going, and the disk access light comes fully on. I am guessing that this 4 second delay is part of how FreeBSD wants it. If that is the case, it shows that the power button is working as it should - it is the power-down process that is not working right. For what it's worth, I have a Tyan S2469GN with dual Athlon MP's in it in a 3U rack mounted case. The power button acts as any other ATX soft power button I've ever seen, which is to say, it does nothing unless I hold it down for four seconds, at which point, all power is cut to the machine and it is officially off at this point. This is regardless of the state of the OS. --- From dmesg: --- acpi0: power button is handled as a fixed feature programming model. and sysctl: --- hw.acpi.power_button_state: S5 hw.acpi.disable_on_poweroff: 1 I'm running 5-CURRENT from a few days ago... -- Mark Nippere-contacts: Computing and Information Services [EMAIL PROTECTED] Texas AM Universityhttp://ops.tamu.edu/nipsy/ College Station, TX 77843-3142 AIM/Yahoo: texasnipsy ICQ: 66971617 (979)575-3193 MSN: [EMAIL PROTECTED] -BEGIN GEEK CODE BLOCK- GG/IT d- s++:+ a-- C++$ UBL+++$ P---+++ L+++$ E--- W++ N+ o K++ w(---) O++ M V(--) PS+++(+) PE(--) Y+ PGP++(+) t 5 X R tv b+++ DI+(++) D+ G e h r++ y+(**) --END GEEK CODE BLOCK-- ---begin random quote of the moment--- Well, I too worry for all young lovers. The darkness is not the light, my child, and there are lights. You are one of the lights, dear Mina, the light of all light. -- Professor Abraham van Helsing, Bram Stoker's Dracula, 1992 end random quote of the moment ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
twe driver, 1+ terabyte array, fdisk and disklabel
So I'm having some problems with 5.1-RELEASE. I'm not sure if these have already been addressed but as I have found no mention of any of these problems on the mailing lists (web searchable anyway) or deja and google, I've subscribed myself to current and am looking for possible answers. :) I have a 3ware 7500-8. I also have 8 Western Digital Special Edition 250GB drives attached to said RAID card. I currently have one RAID-5 array configured for a total of 1.75T. There seem to be no real issues on the hardware side of this equation. I just grabbed the 5.1-RELEASE ISO and tried to install. No dice, although I have had mixed results. The disk geometry as reported (guessed actually, as it tells me the geometry reported by BIOS is obviously wrong and continues to remind me it's guessing every single time I move lines) in fdisk is 212808/255/63, for a grand total of 3418760520 sectors (again, as reported by fdisk). If I, at this point, say use entire disk it gives me roughly: --- offset size(st) endnameftype descsubtype flags 0 63 62 - 12unused 0 63 3418760457 3418760519 twed0s1 8 freebsd 165 -876206776 4536 3418765055 - 12unused 0 Obvious problems there. And also, why do there appear to be more sectors listed here than in the sectors reported at the top of the screen (3418765055 versus 3418760520)? And the negative offset. Riiight... :) So then I try to do dangerously dedicated mode. I eventually give up on the CLI and switch to wizard mode. I'm finally able to make it dedicated. So now I have: --- offset size(st) endnameftype descsubtype flags 0 3418765056 3418765055 twed0s1 8 freebsd 165 Yay. Now on to disklabel, right? Well, at this point, regardless of whether my fdisk looks like example 1 above or example 2, I get this in disklabel: --- Fatal Error: Partitions are larger than actual chunk?? - PRESS ANY KEY TO REBOOT Haha. There are only two ways I've found to make this work so far, and I'm not happy with either really. One is simple. Use RAID-10, and my disk array drops to 1T. Fast, but not what I'm looking for. The second is to use create slice in fdisk, and it puts the default number of 3.4 billion sectors in the field for the size of the slice I want to create. When I hit enter, it actually only ends up using 2 billion some odd sectors, and then I can create a second slice of the remaining drive. At that point, disklabel at least runs without dying right away, but then I have an approximately 1T slice followed by a 600 something gigabyte slice. Again, not what I'm looking for. Any advice? Are the disk tools just not 64 bit clean or something? Or is this a kernel, device driver or fs layer problem? -- Mark Nippere-contacts: Computing and Information Services [EMAIL PROTECTED] Texas AM Universityhttp://ops.tamu.edu/nipsy/ College Station, TX 77843-3142 AIM/Yahoo: texasnipsy ICQ: 66971617 (979)575-3193 MSN: [EMAIL PROTECTED] -BEGIN GEEK CODE BLOCK- GG/IT d- s++:+ a-- C++$ UBL+++$ P---+++ L+++$ E--- W++ N+ o K++ w(---) O++ M V(--) PS+++(+) PE(--) Y+ PGP++(+) t 5 X R tv b+++ DI+(++) D+ G e h r++ y+(**) --END GEEK CODE BLOCK-- ---begin random quote of the moment--- This sentence no verb. end random quote of the moment ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: twe driver, 1+ terabyte array, fdisk and disklabel
On 13 Aug 2003, Brooks Davis wrote: My workaround was to split the array into a 2 disk RAID1 and a 6 disk RAID5. Sysinstall will install on the small mirror and then you can use the RAID5 array raw. On some other systems, I'm not going to be booting from the arrays so I'll use the entire array as a large RAID5 volume without any partions. Duh. I should have thought of something along these lines. I just left my 1.75GB RAID-5 array in place and only took a few gigabytes out of it for slice 1. Then I installed everything into that for the base system. Worked like a charm. Next I went ahead post installation and did cvsup and used fdisk and disklabel (outside sysinstall of course) to create the current, ridiculous slice and partition. Yay. :) --- /dev/twed0s2a 1.5T 2.0K 1.5T 0%/data Which reminds me, any chance of putting in more useful information to fdisk and disklabel from the command line? I had to fire up sysinstall just to figure out all the sector boundaries and sizes. What a pain! :) Anyway, thanks for the feedback. My brain was elsewhere. -- Mark Nippere-contacts: Computing and Information Services [EMAIL PROTECTED] Texas AM Universityhttp://ops.tamu.edu/nipsy/ College Station, TX 77843-3142 AIM/Yahoo: texasnipsy ICQ: 66971617 (979)575-3193 MSN: [EMAIL PROTECTED] -BEGIN GEEK CODE BLOCK- GG/IT d- s++:+ a-- C++$ UBL+++$ P---+++ L+++$ E--- W++ N+ o K++ w(---) O++ M V(--) PS+++(+) PE(--) Y+ PGP++(+) t 5 X R tv b+++ DI+(++) D+ G e h r++ y+(**) --END GEEK CODE BLOCK-- ---begin random quote of the moment--- Do you believe in destiny, that even the powers of time can be ordered to a single purpose? The luckiest man who walks this earth is the one who finds true love. -- Dracula, Bram Stoker's Dracula, 1992 end random quote of the moment ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
