Re: Debian avahi weirdness
what does sudo ifconfig -a cat /etc/network/interfaces sudo dpkg -l | grep avahi show? On Thu, 2010-02-04 at 17:22 +1300, Roy Britten wrote: > A debian server for which the previous administrator has disappeared > is playing up. When bringing up networking we see something like > (copied by hand; may contain typos) > > $ sudo ifdown eth0 > $ sudo ifup eth0 > ADDRCONF(NETDEV_UP): eth0: link is not ready > /etc/network/if-up.d/avahi-daemon: line 9: > /usr/lib/avahi/avahi-daemon-check-dns.sh: No such file or directory > /etc/network/if-up.d/avahi-daemon: line 9: exec: > /usr/lib/avahi/avahi-daemon-check-dns.sh: cannot execute: No such file > or directory > run-parts: /etc/network/if-up.d/avahi-daemon exited with return code 126 > > /usr/lib/avahi doesn't exist, and I can't find > avahi-daemon-check-dns.sh anywhere on the system. An apt-get update > was performed about a week before the issues were noticed; it's > possible that the system was restarted for the first time a week after > the update was applied. My google-foo has failed to find answers this > time. > > I'm assuming (and we all know what a good idea that is...) that > something dodgy happened in the latest apt-get update, and the system > has been left in an inconsistent state. > > I've tried commenting out the offending line in > etc/network/if-up.d/avahi-daemon to no avail; the result is > > $ sudo ifdown eth0 > $ sudo ifup eth0 > ADDRCONF(NETDEV_UP): eth0: link is not ready > run-parts: /etc/network/if-up.d/avahi-daemon exited with return code 1 > > Your suggestions for regaining network access, or of places I should > look for clues, are solicited.
Debian avahi weirdness
A debian server for which the previous administrator has disappeared is playing up. When bringing up networking we see something like (copied by hand; may contain typos) $ sudo ifdown eth0 $ sudo ifup eth0 ADDRCONF(NETDEV_UP): eth0: link is not ready /etc/network/if-up.d/avahi-daemon: line 9: /usr/lib/avahi/avahi-daemon-check-dns.sh: No such file or directory /etc/network/if-up.d/avahi-daemon: line 9: exec: /usr/lib/avahi/avahi-daemon-check-dns.sh: cannot execute: No such file or directory run-parts: /etc/network/if-up.d/avahi-daemon exited with return code 126 /usr/lib/avahi doesn't exist, and I can't find avahi-daemon-check-dns.sh anywhere on the system. An apt-get update was performed about a week before the issues were noticed; it's possible that the system was restarted for the first time a week after the update was applied. My google-foo has failed to find answers this time. I'm assuming (and we all know what a good idea that is...) that something dodgy happened in the latest apt-get update, and the system has been left in an inconsistent state. I've tried commenting out the offending line in etc/network/if-up.d/avahi-daemon to no avail; the result is $ sudo ifdown eth0 $ sudo ifup eth0 ADDRCONF(NETDEV_UP): eth0: link is not ready run-parts: /etc/network/if-up.d/avahi-daemon exited with return code 1 Your suggestions for regaining network access, or of places I should look for clues, are solicited.
Re: link local wiki link in firefox
steve wrote: On Thu, 2010-02-04 at 11:31 +1300, Roger Searle wrote: Browsing to http://jupiter/policymanual/index.html returns I think this is the bit that's tripping you up... you need to have created a DNS entry for policymanual to use name based reporting. To access it in this manner, you just need to move the source tree to /var/www/html/policymanual ( probably wrong, but specifically the default config DocumentRoot/policymanual ), and you're then accessing it through the jupiter ( default ) setup. Steve Is doing an "ln -s" an option here, or do I need to have an actual copy in /var/www/html/? Probably Monday before I can come back to this, but I will. Thanks for your help thus far. Roger
Re: link local wiki link in firefox
steve wrote: You're using name based virtual hosting... bet you didn't know that! it's fair to say (and probably obvious) there is not much i do know about apache config... To do this ( bear with me as every distro does this in different files this is a hardy install. ) 1. You need a NameVirtualhost at the top of the 'default' config. NameVirtualHost * yes, got that. This means that all following VH configs must start with (ok this isn't true, but bear with me!)... and not for example. 2. You need to identify the next host by name, so in it's setup file, you need a ServerName mywiki.example.com "ServerName policymanual" added to /etc/apache2/sites-available/policymanual or similar to identify it. Personally, I also set up specific log files for each site so you can tract traffic, error more easily. ErrorLog /var/log/apache2/mywiki.example.com-error.log CustomLog /var/log/apache2/mywiki.example.com-access.log combined done this for policymanual and nothing of use in there so far. Here's an example of a really simple one of mine ( and anyone who wants to redesign the site... please do! ) --8<-- ServerName dh.greengecko.co.nz ServerAdmin st...@greengecko.co.nz DocumentRoot /www/dh.greengecko.co.nz ErrorLog /var/log/apache2/dh.greengecko.co.nz-error.log CustomLog /var/log/apache2/dh.greengecko.co.nz-access.log combined Options All AllowOverride All Order deny,allow allow from all --8<-- 3. The above name must resolve. On the web server itself, I modify /etc/hosts to resolve all of these websites to the IP address of the server itself ( some use 127.0.0.1, but I don't ). This means that the webserver itself will come up without any errors, and be serving the multiple domains. Not totally sure here. There's local name resolution via IPCop. The server can ping itself by name, other machines can ping it by name, and can browse from the network to http://jupiter to get the "it works!" test page. That enough or are you meaning more than this? 4. Permissions. simplest to ensure there's no problems - not something I'd recommend in a production environment... cd ( eg /www/dh.greengecko.co.nz ) sudo chown -R www-data:www-data . Not really able to do it like that since that will break general access to the folder for other users, but have done chmod -R o+rx on DocumentRoot. Which will ensure that your web server has permissions to access the content. Next, you need to ensure that your site name resolves to the client, so you need to run either a local DNS server, or to modify /etc/hosts on each client. I know what I'd do ( and probably use OpenDNS as resolvers to filter some of the traffic, no matter what abuse they make of the standards ). As mentioned above, got local name resolution. Current attempts to browse to http://jupiter/policymanual no longer return the "forbidden" error, instead the following. What might this indicate? Not Found The requested URL /policymanual/index.html was not found on this server. Apache/2.2.8 (Ubuntu) Server at jupiter Port 80 Thanks for the assistance so far, I'm close hopefully, not ready to give up yet! Cheers, Roger Not difficult once you get your head around it, just more steps than you'd expect. hth, Steve
Re: link local wiki link in firefox
On Thu, 2010-02-04 at 11:31 +1300, Roger Searle wrote: > Browsing to http://jupiter/policymanual/index.html returns > I think this is the bit that's tripping you up... you need to have created a DNS entry for policymanual to use name based reporting. To access it in this manner, you just need to move the source tree to /var/www/html/policymanual ( probably wrong, but specifically the default config DocumentRoot/policymanual ), and you're then accessing it through the jupiter ( default ) setup. Steve -- Steve Holdoway http://www.greengecko.co.nz MSN: st...@greengecko.co.nz GPG Fingerprint = B337 828D 03E1 4F11 CB90 853C C8AB AF04 EF68 52E0 signature.asc Description: This is a digitally signed message part
Re: link local wiki link in firefox
On Thu, 2010-02-04 at 11:31 +1300, Roger Searle wrote: > steve wrote: > > sudo apt-get install apache2 ( approximately ), and adjust the document > > root to point to the local folder containing the wiki. Then the wiki > > will be available at http://jupiter > > > > Which is what I do (: > > > Thanks for all of yesterday's replies, seeing the apache "it works" page > was simple, now I'm trying to set up a second site generally following > this guide > > https://help.ubuntu.com/8.04/serverguide/C/httpd.html > > though have missed something or doing something wrong. I have done the > following: > > *sudo cp /etc/apache2/sites-available/default > /etc/apache2/sites-available/policymanual > > and then in /etc/apache2/sites-enabled/policymanual edited DocumentRoot > and Directory to point to the correct location. > > **Then run "sudo a2ensite policymanual", and "sudo apache2ctl -t" > returns Syntax OK. > > Browsing to http://jupiter/policymanual/index.html returns > > * > > > Forbidden > > You don't have permission to access /policymanual/index.html on this server. > > Have checked that everyone has +x permissions on the DocumentRoot > folder, and the index.html file exists. > > I'm not sure what I have missed that is important and where to go from > here, any pointers or hints would be gratefully received. > > Cheers, > Roger > > > You're using name based virtual hosting... bet you didn't know that! To do this ( bear with me as every distro does this in different files this is a hardy install. ) 1. You need a NameVirtualhost at the top of the 'default' config. NameVirtualHost * This means that all following VH configs must start with (ok this isn't true, but bear with me!)... and not for example. 2. You need to identify the next host by name, so in it's setup file, you need a ServerName mywiki.example.com or similar to identify it. Personally, I also set up specific log files for each site so you can tract traffic, error more easily. ErrorLog /var/log/apache2/mywiki.example.com-error.log CustomLog /var/log/apache2/mywiki.example.com-access.log combined Here's an example of a really simple one of mine ( and anyone who wants to redesign the site... please do! ) --8<-- ServerName dh.greengecko.co.nz ServerAdmin st...@greengecko.co.nz DocumentRoot /www/dh.greengecko.co.nz ErrorLog /var/log/apache2/dh.greengecko.co.nz-error.log CustomLog /var/log/apache2/dh.greengecko.co.nz-access.log combined Options All AllowOverride All Order deny,allow allow from all --8<-- 3. The above name must resolve. On the web server itself, I modify /etc/hosts to resolve all of these websites to the IP address of the server itself ( some use 127.0.0.1, but I don't ). This means that the webserver itself will come up without any errors, and be serving the multiple domains. 4. Permissions. simplest to ensure there's no problems - not something I'd recommend in a production environment... cd ( eg /www/dh.greengecko.co.nz ) sudo chown -R www-data:www-data . Which will ensure that your web server has permissions to access the content. Next, you need to ensure that your site name resolves to the client, so you need to run either a local DNS server, or to modify /etc/hosts on each client. I know what I'd do ( and probably use OpenDNS as resolvers to filter some of the traffic, no matter what abuse they make of the standards ). Not difficult once you get your head around it, just more steps than you'd expect. hth, Steve -- Steve Holdoway http://www.greengecko.co.nz MSN: st...@greengecko.co.nz GPG Fingerprint = B337 828D 03E1 4F11 CB90 853C C8AB AF04 EF68 52E0 signature.asc Description: This is a digitally signed message part
Re: link local wiki link in firefox
steve wrote: sudo apt-get install apache2 ( approximately ), and adjust the document root to point to the local folder containing the wiki. Then the wiki will be available at http://jupiter Which is what I do (: Thanks for all of yesterday's replies, seeing the apache "it works" page was simple, now I'm trying to set up a second site generally following this guide https://help.ubuntu.com/8.04/serverguide/C/httpd.html though have missed something or doing something wrong. I have done the following: *sudo cp /etc/apache2/sites-available/default /etc/apache2/sites-available/policymanual and then in /etc/apache2/sites-enabled/policymanual edited DocumentRoot and Directory to point to the correct location. **Then run "sudo a2ensite policymanual", and "sudo apache2ctl -t" returns Syntax OK. Browsing to http://jupiter/policymanual/index.html returns * Forbidden You don't have permission to access /policymanual/index.html on this server. Have checked that everyone has +x permissions on the DocumentRoot folder, and the index.html file exists. I'm not sure what I have missed that is important and where to go from here, any pointers or hints would be gratefully received. Cheers, Roger
Linux-ish jobs
We have a couple of jobs advertised at the moment for folks with some Linux skills and experience: http://seek.co.nz/job/tech/christchurch/16684516/51/1/ Technician. A junior role suitable for someone with a year or so of experience installing hardware and fixing network and desktop PC issues. The focus of the position is on MS systems and desktop support, but we have a (slowly) growing number of Linux servers in-house and are (slowly) moving in that direction. http://seek.co.nz/job/developer/christchurch/16687372/44/1/ Developer. Someone with experience in web development. No design skills required (we have others to do that) but strong skills in coding the back end of things. The majority of our work is in Joomla on a LAMP stack but we maintain a wide range of legacy systems for clients, so we often need to get on top of all sorts of systems (ColdFusion, .NET, Java, old PHP and more) at short notice. Get in touch off-list if you'd like my take on the company or the jobs. Apologies to those who find this too OT for their taste. Cheers, Roy.
Re: I have a dream of promiscuous sharing...
It's quite feasible. It shares a certain number of features with TCOS systems, and as such should be quite well understood - I mean, even I was able to block out the general characteristics of a RCO in 1998 working from scratch with no previous experience of such a device. Let's see, fping, a modernized finger to swap playlists and preferences, and a small Gaussian-or-Matrix solution engine to find the highest mutually rated track ... I could leave the Bluetooth details to those of you who know what is involved, and anyways, I don't have the money to buy the documentation, or even to download it ... ;) - let alone the device of which we speak!!! No, I don't know of any current project that does that, though I haven't been looking for the past few years ... I'd suggest starting it off in C, as it's still the Highest Common Denominator for most geeks, and while Java is nice, and even C# is nice, I wouldn't want to tie the device to a virtual machine - the exchange protocols, yes! - but playback, no. Just my 0.02c, and don't spend it all at once!!! Wesley Parish On Wed, 03 Feb 2010, cy...@xnet.co.nz wrote: > I watch my daughter who, (totally unlike me), is a fantastic people > person. > > When she meets anyone, she embarks on an exploration of common ground, > seeking common tastes putting aside her own to learn those of the other. > > But so many people have detached themselves from our community by > walling themselves in a closed garden of sound. > > Ear Phones In, Volume Up. > > Tiny embedded linux devices are becoming so common, so cheap these > days... > ...my dream is nearly here. > > What I want to create is this.. > > An ogg music player with blue tooth that comes packed to the brim with > a random selection of Creative Commons Licenced music. > > Jamendo would be my first port of call to find that music... > http://www.jamendo.com/ > > The UI allows you express your liking or disliking for the current > track playing. (Click up arrow or down once or several times.) > > Whenever you meet _anybody_ else with one of these devices, they pair > immediately and promiscuously and without asking begin exchanging the > highest rated tracks, deleting negatively rated tracks if space is needed. > > The highest mutually (A x B) rated track currently on both devices will > begin playing on both devices providing an instant talking point. (If > no common favoured tracks exist, the track currently being exchanged > will play.) > > Instant Party! > > An app on a PC will automagically do the same. > > Anyone want to play with? > > The todo list is something like this... > > * Start spreading the idea and getting feedback and suggestions. (Where > I'm at now). > > * Search for compatible/similar FOSS projects / components. > > * Start savanna / sourceforge site. > > * Define the blue tooth discovery and automatic pairing protocol. > > * Define & implement the track exchange protocol. > > * Find (and purchase) suitable embedded device(s) to implement this > on. > - Need audio out. > - enclosure & battery. > - display > - a few keys. > (maybe android, but a bit too expensive.) > > * Tweak an existing playback app to record preferences. > > * Define the preferences / checksum / path database format. > > I envisage making all these items as loosely coupled and redeployable > as possible. > > It'd perhaps be nice to make the odd buck from selling the hardware... but > I'm not fussed. I aim to make the protocols and implementations > completely open and GPL'd. > > The purpose of the project is create roving and merging and splitting and > spreading communities of sound. > > Further applications can be imagined like... > > * Set your player to play "whatever anybody near me is playing". > > * Set everybodies player in 3 or more person groups to play on > simultaneously on their speakers the mutually highest rated track. > Instant dance party! > > * Bands planning on touring a location can "inject" their best track into > the region a month or so before to drum up enthusiam. > > > John Carter > cy...@xnet.co.nz -- Clinersterton beademung, with all of love - RIP James Blish - George Kelischek - "To impress those high-tech computer types, tell them what an Ocarina really is: an animal-activated-solid-state-multi-frequency-sound-synthesizer." - Mau e ki, he aha te mea nui? You ask, what is the most important thing? Maku e ki, he tangata, he tangata, he tangata. I reply, it is people, it is people, it is people.
Re: I have a dream of promiscuous sharing...
i would buy one On Wed, Feb 3, 2010 at 9:53 PM, Hadley Rich wrote: > On Wed, 03 Feb 2010 21:36:27 you wrote: > > What I want to create is this.. > [..goodstuff..] > > Great stuff, really cool idea. I'd been happy to help out if I can. > > hads > -- > http://nicegear.co.nz > VoIP and Linux compatible hardware >
Re: I have a dream of promiscuous sharing...
On Wed, 03 Feb 2010 21:36:27 you wrote: > What I want to create is this.. [..goodstuff..] Great stuff, really cool idea. I'd been happy to help out if I can. hads -- http://nicegear.co.nz VoIP and Linux compatible hardware
Re: I have a dream of promiscuous sharing...
On Wed, 2010-02-03 at 21:36 +1300, cy...@xnet.co.nz wrote: > I watch my daughter who, (totally unlike me), is a fantastic people > person. > > When she meets anyone, she embarks on an exploration of common ground, > seeking common tastes putting aside her own to learn those of the other. > > But so many people have detached themselves from our community by > walling themselves in a closed garden of sound. > > Ear Phones In, Volume Up. > > Tiny embedded linux devices are becoming so common, so cheap these > days... > ...my dream is nearly here. > > What I want to create is this.. > > An ogg music player with blue tooth that comes packed to the brim with > a random selection of Creative Commons Licenced music. > > Jamendo would be my first port of call to find that music... > http://www.jamendo.com/ > > The UI allows you express your liking or disliking for the current > track playing. (Click up arrow or down once or several times.) > > Whenever you meet _anybody_ else with one of these devices, they pair > immediately and promiscuously and without asking begin exchanging the > highest rated tracks, deleting negatively rated tracks if space is needed. > > The highest mutually (A x B) rated track currently on both devices will > begin playing on both devices providing an instant talking point. (If > no common favoured tracks exist, the track currently being exchanged > will play.) > > Instant Party! > > An app on a PC will automagically do the same. > > Anyone want to play with? > > The todo list is something like this... > > * Start spreading the idea and getting feedback and suggestions. (Where > I'm at now). > > * Search for compatible/similar FOSS projects / components. > > * Start savanna / sourceforge site. > > * Define the blue tooth discovery and automatic pairing protocol. > > * Define & implement the track exchange protocol. > > * Find (and purchase) suitable embedded device(s) to implement this > on. > - Need audio out. > - enclosure & battery. > - display > - a few keys. > (maybe android, but a bit too expensive.) > > * Tweak an existing playback app to record preferences. > > * Define the preferences / checksum / path database format. > > I envisage making all these items as loosely coupled and redeployable > as possible. > > It'd perhaps be nice to make the odd buck from selling the hardware... but > I'm not fussed. I aim to make the protocols and implementations > completely open and GPL'd. > > The purpose of the project is create roving and merging and splitting and > spreading communities of sound. > > Further applications can be imagined like... > > * Set your player to play "whatever anybody near me is playing". > > * Set everybodies player in 3 or more person groups to play on > simultaneously on their speakers the mutually highest rated track. > Instant dance party! > > * Bands planning on touring a location can "inject" their best track into > the region a month or so before to drum up enthusiam. > > > John Carter > cy...@xnet.co.nz What a fabulous concept. Let me know if I can help at all... Steve
RE: Shared access folders in Ubuntu Karmic for Music and the like?
I created a directory in my /home called shared Created a group called localshare Added all the user to this Change the permissions on the /home/shared directory so localshare group had rights Create symbolic links for the users that don't know there away around Learn lots in the process and wonder why they don't do it for you as a matter of course Maurice > -Original Message- > From: Andrew Sands [mailto:and...@theatrix.org.nz] > Sent: Tuesday, 2 February 2010 11:43 p.m. > To: linux-users@it.canterbury.ac.nz; nz...@linux.net.nz > Subject: Shared access folders in Ubuntu Karmic for Music and > the like? > > > Anyone, > > Even though I do know that drive space is cheap, I'd like to try and > implement univerally shared folders for Music, Pictures and > Videos on my > recently installed Ubuntu Karmic. > > My search queries via Google only found references to people > sharing via > samba and not on the local machine. > > Any pointers to where I could look would be appreciated. > > regards, > > Andrew
I have a dream of promiscuous sharing...
I watch my daughter who, (totally unlike me), is a fantastic people person. When she meets anyone, she embarks on an exploration of common ground, seeking common tastes putting aside her own to learn those of the other. But so many people have detached themselves from our community by walling themselves in a closed garden of sound. Ear Phones In, Volume Up. Tiny embedded linux devices are becoming so common, so cheap these days... ...my dream is nearly here. What I want to create is this.. An ogg music player with blue tooth that comes packed to the brim with a random selection of Creative Commons Licenced music. Jamendo would be my first port of call to find that music... http://www.jamendo.com/ The UI allows you express your liking or disliking for the current track playing. (Click up arrow or down once or several times.) Whenever you meet _anybody_ else with one of these devices, they pair immediately and promiscuously and without asking begin exchanging the highest rated tracks, deleting negatively rated tracks if space is needed. The highest mutually (A x B) rated track currently on both devices will begin playing on both devices providing an instant talking point. (If no common favoured tracks exist, the track currently being exchanged will play.) Instant Party! An app on a PC will automagically do the same. Anyone want to play with? The todo list is something like this... * Start spreading the idea and getting feedback and suggestions. (Where I'm at now). * Search for compatible/similar FOSS projects / components. * Start savanna / sourceforge site. * Define the blue tooth discovery and automatic pairing protocol. * Define & implement the track exchange protocol. * Find (and purchase) suitable embedded device(s) to implement this on. - Need audio out. - enclosure & battery. - display - a few keys. (maybe android, but a bit too expensive.) * Tweak an existing playback app to record preferences. * Define the preferences / checksum / path database format. I envisage making all these items as loosely coupled and redeployable as possible. It'd perhaps be nice to make the odd buck from selling the hardware... but I'm not fussed. I aim to make the protocols and implementations completely open and GPL'd. The purpose of the project is create roving and merging and splitting and spreading communities of sound. Further applications can be imagined like... * Set your player to play "whatever anybody near me is playing". * Set everybodies player in 3 or more person groups to play on simultaneously on their speakers the mutually highest rated track. Instant dance party! * Bands planning on touring a location can "inject" their best track into the region a month or so before to drum up enthusiam. John Carter cy...@xnet.co.nz
