-Original Message-
From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On
Behalf Of Robert Nelson
Sent: Thursday, April 23, 2020 9:31 PM
To: Beagle Board
Subject: Re: [beagleboard] When was connmanctl introduced?
>On Thu, Apr 23, 2020 at 10:21 PM wrote:
>>
>> Can som
Can someone please point me to the history of connmanctl and when it was
introduced for Debian on BBB? All of the legacy documentation circa 2015
shows a simple entry in /etc/network/interfaces but clearly connmanctl is
the way to go now.
Thanks!
--
For more options, visit http://beagleboar
I am using this derivative of Robert's eMMC -> img file script
https://elinux.org/BeagleBone_Black_Extracting_eMMC_contents
and it runs instantly and creates a 1K image file. I suspect something has
changed since that Wiki entry was created.
I have tested this on both Element 14 and Beagleboar
Thank you! That is good to hear. I have not tried USB-to-SSD yet but that
is next on my list. Nikon used to make micro hard disks which were the
same size as a Compact Flash drive. It would be fantastic is we had more
options on the BBB so I am continuing to explore.
On Monday, December 30
Has anyone attempted using an SSD card like the NVMe interface cards from
Samsung EVO?
I would love to be able to use storage that is more reliable than SD cards.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Gr
images?
On Thu, Dec 12, 2019 at 8:07 PM Bryan Miller wrote:
>
> Is there a manifest describing contents somewhere online? I am scratching my
> head as to why "IoT" is so much larger than "Console".
Yeap, here you go:
https://github.com/beagleboard/image-build
Is there a manifest describing contents somewhere online? I am scratching my
head as to why "IoT" is so much larger than "Console".
-Original Message-
From: Robert Nelson [mailto:robertcnel...@gmail.com]
Sent: Thursday, December 12, 2019 5:29 PM
To: Beagle Board
Cc: bryan.mil...@owasp.o
Sorry, that should read fsck not fdisk.
On Thursday, December 12, 2019 at 11:30:15 AM UTC-7, Bryan Miller wrote:
>
> You are both correct. I have six BBBs running and forgot this one was
> still using an SD card due to some Docker images I am running. The others
> are all on De
Thank you Robert!
I will likely run node.js inside docker images spun up via GitLab runner so
that is perfect!
Cheers!
Bryan
-Original Message-
From: Robert Nelson [mailto:robertcnel...@gmail.com]
Sent: Thursday, December 12, 2019 5:29 PM
To: Beagle Board
Cc: bryan.mil...@owasp.org
Su
I really like the Debian Stretch and Buster images but they take up the
entire 4GB on BBB. Is anyone aware of slightly slimmed down derivatives of
these versions?
I want to install Docker and Free Radius but there is absolutely no room!
Cheers!
--
For more options, visit http://beagleboard.o
I was logged in as root.
On Thursday, December 12, 2019 at 8:19:20 AM UTC-7, jonnymo wrote:
>
> I agree with Tarmo in that your root is showing what looks like a 32GB SD
> card and not the 4GB eMMC.
> you can run 'df -h' to see the space in a more user friendly format.
>
> Both reboot and ping ma
You are both correct. I have six BBBs running and forgot this one was
still using an SD card due to some Docker images I am running. The others
are all on Debian 9.11 in eMMC.
I ran fdisk and it shows the SD card is indeed failing. I am going to dd
off as much as I can before it complete
I have been monitoring the space. I thought it was /tmp but the usage is
super low:
debian@radius:~$ df
Filesystem 1K-blocksUsed Available Use% Mounted on
udev 219552 0219552 0% /dev
tmpfs 494966156 43340 13% /run
/dev/mmcblk0p1 30714340 42
I am using eMMC. Why would the system work for 4-6 days before dying if it
was broken?
I will make an image of my system and dd it over to another BBB. That will
determine if it is hardware or not.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message becau
I am running Debian 9.11 (4.14.108-ti-r124) on BBB and it runs fine for
about a week and then Bash no longer can find commands and it throws errors
upon every subsequent command. Commands result in one of two errors
depending upon the command. Here are two recent examples:
$debian:/opt/tools$
15 matches
Mail list logo