RE: mounting linux filesystems
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Bob Pekarske Sent: Tuesday, 23 December 2003 3:19 AM To: [EMAIL PROTECTED] Subject: mounting linux filesystems I have two disks (IDE) that came from a dismantled Linux workstation. I would like to scan them for files worthy of saving. Is there any tool which will allow me to mount and read files from a linux filesystem? Thank you, Bob Pekarske [EMAIL PROTECTED] mount will let you do this, but you may need to compile a custom kernel to include EXT2FS support. Dave ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: mounting linux filesystems
-Original Message- From: User [mailto:User ] Sent: Tuesday, 23 December 2003 8:43 AM To: DG; [EMAIL PROTECTED] Subject: Re: mounting linux filesystems Hi Dave, Do you happen to know where to add these options in the kernel? I've been troubled by this problem for some time as well. Thanks, Jorn On Monday 22 December 2003 22:37, DG wrote: mount will let you do this, but you may need to compile a custom kernel to include EXT2FS support. Dave I added the following line to my custom kernel config file: options EXT2FS This option does not appear to be documented anywhere, and it is for a 5.1-RELEASE system btw. Dave ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
how to append multiple dumps to single tape
On the subject of multiple dumps, how does one append several dumps to the same tape? The dump man page does not seem to indicate an 'append' option. I have a SCSI DAT drive (DDS2) if that makes any difference to it's appendability. Thanx Dave ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Out of pty's
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Jez Hancock
Sent: Friday, 5 December 2003 10:46 AM
To: [EMAIL PROTECTED]
Subject: Re: Out of pty's
On Thu, Dec 04, 2003 at 03:25:54PM -0800, Justin Burke wrote:
/etc/ttys lists a ton of pseudo terminals, which is great. However,
after opening up 32 pseudo terminals (/dev/ptyp[0-9] and
/dev/ptyp[a-v]]), none of the other terminals are used (eg.
/dev/ptyq*).
How do I get the system to start using those devices?
Sorry to hear that - I've never gotten that many ttys used up :P I
could try it now I suppose with screen...
Mmm I see what you mean, I get up to ttypv as well and then
it complains
no more ttys :(
Sorry I'm not sure about that then... anyone else know?
--
Jez Hancock
- System Administrator / PHP Developer
This is covered in the FAQ:
10.19. How do I add pseudoterminals to the system?
If you have lots of telnet, ssh, X, or screen users, you will probably
run
out of pseudoterminals. Here is how to add more:
1. Build and install a new kernel with the line
pseudo-device pty 256
in the configuration file.
2. Run the commands
# cd /dev
# sh MAKEDEV pty{1,2,3,4,5,6,7}
to make 256 device nodes for the new terminals.
3. Edit /etc/ttys and add lines for each of the 256 terminals. They
should match the form of the existing entries, i.e. they look like
ttyqc none network
The order of the letter designations is tty[pqrsPQRS][0-9a-v], using
a
regular expression.
4. Reboot the system with the new kernel and you are ready to go.
Dave
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
ejecting a Zip disk using eject(1)
Greetings, I have a 5.1-RELEASE installation with an IDE Zip drive (amongst other IDE devices). # dmesg | grep afd0 afd0: 96MB IOMEGA ZIP 100 ATAPI [96/64/32] at ata1-slave PIO0 I installed the eject package ... # pkg_info | grep eject eject-1.4 Utility for ejecting media from CD or optical disk drive But when I try to eject a Zip disk, the following error occurs: # eject afd0 eject: No such file or directory Altho the package description indicates that eject only works on optical media, the man page states eject is a program to eject removable media from drive. Should eject work on an IDE Zip drive? Thanx Dave ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
size of rpc.statd process
Greetings, I have a 5.1-RELEASE installation running as a NFS server for a Linux client and another FreeBSD client. I haven't done anything unusual that I am aware of when setupping the share, however looking at the output from top shows the following for rpc.statd: PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND 359 root 960 257M80K select 0:01 0.00% 0.00% rpc.statd The SIZE is 257M (this is on a maching with 128M RAM and 1G swap) - that seems rather high. The handbook says that it could occupy a lot of memory with a lot of clients, but for only 2 clients? Is this of concern and, if so, how would I correct it? Thanx Dave ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: ejecting a Zip disk using eject(1)
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of JacobRhoden Sent: Tuesday, 2 December 2003 10:12 AM Subject: Re: ejecting a Zip disk using eject(1) On Tue, 2 Dec 2003 08:13 am, DG wrote: # eject afd0 eject: No such file or directory I dont know the syntax expected but you probably should be doing: eject /dev/afd0 Regards, Jacob I tried that too. The eject command accepts just the device name without a prefix, and prepends /dev/ as necessary. Specifically from man eject(1): SYNOPSIS eject [-fnv] device DESCRIPTION eject is a program to eject removable media from drive. The device is a removable drive name such as cd0, matcd0, mcd0, scd0, wcd0 or od0. eject unmounts the device if it was mounted brefore ejecting. Given that it says removable drive name such as ... I assumed that those listed were just examples, and that any ejectable media should be programatically ejectable. My interpretation of the man page may have been incorrect, or eject might not support Zip drives? Dave ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: ejecting a Zip disk using eject(1)
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Matthew Emmerton Sent: Tuesday, 2 December 2003 10:32 AM To: DG; [EMAIL PROTECTED] Subject: Re: ejecting a Zip disk using eject(1) I tried that too. The eject command accepts just the device name without a prefix, and prepends /dev/ as necessary. Specifically from man eject(1): SYNOPSIS eject [-fnv] device It's probably the case that the actual Zip drive itself doesn't have the hardware to eject the disk automatically -- you have to push the eject button on the front (like a floppy) -- at least with the Zip drives I've used. CD-ROMs, OTOH, can be ejected through software since the tray is motorized. -- Matt Emmerton Not so. The Zip drive ejects quite happily under a different open source UNIX-like operating system, and a similar IDE Zip drive in a different PC ejects quite happily under Windows 98. Dave ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: MySQL question...
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Melvyn Sopacua Sent: Monday, 1 December 2003 3:54 AM To: FreeBSD-questions Cc: Xpression Subject: Re: MySQL question... snip All databases will go under /var/db/mysql and the quick and dirty answer is: mysql -e GRANT ALL ON $dbname.* TO '$dbuser'@'localhost' IDENTIFIED BY '$userpasswd' -- Melvyn Something I've wondered is why the default location for the MySQL databasi is /var/db/mysql? Yes /var/db seems to make sense, but most /var filesystems would be fairly small. Is it generally common practice to create a symbolic link to somewhere on, say, /usr to store the databasi? Dave ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
strange kernel option USER_LDT suggested in wine doc
Greetings, I installed the wine port onto FreeBSD 5.1-RELEASE and noted that the doc suggested the following: To use Wine, your kernel must be rebuilt with the following lines added to the kernel config file (/sys/i386/conf/YourMachine): options USER_LDT options SYSVSHM options SYSVSEM options SYSVMSG The latter 3 are selected by default in my config file, but when I add the USER_LDT line and run config, I get the following output: ROWDY2: unknown option USER_LDT Is this option maybe depracated in 5.1? Thanx Dave ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
compiling ext2fs into a kernel
Greetings, I compiled a kernel from a standard 5.1-RELEASE installation yestreen to include support for ext2fs, but couldn't find any documentation about what option to set to include support for ext2fs. Grepping the handbook and all files in the .../i386/conf directory did not reveal any references to ext2fs at all. I eventually got around it by modifying the Makefile in the modules directory and successfully compiled a kernel with ext2fs support. As the kernel is for my gateway machine at home I temporarily don't have Internet access there, so I did a quick search at work this morning and found a reference to adding options EXT2FS to the config file - probably the more canonical way of setting options. My first question is: what documentation is there on the available kernel options? My second question (coming from a different open source UNIX-like operating system background) is: how does one specify to compile a 5.1 feature as a module as opposed to directly into the kernel, or are all module-capable features automatically compiled as modules? tia Dave ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
