[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#286515: are you sure swap can be labeled?



On Tue, 29 Mar 2005, Harald Dunkel wrote:

> Vassilii Khachaturov wrote:
> >>You could use something like
> >>
> >>LABEL=root /      ext2    defaults    0       1
> >>LABEL=swap none   swap    sw          0       0
> >>LABEL=home /home  ext2    defaults    0       1
> >>
> >>in your /etc/fstab, instead of /dev/hda1 or /dev/sda1.
> >
> >
> > Is your fstab example a real life one, or fictional? in the 1st case,
> > how did you manage to have the swap labeled??
> >
>
> mkswap -L myswap /dev/sda2

-L doesn't work here:

	travel:/home/vassilii# mkswap -L swap /dev/hda8
	Usage: mkswap [-c] [-v0|-v1] [-pPAGESZ] /dev/name [blocks]
	travel:/home/vassilii# mkswap --version
	mkswap from util-linux-2.12
	travel:/home/vassilii# dlocate /sbin/mkswap
	util-linux: /sbin/mkswap
	travel:/home/vassilii# dpkg --status util-linux
	Package: util-linux
	Essential: yes
	Status: install ok installed
	Priority: required
	Section: base
	Installed-Size: 976
	Maintainer: LaMont Jones <lamont@debian.org>
	Architecture: i386
	Version: 2.12-10
	[snip]

What version are you using?

> >  options ide-scsi ignore=hdd
> >
> > added to the modules.conf (via update-modutils), the scsi
> > emulation still grabs hdd (somehow pulled in by the sata_sil?)
> >
> This is obsolete.

What is obsolete? I know that the scsi emulation for cdrw is obsolete,
but I was asking how to make sure that it doesn't happen in 2.6,
even when the SATA hard drive forces the SCSI storage drivers into existence.

> Try something like
>
> 	cdrecord /dev/cdrom my.iso
>
> for writing CDs, regardless whether it is SCSI or IDE.

Yeah, and if /dev/cdrom (/dev/cdrw in my case; the cdrom is another -
R/O - device) is mapped to a scsi emulation device, I get an error.
If I force a link cdrw -> hdd, it doesn't work at all because of
the conflict with the scsi emulation layer (AFAIU you may not use
an IDE device directly once it's grabbed by the scsi emulation).

(I'm away from the PC in question at this time, otherwise I would
have cited the precise error msgs. If you need additional input,
please tell me.)




Reply to: