Newest Debian images from eLinux missing ntp and other packages

I have been working the BBB Rev B and C for over a year, and I’ve been using the Debian images provided by eLinux and Beagleboard, available from -

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Releases

and http://beagleboard.org/latest-images

In the most recent builds from 2015-11-03, I’ve been having a lot of trouble with missing system tools and packages.
Some examples include -

  • wrong date and time set due to ntp service not being installed, installing ntp resolves this issue
  • inability to connect using supported wifi adapter due to missing wireless-tools package
  • missing DNS support which causes apt-get to fail as it is unable to correctly resolve the IP addresses for the rcn.ee repos included in the builds
  • missing /sbin directory in PATH, including missing ifconfig command, adding /sbin to path resolves these issues

Did I miss some announcement or release notes about these releases that says they are lighter than previous builds?

Why didn’t I have most of these issues with previous builds?
IIRC, all the builds I used before included ntp, /sbin in the PATH, and DNS support, and wireless worked OOTB (after editing /etc/network/interfaces)

Thanks all for any help or guidance offered.

I have been working the BBB Rev B and C for over a year, and I've been using
the Debian images provided by eLinux and Beagleboard, available from -

Beagleboard:BeagleBoneBlack Debian - eLinux.org

and Latest Software Images - BeagleBoard

In the most recent builds from 2015-11-03, I've been having a lot of trouble
with missing system tools and packages.
Some examples include -

Please include the file name, there's dozen images...

- wrong date and time set due to ntp service not being installed, installing
ntp resolves this issue

wheezy: ntpdate
jessie: systemd-timesync

- inability to connect using supported wifi adapter due to missing
wireless-tools package

your using the "console" image...

- missing DNS support which causes apt-get to fail as it is unable to
correctly resolve the IP addresses for the rcn.ee repos included in the
builds

okay, this is od..

- missing /sbin directory in PATH, including missing ifconfig command,
adding /sbin to path resolves these issues

yeap, this is the "console" image, can't fix this as patch isn't installed..

Did I miss some announcement or release notes about these releases that says
they are lighter than previous builds?

Why didn't I have most of these issues with previous builds?
IIRC, all the builds I used before included ntp, /sbin in the PATH, and DNS
support, and wireless worked OOTB (after editing /etc/network/interfaces)

Based on that, it sounds like your using the "console" over the
"lxde/lxqt" image. The goal with the "console" image was to be as
small but yet "flash" the eMMC.. Not everyone likes to "apt-get
remove xyz" instead they want something very small, and wireless tools
are not on that requirement list..

Regards,

Thanks so much for the fast response!

I’m helping my coworker out, so I had to ask him which images he used.

But I did a bit of research and confirmed your comments back, and it all makes perfect sense now. =)

We were using the “BBB-eMMC-flasher-debian-7.9-console-armhf-2015-11-03-2gb.img” image, which, as you pointed as, is a console release.
Thanks for clarifying this - I totally understand and appreciate the need for a lightweight image, so I didn’t mean to suggest these things should be added to the console release.
Same goes for wireless-tools.

With the above image, I confirmed the lack of sbin and wrong date on boot up, no biggie.
I tried syncing the time, but I got command not found and didn’t find it in sbin, but installing some version of ntp seems to resolve that.

As for the issue we faced with DNS issues and issues updating the repo, it was the exact same issue in this post - https://groups.google.com/forum/#!category-topic/beagleboard/ubuntu/DjFqxreT1AA
At the time, I had to hard code the IP for the missing repos (I think it was also the ports.ubuntu repo) and it worked.
But I just tested this on a fresh flash and wasn’t able to recreate the issue, so in my test case, everything worked great.
I’ll dig a bit more on this but I think this may have been a weird “freak” occurrence.

Thanks again for your response and help, now back to my BBB!

Have a good one, Robert

Thanks so much for the fast response!

I'm helping my coworker out, so I had to ask him which images he used.

But I did a bit of research and confirmed your comments back, and it all
makes perfect sense now. =)

We were using the
"BBB-eMMC-flasher-debian-7.9-console-armhf-2015-11-03-2gb.img" image, which,
as you pointed as, is a console release.
Thanks for clarifying this - I totally understand and appreciate the need
for a lightweight image, so I didn't mean to suggest these things should be
added to the console release.
Same goes for wireless-tools.

With the above image, I confirmed the lack of sbin and wrong date on boot
up, no biggie.

sbin:

install patch: (sudo apt-get install patch)

sudo su
cd /
patch -p1 < /opt/scripts/mods/debian-add-sbin-usr-sbin-to-default-path.diff

date on boot:

wheezy:
we rely on ntpdate, which needs the network setup first, so if you
search journalctl you'll notice ntpdate failing..

jessie:
we can use systemd-timesync, since systemd knows when the network is
connected, it'll automatically sync the time, plus it'll backup the
clock between reboots. So it's the most accurate..

Overal, we preseed the date so the "2015-11-03" image will always have
a clock after "2015-11-03" and not 1970...

I tried syncing the time, but I got command not found and didn't find it in
sbin, but installing some version of ntp seems to resolve that.

As for the issue we faced with DNS issues and issues updating the repo, it
was the exact same issue in this post -
Redirecting to Google Groups
At the time, I had to hard code the IP for the missing repos (I think it was
also the ports.ubuntu repo) and it worked.
But I just tested this on a fresh flash and wasn't able to recreate the
issue, so in my test case, everything worked great.
I'll dig a bit more on this but I think this may have been a weird "freak"
occurrence.

For that, i'd just run:

sudo ifconfig -a
sudo dhclient eth0

in the wheezy/lxde we have wicd setting up eth0 automaticly (and in
jessie/lxqt we have connman)

Regards,