Pages

Search

tape drive: Error with sense data - Forums Linux

tape drive: Error with sense data - Forums Linux

tape drive: Error with sense data

Posted: 08 Oct 2004 05:36 AM PDT

[cold.system removed, non-existant group col.help removed]
[FollowUp-To: header set to col.misc]

"Mr. Murphy Wong" <hk> writes:

[...]
 
 

[...]
 

[...]

Why didn't you simply change the tape? "Sense key medium error"
is indicating that the tape itself is damaged. That should have been
your first target.


Michael

--
Michael Buchenrieder * greenie.muc.de * http://www.muc.de/~mibu
Lumber Cartel Unit #456 (TINLC) & Official Netscum
Note: If you want me to send you email, don't munge your address.

Problem with 2 users in diferent groups

Posted: 08 Oct 2004 01:32 AM PDT

Deiviz <com> wrote: 
 

Change the directory's mode to use bsd file creation semantics.
Set the directory to g+sw, and make sure its group is "sharegroup".

Peter

Mounting non-Linux partitions

Posted: 07 Oct 2004 06:45 PM PDT

the black rose wrote:
 

You can simply type your entry into /etc/fstab, and there are other entries
there to use as examples.

But if the partition is NTFS, be careful -- writing is not safe.

--
Paul Lutus
http://www.arachnoid.com

help with allowing ftp access.

Posted: 07 Oct 2004 12:14 PM PDT

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

me wrote:
[snip] 

This is better.

The "connection refused" error occured because you had no ftp server running.

The "421 Service not available" error comes directly from the ftp server. A
"4xx" level message is one that indicates a transient error condition. The
"x2x" level of the message indicates that it is a reply referring to a control
or data connection. So, you are connecting with a live ftp server, and it is
telling you that it cannot let you continue.

So, this indicates an ftp server configuration condition that's causing the
ftp server to refuse connections. Take a look at the man page for your ftp
server (in.ftpd) and see what configuration files are used. Take a look at
those files, and see if there's anything that would cause the server to reject
the connection with a 421 error. Try the /etc/ftpaccess file, and see if there
are any date/time limits set, or client address restrictions.


- --
Lew Pitcher

Master Codewright & JOAT-in-training | GPG public key available on request
Registered Linux User #112576 (http://counter.li.org/)
Slackware - Because I know what I'm doing.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBZeOyagVFX4UWr64RAvFAAKCuq+vjZPUMQMKAB0xfc8 JPhKfSsQCgwZem
4VCXYpWB7BWpU1FUSazrFAo=
=XevG
-----END PGP SIGNATURE-----

debian sarge DVD apt setup fails during base install

Posted: 07 Oct 2004 11:42 AM PDT

On Thu, 07 Oct 2004 13:10:50 -0700, Paul Lutus wrote:
 

Did all of the above before seeking help here. As of tonight I was able to
get it working. Ran base-config for the twenty-somethingth time, and
during apt configuration chose filesystem as opposed to editing
sources.list, pointed to /usr/local/src/dvd1 and apt was happy. It may be
that when I first tried to do it that way with the actual DVD that I
forgot to mount the disc. I shouldn't be making that mistake after the
last few years of using linux, but at this point I won't swear I didn't.

Next step is to start over from scratch and see if it works correctly this
time. I want to identify what and where I find any glitch other than the
user ... if there are any;-)

Thanks, Paul, for your response.

Nemomarii

rw vs. umask in mount call, also, conditional mounting

Posted: 07 Oct 2004 08:28 AM PDT

On Thu, 2004-10-07 at 08:28 -0700, gonzalo briceno wrote: 

The 'rw' option is something passed to the mount command that tells it
to mount the selected item as both readable and writable; 'ro' is the
complementary option, which says to mount it as 'read only'. If you
specify 'ro' then that will set the *entire* item as read only,
*regardless* of individual file permissions.

The umask basically sets up the 'default' permissions set that will be
applied to any new file created within that mountpoint (actually, it's a
bit more complicated than that; check 'man 2 umask' for details--it's
essentially a 'mask' for allowable permissions). Essentially, requested
permissions => umask filter = actual permissions applied to created
file. Note, you can use chmod to change the actual permissions of the
file later; the umask only applies to newly created files.
 

Well, technically, no, because the mount command defaults to whichever
option (rw vs. ro) is most appropriate for the media (I believe so
anyway; somebody please correct me if I'm wrong, as the man page doesn't
specify). For instance, a CDROM will always be mounted as 'ro' because
'rw' is meaningless to a CD. However, it's always better to explicitly
specify it in the /etc/fstab file, just so it serves as a reminder of
how the mount point is set up.

Anyway, your presumption isn't true; if you want to be able to write to
the mount point *at all*, you *need* to specify the 'rw' option (whether
explicitly or through mount presuming it for you).
 

Yup. If you need to *ever* be able to write to the device, you *need* to
specify the 'rw' option, either explicitly or through mount presuming it
for you. If you specify 'ro', you won't be able to write to that device
*at all*, regardless of individual file permissions. Think of it as a
master override.
 

Probably not the way you're thinking. Each slot on your card reader is a
separate drive, as far as Linux is concerned, so each slot is assigned
its own device, regardless of whether there's actually a card present or
not (technically, /dev/sda and /dev/sdb are the drives
themselves; /dev/sda1 and /dev/sdb1 refer to the first partition on the
media inserted into the drive). You *can* (and should) have a separate
line in /etc/fstab for each slot. Entries in /etc/fstab just define
*how* to mount the device, not whether it is *actually* mounted
(well ... actually, mount scans entries in /etc/fstab at bootup to
determine which ones to mount automatically, by checking for the 'auto'
and 'noauto' tags).

Supermount has nothing to do with recognizing new drives and/or
partitions; *all* it handles is the mounting and unmounting of removable
media (CDs, floppy disks, media cards, etc). The detection of new
potential devices is handled through the hotplug mechanism. Try
unplugging your card reader; if everything's set up correctly, the
entries in /etc/fstab defining the slots in your card reader will
shortly disappear. Once you plug it back in, they should shortly
reappear (although they will be the defaults that Mandrake sets up,
rather than any customizations you may have made).

Grub: can grub execute a script/batch file?

Posted: 06 Oct 2004 06:35 PM PDT

Sean Cleary <com> wrote: 
 

Then why do you ask the boot loader to do it now, instead of leaving it
to the [d]O/S, like you did before?
 
 

Oh. Well, the windows o/s as it comes has no driver for linux file
systems, so you would have to put your grub.conf and other stuff on a
vfat filesystem so that windows can edit it (and so can linux).

Grub is lacking in the "do what I want, not what you want me to do"
department.
 

Well, you can't do that all in grub. The grub boot loader (second
stage?) reads the conf file to find out what image or boot sector it
ought to transfer control to next. That's where the "default" info
comes from. There is no "default" info implanted into the boot sector or
map file as with lilo, so you have toedit that file.

Thus you need to boot an operating system that can launch an
application that can edit it. It seems to me that you will have to
handle the windows "default" by doing whatever trick you did before
with msdos and moving into place a grub.conf file that says "boot to
a windows boot sector and let it decide via its boot.ini what to do
next".

 

Well, find out.
 

File: grub.info, Node: Command-line and menu entry commands, Prev: General co

The list of command-line and menu entry commands
================================================

These commands are usable in the command-line and in menu entries.
If you forget a command, you can run the command `help' (*note help::).

* Menu:

* blocklist:: Get the block list notation of a file
* boot:: Start up your operating system
* cat:: Show the contents of a file
* chainloader:: Chain-load another boot loader
* cmp:: Compare two files
* configfile:: Load a configuration file
* debug:: Toggle the debug flag
* displayapm:: Display APM information
* displaymem:: Display memory configuration
* embed:: Embed Stage 1.5
* find:: Find a file
* fstest:: Test a filesystem
* geometry:: Manipulate the geometry of a drive
* halt:: Shut down your computer
* help:: Show help messages
* impsprobe:: Probe SMP
* initrd:: Load an initrd
* install:: Install GRUB
* ioprobe:: Probe I/O ports used for a drive
* kernel:: Load a kernel
* lock:: Lock a menu entry
* makeactive:: Make a partition active
* map:: Map a drive to another
* md5crypt:: Encrypt a password in MD5 format
* module:: Load a module
* modulenounzip:: Load a module without decompression
* pause:: Wait for a key press
* quit:: Exit from the grub shell
* reboot:: Reboot your computer
* read:: Read data from memory
* root:: Set GRUB's root device
* rootnoverify:: Set GRUB's root device without mounting
* savedefault:: Save current entry as the default entry
* setup:: Set up GRUB's installation
* automatically
* testload:: Load a file for testing a filesystem
* testvbe:: Test VESA BIOS EXTENSION
* uppermem:: Set the upper memory size
* vbeprobe:: Probe VESA BIOS EXTENSION


Note "savedefault".

Peter

Laurenz Albe: I apolgise.

Posted: 06 Oct 2004 06:33 PM PDT

Laurenz Albe <com> wrote in message news:<ck2sge$htd$nextra.at>... 

No, you are not a trouble maker. You are a kind helpfull person.
Sean

Changed root permissions, can't log on..

Posted: 06 Oct 2004 04:37 PM PDT

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message

In comp.os.linux.setup Moe Trin <example.tld>: 
 

Yup, quite shorter and seems to work, I'll see if I can remember
next time typing the command.;)

--
Michael Heiming (GPG-Key ID: 0xEDD27B94)
mail: echo qr | perl -pe 'y/a-z/n-za-m/'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBZY7ZAkPEju3Se5QRAlvnAKDSV//KC5kuL0SmV2jcMlPx55rHswCfbGV9
oUUVCfELPAkTK3M8jDefGaM=
=KEsi
-----END PGP SIGNATURE-----

To kernel 2.6.8:after compiling and installing, no initrd.img generated

Posted: 06 Oct 2004 11:26 AM PDT

In comp.os.linux.setup, wildchild uttered these immortal words:
 

I use this:
http://www.debian.org/doc/manuals/reference/ch-kernel.en.html

It talks about a 2.4 kernel but it works with 2.6 as well. It's never failed
for me.

--
Andy.

do you need to 'register' a custom module in linux 2.6.x

Posted: 06 Oct 2004 10:17 AM PDT

On Wed, 2004-10-06 at 10:17 -0700, gonzo wrote: 

Modules in 2.6 end in a .ko extension (for "kernel object"); however,
using a 2.4 module in 2.6 will, very likely, just fail to work, as the
API is certainly different (although perhaps not in ways that matter to
this module), and the ABI is probably different.

AFAIK, the only way to use a 2.4 module in 2.6 is to recompile it from
source, using the desired 2.6 kernel as the base. If the APIs that the
module relies on have not changed, that should work; if they have
changed, then the module will need to be adapted to the 2.6 APIs.

Also, if you do not have MOD_VERSIONS enabled, this just won't work,
period, as the kernel will be unable to verify which ABI the module is
compiled for. It *may* appear to install, but I wouldn't rely on it.

After a quick search, however, I'd guess your hopes of getting it to
work under 2.6 are probably doomed; check
http://netevil.org/node.php?nid=90

You can also check out the same search results I browsed through at
http://www.google.com/search?q=rtl8180%20linux%202.6

What happened to GRUB?

Posted: 06 Oct 2004 01:18 AM PDT

On Wed, 06 Oct 2004 13:33:01 -0700, Nick the bubble wrote:
 

Good, now boot with the FC2 installation CD or DVD at the displayed menu
screen type; linux rescue

Answer a few questions and read the screens as they appear, they will tell
you how to use the 'chroot' command. Follow the chroot instructions and
type something like; /sbin/grub-install --recheck /dev/hda


--
Hi! I'm a .sig virus! Please copy me to your .sig! so I can spread
This E-mail is safe, no Microsoft products were used in creating me!

How to enable new videocard in Fedora?

Posted: 05 Oct 2004 01:40 PM PDT

Digital Puer <com> wrote: 

Are you sure it is supported? I looked at

http://www.nvidia.com/object/products_supported.html

and it wasn't there...

Laurenz Albe

[Debian/Knoppix] LVM at boot time

Posted: 04 Oct 2004 09:44 PM PDT

Bill Marcum <com.urgent> wrote: 
 

Well, er, :

$ cat /etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file should contain the names of kernel modules that are
# to be loaded at boot time, one per line. Comments begin with
# a '#', and everything on the line after them are ignored.
jbd
dm-mod
ext3
rtc
ide_scsi
.... etc

so, the point is not here.

--
Laurent Bloch - http://mssi.auteuil.inserm.fr - INSERM

SB 16 ISA

Posted: 03 Oct 2004 09:18 AM PDT

Dzn wrote:
 

You never said what the problem was. No sound? Since your sb module is
running my guess is that everything's fine, but you need to turn up the
volume with a mixer.

I have a Soundblaster 16 ISA non-PnP soundcard and whenever I install a new
system I have to personally enable it. I've always had good luck running
sndconfig.

--
OS squared: open software times open standards.