What is the script i can put in my schedule to have it announce the time hourly?
Thanks
···
On Nov 18, 2013, at 12:00 PM, app_rpt-users-request@ohnosec.org wrote:
Send App_rpt-users mailing list submissions to
app_rpt-users@ohnosec.orgTo subscribe or unsubscribe via the World Wide Web, visit
ohnosec.org
or, via email, send a message with subject or body 'help' to
app_rpt-users-request@ohnosec.orgYou can reach the person managing the list at
app_rpt-users-owner@ohnosec.orgWhen replying, please edit your Subject line so it is more specific
than "Re: Contents of App_rpt-users digest..."Today's Topics:
1. Re: e2fsck (Benjamin L. Naber)
----------------------------------------------------------------------
Message: 1
Date: Mon, 18 Nov 2013 11:45:24 -0500
From: "Benjamin L. Naber" <Benjamin@kb9lfz.com>
To: "app_rpt-users@ohnosec.org" <app_rpt-users@ohnosec.org>
Subject: Re: [App_rpt-users] e2fsck
Message-ID: <1384793124.3179.8.camel@benjamin-hp>
Content-Type: text/plain; charset="UTF-8"That's what it appears to me.
A ham this morning told me the problem maybe the person making the
distro images is using a windows machine, not linux, and he is making
the .img files for FAT when they *should* be ext2I've been trying everything that I can find to do the filesystem check,
but every embedded distro I've tried doesn't support checking DOS or FAT
files systems.~Benjamin, KB9LFZ
allstar node 28569On Mon, 2013-11-18 at 09:37 -0600, Geoff wrote:
On 11/18/2013 07:44 AM, Benjamin L. Naber wrote:
this is coming up when trying to boot a new install of Limey Linux
last time I checked, e2fsck is for EXT2 and other Linux extensions, not
FAT.Booting comes to a dead halt when the e2fsck checktime has been
reached.Any way around this, or disable this checking when booting?
I'm no expert on Limey Linux, but last I checked, when Linux formats and
prepares a drive, it is most certainly -not- in a FAT format.e2fsck is probably checking your drive on -every- bootup because there's
an issue with the drive.From 'man e2fsck' :
DESCRIPTION
e2fsck is used to check a Linux second extended file system (ext2fs).
E2fsck also supports ext2 filesystems containing a journal, which are
also sometimes known as ext3
filesystems, by first applying the journal to the filesystem before
continuing with normal e2fsck processing. After the journal has been
applied, a filesystem will normally
be marked as clean. Hence, for ext3 filesystems, e2fsck will normally
run the journal and exit, unless its superblock indicates that further
checking is required.device is the device file where the filesystem is stored (e.g. /dev/hdc1).
Note that in general it is not safe to run e2fsck on mounted
filesystems. The only exception is if the -n option is specified, and
-c, -l, or -L options are not specified.
However, even if it is safe to do so, the results printed by e2fsck are
not valid if the filesystem is mounted. If e2fsck asks whether or not
you should check a filesystem
which is mounted, the only correct answer is ??no??. Only experts who
really know what they are doing should consider answering this question
in any other way.73 = Best Regards,
-Geoff/W5OMR_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
ohnosec.org------------------------------
_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
ohnosec.orgEnd of App_rpt-users Digest, Vol 57, Issue 56
*********************************************