Correction it was OwnCloud not open cloud.
On Jun 17, 2014 4:45 PM, "Wilfredo Nieves" <[email protected]> wrote:

> In all honesty I don't think you have to disable the default web server. A
> few months back I picked up a my book live nas and cracked it open to find
> that the hardware was similar to BBB. So I decided to see if I could do
> something similar with the BBB and I got it working but I don't remember
> having to disable the default web server. I may be wrong though as I did
> not take notes on the procedure because I figured it was a one time deal
> and did it just to see if it could be done. Any ways all I remember doing
> was following a guide to install open cloud on debian. So you may want to
> look at some of those guides and see if you can get your web server
> working.
> On Jun 17, 2014 9:05 AM, "Michael Thompson" <[email protected]>
> wrote:
>
>> Hi William, I have actually been reading about how to do a netinstall all
>> morning. Never a better time than now to learn something useful, right? I
>> think I may give this a go in the next few days. Thanks for the advice :)
>>
>> On Tuesday, June 17, 2014 8:44:50 AM UTC-7, William Hermans wrote:
>>
>>> Micheal,
>>>
>>> The best solution IMHO would be to start with a minimal or bare
>>> filesystem, and install *only* the packages that you need. But this means
>>> you're going to have to take time and learn how to do so. Using these
>>> instructions: http://eewiki.net/display/linuxonarm/BeagleBone+Black You
>>> would skip anything related to compiling / copying over the kernel or
>>> u-boot and do something like the following
>>>  . . .
>>>
>>> 1) remove the rootfs partition on the sdcard.
>>> 2) create a new partition on the sdcard.
>>> 3) extract the barefs rootfs image onto this new partition.
>>> 4) follow the directions for modifying configuration file on the newly
>>> extracted rootfs so Debian knows how to behave.
>>> 5) once logged into the new system su to root, and apt-get install what
>>> you need.
>>>
>>> *NOW* do keep in mind it is rather early for me ( have not had my
>>> morning coffee so to speak ), and I have not personally tested, or given
>>> this much thought aside from the occasional musing. So I may not have
>>> remembered *EVERYTHING*. However this is the gist of how to achieve what I
>>> propose.
>>>
>>> Eventually though, you're going to have to get your hands dirty and
>>> learn this stuff. Maybe not for this project, but perhaps for another. You
>>> may as well start learning now.
>>>
>>>
>>> On Tue, Jun 17, 2014 at 8:24 AM, Michael Thompson <
>>> [email protected]> wrote:
>>>
>>>> Yeah, that's why I am going to retry it later today. I followed the
>>>> last instructions before I left for work and didn't keep notes on which
>>>> steps failed and why. I am going to start from a fresh install this
>>>> afternoon and keep track of what happens so that I will be able to give
>>>> more detail instead of just posting a dejected "Nothing works!!" reply.
>>>> Sorry for being whiney, I'm just getting frustrated :(
>>>>
>>>> On Tuesday, June 17, 2014 8:19:52 AM UTC-7, William Hermans wrote:
>>>>
>>>>> It might be helpful if you told us why it does not work.
>>>>>
>>>>>
>>>>> On Tue, Jun 17, 2014 at 8:15 AM, Michael Thompson <
>>>>> [email protected]> wrote:
>>>>>
>>>>>> This didn't work either. I am losing all hope that I will ever get
>>>>>> this thing to work. I guess I will try again later today and maybe some
>>>>>> magic will happen.
>>>>>>
>>>>>> On Monday, June 16, 2014 9:54:22 PM UTC-7, crazybucket wrote:
>>>>>>
>>>>>>> You do use the /var/www directory for apache. The problem, as
>>>>>>> someone else mentioned, is that there is another webserver running on it
>>>>>>> out of the box, so you need to disable it and the associated mess with
>>>>>>> systemctl:
>>>>>>>
>>>>>>> systemctl disable cloud9.service
>>>>>>> systemctl disable gateone.service
>>>>>>> systemctl disable bonescript.service
>>>>>>> systemctl disable bonescript.socket
>>>>>>> systemctl disable bonescript-autorun.service
>>>>>>> systemctl disable avahi-daemon.service
>>>>>>> systemctl disable gdm.service
>>>>>>> systemctl disable mpd.service
>>>>>>>
>>>>>>>
>>>>>>> Now we can use the beaglebone more like a headless linux machine.
>>>>>>> Last time I played with it, apache was already installed (!) but 
>>>>>>> running on
>>>>>>> an alternate port. So lets fix that - open /etc/apache2/ports.conf and
>>>>>>> change this:
>>>>>>>
>>>>>>> NameVirtualHost *:8080
>>>>>>> Listen 8080
>>>>>>>
>>>>>>> to this:
>>>>>>>
>>>>>>>
>>>>>>> NameVirtualHost *:80
>>>>>>> Listen 80
>>>>>>>
>>>>>>>
>>>>>>> Save it and restart apache:
>>>>>>>
>>>>>>>
>>>>>>> apachectl graceful
>>>>>>>
>>>>>>>
>>>>>>> Then you should see the "It works!" page by navigating to the
>>>>>>> beaglebone's IP address. Apache runs just fine on the beaglebone - much
>>>>>>> faster than the pentium II that I used to to learned linux on...
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Saturday, June 7, 2014 12:07:15 AM UTC-5, Michael Thompson wrote:
>>>>>>>>
>>>>>>>> I flashed Debian to the eMMC and it seems to be working fine. My
>>>>>>>> plan is to host a small web page using Apache. I installed Apache and 
>>>>>>>> using
>>>>>>>> the IP address the BeagleBone 101 loads fine from outside my network.
>>>>>>>>
>>>>>>>> So, my question is, in what directory do I save my index.html file
>>>>>>>> in order to see it as the default page served by Apache? There are no 
>>>>>>>> files
>>>>>>>> in the /var/www/ directory so I am confused. On my Linux Mint (Debian
>>>>>>>> edition) all I had to do was save my index file in the www directory.
>>>>>>>>
>>>>>>>> Anyone know where I am going wrong?
>>>>>>>>
>>>>>>>> Thanks!!
>>>>>>>>
>>>>>>>  --
>>>>>> For more options, visit http://beagleboard.org/discuss
>>>>>> ---
>>>>>> You received this message because you are subscribed to the Google
>>>>>> Groups "BeagleBoard" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>> send an email to [email protected].
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>
>>>>>
>>>>>  --
>>>> For more options, visit http://beagleboard.org/discuss
>>>> ---
>>>> You received this message because you are subscribed to the Google
>>>> Groups "BeagleBoard" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to [email protected].
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>  --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to