Help
SwineFlew's Private Thread
#18
Posted 18 June 2012 - 05:39 AM
][][][
[Edited to fix typo]
[Edited for brevity]
[Edited to fix typo]
[Edited for brevity]
This post has been edited by knowschad: 18 June 2012 - 05:42 AM
#24
Posted 18 June 2012 - 09:19 AM
.
This post has been edited by knowschad: 18 June 2012 - 09:21 AM
#25
Posted 18 June 2012 - 09:50 AM
_ _ _ _
/' /|
/ / |_
/ / //|
/_________/ ////|
| _ _ | 8o////|
| /'// )_ | 8///|
|/ // // ) | 8o///|
/ // // //,| / 8//|
/ // // /// | / 8//|
/ // // ///__|/ 8//|
/.(_)// /// | 8///|
(_)' `(_)//| | 8////|___________
(_) /_\ (_)'| | 8///////////////
(_) \"/ (_)'|_| 8/////////////
(_)._.(_) d' Hb 8oooooooopb'
`(_)' d' H`b
d' `b`b
d' H `b
d' `b `b
d' `b
d' `b
#26
Posted 18 June 2012 - 10:36 AM
sudo chmod 700 "SwineFlew's Private Thread"
This post has been edited by Dgwphotos: 18 June 2012 - 10:36 AM
#27
Posted 18 June 2012 - 10:54 AM
Dgwphotos, on 18 June 2012 - 10:36 AM, said:
sudo chmod 700 "SwineFlew's Private Thread"
sudo chmod go+x "SwineFlew's Private Thread"
#28
Posted 18 June 2012 - 11:07 AM
knowschad, on 18 June 2012 - 10:54 AM, said:
Dgwphotos, on 18 June 2012 - 10:36 AM, said:
sudo chmod 700 "SwineFlew's Private Thread"
sudo chmod go+x "SwineFlew's Private Thread"
I think you have to give the permissions separately, i.e. g+x,o+x, when assigning permissions in that manner.
#29
Posted 18 June 2012 - 11:10 AM
Dgwphotos, on 18 June 2012 - 11:07 AM, said:
knowschad, on 18 June 2012 - 10:54 AM, said:
Dgwphotos, on 18 June 2012 - 10:36 AM, said:
sudo chmod 700 "SwineFlew's Private Thread"
sudo chmod go+x "SwineFlew's Private Thread"
I think you have to give the permissions separately, i.e. g+x,o+x, when assigning permissions in that manner.
http://www.washingto...ermissions.html
#30
Posted 18 June 2012 - 11:13 AM
10 PRINT "DON'T POST HERE, THIS IS SWINEFLEW'S PRIVATE THREAD" 20 GOTO 10 30 END
#31
Posted 18 June 2012 - 11:15 AM
thistleRacers, on 18 June 2012 - 11:10 AM, said:
Dgwphotos, on 18 June 2012 - 11:07 AM, said:
knowschad, on 18 June 2012 - 10:54 AM, said:
Dgwphotos, on 18 June 2012 - 10:36 AM, said:
sudo chmod 700 "SwineFlew's Private Thread"
sudo chmod go+x "SwineFlew's Private Thread"
I think you have to give the permissions separately, i.e. g+x,o+x, when assigning permissions in that manner.
http://www.washingto...ermissions.html
Ok, it can be done both ways.
#32
Posted 18 June 2012 - 11:19 AM
hzoi, on 18 June 2012 - 11:13 AM, said:
10 PRINT "DON'T POST HERE, THIS IS SWINEFLEW'S PRIVATE THREAD" 20 GOTO 10 30 END
You could dispense with the last line. (line numbering and GOTOs?
)
This post has been edited by knowschad: 18 June 2012 - 11:20 AM
#33
Posted 18 June 2012 - 11:25 AM
BRB
This post has been edited by Dgwphotos: 18 June 2012 - 11:25 AM
#34
Posted 18 June 2012 - 11:26 AM
while ( true )
{
printf("DON'T POST HERE, THIS IS SWINEFLEW'S PRIVATE THREAD");
}
This post has been edited by knowschad: 18 June 2012 - 11:30 AM
#35
Posted 18 June 2012 - 11:28 AM
#!/bin/bash
#This script checks users to see if they are SwineFlew and can post in this thread.
echo "What is your user name?"
read USERNAME
if [$USERNAME = "SwineFlew" ]
then
echo "You can post in this thread!"
else
echo "You cannot post here, this thread is SwineFlew's Private Thread!
fi
exit 0
#This script checks users to see if they are SwineFlew and can post in this thread.
echo "What is your user name?"
read USERNAME
if [$USERNAME = "SwineFlew" ]
then
echo "You can post in this thread!"
else
echo "You cannot post here, this thread is SwineFlew's Private Thread!
fi
exit 0
This post has been edited by Dgwphotos: 18 June 2012 - 11:29 AM
#36
Posted 18 June 2012 - 11:32 AM
I only know HTML and BASIC. So sue me.
The "END" line, FYI, was troll bait.
The "END" line, FYI, was troll bait.
#37
Posted 18 June 2012 - 11:35 AM
hzoi, on 18 June 2012 - 11:32 AM, said:
I only know HTML and BASIC. So sue me.
The "END" line, FYI, was troll bait.
The "END" line, FYI, was troll bait.
Leave it to a lawyer.
#38
Posted 18 June 2012 - 11:38 AM
This post has been edited by thistleRacers: 18 June 2012 - 11:43 AM
#41
Posted 19 June 2012 - 01:09 PM
Dgwphotos, on 18 June 2012 - 11:28 AM, said:
#!/bin/bash
#This script checks users to see if they are SwineFlew and can post in this thread.
echo "What is your user name?"
read USERNAME
if [$USERNAME = "SwineFlew" ]
then
echo "You can post in this thread!"
else
echo "You cannot post here, this thread is SwineFlew's Private Thread!
fi
exit 0
#This script checks users to see if they are SwineFlew and can post in this thread.
echo "What is your user name?"
read USERNAME
if [$USERNAME = "SwineFlew" ]
then
echo "You can post in this thread!"
else
echo "You cannot post here, this thread is SwineFlew's Private Thread!
fi
exit 0
Shouldn't it be if [$USERNAME == "SwineFlew" ] ?
You want a comparision, not an assignation - the way you have it now, ANYONE can post in this thread.
#42
Posted 19 June 2012 - 01:41 PM
Sioneva, on 19 June 2012 - 01:09 PM, said:
Dgwphotos, on 18 June 2012 - 11:28 AM, said:
#!/bin/bash
#This script checks users to see if they are SwineFlew and can post in this thread.
echo "What is your user name?"
read USERNAME
if [$USERNAME = "SwineFlew" ]
then
echo "You can post in this thread!"
else
echo "You cannot post here, this thread is SwineFlew's Private Thread!
fi
exit 0
#This script checks users to see if they are SwineFlew and can post in this thread.
echo "What is your user name?"
read USERNAME
if [$USERNAME = "SwineFlew" ]
then
echo "You can post in this thread!"
else
echo "You cannot post here, this thread is SwineFlew's Private Thread!
fi
exit 0
Shouldn't it be if [$USERNAME == "SwineFlew" ] ?
You want a comparision, not an assignation - the way you have it now, ANYONE can post in this thread.
It's an If, Then, Else statement. If you meet this condition, then you can post in this thread. If you don't meet this condition, then you cannot post in this thread. Of course, it doesn't actually prevent anyone from posting here, because that would be managed by permissions. But the script would display the messages correctly as as it is written. I'll try it on a virtual Linux machine later.
#43
Posted 19 June 2012 - 02:25 PM
Dgwphotos, on 19 June 2012 - 01:41 PM, said:
Sioneva, on 19 June 2012 - 01:09 PM, said:
Dgwphotos, on 18 June 2012 - 11:28 AM, said:
#!/bin/bash
#This script checks users to see if they are SwineFlew and can post in this thread.
echo "What is your user name?"
read USERNAME
if [$USERNAME = "SwineFlew" ]
then
echo "You can post in this thread!"
else
echo "You cannot post here, this thread is SwineFlew's Private Thread!
fi
exit 0
#This script checks users to see if they are SwineFlew and can post in this thread.
echo "What is your user name?"
read USERNAME
if [$USERNAME = "SwineFlew" ]
then
echo "You can post in this thread!"
else
echo "You cannot post here, this thread is SwineFlew's Private Thread!
fi
exit 0
Shouldn't it be if [$USERNAME == "SwineFlew" ] ?
You want a comparision, not an assignation - the way you have it now, ANYONE can post in this thread.
It's an If, Then, Else statement. If you meet this condition, then you can post in this thread. If you don't meet this condition, then you cannot post in this thread. Of course, it doesn't actually prevent anyone from posting here, because that would be managed by permissions. But the script would display the messages correctly as as it is written. I'll try it on a virtual Linux machine later.
I know, I'm a programmer. At least in Perl, you'd have to use ==, but I'm not sure if your shell script needs that.
#44
Posted 19 June 2012 - 02:30 PM
Dgwphotos, on 19 June 2012 - 01:41 PM, said:
Sioneva, on 19 June 2012 - 01:09 PM, said:
Dgwphotos, on 18 June 2012 - 11:28 AM, said:
#!/bin/bash
#This script checks users to see if they are SwineFlew and can post in this thread.
echo "What is your user name?"
read USERNAME
if [$USERNAME = "SwineFlew" ]
then
echo "You can post in this thread!"
else
echo "You cannot post here, this thread is SwineFlew's Private Thread!
fi
exit 0
#This script checks users to see if they are SwineFlew and can post in this thread.
echo "What is your user name?"
read USERNAME
if [$USERNAME = "SwineFlew" ]
then
echo "You can post in this thread!"
else
echo "You cannot post here, this thread is SwineFlew's Private Thread!
fi
exit 0
Shouldn't it be if [$USERNAME == "SwineFlew" ] ?
You want a comparision, not an assignation - the way you have it now, ANYONE can post in this thread.
It's an If, Then, Else statement. If you meet this condition, then you can post in this thread. If you don't meet this condition, then you cannot post in this thread. Of course, it doesn't actually prevent anyone from posting here, because that would be managed by permissions. But the script would display the messages correctly as as it is written. I'll try it on a virtual Linux machine later.
In some languages, "=" is only a assignation symbol. In some, it can also be a conditional. Some languages require "==" to make a comparison. I have no idea which way bash works.
#46
Posted 19 June 2012 - 02:43 PM
Sioneva, on 19 June 2012 - 02:25 PM, said:
Dgwphotos, on 19 June 2012 - 01:41 PM, said:
Sioneva, on 19 June 2012 - 01:09 PM, said:
Dgwphotos, on 18 June 2012 - 11:28 AM, said:
#!/bin/bash
#This script checks users to see if they are SwineFlew and can post in this thread.
echo "What is your user name?"
read USERNAME
if [$USERNAME = "SwineFlew" ]
then
echo "You can post in this thread!"
else
echo "You cannot post here, this thread is SwineFlew's Private Thread!
fi
exit 0
#This script checks users to see if they are SwineFlew and can post in this thread.
echo "What is your user name?"
read USERNAME
if [$USERNAME = "SwineFlew" ]
then
echo "You can post in this thread!"
else
echo "You cannot post here, this thread is SwineFlew's Private Thread!
fi
exit 0
Shouldn't it be if [$USERNAME == "SwineFlew" ] ?
You want a comparision, not an assignation - the way you have it now, ANYONE can post in this thread.
It's an If, Then, Else statement. If you meet this condition, then you can post in this thread. If you don't meet this condition, then you cannot post in this thread. Of course, it doesn't actually prevent anyone from posting here, because that would be managed by permissions. But the script would display the messages correctly as as it is written. I'll try it on a virtual Linux machine later.
I know, I'm a programmer. At least in Perl, you'd have to use ==, but I'm not sure if your shell script needs that.I wish you were having this conversation with SwineFlew instead. I'd love the chance to make a Perl before Swine pun.
