Re: Where is FreeBSD going?
On Thu, 08 Jan 2004 17:29:34 + Doug Rabson [EMAIL PROTECTED] wrote: The three main showstoppers for moving FreeBSD to subversion would be: [...] 2. Support for $FreeBSD$ - user-specified keywords are not supported and won't be until after svn-1.0 by the looks of things. subversion properties (svn propset) would allow you to do this in a satisfactory manner. -- +---+ | Samy Al Bahra | [EMAIL PROTECTED] | |---| | B3A7 F5BE B2AE 67B1 AC4B | | 0983 956D 1F4A AA54 47CB | |---| | http://www.kerneled.com | +---+ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Questions on intercepting execve syscall
Quoting Murat Balaban [EMAIL PROTECTED]: It might be that you have some bad address in the execve index of sysent array. This is likely. He could add a printf statement before calling the original execve just to be sure. See http://www.enderunix.org/murat/linux_subexec/linux_subexec.c for a simple example. This is 4.X specific (proc usage). I would just like to note that there is an execve symbol which you can reference in your code directly (rather than creating your own pointer for deinitialization). EX: -sysent[SYS_execve].sy_call = (sy_call_t *)oldexecve; +sysent[SYS_execve].sy_call = (sy_call_t *)execve; On Sun, Nov 16, 2003 at 07:53:30AM -0800, Kai Zhu wrote: [...] As you can see, I first just want to make sure that my_execve won't affect the original execve, then I will add some new logic in my_execve before returning to execve(). How exactly are you modifying the system call entry table? Are you modifying sysent even? -- +---+ | Samy Al Bahra | [EMAIL PROTECTED] | |---| | B3A7 F5BE B2AE 67B1 AC4B | | 0983 956D 1F4A AA54 47CB | |---| | http://www.kerneled.com | +---+ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: On-line judgment kernel module
On Thu, 16 Oct 2003 18:28:15 -0400 David Gilbert [EMAIL PROTECTED] wrote: As you conjecture, a syscall-less or syscall-restricted environment *should* be safe ... if your syscall changes are bulletproof *_and_* the rest of the runtime environment is bulletproof. Good system call policies are a WONDERFUL feature at a system administrator's hands. There is no such thing as a syscall-less environment but only a restricted (either at the same layer as the system calls or above in terms of code path). Isn't a syscall required to finish off exit()? Yes, consult kern_exit.c How is this related to the discussion though? The fact is, most people would not even want to TOUCH sys_exit and friends since there are no real security advantages there. In otherwords, an exit system call remains completely the same. -- +---+ | Samy Al Bahra | [EMAIL PROTECTED] | |---| | B3A7 F5BE B2AE 67B1 AC4B | | 0983 956D 1F4A AA54 47CB | |---| | http://www.kerneled.com | +---+ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: On-line judgment kernel module
On Thu, 9 Oct 2003 07:46:45 +0300 earthman [EMAIL PROTECTED] wrote: Now I'm thinking how to do this. Possibly it would be easy to point p-sv_sysent to the structure that points sv_prepsyscall to some function that denies some system calls. (kill process, make some record in module about restricted call That would work. If you prefer more granularity you may change individual sysent entries as well to point to your own functions/system calls. But I don't understand how to cancel syscall out of those function. Maybe it's possible to change code parameter to something else. You may return a value (from the system call) that designates an error. Please consult the errno man page for more information. -- +---+ | Samy Al Bahra | [EMAIL PROTECTED] | |---| | B3A7 F5BE B2AE 67B1 AC4B | | 0983 956D 1F4A AA54 47CB | |---| | http://www.kerneled.com | +---+ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Drawing graphics on terminal
If we adopt a dl-based framework for the installer, we can shrink it down pretty much to whatever size we want (and memory usage can be less. YaST, one of the most feature-packed installers out there (SuSE) takes up less RAM than sysinstall!). This also gives us the ability to have plugins across various floppies. - The project will never agree what is required of the installer, as everybody has their own agenda. Some see FBSD as a server OS that could do desktop, others want to push it forward as generic one-fits-all OS that's as good at desktop work as it is at server work. The installer needs to be able to mirror the user's wishes there and then. A plugin-based architecture will allow us to choose between various UIs (ncurses, QT, etc...). - Whether the installer is graphical or not is not the issue. Grey boxes on a blue background with yellow, red and black text is just plain ugly to a society that understands art and interior design. I know you're limited on pallet due to the restrictions of the console, but you can make sysinstall nicer just by changing the colour scheme. You can make it a hell of a lot nicer by making it consistent and functionally useful. Just as YaST, a libsysinstall can be provided to provide a standard UI API for applications to use + various UI plugins (ncurses, QT, GTK, Xaw, you name it) and configuration modules (users, network, ports, etc...). Though, before we all get excited about the possibilities of such an installer, what's happening with libh? Isn't it supposed to deal with all of sysintall's short-comings? All I see now is a lot of talk and no code, maybe such discussion should go to libh's mailing list (where we can talk design there)? - The KDE and Gnome stuff going on around FBSD, in my opinion, needs a helping hand or three so that when somebody installs KDE on FBSD, there is FBSD related stuff in the menus, FBSD themes, the whole lot, a la Redhat, Mandrake, and so on. This is not dumbing down. This is helping people who want to run a fancy window manager get the most out of their system. It helps advocacy. And besides, those guys could do with the help anyway, it's a lonely thankless job, and yet it has one of the biggest potential impacts on manager and/or investor perception. marcus@ is working on this for GNOME's case ATL. A new splash screen for GNOME2 will be there soon (bunch of backgrounds hopefully soon). I really do believe all interested artists should come and work together to finish off a whole FreeBSD art pack (for use by KDE and GNOME2). We should look around for them, maybe create a mailing list of some sort for them and get them to work together. -- +---+ | Samy Al Bahra | [EMAIL PROTECTED] | +---+ Arabeyes.org Kerneled.com FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Drawing graphics on terminal
and amen to anarcat's words :) -- +---+ | Samy Al Bahra | [EMAIL PROTECTED] | +---+ Arabeyes.org Kerneled.com FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Multimedia Keyboard (extra keys) on console
I suggest you take a look at the acme port. It may be found in ports/multimedia/acme. It provides an intuitive configuration interface for mapping certain keys to certain actions. If you don't find it of use in your scenario, the source code is always there. +---+ | Samy Al Bahra | [EMAIL PROTECTED] | +---+ Arabeyes.org Kerneled.com FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problem my mouse
This is not exactly a -hackers topic :) Could you provide us with more details? Do you have USB support compiled into your kernel? If not, do you have the appropriate modules (including ums) loaded? Have you researched your problem before taking it to the mailing list? +---+ | Samy Al Bahra | [EMAIL PROTECTED] | +---+ Arabeyes.org Kerneled.com FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP! Major commits in the tree coming soon
To all interested parties... THIS WHOLE THREAD IS GARBAGE, PLEASE DISREGARD IT. IT IS A HOAX STARTED BY A GOOD-FOR-NOTHING TROLL. THERE IS NO Thorsten Futrega IN -CORE AND THERE ARE NO PLANS A LONG THE LINES THAT HE LISTED ORIGINALLY. P.S. Troll: Stop, or atleast move this to -chat Thank you for your time... On Thu, 29 May 2003 20:22:50 +0100 (BST) Thorsten Futrega [EMAIL PROTECTED] wrote: --- Scott Long [EMAIL PROTECTED] wrote: Please go away. Scott, learn how to quote. Only Outlook users do top quoting. Then we'll talk about the myriad of crap patches you committed and I had to back out to reach minimal stability before code freeze. Thank you. Thorsten. __ Yahoo! Plus - For a better Internet experience http://uk.promotions.yahoo.com/yplus/yoffer.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
