Your style of reporting makes this hard to interpret. Here are a few thoughts.
Initially, a style note -- case counts in Unix/Linux, and the correct names
are ttyS00, ttyS01, and so forth ... so TTYS02, TTYS03, and the like are
not designators for serial ports on Linux systems.
Now the substan
e2fsck checks ext2 filesystems, not drives. /dev/hdb is NOT a filesystem;
it is a drive. The drive contains partitions; according to your (I
presume) fdisk output, partitions /dev/hdb1 and /dev/hdb2 contain ext2
filesystems.
The message you get in response to "e2fsck -b 131073 /dev/hdb" is
[root@Webby root]# e2fsck -b 131073 /dev/hdb
e2fsck 1.23, 15-Aug-2001 for EXT2 FS 0.5b, 95/08/09
e2fsck: Bad magic number in super-block while trying to open /dev/hdb
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an
OK, made a loop back cable. Works great on the windows box, fast and accurate.
On the linux box it's INCREDIBLY slow, makes 300 baud look blazing. Take like 2 hours
to print the whole dmesg:
cat dmesg (I have it saved to a file) >/dev/ttyS01
on second terminal
od -v /dev/ttyS01
nothing is
Give this a try
> string somevariable="somediretory/somesubdirectory/some\ directory\
with\ spaces/*"
string somevariable="somediretory/somesubdirectory/some directory with
spaces/*"
> cp $somevarable $somedestination
cp "$somevarable" $somedestination
-
To unsubscribe from this list: se
On Monday 14 October 2002 21:55, Paul Kraus wrote:
> GOT IT!!!
>
> Cp "$variable"*
Sort of. That obviously works. Since the asterisks and the variable are
expanded seperately in this case, it works. However, it may not work in every
case depending on what you are trying to accomplished. If you
GOT IT!!!
Cp "$variable"*
Thanks again!
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of James Mohr
Sent: Monday, October 14, 2002 3:58 PM
To: [EMAIL PROTECTED]
Subject: Re: Variable Quoting
On Monday 14 October 2002 20:38, Paul Kraus wrote:
> Now
Ok I lied. I understand why its not working but how should I workaround
it?
Do I have to have my script gather a list of the files and the pass it
the variable?
That sucks that I can not use a wildcard to just get all.
I have made these changes. Which I though would fix my problem.
string="My Doc
On Monday 14 October 2002 20:38, Paul Kraus wrote:
> Now with this change
> string="My Documents/*"
> cp "$string" /tmp
>
> cp: cannot stat 'My Documents/*':no such file or directory
Sure because the token that is passed to the cp command includes the asterisk,
it doesn't know that it should e
That is what I did.
---Directory is real and does exist and path verified using file
completion.
Here is an example.
string="/My Documents"
ls "$string"
Does work as it is intended.
Now with this change
string="My Documents/*"
cp "$string" /tmp
cp: cannot stat 'My Documents/*':no such file or
Ok I found out how to prevent it for separating the words as different
arguments. I need to encapsulate the variable with quotes.
How ever I am needing to do this with the cp command. When I try double
quoting a path with spaces in it for cp I get an error. If I make the
string somevariable="some
you want to read up on useradd program. You get to enter all information
on command line for each account. You could use $1 for user name, and
have password field filled in with starting password.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a mess
I have a problem with making a bash script. I have to make
many account sometimes on a Linux server (SuSE 7.0).
I would like to set a 'default' password for the new users,
just something like '123' or so (no vital information, just some
server for students, so a password like this is okay
> ( by the way
>
> you don't have to surround the variable name with braces unless it's
> right up against something else, as in
>
> filename="test"
> cp somefile ${test}.txt
>
> if it's seperated by white space they don't have to be there
>
> )
oops - my face is red now.
that should
Paul Kraus wrote:
> I am having trouble quoting with variables.
>
> For example
>
> source="/backup/My\ Documents/*"
> cp ${source} /tmp
either protect with quotes -or- escape the space...
source="/backup/My Documents/*" (quotes, no escape)
or
source=/backup/My\ Documents/* (escape,
At 16:49 14/10/2002 +0100, Mike Ricketts wrote:
>On Mon, 14 Oct 2002, Alan Womack wrote:
>
>> What I'd like is a console app that would pick up any gibberesh the
>> mouse would generate while I scroll it 's test wheel.
>>
>minicom, maybe?
>Or possibly a simple cat /dev/ttyS0 might work?
>
I have
I am having trouble quoting with variables.
For example
source="/backup/My\ Documents/*"
cp ${source} /tmp
When I run this it will see everything up to my and bomb.
Now if I type the exact same path in the exact same way into the code
cp /backup/My\ Documents/*"
It will work fine.
This is no
On Mon, 14 Oct 2002, Alan Womack wrote:
> What I'd like is a console app that would pick up any gibberesh the
> mouse would generate while I scroll it 's test wheel.
>
minicom, maybe?
Or possibly a simple cat /dev/ttyS0 might work?
--
Mike Ricketts <[EMAIL PROTECTED]> htt
port with a mouse attached outside of X? I have a linuxfromscratch 3.3 system with
console and SVGAlib installed only. I have installed a 4 port STB card and am now
trying to get my mouse going for links on port 1 which I have run setserial on and I
think I have the correct information, but t
19 matches
Mail list logo
