Ubuntu 9.10 to 10.04 one shot update
sudo sed -i 's/karmic/lucid/g' /etc/apt/sources.list && sudo aptitude update && sudo aptitude dist-upgrade
sudo sed -i 's/karmic/lucid/g' /etc/apt/sources.list && sudo aptitude update && sudo aptitude dist-upgrade
Wanted: files with 0660, directories with 770
Config:
Problem: OS X clients creates
Solution:
unix extensions = no
in smb.conf on server
find . -type d -exec chmod 755 {} \;
oder (mit Ausgabe)
find . -type d -exec chmod 755 {} \; -print
is it so hard to understand that linux and open source software are major players on servers and desktops nowadays?
I wasted several hours getting the best out of the “industry leading” Mobility Radeon X1600 graphics card in my shiny HP n8430 notebook.
My experience: whenever you install a major linux distribution, an “up to date” ATI graphics card will provide you with all kind of troubles. Suspend/wakeup is never working reliable, dual monitor setups configured from within the ATI control center producing wrong screen resolutions and so on.
I respect that proprietary graphic card drivers include lots of optimizations and hacks to achieve better performance. These optimizations may give a company a competitive advantage in the proprietary software market. In the linux and open source world (to my knowledge) no company has ever increased their market share by relying on proprietary software. On the other side, vendors which are involved in the community process and actively support developers to adopt their hardware have seen noticeable benefit in the growing linux market.
I’m pretty sure that there is a way for ATI to support linux driver development without giving away company secrets. I hope they have read Greg’s offer and take part of it!
1) configure Apache
ProxyPass /balancer-manager ! ProxyPass / balancer://myCluster/ stickysession=JSESSIONID lbmethod=bytraffic nofailover=Off SetHandler balancer-manager AuthType Basic AuthName "Cluster manager" AuthUserFile /etc/httpd/conf.d/htpasswd Require valid-user BalancerMember ajp://10.0.0.1:8009 route=member01 BalancerMember ajp://10.0.0.2:8009 route=member02
2) For all application-server instances
edit %JBOSS_HOME%/server/%your_config_dir%/deploy/jboss-web.deployer/server.xml
Look for the “engine name” tag in the ajp1.3 connector, add a corresponding “jvmRoute”
<!-- Define an AJP 1.3 Connector on port 8009 --> emptySessionPath="true" enableLookups="false" redirectPort="8443"
edit %JBOSS_HOME%/server/%your_config_dir%/deploy/jboss-web.deployer/META-INF/jboss-service.xml and look for
useJK
it has to be set to “true”
true