Sponsored Content
Full Discussion: Windows to UNIX issues
Top Forums Shell Programming and Scripting Windows to UNIX issues Post 302433601 by Dird on Wednesday 30th of June 2010 06:03:18 AM
Old 06-30-2010
Thanks for the info pludi. There was reference to CAT instead of cat and once it was changed the script worked.

Thanks <3

---------- Post updated at 05:03 AM ---------- Previous update was at 04:10 AM ----------

The next error I can't manage to fix (or google) is: stty: invalid argument `-oproc'
It's from the line: echo "$PROMPT\c"; stty -oproc; read ANS

I tried just removing the -oproc but I get: speed 38400 baud; line = 0;
being displayed.

I tried removing the stty part all together but it becomes a never ending loop (loop only ends when S or D is specified but without the stty S or D isn't accepted either despite the rest appearing right).

Here's the function for more info on the code: pastebin - Stuff - post number 1892380

Last edited by Dird; 06-30-2010 at 07:17 AM..
 

4 More Discussions You Might Find Interesting

1. Solaris

Windows,Solaris, Red Hat triple boot issues

I have a pentium IV with 512 MB ram and 80 GB HDD. I first installed windows XP on the first primary partition, then Solaris on the second with 20 GB for the solaris partition, and when rebooted , the grub menu functioned as expected giving me the options to dual boot, so next I wanted to install... (3 Replies)
Discussion started by: saagar
3 Replies

2. UNIX for Dummies Questions & Answers

Cygwin/X11 issues on Windows 7

Hi All, I recently upgraded to windows 7 and am therefore reinstalling cygwin/x11 after a long time. On XP I would start xterm from the startxwin.bat file. I am experiencing trouble starting with the startxwin executable which is the new recommended startup method as well as afew other... (2 Replies)
Discussion started by: ScKaSx
2 Replies

3. Windows & DOS: Issues & Discussions

Windows 7 64 bit issues with X11

Hi, I was hoping that somebody could assist me with the following issue. I recently installed a windows 7 64 bit professional on a desktop with following specs: Intel Core i7 3.4Ghz, 16 GB DDR3 RAM, AMD Radeon HD 6450. (Which was a upgrade of a xp 32 bit based system) Since I'm more... (10 Replies)
Discussion started by: kristofvdo
10 Replies

4. UNIX for Advanced & Expert Users

Issues with passwordless sftp2 from windows to Linux using F-Secure SSH Client

Hi, I am facing problems whie trying to do a passwordless ssh to Unix box from windows. Public key was generated using F-secure. When the F-secure client attempts it connects without password but when I try to use sftp2 in command line it prompts for password. I have tried several options and... (0 Replies)
Discussion started by: dhrajj
0 Replies
FINDSMB(1)																FINDSMB(1)

NAME
findsmb - list info about machines that respond to SMB name queries on a subnet SYNOPSIS
findsmb [subnetbroadcastaddress] DESCRIPTION
This perl script is part of the samba(7) suite. findsmb is a perl script that prints out several pieces of information about machines on a subnet that respond to SMB name query requests. It uses nmblookup(1) and smbclient(1) to obtain this information. OPTIONS
-r Controls whether findsmb takes bugs in Windows95 into account when trying to find a Netbios name registered of the remote machine. This option is disabled by default because it is specific to Windows 95 and Windows 95 machines only. If set, nmblookup(1) will be called with -B option. subnet broadcast address Without this option, findsmb will probe the subnet of the machine where findsmb(1) is run. This value is passed to nmblookup(1) as part of the -B option. EXAMPLES
The output of findsmb lists the following information for all machines that respond to the initial nmblookup for any name: IP address, Net- BIOS name, Workgroup name, operating system, and SMB server version. There will be a '+' in front of the workgroup name for machines that are local master browsers for that workgroup. There will be an '*' in front of the workgroup name for machines that are the domain master browser for that workgroup. Machines that are running Windows for Work- groups, Windows 95 or Windows 98 will not show any information about the operating system or server version. The command with -r option must be run on a system without nmbd(8) running. If nmbd is running on the system, you will only get the IP address and the DNS name of the machine. To get proper responses from Windows 95 and Windows 98 machines, the command must be run as root and with -r option on a machine without nmbd running. For example, running findsmb without -r option set would yield output similar to the following IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION --------------------------------------------------------------------- 192.168.35.10 MINESET-TEST1 [DMVENGR] 192.168.35.55 LINUXBOX *[MYGROUP] [Unix] [Samba 2.0.6] 192.168.35.56 HERBNT2 [HERB-NT] 192.168.35.63 GANDALF [MVENGR] [Unix] [Samba 2.0.5a for IRIX] 192.168.35.65 SAUNA [WORKGROUP] [Unix] [Samba 1.9.18p10] 192.168.35.71 FROGSTAR [ENGR] [Unix] [Samba 2.0.0 for IRIX] 192.168.35.78 HERBDHCP1 +[HERB] 192.168.35.88 SCNT2 +[MVENGR] [Windows NT 4.0] [NT LAN Manager 4.0] 192.168.35.93 FROGSTAR-PC [MVENGR] [Windows 5.0] [Windows 2000 LAN Manager] 192.168.35.97 HERBNT1 *[HERB-NT] [Windows NT 4.0] [NT LAN Manager 4.0] VERSION
This man page is correct for version 3.0 of the Samba suite. SEE ALSO
nmbd(8), smbclient(1), and nmblookup(1) AUTHOR
The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed. The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was done by Alexander Bokovoy. FINDSMB(1)
All times are GMT -4. The time now is 07:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy