local10 wrote on 24/01/2022 at 00:32:10+0100:
> Jan 23, 2022, 21:43 by p...@debian.org:
>
>> What happened is that DAM took a decision, which was challenged by some
>> Developers, among with some were willing to start a General Resolution
>> to overturn DAM's decision.
>>
>> In that heated discu
Polyna-Maude Racicot-Summerside wrote:
> This seems to me close to harassment.
its just popcorn but you'll obviously never get it.
please stop as well and thank you in advance
--
FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0
On 2022-01-23 21:27, deloptes wrote:
> local10 wrote:
>
>> I asked you a simple question: Is there a list of all the horrible things
>> Norbert Preining said that was used to support the decision to demote him?
>>
>> Instead of providing a clear answer to the question you seem to be more
>> inte
local10 wrote:
> I asked you a simple question: Is there a list of all the horrible things
> Norbert Preining said that was used to support the decision to demote him?
>
> Instead of providing a clear answer to the question you seem to be more
> interesting in engaging in sophism and detracting f
On 2022-01-23 19:27, local10 wrote:
> Jan 23, 2022, 23:58 by deb...@polynamaude.com:
>
>>
>>
>>> Sounds sketchy but whatever. Is there a list of all the horrible things
>>> Norbert Preining said that was used to support the decision to demote him?
>>> As a Debian and KDE user I'm trying to un
Jan 23, 2022, 23:58 by deb...@polynamaude.com:
>
>
>> Sounds sketchy but whatever. Is there a list of all the horrible things
>> Norbert Preining said that was used to support the decision to demote him?
>> As a Debian and KDE user I'm trying to understand if Debian leadership was
>> reasonabl
On 2022-01-23 18:32, local10 wrote:
> Jan 23, 2022, 21:43 by p...@debian.org:
>
>> What happened is that DAM took a decision, which was challenged by some
>> Developers, among with some were willing to start a General Resolution
>> to overturn DAM's decision.
>>
>> In that heated discussion, Ian
Jan 23, 2022, 21:43 by p...@debian.org:
> What happened is that DAM took a decision, which was challenged by some
> Developers, among with some were willing to start a General Resolution
> to overturn DAM's decision.
>
> In that heated discussion, Ian decided to collect any bad interaction
> betwe
n 1/23/22 13:43, Pierre-Elliott Bécue wrote:
local10 wrote on 23/01/2022 at 21:34:19+0100:
Jan 23, 2022, 20:12 by deb...@polynamaude.com:
You'd leave because you have to be held responsible for your actions ?
What actions? Based on the message
( https://lists.debian.org/debian-project/2019
local10 wrote on 23/01/2022 at 21:34:19+0100:
> Jan 23, 2022, 20:12 by deb...@polynamaude.com:
>
>> You'd leave because you have to be held responsible for your actions ?
>>
>
> What actions? Based on the message
> ( https://lists.debian.org/debian-project/2019/01/msg00186.html ) it
> looks like
On Sun, 2022-01-23 at 21:34 +0100, local10 wrote:
> Jan 23, 2022, 20:12 by deb...@polynamaude.com:
>
> > You'd leave because you have to be held responsible for your actions ?
> >
>
> What actions? Based on the message (
> https://lists.debian.org/debian-project/2019/01/msg00186.html ) it looks
Jan 23, 2022, 20:12 by deb...@polynamaude.com:
> You'd leave because you have to be held responsible for your actions ?
>
What actions? Based on the message (
https://lists.debian.org/debian-project/2019/01/msg00186.html ) it looks like
they came up with the verdict first and then started to lo
On 2022-01-23 14:10, local10 wrote:
> Jan 23, 2022, 18:48 by ta...@debianlists.mobilxpress.net:
>
>> On 23.01.22 00:24, Andrew M.A. Cater wrote:
>>
>>>
>>>
>> I think the further deterioration of his relation with Debian stems from
>> there, but i did not explore 900 matches of
>>
>>
local10 wrote on 23/01/2022 at 20:10:26+0100:
> Jan 23, 2022, 18:48 by ta...@debianlists.mobilxpress.net:
>
>> On 23.01.22 00:24, Andrew M.A. Cater wrote:
>>
>>>
>>>
>> I think the further deterioration of his relation with Debian stems from
>> there, but i did not explore 900 matches o
On Sun, Jan 23, 2022 at 08:10:26PM +0100, local10 wrote:
> Jan 23, 2022, 18:48 by ta...@debianlists.mobilxpress.net:
>
> > On 23.01.22 00:24, Andrew M.A. Cater wrote:
> >
> >>
> >>
> > I think the further deterioration of his relation with Debian stems from
> > there, but i did not explore
Jan 23, 2022, 18:48 by ta...@debianlists.mobilxpress.net:
> On 23.01.22 00:24, Andrew M.A. Cater wrote:
>
>>
>>
> I think the further deterioration of his relation with Debian stems from
> there, but i did not explore 900 matches of
>
> >
> https://lists.debian.org/cgi-bi
E Plasma desktop
environment as available in Debian, I do not feel it to be, lets say,
insolent, if interested in community affairs. Actually, I feel it desirable
to stay well informed for reinforcing advocacy, and asking for transparency
is to me a coherent step.
I feel that a concise statement fr
ul user of Debian, and being in my circle of influence a
> strong advocate of the Debian project, and also of the KDE Plasma desktop
> environment as available in Debian, I do not feel it to be, lets say,
> insolent, if interested in community affairs. Actually, I feel it desirable
> to stay
Not too long ago, I made a statement like "64 GB should be enough for anybody
;-)" (when talking about a new Lenovo micro computer).
It turns out I was wrong, Over on the "Libre-Soc General Development" maillist (where they are working on building a
new basically "op
* On 2020 08 Jul 08:38 -0500, Greg Wooledge wrote:
> There are lots of choices here. And this is with only the login shell
> layer involved -- no X11 or Wayland.
Good points and it must be emphasized that ~/.profile or ~/.bash_profile
are for *login* shells only. Ordinarily shells started from a
On Wed, Jul 08, 2020 at 07:53:53AM -0500, Nate Bargmann wrote:
> https://noah.meyerhans.us/2020/07/07/setting-environment-variables-for-gnome-session/
> As I read it, where an environment variable should be set depends on the
> intended scope of the variable. One comment in response to the blog
>
* On 2020 07 Jul 08:58 -0500, Stephen P. Molnar wrote:
> The Subject line is the problem with my Debian Buster platform. Now from
> Google I see that there has been a change in the way Debian handles this
> problem.
>
> My user path statement is:
>
> comp@AbNormal:~$ echo $
On Wed, Jul 08, 2020 at 07:39:40AM -0400, Greg Wooledge wrote:
> On Wed, Jul 08, 2020 at 10:44:39AM +1000, Zenaan Harkness wrote:
> > - XFCE acts as, or uses, Dash or something that does not propagate shell
> > functions in the parent env
>
> There are many layers involved. Assuming you're logg
On Wed, Jul 08, 2020 at 10:44:39AM +1000, Zenaan Harkness wrote:
> - XFCE acts as, or uses, Dash or something that does not propagate shell
> functions in the parent env
There are many layers involved. Assuming you're logging in with a "Debian
X session", a POSIX shell (sh) is used to read most
On Mi, 08 iul 20, 10:44:39, Zenaan Harkness wrote:
>
> - so try somewhere in the session startup apps - nope, courdn't
> figure it out at least
For Debian you want ~/.xsessionrc
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
signature.asc
Description: PGP signature
On Mi, 08 iul 20, 09:59:52, Zenaan Harkness wrote:
> On Tue, Jul 07, 2020 at 10:29:47AM -0400, Greg Wooledge wrote:
> >
> > $HOME/bin is placed into the user's default PATH by Debian's ~/.profile
> > (the one in /etc/skel/.profile) if it exists at the time the ~/.profile
> > is read, if the ~/.pro
On Tue 07 Jul 2020 at 20:20:11 (-0400), Roberto C. Sánchez wrote:
> On Wed, Jul 08, 2020 at 09:59:52AM +1000, Zenaan Harkness wrote:
> > On Tue, Jul 07, 2020 at 10:29:47AM -0400, Greg Wooledge wrote:
> > > On Tue, Jul 07, 2020 at 03:17:37PM +0100, Jonathan Dowland wrote:
> > > > On Tue, Jul 07, 202
On Tue, Jul 07, 2020 at 10:16:21AM -0400, Greg Wooledge wrote:
> Gods, I am so tired of this question and having to repeat my demands
> for BASIC information over and over.
>
> Here are some resources for those of you who refuse to reveal any of
> the necessary background information to get answe
On Wed, Jul 08, 2020 at 09:59:52AM +1000, Zenaan Harkness wrote:
> On Tue, Jul 07, 2020 at 10:29:47AM -0400, Greg Wooledge wrote:
> > On Tue, Jul 07, 2020 at 03:17:37PM +0100, Jonathan Dowland wrote:
> > > On Tue, Jul 07, 2020 at 04:14:16PM +0200, Nicolas George wrote:
> > > > cd ~/bin
> > > > ln -
Ahh, asked too soon. Thanks Greg.
On Tue, Jul 07, 2020 at 10:16:21AM -0400, Greg Wooledge wrote:
> On Tue, Jul 07, 2020 at 09:57:34AM -0400, Stephen P. Molnar wrote:
> > The Subject line is the problem
>
> Yeah. The Subject: line reveals the problem: you believe that PATH is
> set primarily by
On Tue, Jul 07, 2020 at 10:29:47AM -0400, Greg Wooledge wrote:
> On Tue, Jul 07, 2020 at 03:17:37PM +0100, Jonathan Dowland wrote:
> > On Tue, Jul 07, 2020 at 04:14:16PM +0200, Nicolas George wrote:
> > > cd ~/bin
> > > ln -s ../opt/something/bin/something
> >
> > Not in the default PATH either.
>
Jonathan Dowland (12020-07-07):
> Not in the default PATH either.
No, but probably one of the first things anybody who has non-elementary
use will have configured anyway.
Regards,
--
Nicolas George
signature.asc
Description: PGP signature
On Tue, Jul 07, 2020 at 03:17:37PM +0100, Jonathan Dowland wrote:
> On Tue, Jul 07, 2020 at 04:14:16PM +0200, Nicolas George wrote:
> > cd ~/bin
> > ln -s ../opt/something/bin/something
>
> Not in the default PATH either.
$HOME/bin is placed into the user's default PATH by Debian's ~/.profile
(th
On Tue, Jul 07, 2020 at 04:14:16PM +0200, Nicolas George wrote:
cd ~/bin
ln -s ../opt/something/bin/something
Not in the default PATH either.
--
👱🏻 Jonathan Dowland
✎j...@debian.org
🔗 https://jmtd.net
On Tue, Jul 07, 2020 at 09:57:34AM -0400, Stephen P. Molnar wrote:
> The Subject line is the problem
Yeah. The Subject: line reveals the problem: you believe that PATH is
set primarily by your shell.
It's not. It's set primarily by your method of login, and then by your
session tools, whether t
Roberto C. Sánchez (12020-07-07):
> You should add the export command to ~/.bashrc (for it to only be in
> effect for that user)
Except ~/.bashrc is only sourced for interactive shells, it will not be
run when applications are executed by a GUI, for example.
(Also, for some reason, the bash autho
but from what you
describe below I find it unlikely that anything has changed in the
observed behavior.
> My user path statement is:
>
> comp@AbNormal:~$ echo $PATH
> /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
>
> Now I have a number of applications that have mu
The Subject line is the problem with my Debian Buster platform. Now from
Google I see that there has been a change in the way Debian handles this
problem.
My user path statement is:
comp@AbNormal:~$ echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
Now I have a number of
Here you go! Please confirm receipt and let me know if you need anything else.
Have a great day!
Sharon Smith | Representative Closing Services Department
ATTORNEYS' TITLE GUARANTY FUND,
Phone: 847.236.2950 |Fax: 312.237.4764
0018733.pdf
Description: Adobe PDF document
Maybe, the following little shell example can help:
file_pattern='-name \*.c -o -name \*.h'
eval find . $file_pattern
The stars ("*") have to be protected from being evaluated by the shell in the
second line, therefore, the backslashes. The eval command does the trick, its a
shell built-in. By t
-name "*2010[01][1234567890]*" -o -name "*2011[01][1234567890]*"
But when I use $filter in my find statement:
list=`find . $filter`
echo $list;
The variable $list is empty!
I think that the ksh cant resolv the quotes in the $filter string.
I try using combinations of hard quo
On 02/20/2011 08:23 PM, Andrei Popescu wrote:
On Du, 20 feb 11, 03:20:52, Ron Johnson wrote:
Then it should be named:
Debian GNU/X/GNOME/KDE/Lots-of-other-stuff Linux.
Well, I guess that depends very much on the definition of an OS. IMVHO a
kernel (Linux of kFreeBSD in case of Debian) plu
On Du, 20 feb 11, 03:20:52, Ron Johnson wrote:
>
> Then it should be named:
>Debian GNU/X/GNOME/KDE/Lots-of-other-stuff Linux.
Well, I guess that depends very much on the definition of an OS. IMVHO a
kernel (Linux of kFreeBSD in case of Debian) plus the GNU tools can
already be called an OS
On 02/20/2011 07:37 AM, Stephen Powell wrote:
On Sun, 20 Feb 2011 04:20:52 -0500 (EST), Ron Johnson wrote:
On 02/17/2011 07:54 PM, Stephen Powell wrote:
The longer, more formal name of Debian is "Debian GNU/Linux". It is called that
because the core of the system is the fusion of the Linux ker
On Sun, 20 Feb 2011 04:20:52 -0500 (EST), Ron Johnson wrote:
> On 02/17/2011 07:54 PM, Stephen Powell wrote:
>> The longer, more formal name of Debian is "Debian GNU/Linux". It is called
>> that
>> because the core of the system is the fusion of the Linux kernel (which is
>> not
>> part of the G
Ron Johnson put forth on 2/20/2011 3:20 AM:
> Then it should be named:
>Debian GNU/X/GNOME/KDE/Lots-of-other-stuff Linux.
>
> I remember when RMS got all pissy about Hurd getting overshadowed by a
> little punk from Finland and fearing that people would forget about his
> greatness.
I defini
On Thursday 17 February 2011 17:37:37 Lisi wrote:
Thanks for such helpful replies. :-)
Lisi
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201102201010.55990.lisi.r
On 02/17/2011 07:54 PM, Stephen Powell wrote:
On 17:37 Thu 17 Feb, Lisi (lisi.re...@gmail.com) wrote:
Is this statement correct? It comes in the textbook for a course I am doing.
Grub (Grand Unified Bootloader) is the boot program of the GNU project.
If so, where does LILO fit in?
The
On Thu, 17 Feb 2011 22:12:42 -0500 (EST), Jesús M. Navarro wrote:
> On Friday 18 February 2011 02:54:03 Stephen Powell wrote:
>> ...
>> The longer, more formal name of Debian is "Debian GNU/Linux".
>> ...
>
> Unless it isn't, of course.
>
> As it's the case for Debian GNU/kFreeBSD.
And Debian GN
Hi, Stephen:
On Friday 18 February 2011 02:54:03 Stephen Powell wrote:
> On 17:37 Thu 17 Feb, Lisi (lisi.re...@gmail.com) wrote:
> > Is this statement correct? It comes in the textbook for a course I am
> > doing.
> > Grub (Grand Unified Bootloader) is the boot progr
On 17:37 Thu 17 Feb, Lisi (lisi.re...@gmail.com) wrote:
> Is this statement correct? It comes in the textbook for a course I am doing.
>
> Grub (Grand Unified Bootloader) is the boot program of the GNU project.
>
>
> If so, where does LILO fit in?
The longer, more formal
The first Linux I installed (that was back to 2003) defaulted to GRUB as
bootloader and GRUB (legacy) is the only bootloader I've installed -and
tweaked- since then. While I've seen "LILOs" when testing another
distributions, true is that I have not a deep knowdledge of how it works.
But, for wha
on 12:55 Thu 17 Feb, Boyd Stephen Smith Jr. (b...@iguanasuicide.net) wrote:
> On Thursday 17 February 2011 12:44:05 Dr. Ed Morbius wrote:
> > LILO was an earlier bootloader. For Linux. Hence: LInux LOader.
>
> It was a successor to LoadLin, a program to LOAD LINux.
That is a DOS executable: L
On Thu, 17 Feb 2011 12:35:04 -0600, Kent West wrote:
> On 02/17/2011 12:04 PM, Camaleón wrote:
>> LILO is another bootloader available for Linux.
>>
>> What was your concern? The sponsor? :-)
>>
>>
>>
>>
> LILO was the boot loader used a version or few back. It can still be
> used, but it's n
On Thursday 17 February 2011 12:44:05 Dr. Ed Morbius wrote:
> LILO was an earlier bootloader. For Linux. Hence: LInux LOader.
It was a successor to LoadLin, a program to LOAD LINux.
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
b...@iguanasuicide.net ((_/)o o(\_))
IC
on 17:37 Thu 17 Feb, Lisi (lisi.re...@gmail.com) wrote:
> Is this statement correct? It comes in the textbook for a course I am doing.
1: Why does this matter?
>
> Grub (Grand Unified Bootloader) is the boot program of the GNU project.
>
>
> If so, where does LILO fi
On 02/17/2011 12:04 PM, Camaleón wrote:
On Thu, 17 Feb 2011 17:37:37 +, Lisi wrote:
Is this statement correct? It comes in the textbook for a course I am
doing.
Grub (Grand Unified Bootloader) is the boot program of the GNU project.
Yep, is correct.
If so, where does
Lisi wrote:
Is this statement correct? It comes in the textbook for a course I am doing.
Grub (Grand Unified Bootloader) is the boot program of the GNU project.
http://en.wikipedia.org/wiki/GNU_GRUB
If so, where does LILO fit in?
Well, LILO is short for "LInux LOader" ... fo
On Thu, 17 Feb 2011 17:37:37 +, Lisi wrote:
> Is this statement correct? It comes in the textbook for a course I am
> doing.
> Grub (Grand Unified Bootloader) is the boot program of the GNU project.
>
Yep, is correct.
> If so, where does LILO fit in?
LILO is ano
On Thursday 17 February 2011 11:37:37 Lisi wrote:
> Is this statement correct?
> Grub (Grand Unified Bootloader) is the boot program of the GNU project.
Yes.
> If so, where does LILO fit in?
LILO isn't a GNU project.
LILO is licensed under the GNU GPL. The GNU GPL is the li
Is this statement correct? It comes in the textbook for a course I am doing.
Grub (Grand Unified Bootloader) is the boot program of the GNU project.
If so, where does LILO fit in?
Thanks,
Lisi
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubs
On 20/08/2010 3:43 p, Martin McCormick wrote:
Jangita writes:
Not a question for this list but
Sorry.
1. Is there any statement in the while loop that changes NEXTSYS? (or
better still, send any statement that has NEXTSYS in it while inside the
loop)
Yes! I didn't even think about
Jangita writes:
> Not a question for this list but
Sorry.
>
> 1. Is there any statement in the while loop that changes NEXTSYS? (or
> better still, send any statement that has NEXTSYS in it while inside the
> loop)
Yes! I didn't even think about that but there is a test in
Martin McCormick wrote:
I have written some C code that appeared to be good until I put
a while statement in to one of the modules and then all went to
at least Purgatory. It all compiles beautifully but I was
alerted to something terribly wrong when the program began
misbehaving. I can't
Jangita writes:
> Not a question for this list but
Sorry.
>
> 1. Is there any statement in the while loop that changes NEXTSYS? (or
> better still, send any statement that has NEXTSYS in it while inside the
> loop)
Yes! I didn't even think about that but there is a test in
On 2010-08-20 08:01:46 -0500, Martin McCormick wrote:
[...]
> Reading about the while loop tells me that the statement
Actually, that's an expression, not a statement.
> after while must be true to execute. If I put a boolean variable
> inside the statement as in (NEXTSYS) do
On 08/20/2010 08:01 AM, Martin McCormick wrote:
I have written some C code that appeared to be good until I put
a while statement in to one of the modules and then all went to
at least Purgatory. It all compiles beautifully but I was
alerted to something terribly wrong when the program began
On 20/08/2010 3:01 p, Martin McCormick wrote:
I have written some C code that appeared to be good until I put
a while statement in to one of the modules and then all went to
at least Purgatory. It all compiles beautifully but I was
alerted to something terribly wrong when the program began
I have written some C code that appeared to be good until I put
a while statement in to one of the modules and then all went to
at least Purgatory. It all compiles beautifully but I was
alerted to something terribly wrong when the program began
misbehaving. I can't even say that it is
On Wed, Dec 12, 2007 at 07:03:29PM -0600, Bob Goldberg wrote:
> nevermind - I finally figured it out...
do tell Bob!
A
signature.asc
Description: Digital signature
nevermind - I finally figured it out...
running debian etch (which is exim4);
I'm having problems with an ACL; so i've gone to absolute basics, and I
still have a problem :)
So here's what I have in my ACL:
accept message = condition is false
condition = ${if eq{23}{123}{1}{0}}
next, I telnet in, and transact an email up to th
At 05:29 PM 6/22/2005, Chris F.A. Johnson wrote:
On 2005-06-22, [EMAIL PROTECTED] wrote:
> Hello,
>
> I have an if statement, something like:
>
> if [ "$day" = "Thu" ]; then
> tar -cpf /var/backups/homethu.tar /home
> fi
>
> If I decide to pound ou
On 2005-06-22, [EMAIL PROTECTED] wrote:
> Hello,
>
> I have an if statement, something like:
>
> if [ "$day" = "Thu" ]; then
> tar -cpf /var/backups/homethu.tar /home
> fi
>
> If I decide to pound out the tar command, then the script
> will error a
[EMAIL PROTECTED] wrote:
Quoting [EMAIL PROTECTED]:
Quoting [EMAIL PROTECTED]:
You have to have something for the shell to run. Try setting a new
variable to
1 or some such silly-ness and it will work. Or else you have to comment out
the entire if statement.
I guess I could just add an
Quoting [EMAIL PROTECTED]:
Quoting [EMAIL PROTECTED]:
You have to have something for the shell to run. Try setting a new
variable to
1 or some such silly-ness and it will work. Or else you have to comment out
the entire if statement.
I guess I could just add an blank echo command
On 6/22/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I have an if statement, something like:
>
> if [ "$day" = "Thu" ]; then
> tar -cpf /var/backups/homethu.tar /home
> fi
Try the following:
if [ "$day" = "Thu" ]; then
tar -cp
On Wednesday 22 June 2005 14:35, [EMAIL PROTECTED] wrote:
> Hello,
>
> I have an if statement, something like:
>
> if [ "$day" = "Thu" ]; then
> tar -cpf /var/backups/homethu.tar /home
> fi
>
> If I decide to pound out the tar command, then the script
Hello,
I have an if statement, something like:
if [ "$day" = "Thu" ]; then
tar -cpf /var/backups/homethu.tar /home
fi
If I decide to pound out the tar command, then the script
will error and it won't continue on.
Is it possible to pound out the tar command and sti
has to have been set
somewhere. The PATH statement is spread out through a couple of Xsessions,
but neither builds up the give me the path I currently have. So my question
still stand.
--
John L. Fjellstad
web: http://www.fjellstad.org/ Qui
t that simple. Neither UserPath nor SystemPath occurs in my kdmrc. When I
> follow Xsession, that do set my PATH statement, I don't get the path that I
> see in the konsole (by doing echo $PATH), which is why I'm asking where all
> the places the PATH is set in the first place.
So,
that do set my PATH statement, I don't get the path that I
see in the konsole (by doing echo $PATH), which is why I'm asking where all
the places the PATH is set in the first place.
--
John L. Fjellstad
web: http://www.fjellstad.org/
On Mon, 2003-12-01 at 14:50, John L. Fjellstad wrote:
> Where are all the places the PATH is set when you are using X-Window (kdm)?
>
> Problem is, when I log in from the console, I get this path:
> /usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/usr/bin:/usr/games
>
> when I open a xterm, and do ec
Where are all the places the PATH is set when you are using X-Window (kdm)?
Problem is, when I log in from the console, I get this path:
/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/usr/bin:/usr/games
when I open a xterm, and do echo $PATH, I get this:
/bin:/usr/bin:/usr/X11R6/bin:/usr/local/bin
http://www.iab.org/documents/docs/2003-09-20-dns-wildcards.html
"Proposed guideline: If you want to use wildcards in your zone and
understand the risks, go ahead, but only do so with the informed consent
of the entities that are delegated within your zone."
--
Bill Moseley
[EMAIL PROTECTED]
I want to run the shell-script
#!/bin/csh
if ($?EDITOR) echo "Setting EDITOR"
the result is as follows:
then: then/endif not found.
what was not my intention.
Any help? (I have to use csh instead of bash since I have to install some
software package with twenty csh-Shell-scripts, which I do
>>[10-31]) SearchStr="$Month $Day";;
That means "a single character in the set 1, 0 through 3, and 1", so
it will match any of 0 1 2 3 and nothing else.
>># [12][0-9]) SearchStr="$Month $Day";;
>># 30 | 31 ) Day=02; SearchStr="$Month 9";;
That's more like it; the [12][0-9]
Oliver Elphick writes:
> On the other hand, this does not properly handle invalid day/month
> combinations, such as 31 February. Do you handle that somewhere else?
Use the 'date' command. For example:
date +%D --date '1/1/97 +60days'
returns:
03/02/97
Like most GNU utilities,
David Oswald wrote:
>Hello all - I have a KSH script question...
>
>sorry - the offending line is [10-31]) not [30-31])
What `[10-31]' says is: match any single character which is a 1, a character
from 0 to 3 inclusive, or (another) 1. What you want is `[12][0-9]|3[0-1]'.
On the other hand
David Oswald <[EMAIL PROTECTED]> writes:
>
> Hello all - I have a KSH script question...
>
> Can someone out there take a look at this script. I want to perform an
> operation based on the day of month. but the days (10 - 31) are giving
> me a problem. I would really like to keep this a one line
Hello all - I have a KSH script question...
sorry - the offending line is [10-31]) not [30-31])
Can someone out there take a look at this script. I want to perform an
operation based on the day of month. but the days (10 - 31) are giving
me a problem. I would really like to keep this a one liner
Hello all - I have a KSH script question...
Can someone out there take a look at this script. I want to perform an
operation based on the day of month. but the days (10 - 31) are giving
me a problem. I would really like to keep this a one liner if i can. How
bout anybody out there done something l
92 matches
Mail list logo
