Re: Screen Resolution

rusel a écrit : show error log there is no erreor log, I've a display in 640*480 I just can't increase the resolution :-) hervé On 5/31/05, Joerg Sonnenberger <[EMAIL PROTECTED]> wrote: On Tue, May 31, 2005 at 07:00:58AM +0100, Rob MacGregor wrote: So have I (in fact that's how

Re: Screen Resolution

Joerg Sonnenberger a écrit : On Tue, May 31, 2005 at 09:56:37AM +0200, Hervé Kergourlay wrote: Joerg Sonnenberger a écrit : Doesn't the vmware driver shipped with Xorg work? only in 640*480 which is very small (a) check monitor config (it must support something above 640

Re: Screen Resolution

Makoto Matsushita a écrit : So have I (in fact that's how I started using FreeBSD 5.0). However the drivers required for their emulated graphics card are only supplied for FreeBSD 4.x with VMWare 4.5. You can use graphic driver modules (${X11}/lib/modules/drivers/vmware_drv.o) that is bun

Re: Screen Resolution

Joerg Sonnenberger a écrit : On Tue, May 31, 2005 at 07:00:58AM +0100, Rob MacGregor wrote: So have I (in fact that's how I started using FreeBSD 5.0). However the drivers required for their emulated graphics card are only supplied for FreeBSD 4.x with VMWare 4.5. Doesn't the vmware

Re: Screen Resolution

Rob MacGregor a écrit : On Monday, May 30, 2005 7:58 PM, Peter Jeremy unleashed the infinite monkeys and produced: On Mon, 2005-May-30 10:30:30 +0100, Rob MacGregor wrote: Looking at VMWare's list of supported client OSs, FreeBSD 5 is only supported in the r

Re: Screen Resolution

Rob MacGregor a écrit : On Monday, May 30, 2005 8:18 AM, Erich Dollansky <> unleashed the infinite monkeys and produced: Someone at the list might even have the right one to start with for you if you tell us the graphic card and the monitor you are using. If it's inside VMWare then t

PAM and nullok

PAM it's working, the only problem is with the null password users, the answer is allways NO. the nullok doesn't seem active here is my PAM file auth required /usr/lib/pam_unix.so nullok account required /usr/lib/pam_unix.so nullok is it a bug ? or a configuration problem I test it

Re: Screen Resolution

Erich Dollansky a écrit : Hi, Hervé Kergourlay wrote: thanks for the doc It seems that in FreeBSD 5.3, Xorg is installed as default but there is no xorg.conf file in /etc/X11 This is normal. I deinstall and reinstall Xorg manually but there is no more xorg.conf file in /etc/X11 so I

Re: Screen Resolution

thanks for the doc It seems that in FreeBSD 5.3, Xorg is installed as default but there is no xorg.conf file in /etc/X11 I deinstall and reinstall Xorg manually but there is no more xorg.conf file in /etc/X11 so I can't modify the screen resolution else when I run xorg -configure, I've a b

Re: Screen Resolution

Erich Dollansky a écrit : Hi, Hervé Kergourlay wrote: Erich Dollansky a écrit : I install FreeBSD 5.3 with the standard option, the X process in /usr/X11R6/bin/X is running So, it should be X.Org. I run startx to start the X server edit /etc/X11/xorg.conf I don't have any xorg.conf

Re: Screen Resolution

Erich Dollansky a écrit : Hi, what X do you run? I install FreeBSD 5.3 with the standard option, the X process in /usr/X11R6/bin/X is running I run startx to start the X server Did you configure X for a higher resolution? I woul like but the only way seems to be the Desktop Preferences /

Screen Resolution

Just one simple question on the screen resolution on FreeBSD 5.3 I change the xinitrc to launch gnome-wm and gnome-panel but I can't change the resolution in the Desktop Preferences / Screen Resolution tool only 640*480 is listed which is very small I can't change to 800*600 ? any idea ? he

Re: Porting on FreeBSD 53

John-Mark Gurney a écrit : Hervé Kergourlay wrote this message on Thu, May 12, 2005 at 09:37 +0200: what about files more than 4GB, do I need to use specific APIs as open64, stat64 or the current open and stat API are managing the big file ? Nope... FreeBSD's off_t has been 64bits since 2.

Re: Porting on FreeBSD 53

Seán C. Farley a écrit : On Thu, 12 May 2005, Seán C. Farley wrote: On Thu, 12 May 2005, Hervé Kergourlay wrote: 4) wait() API 2 problems, the first is a ECHILD error on a wait call after a fork fork The code is generic for most of unix system. Is there any specific problems to manage the fork and

Re: Porting on FreeBSD 53

Robert Watson a écrit : On Thu, 12 May 2005, Hervé Kergourlay wrote: 2) ACLs I'm using the API acl_get_file and family with success with ACL_TYPE_ACCESS defined in /usr/include/sys/acl.h #define ACL_TYPE_ACCESS 0x #define ACL_TYPE_DEFAULT0x0001 #define ACL_TYPE_AFS

Porting on FreeBSD 53

we are porting our product on FreeBSD 5.3 it's a backup product which is still running on FreeBSD 4.0 here's a list of questions after checking the documentation 1) PAM it's working, the only problem is with the null password users, the answer is allways NO. the nullok doesn't seem active here is