DaemonForums  

Go Back   DaemonForums > FreeBSD > FreeBSD General

FreeBSD General Other questions regarding FreeBSD which do not fit in any of the categories below.

Reply
 
Thread Tools Display Modes
  #1   (View Single Post)  
Old 12th November 2008
mfaridi's Avatar
mfaridi mfaridi is offline
Spam Deminer
 
Join Date: May 2008
Location: Afghanistan
Posts: 282
Thanked 5 Times in 5 Posts
Default my X11 or Gnome kill after 5 days

I use FreeBSD 7 with Gnome , and my system is ON always and I use it for my work and use it for torrent and I use Ktorrent
it is one month , some morning I come to office I see my Gnome is kill and my system is logout from Gnome and go to command line and I have to type
Code:
startx
for start Gnome , when I type
Code:
startx
it take long time to start Gnome and sometimes Gnome dose not start and I have to reboot my system , last week I understand when see my gnome is killed and when I go to

Code:
/var/tmp
and delete all thing and clear this directory and then I type
Code:
startx
I see Gnome start very fast and work good and I do not have to reboot my system

what is problem ?

this is my xorg.log
Code:
--) NV(0): Virtual size is 1280x1024 (pitch 1280)
(**) NV(0): *Driver mode "1024x768": 78.8 MHz, 60.1 kHz, 75.1 Hz
(II) NV(0): Modeline "1024x768"x75.1   78.80  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.1 kHz)
(**) NV(0): *Driver mode "1280x1024": 108.0 MHz, 64.0 kHz, 60.0 Hz
(II) NV(0): Modeline "1280x1024"x60.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
(**) NV(0):  Driver mode "1280x1024": 109.0 MHz, 63.7 kHz, 59.9 Hz
(II) NV(0): Modeline "1280x1024"x59.9  109.00  1280 1368 1496 1712  1024 1027 1034 1063 -hsync +vsync (63.7 kHz)
(**) NV(0):  Driver mode "1280x1024": 90.8 MHz, 63.0 kHz, 59.8 Hz
(II) NV(0): Modeline "1280x1024"x59.8   90.75  1280 1328 1360 1440  1024 1027 1034 1054 +hsync -vsync (63.0 kHz)
(**) NV(0):  Default mode "1280x1024": 108.0 MHz, 64.0 kHz, 60.0 Hz
(II) NV(0): Modeline "1280x1024"x60.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
(**) NV(0):  Driver mode "1280x960": 101.2 MHz, 59.7 kHz, 59.9 Hz
(II) NV(0): Modeline "1280x960"x59.9  101.25  1280 1360 1488 1696  960 963 967 996 -hsync +vsync (59.7 kHz)
(**) NV(0):  Default mode "1280x960": 108.0 MHz, 60.0 kHz, 60.0 Hz
(II) NV(0): Modeline "1280x960"x60.0  108.00  1280 1376 1488 1800  960 961 964 1000 +hsync +vsync (60.0 kHz)
(**) NV(0):  Driver mode "1152x864": 108.0 MHz, 67.5 kHz, 75.0 Hz
(II) NV(0): Modeline "1152x864"x75.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz)
(**) NV(0):  Driver mode "1152x864": 104.0 MHz, 67.7 kHz, 74.8 Hz
(II) NV(0): Modeline "1152x864"x74.8  104.00  1152 1224 1344 1536  864 867 871 905 -hsync +vsync (67.7 kHz)
(**) NV(0):  Default mode "1152x864": 108.0 MHz, 67.5 kHz, 75.0 Hz
(II) NV(0): Modeline "1152x864"x75.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz)
(**) NV(0):  Default mode "1152x768": 65.0 MHz, 44.2 kHz, 54.8 Hz
(II) NV(0): Modeline "1152x768"x54.8   65.00  1152 1178 1314 1472  768 771 777 806 +hsync +vsync (44.2 kHz)
(**) NV(0):  Driver mode "1024x768": 75.0 MHz, 56.5 kHz, 70.1 Hz
(II) NV(0): Modeline "1024x768"x70.1   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz)
(**) NV(0):  Driver mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz
(II) NV(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz)
(**) NV(0):  Default mode "1024x768": 94.5 MHz, 68.7 kHz, 85.0 Hz
(II) NV(0): Modeline "1024x768"x85.0   94.50  1024 1072 1168 1376  768 769 772 808 +hsync +vsync (68.7 kHz)
(**) NV(0):  Default mode "1024x768": 78.8 MHz, 60.0 kHz, 75.0 Hz
(II) NV(0): Modeline "1024x768"x75.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz)
(**) NV(0):  Default mode "1024x768": 75.0 MHz, 56.5 kHz, 70.1 Hz
(II) NV(0): Modeline "1024x768"x70.1   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz)
(**) NV(0):  Default mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz
(II) NV(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz)
(**) NV(0):  Driver mode "832x624": 57.3 MHz, 49.7 kHz, 74.6 Hz
(II) NV(0): Modeline "832x624"x74.6   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync (49.7 kHz)
(**) NV(0):  Default mode "832x624": 57.3 MHz, 49.7 kHz, 74.6 Hz
(II) NV(0): Modeline "832x624"x74.6   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync (49.7 kHz)
(**) NV(0):  Driver mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz
(II) NV(0): Modeline "800x600"x75.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz)
(**) NV(0):  Driver mode "800x600": 50.0 MHz, 48.1 kHz, 72.2 Hz
(II) NV(0): Modeline "800x600"x72.2   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz)
(**) NV(0):  Driver mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz
(II) NV(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz)
(**) NV(0):  Driver mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz
(II) NV(0): Modeline "800x600"x56.2   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz)
(**) NV(0):  Default mode "800x600": 56.3 MHz, 53.7 kHz, 85.1 Hz
(II) NV(0): Modeline "800x600"x85.1   56.30  800 832 896 1048  600 601 604 631 +hsync +vsync (53.7 kHz)
(**) NV(0):  Default mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz
(II) NV(0): Modeline "800x600"x75.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz)
(**) NV(0):  Default mode "800x600": 50.0 MHz, 48.1 kHz, 72.2 Hz
(II) NV(0): Modeline "800x600"x72.2   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz)
(**) NV(0):  Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz
(II) NV(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz)
(**) NV(0):  Default mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz
(II) NV(0): Modeline "800x600"x56.2   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz)
(**) NV(0):  Driver mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz
(II) NV(0): Modeline "640x480"x75.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz)
(**) NV(0):  Driver mode "640x480": 31.5 MHz, 37.9 kHz, 72.8 Hz
(II) NV(0): Modeline "640x480"x72.8   31.50  640 664 704 832  480 489 491 520 -hsync -vsync (37.9 kHz)
(**) NV(0):  Driver mode "640x480": 30.2 MHz, 35.0 kHz, 66.7 Hz
(II) NV(0): Modeline "640x480"x66.7   30.24  640 704 768 864  480 483 486 525 -hsync -vsync (35.0 kHz)
(**) NV(0):  Driver mode "640x480": 25.2 MHz, 31.5 kHz, 60.0 Hz
(II) NV(0): Modeline "640x480"x60.0   25.20  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz)
(**) NV(0):  Default mode "640x480": 36.0 MHz, 43.3 kHz, 85.0 Hz
(II) NV(0): Modeline "640x480"x85.0   36.00  640 696 752 832  480 481 484 509 -hsync -vsync (43.3 kHz)
(**) NV(0):  Default mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz
(II) NV(0): Modeline "640x480"x75.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz)
(**) NV(0):  Default mode "640x480": 31.5 MHz, 37.9 kHz, 72.8 Hz
(II) NV(0): Modeline "640x480"x72.8   31.50  640 664 704 832  480 489 492 520 -hsync -vsync (37.9 kHz)
(**) NV(0):  Default mode "640x480": 25.2 MHz, 31.5 kHz, 59.9 Hz
(II) NV(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz)
(**) NV(0):  Driver mode "720x400": 28.3 MHz, 31.5 kHz, 70.1 Hz
(II) NV(0): Modeline "720x400"x70.1   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz)
(**) NV(0):  Default mode "720x400": 35.5 MHz, 37.9 kHz, 85.0 Hz
(II) NV(0): Modeline "720x400"x85.0   35.50  720 756 828 936  400 401 404 446 -hsync +vsync (37.9 kHz)
(**) NV(0):  Default mode "640x400": 31.5 MHz, 37.9 kHz, 85.1 Hz
(II) NV(0): Modeline "640x400"x85.1   31.50  640 672 736 832  400 401 404 445 -hsync +vsync (37.9 kHz)
(**) NV(0):  Default mode "640x350": 31.5 MHz, 37.9 kHz, 85.1 Hz
(II) NV(0): Modeline "640x350"x85.1   31.50  640 672 736 832  350 382 385 445 +hsync -vsync (37.9 kHz)
(**) NV(0): Display dimensions: (380, 300) mm
(**) NV(0): DPI set to (85, 86)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/local/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
	compiled for 1.4.2, module version = 1.0.0
	ABI class: X.Org ANSI C Emulation, version 0.3
(II) Loading sub module "xaa"
(II) LoadModule: "xaa"
(II) Loading /usr/local/lib/xorg/modules//libxaa.so
(II) Module xaa: vendor="X.Org Foundation"
	compiled for 1.4.2, module version = 1.2.0
	ABI class: X.Org Video Driver, version 2.0
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"(II) Module "ramdac" already built-in
(==) NV(0): Write-combining range (0x0,0x1000) was already clear
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC?  No, I don't.
(II) resource ranges after preInit:
	[0] 0	0	0xfc000000 - 0xfcffffff (0x1000000) MX[B]
	[1] 0	0	0xc0000000 - 0xcfffffff (0x10000000) MX[B]
	[2] 0	0	0xfd000000 - 0xfdffffff (0x1000000) MX[B]
	[3] -1	0	0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
	[4] -1	0	0x000f0000 - 0x000fffff (0x10000) MX[B]
	[5] -1	0	0x000c0000 - 0x000effff (0x30000) MX[B]
	[6] -1	0	0x00000000 - 0x0009ffff (0xa0000) MX[B]
	[7] -1	0	0xfeaff000 - 0xfeafffff (0x1000) MX[B]E
	[8] -1	0	0xfe9fe000 - 0xfe9fffff (0x2000) MX[B]E
	[9] -1	0	0xfebff800 - 0xfebffbff (0x400) MX[B]E
	[10] -1	0	0xfebf8000 - 0xfebfbfff (0x4000) MX[B]E
	[11] -1	0	0xfebffc00 - 0xfebfffff (0x400) MX[B]E
	[12] -1	0	0xfe8e0000 - 0xfe8fffff (0x20000) MX[B](B)
	[13] -1	0	0xfc000000 - 0xfcffffff (0x1000000) MX[B](B)
	[14] -1	0	0xc0000000 - 0xcfffffff (0x10000000) MX[B](B)
	[15] -1	0	0xfd000000 - 0xfdffffff (0x1000000) MX[B](B)
	[16] 0	0	0x000a0000 - 0x000affff (0x10000) MS[B](OprD)
	[17] 0	0	0x000b0000 - 0x000b7fff (0x8000) MS[B](OprD)
	[18] 0	0	0x000b8000 - 0x000bffff (0x8000) MS[B](OprD)
	[19] -1	0	0x0000ffff - 0x0000ffff (0x1) IX[B]
	[20] -1	0	0x00000000 - 0x000000ff (0x100) IX[B]
	[21] -1	0	0x0000b800 - 0x0000b8ff (0x100) IX[B]E
	[22] -1	0	0x0000a400 - 0x0000a47f (0x80) IX[B]E
	[23] -1	0	0x0000a480 - 0x0000a4ff (0x80) IX[B]E
	[24] -1	0	0x0000a800 - 0x0000a87f (0x80) IX[B]E
	[25] -1	0	0x0000a880 - 0x0000a8ff (0x80) IX[B]E
	[26] -1	0	0x0000ac00 - 0x0000acff (0x100) IX[B]E
	[27] -1	0	0x0000c800 - 0x0000c87f (0x80) IX[B]E
	[28] -1	0	0x0000c880 - 0x0000c8ff (0x80) IX[B]E
	[29] -1	0	0x0000cc00 - 0x0000ccff (0x100) IX[B]E
	[30] -1	0	0x0000d000 - 0x0000d07f (0x80) IX[B]E
	[31] -1	0	0x0000d080 - 0x0000d0ff (0x80) IX[B]E
	[32] -1	0	0x0000d400 - 0x0000d47f (0x80) IX[B]E
	[33] -1	0	0x00000400 - 0x000004ff (0x100) IX[B]E
	[34] -1	0	0x0000e080 - 0x0000e0ff (0x80) IX[B]E
	[35] -1	0	0x0000e400 - 0x0000e47f (0x80) IX[B]E
	[36] -1	0	0x0000e480 - 0x0000e4ff (0x80) IX[B]E
	[37] -1	0	0x0000e800 - 0x0000e87f (0x80) IX[B]E
	[38] -1	0	0x0000e880 - 0x0000e8ff (0x80) IX[B]E
	[39] -1	0	0x0000ec00 - 0x0000ecff (0x100) IX[B]E
	[40] -1	0	0x0000d880 - 0x0000d8ff (0x80) IX[B]E
	[41] -1	0	0x0000d800 - 0x0000d87f (0x80) IX[B]E
	[42] -1	0	0x0000d480 - 0x0000d4ff (0x80) IX[B]E
	[43] -1	0	0x0000e000 - 0x0000e07f (0x80) IX[B]E
	[44] -1	0	0x0000dc00 - 0x0000dcff (0x100) IX[B]E
	[45] 0	0	0x000003b0 - 0x000003bb (0xc) IS[B](OprU)
	[46] 0	0	0x000003c0 - 0x000003df (0x20) IS[B](OprU)
(==) NV(0): Write-combining range (0xc0000000,0x10000000)
(==) NV(0): Write-combining range (0xa0000,0x10000) was already clear
(II) NV(0): Using XFree86 Acceleration Architecture (XAA)
	Screen to screen bit blits
	Solid filled rectangles
	8x8 mono pattern filled rectangles
	Indirect CPU to Screen color expansion
	Solid Lines
	Scanline Image Writes
	Offscreen Pixmaps
	Setting up tile and stipple cache:
		32 128x128 slots
		32 256x256 slots
		16 512x512 slots
(==) NV(0): Backing store disabled
(==) NV(0): Silken mouse enabled
(**) Option "dpms"
(**) NV(0): DPMS enabled
(==) RandR enabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension XAccessControlExtension
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(II) Loading sub module "GLcore"
(II) LoadModule: "GLcore"
(II) Loading /usr/local/lib/xorg/modules/extensions//libGLcore.so
(II) Module GLcore: vendor="X.Org Foundation"
	compiled for 1.4.2, module version = 1.0.0
	ABI class: X.Org Server Extension, version 0.3
(II) GLX: Initialized MESA-PROXY GL provider for screen 0
(**) Option "Protocol" "auto"
(**) Mouse0: Device: "/dev/sysmouse"
(**) Mouse0: Protocol: "auto"
(**) Option "CorePointer"
(**) Mouse0: always reports core events
(**) Option "Device" "/dev/sysmouse"
(==) Mouse0: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "ZAxisMapping" "4 5 6 7"
(**) Mouse0: ZAxisMapping: buttons 4, 5, 6 and 7
(**) Mouse0: Buttons: 11
(**) Mouse0: Sensitivity: 1
(**) Option "CoreKeyboard"
(**) Keyboard0: always reports core events
(**) Option "Protocol" "standard"
(**) Keyboard0: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) Keyboard0: XkbRules: "xorg"
(**) Option "XkbModel" "pc105"
(**) Keyboard0: XkbModel: "pc105"
(**) Option "XkbLayout" "us"
(**) Keyboard0: XkbLayout: "us"
(**) Option "CustomKeycodes" "off"
(**) Keyboard0: CustomKeycodes disabled
(II) evaluating device (Keyboard0)
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(II) evaluating device (Mouse0)
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
(II) Mouse0: SetupAuto: hw.iftype is 4, hw.model is 0
(II) Mouse0: SetupAuto: protocol is SysMouse
(II) 3rd Button detected: disabling emulate3Button
SetGrabKeysState - disabled
SetGrabKeysState - enabled
SetGrabKeysState - disabled
SetGrabKeysState - enabled
SetGrabKeysState - disabled
SetGrabKeysState - enabled
SetGrabKeysState - disabled
SetGrabKeysState - enabled
SetGrabKeysState - disabled
SetGrabKeysState - enabled
SetGrabKeysState - disabled
SetGrabKeysState - enabled
SetGrabKeysState - disabled
SetGrabKeysState - enabled
AUDIT: Tue Nov 11 13:17:03 2008: 1159 X: client 24 rejected from local host (uid 1002)
SetGrabKeysState - disabled
SetGrabKeysState - enabled
Mostafa ~ [257]                                                                                                                                                                       12:34
Reply With Quote
  #2   (View Single Post)  
Old 12th November 2008
richardpl richardpl is offline
Spam Deminer
 
Join Date: May 2008
Location: Croatia
Posts: 284
Thanked 25 Times in 24 Posts
Talking

Quote:
Originally Posted by mfaridi View Post
what is problem ?
GNOME is the problem.
Reply With Quote
  #3   (View Single Post)  
Old 12th November 2008
mfaridi's Avatar
mfaridi mfaridi is offline
Spam Deminer
 
Join Date: May 2008
Location: Afghanistan
Posts: 282
Thanked 5 Times in 5 Posts
Default

Quote:
Originally Posted by richardpl View Post
GNOME is the problem.
problem is this

why kill gnome after 5 days , and I have to type startx to start again or delete all thing in

Code:
/vat/tmp
Reply With Quote
  #4   (View Single Post)  
Old 12th November 2008
richardpl richardpl is offline
Spam Deminer
 
Join Date: May 2008
Location: Croatia
Posts: 284
Thanked 25 Times in 24 Posts
Default

Ask GNOME and Xorg developers.
As workaround you could start startx in another script which would automatically start another startx instance when previous one got into void.
Reply With Quote
  #5   (View Single Post)  
Old 12th November 2008
mfaridi's Avatar
mfaridi mfaridi is offline
Spam Deminer
 
Join Date: May 2008
Location: Afghanistan
Posts: 282
Thanked 5 Times in 5 Posts
Default

but I do not have this problem with OpenBSD and Gnome , before I use OpenBSD 4.2 and it was ON for 56 days and I use Gnome without problem.
Reply With Quote
  #6   (View Single Post)  
Old 12th November 2008
DrJ DrJ is offline
ISO Quartermaster
 
Join Date: Apr 2008
Location: Gold Country, CA
Posts: 506
Thanked 39 Times in 39 Posts
Default

I can't offer any useful advice, but what you describe is something I've not seen in Gnome, ever, and I have used it since 2.4. Admittedly I am on 6.3 instead of 7.x, but that should not matter much.

Gnome for me stays up for a couple of months at a time; the crash then seems to be related to X11. I'd look there, perhaps looking at the video driver.
Reply With Quote
  #7   (View Single Post)  
Old 12th November 2008
lvlamb's Avatar
lvlamb lvlamb is offline
Real Name: Louis V. Lambrecht
Spam Deminer
 
Join Date: May 2008
Location: .be
Posts: 221
Thanked 25 Times in 24 Posts
Default

Both GNOME ands KDE are the problems.
In a certain way, XFCE also joins the group.
All try to manage sessions, security, X and the kitchensink. Be a better Windows than Windows (better than worse still is bad )
Obviously they will run into precedence/incompatibility problems sooner or later.
One of which is reserved/mapping memory.

Then, you have OS problems. On a multi-boot machine I need both PS/2 and USB keyboards and mice.

Then you have BIOS problems.

All you can say is:
GNOME version xxx breaks on OS yyy, is bad luck while
GNOME version zzz on OS nnn was working correctly.
GNOME version xxx on OS nnn might not work either.
__________________
da more I know I know I know nuttin'
Reply With Quote
  #8   (View Single Post)  
Old 12th November 2008
DrJ DrJ is offline
ISO Quartermaster
 
Join Date: Apr 2008
Location: Gold Country, CA
Posts: 506
Thanked 39 Times in 39 Posts
Default

Well, I've ten major versions (and probably 30 minor versions) of Gnome on FreeBSD, and after the initial problems are worked out of the initial version (the ".1" release) I've not had any real issues with it.

I do think it does not care much for Wine, though. And how it works with CUPS is a major pain in the a**.
Reply With Quote
  #9   (View Single Post)  
Old 12th November 2008
DrJ DrJ is offline
ISO Quartermaster
 
Join Date: Apr 2008
Location: Gold Country, CA
Posts: 506
Thanked 39 Times in 39 Posts
Default

mfaridi, you would be served better to take your question to the freebsd gnome mailing list. Joe and Mezz are usually very helpful and responsive, and they know Gnome inside and out. They better, since they are porters and maintainers.
Reply With Quote
Old 13th November 2008
lvlamb's Avatar
lvlamb lvlamb is offline
Real Name: Louis V. Lambrecht
Spam Deminer
 
Join Date: May 2008
Location: .be
Posts: 221
Thanked 25 Times in 24 Posts
Default

Specific to FreeBSD is the habit of upgrading the apps continuously.
You can have a set of apps breaking but have those apps working perfectly if you portsnapped 5 minutes later.
__________________
da more I know I know I know nuttin'
Reply With Quote
Old 13th November 2008
DrJ DrJ is offline
ISO Quartermaster
 
Join Date: Apr 2008
Location: Gold Country, CA
Posts: 506
Thanked 39 Times in 39 Posts
Default

Indeed. That is my main complaint about FreeBSD, incidentally. I have never had the pleasure of having everything installed working properly. As soon as one thing is fixed, another something breaks. That's the ports, not the base system.

Well, that's not quite true. Everything works on my main server. I have not updated it for two years.
Reply With Quote
Old 13th November 2008
Oko's Avatar
Oko Oko is offline
Fsck Surgeon
 
Join Date: May 2008
Location: Kosovo, Serbia
Posts: 774
Thanked 36 Times in 32 Posts
Default

Quote:
Originally Posted by lvlamb View Post
Specific to FreeBSD is the habit of upgrading the apps continuously.
You can have a set of apps breaking but have those apps working perfectly if you portsnapped 5 minutes later.
Quote:
Originally Posted by DrJ View Post
Indeed. That is my main complaint about FreeBSD, incidentally.
That is the major difference between continuously updated systems like FreeBSD and Debian comparing to cascade systems (I coined the term) like OpenBSD and RedHat which one usually updates every 6 months.

My way of avoiding any troubles when I run FreeBSD was to install a snapshot of stable and remain with it until major update (system or application) and then do the fresh installation. I personally burnt myself couple times by unnecessary updating a port three and breaking my system because of dependence issues due to the compilation of the single new port. I also found out that fresh installation is far more efficient way
of keeping your system updated than anything else.

Some of my friends on the another hand use cron to do overnight port fetching and ports updating. That usually work very well until major update which brakes the system. I personally have to hear a single good argument of advantage of continuous updating. For me it boils down that those people who are continuously updating system are doing that in order to have version 2.9999 of some program instead of version 2.9998.

Last edited by Oko; 13th November 2008 at 05:46 AM.
Reply With Quote
Old 13th November 2008
DrJ DrJ is offline
ISO Quartermaster
 
Join Date: Apr 2008
Location: Gold Country, CA
Posts: 506
Thanked 39 Times in 39 Posts
Default

Well, I am in no way compulsive about updating. Usually I do it only to fix certain bugs, and that is only once every few months. Sometimes, but rarely, it is to get new features. But the way the FreeBSD ports are set up, you have to do it on a regular basis, or reinstall. I really hate to reinstall.

On my server, though, it is about the only way. I also use it as a light-duty input station, and it has the pre-modular version of X11 (6.9??), and a bunch of other really stale ports. There practically is no way to update it. So for now, it sits without updating.

Gnome on my main box is a slightly different matter, since I often serve as a test site for the newer versions. I usually find ten or more bugs that are fixed quickly.

In spite of the accolades of many, I think the way ports work is a pain. And it is a real problem. My W2K box is still supported. Just try to get support for FBSD 4.8 or earlier ports.
Reply With Quote
Old 13th November 2008
Oko's Avatar
Oko Oko is offline
Fsck Surgeon
 
Join Date: May 2008
Location: Kosovo, Serbia
Posts: 774
Thanked 36 Times in 32 Posts
Default

Quote:
Originally Posted by DrJ View Post

In spite of the accolades of many, I think the way ports work is a pain. And it is a real problem. My W2K box is still supported. Just try to get support for FBSD 4.8 or earlier ports.
You can look that from different prospective. The freedom that open source project have to brake backward compatibility is a major advantage over the proprietary systems. Just compare Solaris and BSD in terms of complexity.
Reply With Quote
Old 13th November 2008
DrJ DrJ is offline
ISO Quartermaster
 
Join Date: Apr 2008
Location: Gold Country, CA
Posts: 506
Thanked 39 Times in 39 Posts
Default

That's true, but I have many custom applications running on my server. All the work that went into creating those custom ports would have to be redone.

I'd happily live with some added complexity. Programmers are costly.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
GNOME st89 OpenBSD Packages and Ports 3 8th October 2009 07:13 AM
Get the Days of the Week cksraj Programming 3 26th September 2009 11:01 AM
How to remove Gnome and X Malakim Solaris 2 12th April 2009 12:10 PM
Screensave for gnome disappearedng FreeBSD General 1 8th September 2008 11:06 PM
Gnome PBI for PC-BSD s0xxx Other BSD and UNIX/UNIX-like 2 22nd July 2008 01:34 PM


All times are GMT. The time now is 12:43 AM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick