Index
Subject
: [lug] Digest (5 messages)
From
: lug-owner@lists.ncsu.[redacted]
Date
: Tue, 13 Sep 2016 11:18:05 -0400
The Lug Digest
Volume 1 : Issue 392 : "text" Format
Messages in this Issue:
201609/33 : Re: Updates
Neill Robson <nlrobson@ncsu.[redacted]>
201609/35 : Re: Updates
Quentin Young <qlyoung@ncsu.[redacted]>
201609/34 : Test message
Michael Marley <michael@michaelmarley.[redacted]>
201609/36 : Re: Test message
juanjose Guitian <juanjoseguitian@hotmail.[redacted]>
201609/37 : Bash Scripting: If and Command Line arguments and shrinking SD images.
Jeffery Mewtamer <mewtamer@gmail.[redacted]>
----------------------------------------------------------------------
Date: Mon, 12 Sep 2016 22:03:34 -0400
From: Neill Robson <nlrobson@ncsu.[redacted]>
To: lug@lists.ncsu.[redacted]
Subject: Re: Updates
Message-ID: <CAA+z_tswR0XaDcYk2ymn3YCR+oe05M=y_70-0Z1ANyPtzH47Dw@mail.gmail.[redacted]>
Discourse appeals to my inner desire for elegant and approachable software
design, but I also understand it might not be quite the atmosphere that the
LUG is trying to foster.
Jsoftware (people who developed the language my high school CS teacher
taught us) used GNU Mailman with great success. I liked their interface
better than NCSU's system, and would happily make the switch.
We do definitely need to think about a more appropriate medium for
chat-like club communication in the long term, though.
Neill R.
On Sep 12, 2016 7:29 PM, "Antonious Iskander" <amiskand@ncsu.[redacted]> wrote:
can we add or subscribe the NCSU Google Group to the the mailing list?
that way we can have external users and still use the features of the
Google Group?
On Mon, Sep 12, 2016 at 7:17 PM, Kushagra Mishra <kmishra@ncsu.[redacted]> wrote:
> DIscourse looks cool and simpler to handle than GNU mailman.
>
> On Mon, Sep 12, 2016 at 7:12 PM, Brian Cottingham <spiffytech@gmail.[redacted]>
> wrote:
>
>> How about running a Discourse installation? Forum software reinvented by
>> one of the guy behind StackOverflow.
>>
>> On Mon, Sep 12, 2016 at 6:05 PM, Quentin Young <qlyoung@ncsu.[redacted]> wrote:
>>
>>> Hi LUG,
>>>
>>> A few updates:
>>>
>>> - The Facebook event on Wednesday will replace our regularly
>>> scheduled dinner meeting this month. We will not be meeting tomorrow.
>>> - 4 help tickets later, the Google Group has been created. However,
>>> NCSU has graciously disabled the features that allow us to add users
>>> without @ncsu.edu email addresses.
>>>
>>> I'm looking for suggestions on the second point. Obviously if we can't
>>> collaborate with external users that's a blocker, but the mailing list kind
>>> of sucks. There's no way to see who's on it and who isn't. A lot of folks
>>> seem to have trouble subscribing and unsubscribing. We could host something
>>> ourselves, alongside the website perhaps. But it needs to integrate with
>>> email... I don't really know anything that fits our needs, except perhaps a
>>> consumer Google Group, which has the disadvantage of not being under the
>>> ncsu.edu domain.
>>>
>>> Suggestions / questions / concerns / etc welcome.
>>>
>>> --
>>> Quentin Young
>>> President, LUG @ NC State
>>>
>>
>>
>
[Attachment of type text/html removed.]
------------------------------
Date: Mon, 12 Sep 2016 22:22:11 -0400
From: Quentin Young <qlyoung@ncsu.[redacted]>
To: lug@lists.ncsu.[redacted]
Subject: Re: Updates
Message-ID: <CANhSzx2ZCCq=K-GEz1LrKV196obSCcGdU4RNb4HT7Gz9SV1o=Q@mail.gmail.[redacted]>
I like Discourse. Looks really good, we could have it on forum.lug.ncsu.edu or
whatever. Will look into that.
GNU Mailman is certainly an improvement over Majordomo. However, it merely
solves the problem of the listserv software being a PITA, not the problem
of being a listserv.
Should note that with either of these options we will be sending email from
@*.ncsu.edu domains. Thus we will need to comply with some regulations
regarding that mail.
As for subbing the mailing list to the Google group: as evidenced by the
four testing emails you all received, subscribing `lug@lists.ncsu.[redacted]` to
the Google Group works as a broadcast mechanism for external users, but
since that address merely broadcasts any incoming mail to all subscribers
this results in duplicate messages to all internal users. And it's pretty
ghetto. Striking that off the options list.
On Mon, Sep 12, 2016 at 10:03 PM, Neill Robson <nlrobson@ncsu.[redacted]> wrote:
> Discourse appeals to my inner desire for elegant and approachable software
> design, but I also understand it might not be quite the atmosphere that the
> LUG is trying to foster.
>
> Jsoftware (people who developed the language my high school CS teacher
> taught us) used GNU Mailman with great success. I liked their interface
> better than NCSU's system, and would happily make the switch.
>
> We do definitely need to think about a more appropriate medium for
> chat-like club communication in the long term, though.
>
> Neill R.
>
> On Sep 12, 2016 7:29 PM, "Antonious Iskander" <amiskand@ncsu.[redacted]> wrote:
>
> can we add or subscribe the NCSU Google Group to the the mailing list?
> that way we can have external users and still use the features of the
> Google Group?
>
> On Mon, Sep 12, 2016 at 7:17 PM, Kushagra Mishra <kmishra@ncsu.[redacted]> wrote:
>
>> DIscourse looks cool and simpler to handle than GNU mailman.
>>
>> On Mon, Sep 12, 2016 at 7:12 PM, Brian Cottingham <spiffytech@gmail.[redacted]>
>> wrote:
>>
>>> How about running a Discourse installation? Forum software reinvented by
>>> one of the guy behind StackOverflow.
>>>
>>> On Mon, Sep 12, 2016 at 6:05 PM, Quentin Young <qlyoung@ncsu.[redacted]> wrote:
>>>
>>>> Hi LUG,
>>>>
>>>> A few updates:
>>>>
>>>> - The Facebook event on Wednesday will replace our regularly
>>>> scheduled dinner meeting this month. We will not be meeting tomorrow.
>>>> - 4 help tickets later, the Google Group has been created. However,
>>>> NCSU has graciously disabled the features that allow us to add users
>>>> without @ncsu.edu email addresses.
>>>>
>>>> I'm looking for suggestions on the second point. Obviously if we can't
>>>> collaborate with external users that's a blocker, but the mailing list kind
>>>> of sucks. There's no way to see who's on it and who isn't. A lot of folks
>>>> seem to have trouble subscribing and unsubscribing. We could host something
>>>> ourselves, alongside the website perhaps. But it needs to integrate with
>>>> email... I don't really know anything that fits our needs, except perhaps a
>>>> consumer Google Group, which has the disadvantage of not being under the
>>>> ncsu.edu domain.
>>>>
>>>> Suggestions / questions / concerns / etc welcome.
>>>>
>>>> --
>>>> Quentin Young
>>>> President, LUG @ NC State
>>>>
>>>
>>>
>>
>
>
--
Quentin Young
President, LUG @ NC State
[Attachment of type text/html removed.]
------------------------------
Date: Mon, 12 Sep 2016 22:08:55 -0400
From: Michael Marley <michael@michaelmarley.[redacted]>
To: group-linux-users@ncsu.[redacted]
Subject: Test message
Message-ID: <4a4bf827-fedf-30ce-232a-babe497a820c@michaelmarley.[redacted]>
This is a test message.
------------------------------
Date: Tue, 13 Sep 2016 13:06:33 +0000
From: juanjose Guitian <juanjoseguitian@hotmail.[redacted]>
To: "lug@lists.ncsu.[redacted]" <lug@lists.ncsu.[redacted]>,
"group-linux-users@ncsu.[redacted]"
<group-linux-users@ncsu.[redacted]>
Subject: Re: Test message
Message-ID: <BAY179-W133F7810CCDF78E108222EA5FE0@phx.[redacted]>
Hello my friends, how are you? of course a test, but when and how?
cheers, Juan
> To: group-linux-users@ncsu.[redacted]
> From: michael@michaelmarley.[redacted]
> Subject: LUG: Test message
> Date: Mon, 12 Sep 2016 22:08:55 -0400
>
> This is a test message.
>
[Attachment of type text/html removed.]
------------------------------
Date: Tue, 13 Sep 2016 15:18:01 +0000
From: Jeffery Mewtamer <mewtamer@gmail.[redacted]>
To: lug <lug@lists.ncsu.[redacted]>, raspberry-vi@freelists.[redacted]
Subject: Bash Scripting: If and Command Line arguments and shrinking SD images.
Message-ID: <CAO2sX30BzOQGY4Sd+km78ammowG_FuC+-yWHbdYrSD_srcH0Og@mail.gmail.[redacted]>
Okay, I want to use if statements and command line arguments to
combine some of my existing scripts that do similar things and to
reduce cases of needing to make small edits to a script.
In particular, I've got two pairs of scripts for creating and
restoring backups, one pair that uses partimage for creating and
restoring compressed backups of my root partition, and another pair
that uses dd to create and restore uncompressed backups of SD cards
for my Raspberry Pis.
For the backups of my root partition, I'd like to combine the two
scripts into one that I can give a -b or -r argument and it will
execute the backup and restore commands respectively.
Based on my Google searches, this script might look something like:
#! /bin/bash
if [$1 == -b]
then
<backup command>
fi
if [$1 == -r]
then
<restore-command>
fi
but I'm not sure if this is the correct syntax for comparing the first
command line argument to a string literal.
For the Raspberry Pi images, I'd like something that:
1. takes the device label of the card as the first command line argument.
2. if there is no second argument, creates an image of the designated
card with a name like "pi-backup-[date].img in the working directory.
3. if the second arguement is the name of an existing image, it writes
that image to the SD card.
Could I use /dev/$1 in place of a hardcoded device label within the
script if I just want to type sdb or sdc at the command line?
How would I write the test conditions for $2 being empty or $2 being
the name of an existing file?
Also, at present, the dd command I have for creating an image leaves
the image as the size of the SD card, which takes up a lot of space on
my harddrive and means a lot of time would be wasted writing free
space when writing the image to another SD card. It's possible to
shrink an image to get rid of free space within the image, but all the
guides I can find via Google use Gparted, which isn't scriptable, and
since I do most things from the command line isn't an option for doing
it manually. I could just gzip the image and it's my understanding I
can have dd do this instead of having a separate gzip command after
creating the image and gunzip before the write command, but it doesn't
speed up writing images, and means I'd run out of SD card if the card
I'm writing to is smaller than the the image was created from(I
learned the hard way that results in an unbootable card if the image
contains more data than the card can hold, but have no idea if it
causes problems if the overflow is all free space). So, is there
anything I could add in the create image if block to shrink the
image's partitions?
--
Sincerely,
Jeffery Wright
President Emeritus, Nu Nu Chapter, Phi Theta Kappa.
Former Secretary, Student Government Association, College of the Albemarle.
------------------------------
End of [lug] Digest (5 messages)
**********