DaemonForums  

Go Back   DaemonForums > OpenBSD > OpenBSD Packages and Ports

OpenBSD Packages and Ports Installation and upgrading of packages and ports on OpenBSD.

Reply
 
Thread Tools Display Modes
  #1   (View Single Post)  
Old 3rd October 2016
philo_neo71 philo_neo71 is offline
Package Pilot
 
Join Date: Jul 2009
Posts: 214
Default compiling NextStep WM?

Hi,
I've Sun blade 1500, intalled the ports, i going to compile NextStep window manager.
I ask me if i do activate :
1/ GDM
2/ XDM
3/ KDM

Someone know witch bus that i must use ?

Regards
Philippe
Reply With Quote
  #2   (View Single Post)  
Old 3rd October 2016
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 5,889
Default

xdm(1) is built-in with the X11 Windows System on OpenBSD.

gdm is packaged with Gnome, kdm is packaged with KDE.

My recommendation is to use packages available for OpenBSD on the sparc64 architecture, rather than trying to build applications yourself. For example, afterstep and windowmaker are both available as packages for sparc64.

Porting your own applications to OpenBSD will usually require skills and knowledge you do not appear to have.

Last edited by jggimi; 3rd October 2016 at 03:16 AM. Reason: added WindowMaker reference, porting comment
Reply With Quote
  #3   (View Single Post)  
Old 3rd October 2016
philo_neo71 philo_neo71 is offline
Package Pilot
 
Join Date: Jul 2009
Posts: 214
Default

hi,
finaly i've installed gnome3, but it doesn't work ! because i don't have skills for build daemon for afterstep !

Code:
# pkg_add gnome
# rcctl disable xdm
# rcctl enable multicast messagebus avahi_daemon gdm
# reboot
this is my output :
Quote:
pkg_scripts absent
dbus_daemon absent
avahi_daemon failed
cupsd absent
gdm ok
someone have ideas

regards
philippe

Last edited by philo_neo71; 3rd October 2016 at 07:54 PM.
Reply With Quote
  #4   (View Single Post)  
Old 3rd October 2016
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 5,889
Default

Quote:
Originally Posted by philo_neo71 View Post
...someone have ideas...
Focus on one error message at a time. Start with the first.

The error message "pkg_scripts" absent, indicates a problem with your rc.conf.local(5) file.

This file is manipulated by rcctl(8), and the pkg_scripts variable is revised with rcctl enable and disable commands.

You will find this variable described in the rc.conf.local(5) man page.

Look to a broken, missing, or damaged /etc/rc.conf.local.

I am guessing your rcctl(8) commands produced warnings or errors which you did not notice.
Reply With Quote
  #5   (View Single Post)  
Old 3rd October 2016
philo_neo71 philo_neo71 is offline
Package Pilot
 
Join Date: Jul 2009
Posts: 214
Default

this is my /etc/rc.conf.local

Code:
multicast=YES
pkg_scripts=${pkg_scripts} dbus_daemon avahi_daemon toadd cupsd messagebus gdm
Reply With Quote
  #6   (View Single Post)  
Old 3rd October 2016
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 5,889
Default

Where did the Bourne shell substitution string "{$pkg_scripts}" come from? It did not come from OpenBSD -release 6.0, nor from any of its packages, nor from any rcctl command string you could possibly have entered. The rc.conf(5) files have not been shell scripts for two years.

You did this damage to yourself once before, and you did it only three weeks ago.

I have some simple advice to keep this from happening to you again.

Put the mouse down, and step away from the 3rd-party "how to" documents.
Reply With Quote
  #7   (View Single Post)  
Old 3rd October 2016
LeFrettchen's Avatar
LeFrettchen LeFrettchen is offline
Marveled user
 
Join Date: Aug 2012
Location: Bronvaux, France
Posts: 246
Default

philo_neo71, you could try XFCE, works fine on my Blade 2500.

Code:
# pkg_add xfce
# pkg_add xfce-extras
# startxfce4
---------------------------------------------

Quote:
Originally Posted by jggimi View Post
Put the mouse down, and step away from the 3rd-party "how to" documents.
Come on jggimi, you just killed me !
__________________
The secret of wisdom is not wisdom itself, it's the road that leads us there.

Last edited by LeFrettchen; 3rd October 2016 at 11:58 PM.
Reply With Quote
  #8   (View Single Post)  
Old 3rd October 2016
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 5,889
Default

Quote:
Originally Posted by LeFrettchen View Post
...you just killed me...
Well, I tried to add a little bit of humor to a continuing problem for Philippe. He's not the only person who turns first -- and sometimes wrongly -- to the Internet for instructions, and it is not just OpenBSD that sees poor, misleading, or out-of-date "how-to" documents published by people who are trying to be helpful. But it's more noticeable with the BSDs, because they have excellent documentation that should be reviewed first.

The OpenBSD Project frowns on third party "how-to" documents, for very good reason. Most are written by newbies, who are proud of their accomplishments and eager to share their success. But because they are written by newbies, they are often only applicable to limited use-cases, and relatively poorly documented. Unfortunately, to other new users, it then is unclear what may be implied, unclear what is missing, and unclear what is misstated.

In this case, OpenBSD has very clear, very helpful documentation, which was not followed a year ago when Philippe first attempted to install Gnome, was not followed a month ago when Philippe tried to install Gnome again, and .... here we are, once more. Three times, with the same "how-to."

Are third party "how to" documents always useless? No. But one should be very careful to understand what is in them, what may be applicable, what may not be. One should never blindly copy and paste anything out of them, instead, one should do one's own research to validate (or invalidate) the information provided.

And if you find what appears to be a valid third party "how-to" and it fails to function as described .. why not ask the author to review and revise?

---

I have written "how-to" documentation. Mostly on this forum, often to help someone with a specific problem. And yes, even for Philippe, as noted in the thread I linked above. I've also written a "how-to" that was published in the OpenBSD Journal. That document had half a dozen developer/editors review, recommend, revise, and correct before it was published....and it was out-of-date in less than a single year.
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
Compiling e17 from source divadgnol67 OpenBSD Packages and Ports 3 2nd January 2011 02:57 PM
Compiling Epkowa Oko OpenBSD Packages and Ports 3 30th December 2008 10:01 PM
c++ compiling hello world Gates Programming 3 26th July 2008 12:48 PM
Compiling Nagios 3.02 roundkat Solaris 1 2nd June 2008 09:09 PM
Compiling OpenBSD code WeakSauceIII OpenBSD General 4 19th May 2008 12:59 AM


All times are GMT. The time now is 07:01 AM.


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