Reinstalling Applications after upgrading to Linux ubuntu-armhf 3.8.13-bone28

195 views
Skip to first unread message

Bit Pusher

unread,
Nov 7, 2013, 5:49:43 PM11/7/13
to beagl...@googlegroups.com
I am interesting in downloading and upgrading my kernel to Linux ubuntu-armhf 3.8.13-bone28 from Linux ubuntu-armhf 3.8.13-bone20.
I have been working in 20 for a few months and have installed quite a few applications. Are there any directions on:
1) Listing current apt-get packages that need to be re-installed (without listing dependencies).
2) What directories besides /etc, /home, /lib/firmware and /boot, etc should be backed up and re-copied to new system
3) Any other considerations for the backup.
This could be a good area for a tutorial; any takers? I could try, but I'm not knowledgeable enough in kernel/driver issues.
Related question: how often should one be considering going through this process? Can it be scripted? Thanks.
-Bit Pusher

Robert Nelson

unread,
Nov 7, 2013, 6:00:33 PM11/7/13
to Beagle Board
On Thu, Nov 7, 2013 at 4:49 PM, Bit Pusher <ken.w....@gmail.com> wrote:
> I am interesting in downloading and upgrading my kernel to Linux
> ubuntu-armhf 3.8.13-bone28 from Linux ubuntu-armhf 3.8.13-bone20.

If it helps, since it sounds like your starting over to "upgrading"
your system, this time maybe start with an image with easy kernel
upgrades?

http://elinux.org/BeagleBoardUbuntu#Demo_Image

(or if your in a none linux environment..)
http://elinux.org/BeagleBoardUbuntu#eMMC:_BeagleBone_Black

as kernel upgrades are as easy as:

wget http://rcn-ee.net/deb/raring-armhf/v3.8.13-bone28/install-me.sh
sudo /bin/bash install-me.sh


> I have been working in 20 for a few months and have installed quite a few
> applications. Are there any directions on:
> 1) Listing current apt-get packages that need to be re-installed (without
> listing dependencies).

dpkg --get-selections > /backup/installed-software.log

sudo aptitude install $(cat /backup/installed-software.log)

> 2) What directories besides /etc, /home, /lib/firmware and /boot, etc should
> be backed up and re-copied to new system

ignore /boot/ the new image should populate the bootloader...

> 3) Any other considerations for the backup.
> This could be a good area for a tutorial; any takers? I could try, but I'm
> not knowledgeable enough in kernel/driver issues.
> Related question: how often should one be considering going through this
> process? Can it be scripted? Thanks.

ah, store your application/scripts off the device and into a private
git/github/etc location... ;)

Regards,

--
Robert Nelson
http://www.rcn-ee.com/

Kenneth Martin

unread,
Nov 7, 2013, 8:26:35 PM11/7/13
to beagl...@googlegroups.com, ken Martin
Robert, thank you; this information should prove to be very helpful. I
will probably take some time to try and do it right so that in time it
can be shared. Thanks again.
-Ken

Kenneth Martin

unread,
Nov 8, 2013, 4:02:39 PM11/8/13
to beagl...@googlegroups.com
Robert, I seem to be having bad luck and back to ground 0 with nothing
running. Could you please send me the preferred link to start completely
from scratch? That is reformatting the SD card, installing everything,
etc. I am aiming at a system that boots the SD card. Sorry to bother you
again, but if you have the time, this would real helpful. A lot of the
material I google seems to be pointing at other systems, systems that
flash to the eMMC, systems that need to be compiled, systems that are
images to be dd'd in, etc. The links below seem to be for the kernel,
but not for the complete system. Thanks again.
-Ken

On 13-11-07 06:00 PM, Robert Nelson wrote:

Robert Nelson

unread,
Nov 8, 2013, 4:39:01 PM11/8/13
to Beagle Board
On Fri, Nov 8, 2013 at 3:02 PM, Kenneth Martin <mar...@granitesemi.com> wrote:
> Robert, I seem to be having bad luck and back to ground 0 with nothing
> running. Could you please send me the preferred link to start completely
> from scratch? That is reformatting the SD card, installing everything, etc.
> I am aiming at a system that boots the SD card. Sorry to bother you again,
> but if you have the time, this would real helpful. A lot of the material I
> google seems to be pointing at other systems, systems that flash to the
> eMMC, systems that need to be compiled, systems that are images to be dd'd
> in, etc. The links below seem to be for the kernel, but not for the complete
> system. Thanks again.

The trick is to scroll down a little bit past all the
background/advanced stuff etc. It's right there because everyone
asked for it upfront, when it wasn't there..

First, if your development system is linux based (non windows/osx
etc..) and you want to install 13.04, use this link..

http://elinux.org/BeagleBoardUbuntu#Raring_13.04_armhf

(it's the first section under the #Demo_Image header tag..)

Then just follow the download/unpacking/run setup_sdcard.sh
instructions.. This will create a bootable microSD card.

BTW: since your eMMC is messed up, the first thing you should run when
booting this image is run:

/boot/uboot/tools/scripts/beaglebone-black-copy-microSD-to-eMMC.sh



If you on the other non-linux platforms use:

http://elinux.org/BeagleBoardUbuntu#eMMC:_BeagleBone_Black

Which is, download, extract, use write img to your microSD..

In either case, since your eMMC is messed up, make sure to hold down
the boot push button..

Kenneth Martin

unread,
Nov 8, 2013, 4:59:27 PM11/8/13
to beagl...@googlegroups.com, Ken Martin
Robert, just for your info: after a day, I was unsuccessful with below. So I decided to go back to an image install. From
http://www.armhf.com/index.php/getting-started-with-ubuntu-img-file/
I dfollowed the link to
http://www.armhf.com/index.php/download/
and downloaded http://s3.armhf.com/debian/saucy/bone/ubuntu-saucy-13.10-armhf-3.8.13-bone28.img.xz
which I believe is your image file. I installed it my sd card using xz -cd *.xz > dev/sdf
mounted the new sd card (looked fine), copied in my old /etc/network/intefaces file
plugged it into my beagle and I am back where I was about 3 months ago with all ports closed.

> nmap -A beagle

Starting Nmap 6.00 ( http://nmap.org ) at 2013-11-08 16:45 EST
Nmap scan report for beagle (192.168.1.128)
Host is up (0.0022s latency).
rDNS record for 192.168.1.128: beaglebone.local
All 1000 scanned ports on beagle (192.168.1.128) are closed

Service detection performed. Please report any incorrect results at http://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 0.20 seconds
>

If I plug in my bone20 sd card and do the same, I get

> nmap -A beagle

Starting Nmap 6.00 ( http://nmap.org ) at 2013-11-08 16:54 EST
Nmap scan report for beagle (192.168.1.128)
Host is up (0.0021s latency).
rDNS record for 192.168.1.128: beaglebone.local
Not shown: 999 closed ports
PORT   STATE SERVICE VERSION
22/tcp open  ssh     OpenSSH 6.1p1 Debian 4 (protocol 2.0)
| ssh-hostkey: 1024 5d:84:2e:7c:c4:1a:10:ee:1c:d3:97:76:66:b5:92:8f (DSA)
|_2048 08:8b:d8:8e:4c:fc:d2:74:f1:46:e9:6e:b8:28:eb:ab (RSA)
Service Info: OS: Linux; CPE: cpe:/o:linux:kernel

Service detection performed. Please report any incorrect results at http://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 0.55 seconds
>

so I believe my network is fine.

I have no idea why I can't connect with your images, but without being able to connect, I have no way of figuring out what is going wrong. Any thoughts on
uEnv.txt not being compatible. Any thoughts about the best way to try and get a serial usb link going? I will keep trying, but am totally lost on what to do. Everything seems to be going right until I try to login in over the internet. Your image seems to boot up fine, with the lights doing the right things, and booting down after 10 seconds when holding the reset key down etc., just can't get into it over the ethernet.

-Ken


On 13-11-07 06:00 PM, Robert Nelson wrote:

Robert Nelson

unread,
Nov 8, 2013, 8:18:03 PM11/8/13
to Beagle Board


On Nov 8, 2013 6:26 PM, "Kenneth Martin" <mar...@granitesemi.com> wrote:
>
> Robert, just for your info: after a day, I was unsuccessful with below. So I decided to go back to an image install. From
> http://www.armhf.com/index.php/getting-started-with-ubuntu-img-file/
> I dfollowed the link to
> http://www.armhf.com/index.php/download/
> and downloaded http://s3.armhf.com/debian/saucy/bone/ubuntu-saucy-13.10-armhf-3.8.13-bone28.img.xz
> which I believe is your image file. I

It's not...

> --
> 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 beagleboard...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

Kenneth Martin

unread,
Nov 9, 2013, 8:34:10 PM11/9/13
to beagl...@googlegroups.com, ken Martin
My apologies; could you possibly point me to a link to one of your images? or would you recommend keep working on being able to download and compile an image myself in order to simplify staying current? I appreciate whatever time you have to point me in a direction as I understand the demands on your considerable expertise.
-Ken
You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/FjBRQ1RfqzU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.

Kenneth Martin

unread,
Nov 11, 2013, 5:53:30 PM11/11/13
to beagl...@googlegroups.com
Robert, I'm finally back up but now with a bone28 based on your kernel
so I should be able to stay current. For your info, there was some very
weird stuff happening; when the board came up, nmap -A from my desktop
couldn't find the board, nmap -Pn stated all ports were closed, but by
chance after about 10 minutes I ran nmap -Pn again, and port 22 was
open! and I was able to log in. It might have had something to do with
setting the clock? in case your interested the last part of
/var/log/syslog is below. Anyways, thanks for the help and now that I am
up and running I should not have to bother you very much (at least not
before I start writing drivers - but that should be many months away).
-Ken

p.s. do you know if /etc/rc.local is run at boot? I have in it currently:

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
service ssh start
iptables -A OUTPUT -j ACCEPT
iptables -A INPUT -j ACCEPT
iptables -L > /home/martin/iptables_log

exit 0
~\>

but since nothing was written to /home/martin/iptables_log, I'm guessing
it was not run. No need to get back to me on this as I've bothered you
enough; again appreciated.

~\> cat /var/log/syslog | tail -100
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.119538] omap_hsmmc mmc.5:
pins are not configured from the driver
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.126508] hub 1-0:1.0: state 7
ports 1 chg 0000 evt 0000
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.126586] hub 1-0:1.0: hub_suspend
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.126629] usb usb1: bus
auto-suspend, wakeup 1
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.153998]
of_get_named_gpio_flags: can't parse gpios property
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.154024]
of_get_named_gpio_flags: can't parse gpios property
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.154039]
of_get_named_gpio_flags: can't parse gpios property
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.154094] gpio-rctrl rstctl.4:
gpio_rctrl_request eMMC_RSTn
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.160341] omap_hsmmc mmc.11:
Got rstctl (gpio:#0 name eMMC_RSTn) label:eMMC_RSTn
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.168367] gpio-rctrl rstctl.4:
gpio_rctrl_deassert eMMC_RSTn
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.174878] edma-dma-engine
edma-dma-engine.0: allocated channel for 0:3
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.182061] edma-dma-engine
edma-dma-engine.0: allocated channel for 0:2
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.189626] mmc.11 supply
vmmc_aux not found, using dummy regulator
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.196427] omap_hsmmc mmc.11:
pins are not configured from the driver
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.230429] pinctrl-single
44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux;
cannot claim for gpio-leds.8
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.242181] pinctrl-single
44e10800.pinmux: pin-21 (gpio-leds.8) status -22
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.249497] pinctrl-single
44e10800.pinmux: could not request pin 21 on device pinctrl-single
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.258486] leds-gpio
gpio-leds.8: pins are not configured from the driver
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.265769]
of_get_named_gpio_flags exited with status 53
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.265792]
of_get_named_gpio_flags exited with status 54
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.265812]
of_get_named_gpio_flags exited with status 55
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.265831]
of_get_named_gpio_flags exited with status 56
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.265860]
of_get_named_gpio_flags exited with status 53
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.266093]
of_get_named_gpio_flags exited with status 54
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.266296]
of_get_named_gpio_flags exited with status 55
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.266518]
of_get_named_gpio_flags exited with status 56
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.267138] ledtrig-cpu:
registered to indicate activity on CPUs
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.274019] edma-dma-engine
edma-dma-engine.0: allocated channel for 0:36
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.281301] omap-sham
53100000.sham: hw accel on OMAP rev 4.3
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.289926] omap-aes
53500000.aes: OMAP AES hw accel rev: 3.2
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.296508] edma-dma-engine
edma-dma-engine.0: allocated channel for 0:5
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.303691] mmc0: host does not
support reading read-only switch. assuming write-enable.
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.312282] edma-dma-engine
edma-dma-engine.0: allocated channel for 0:6
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.320621] usbcore: registered
new interface driver usbhid
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.326584] usbhid: USB HID core
driver
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.330940] mmc0: new high speed
SDHC card at address b368
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.338091] ashmem: initialized
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.342601] logger: created 256K
log 'log_main'
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.347531] mmcblk0: mmc0:b368
LEXAR 14.9 GiB
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.353726] logger: created 256K
log 'log_events'
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.358944] mmcblk0: p1 p2
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.363729] logger: created 256K
log 'log_radio'
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.369101] logger: created 256K
log 'log_system'
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.377368]
of_get_named_gpio_flags exited with status 59
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.378816] davinci_evm
sound.14: nxp-hdmi-hifi <-> 48038000.mcasp mapping ok
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.391011] TCP: cubic registered
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.394720] NET: Registered
protocol family 10
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.400892] NET: Registered
protocol family 17
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.406073] Key type
dns_resolver registered
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.410853] VFP support v0.3:
implementor 41 architecture 3 part 30 variant c rev 3
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.419031] ThumbEE CPU
extension supported.
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.423594] Registering SWP/SWPB
emulation handler
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.429746] registered taskstats
version 1
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.436632]
of_get_named_gpio_flags: can't parse gpios property
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.436666] tilcdc 4830e000.fb:
No power control GPIO
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.456236] mmc1: BKOPS_EN bit
is not set
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.463225] mmc1: new high speed
MMC card at address 0001
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.469855] mmcblk1: mmc1:0001
MMC02G 1.78 GiB
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.475048] mmcblk1boot0:
mmc1:0001 MMC02G partition 1 1.00 MiB
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.481650] mmcblk1boot1:
mmc1:0001 MMC02G partition 2 1.00 MiB
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.490181] mmcblk1: p1 p2
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.496072] mmcblk1boot1:
unknown partition table
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.503400] mmcblk1boot0:
unknown partition table
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.551318] tilcdc 4830e000.fb:
found TDA19988
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.556821] [drm] Supports
vblank timestamp caching Rev 1 (10.10.2010).
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.563797] [drm] No driver
support for vblank timestamp query.
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.570428] tilcdc 4830e000.fb:
No connectors reported connected with modes
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.577763] [drm] Cannot find
any crtc or sizes - going 1024x768
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.598194] Console: switching
to colour frame buffer device 128x48
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.614170] tilcdc 4830e000.fb:
fb0: frame buffer device
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.619869] tilcdc 4830e000.fb:
registered panic notifier
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.625647] [drm] Initialized
tilcdc 1.0.0 20121205 on minor 0
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.681105] davinci_mdio
4a101000.mdio: davinci mdio revision 1.6
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.687553] davinci_mdio
4a101000.mdio: detected phy mask fffffffe
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.695277] libphy:
4a101000.mdio: probed
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.699578] davinci_mdio
4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.709468] Detected MACID =
90:59:af:69:0f:f0
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.714165] cpsw
4a100000.ethernet: NAPI disabled
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.721283] omap_rtc
44e3e000.rtc: setting system clock to 2000-01-01 00:00:01 UTC (946684801)
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.737726] ALSA device list:
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.740879] #0: TI BeagleBone
Black
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.757456] EXT4-fs (mmcblk0p2):
mounted filesystem with ordered data mode. Opts: (null)
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.766043] VFS: Mounted root
(ext4 filesystem) readonly on device 179:2.
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.774910] devtmpfs: mounted
Jan 1 00:00:08 ubuntu-armhf kernel: [ 2.778469] Freeing init memory:
292K
Jan 1 00:00:08 ubuntu-armhf kernel: [ 6.810510] net eth0:
initializing cpsw version 1.12 (0)
Jan 1 00:00:08 ubuntu-armhf kernel: [ 6.816686] net eth0: phy found
: id is : 0x7c0f1
Jan 1 00:00:08 ubuntu-armhf kernel: [ 6.816725] libphy: PHY
4a101000.mdio:01 not found
Jan 1 00:00:08 ubuntu-armhf kernel: [ 6.821810] net eth0: phy
4a101000.mdio:01 not found on slave 1
Jan 1 00:00:08 ubuntu-armhf kernel: [ 6.884975] IPv6:
ADDRCONF(NETDEV_UP): eth0: link is not ready
Jan 1 00:00:08 ubuntu-armhf kernel: [ 7.140940] EXT4-fs (mmcblk0p2):
re-mounted. Opts: errors=remount-ro
Jan 1 00:00:08 ubuntu-armhf failsafe: Failsafe of 120 seconds reached.
Jan 1 00:00:08 ubuntu-armhf kernel: [ 9.892624] libphy:
4a101000.mdio:00 - Link is Up - 100/Full
Jan 1 00:00:08 ubuntu-armhf kernel: [ 9.892695] IPv6:
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Nov 11 21:57:30 ubuntu-armhf ntpdate[331]: step time server 91.189.94.4
offset 437522234.429057 sec
Nov 11 21:57:46 ubuntu-armhf ntpdate[512]: adjust time server
91.189.94.4 offset -0.000883 sec
Nov 11 21:59:24 ubuntu-armhf cron[543]: (CRON) INFO (pidfile fd = 3)
Nov 11 21:59:24 ubuntu-armhf cron[585]: (CRON) STARTUP (fork ok)
Nov 11 21:59:24 ubuntu-armhf cron[585]: (CRON) INFO (Running @reboot jobs)
Nov 11 22:17:02 ubuntu-armhf CRON[854]: (root) CMD ( cd / && run-parts
--report /etc/cron.hourly)
~\>

Reply all
Reply to author
Forward
0 new messages