On Thu, Jun 13, 2024 at 06:59:49AM +0200, Kamil Jońca wrote:
> to...@tuxteam.de writes:
[...]
> > and of course, if you are using a desktop environment and NetworkManager
> > or systemd-networkd, it's probably better to go with the flow and let
> > them do.
>
> About year ago none of them was ab
to...@tuxteam.de writes:
> On Thu, Jun 13, 2024 at 06:30:27AM +0200, to...@tuxteam.de wrote:
>
> [following up on myself, bad style, I know]
>
>> For my laptop, I very much prefer to say "sudo ifup eth0" than to
>> say "sudo ifup en0ps&&@*#!☠" thankyouverymuch :)
>
> and of course, if you are usin
On Thu, Jun 13, 2024 at 06:30:27AM +0200, to...@tuxteam.de wrote:
[following up on myself, bad style, I know]
> For my laptop, I very much prefer to say "sudo ifup eth0" than to
> say "sudo ifup en0ps&&@*#!☠" thankyouverymuch :)
and of course, if you are using a desktop environment and NetworkMa
20.06.23, 08:36 +0200, Rick Thomas:
I've been upgrading my machines Bullseye => Bookworm recently. In a few of these
upgrades, the name of the ethernet device changed. (E.g. enP2p32s15f0 =>
enP2p0s15f0) This required changes to /etc/network/interfaces in order to start up
the interface.
T
I've been upgrading my machines Bullseye => Bookworm recently. In a few of
these upgrades, the name of the ethernet device changed. (E.g. enP2p32s15f0 =>
enP2p0s15f0) This required changes to /etc/network/interfaces in order to
start up the interface.
This is only a minor inconvenience (thou
On Tue 09 Nov 2021 at 23:04:13 (+0100), deloptes wrote:
> pe...@easthope.ca wrote:
>
> > OK, although
> > surround21:CARD=Set,DEV=0
> > and
> > surround40:CARD=Set,DEV=0
> > aren't atomic names. Is the syntax and semantics explained in
> > documentation?
> >
> > No surround22, surround23 ... sur
pe...@easthope.ca wrote:
> surround21:CARD=Set,DEV=0
> and
> surround40:CARD=Set,DEV=0
> aren't atomic names. Is the syntax and semantics explained in
> documentation?
>
> No surround22, surround23 ... surround39 evident here. How does ALSA
> derive or find the names and numbers?
you hopefully
Ref. https://lists.debian.org/debian-user/2021/09/msg01112.html
Subject: Re: Persistent names for audio devices.
From: David Wright
Date: Wed, 29 Sep 2021 22:35:11 -0500
Message-id: <20210930033511.gc22...@axis.corp>
References:
<_Vy48xSpy3r0uj8kBgbIiS_l-GGEeoinqJc5I64K4YfKpq
On Monday, April 05, 2021 08:36:04 AM Richard Hector wrote:
> On 5/04/21 11:48 pm, Greg Wooledge wrote:
> > On Mon, Apr 05, 2021 at 09:29:59PM +1200, Richard Hector wrote:
> >> /dev/vg-backup0/d-rh-rm1-home
> >>
> >> /dev/mapper/vg--backup0-d--rh--rm1--home
> >>
> >> Apr 5 07:06:25 backup system
On 05.04.2021 17:36, Richard Hector wrote:
On 5/04/21 11:48 pm, Greg Wooledge wrote:
On Mon, Apr 05, 2021 at 09:29:59PM +1200, Richard Hector wrote:
/dev/vg-backup0/d-rh-rm1-home
/dev/mapper/vg--backup0-d--rh--rm1--home
Apr 5 07:06:25 backup systemd[1]:
dev-mapper-vg\x2d\x2dbackup0\x2dd\
On 5/04/21 11:48 pm, Greg Wooledge wrote:
On Mon, Apr 05, 2021 at 09:29:59PM +1200, Richard Hector wrote:
/dev/vg-backup0/d-rh-rm1-home
/dev/mapper/vg--backup0-d--rh--rm1--home
Apr 5 07:06:25 backup systemd[1]:
dev-mapper-vg\x2d\x2dbackup0\x2dd\x2d\x2drh\x2d\x2drm1\x2d\x2dsrv.device:
Job
On Mon, Apr 05, 2021 at 09:29:59PM +1200, Richard Hector wrote:
> /dev/vg-backup0/d-rh-rm1-home
> /dev/mapper/vg--backup0-d--rh--rm1--home
> Apr 5 07:06:25 backup systemd[1]:
> dev-mapper-vg\x2d\x2dbackup0\x2dd\x2d\x2drh\x2d\x2drm1\x2d\x2dsrv.device:
> Job
> dev-mapper-vg\x2d\x2dbackup0\x2dd\x2
Hi all,
I use LVM quite a lot.
> richard@backup:~$ sudo lvs|wc -l
> 140
The trouble is, things like device mapper seem to involve lots of name
translations.
So the volume I call
d-rh-rm1-home
(for dirvish backups of /home on rh-rm1 (my (rh) first (1) redmine
(rm) server)) on
vg-backu
On Fri 25 Aug 2017 at 09:22:56 (-0400), Dan Ritter wrote:
> On Fri, Aug 25, 2017 at 02:20:38AM -0400, Gene Heskett wrote:
> > On Friday 25 August 2017 01:27:47 David Wright wrote:
> >
> > > > But what has that to do with having the proper entry's
> > > > in /etc/resolv.conf? Whose active lines ar
On Fri, Aug 25, 2017 at 02:20:38AM -0400, Gene Heskett wrote:
> On Friday 25 August 2017 01:27:47 David Wright wrote:
>
> > > But what has that to do with having the proper entry's
> > > in /etc/resolv.conf? Whose active lines are:
> > >
> > > nameserver 192.168.71.1
> > > search host,dns
> >
> >
Hi all,
with great interest I read all your discusssions. They were very interesting
and I got a lot of informations. Thanks for it!
I still wondered, if the new naming scheme is more usable for unexperienced
users, say, someone with a notebook and often changing devices, like usb-
drives, usb
On Friday 25 August 2017 01:27:47 David Wright wrote:
> On Fri 25 Aug 2017 at 00:54:11 (-0400), Gene Heskett wrote:
> > On Thursday 24 August 2017 22:15:53 David Wright wrote:
> > > On Thu 24 Aug 2017 at 20:58:18 (-0400), Gene Heskett wrote:
> > > > On Thursday 24 August 2017 12:30:37 Dan Ritter w
On Fri 25 Aug 2017 at 00:54:11 (-0400), Gene Heskett wrote:
> On Thursday 24 August 2017 22:15:53 David Wright wrote:
>
> > On Thu 24 Aug 2017 at 20:58:18 (-0400), Gene Heskett wrote:
> > > On Thursday 24 August 2017 12:30:37 Dan Ritter wrote:
> > > > On Thu, Aug 24, 2017 at 10:43:56AM -0500, Davi
On Thu 24 Aug 2017 at 23:00:19 (-0400), The Wanderer wrote:
> On 2017-08-24 at 12:40, David Wright wrote:
>
> > On Thu 24 Aug 2017 at 12:02:11 (-0400), The Wanderer wrote:
>
> >> On 2017-08-24 at 11:43, David Wright wrote:
>
> >>> There are plenty of ways that you, or Debian, can set a default.
On Thursday 24 August 2017 22:15:53 David Wright wrote:
> On Thu 24 Aug 2017 at 20:58:18 (-0400), Gene Heskett wrote:
> > On Thursday 24 August 2017 12:30:37 Dan Ritter wrote:
> > > On Thu, Aug 24, 2017 at 10:43:56AM -0500, David Wright wrote:
> > > > The history of computing is littered with stat
On 2017-08-24 at 12:40, David Wright wrote:
> On Thu 24 Aug 2017 at 12:02:11 (-0400), The Wanderer wrote:
>> On 2017-08-24 at 11:43, David Wright wrote:
>>> There are plenty of ways that you, or Debian, can set a default.
>>> But it surprises me that so many people grumble about this
>>> change.
On Thu 24 Aug 2017 at 20:58:18 (-0400), Gene Heskett wrote:
> On Thursday 24 August 2017 12:30:37 Dan Ritter wrote:
> > On Thu, Aug 24, 2017 at 10:43:56AM -0500, David Wright wrote:
> > > The history of computing is littered with statements like
> > > "virtually every computer has exactly one or t
On Thursday 24 August 2017 12:30:37 Dan Ritter wrote:
> On Thu, Aug 24, 2017 at 10:43:56AM -0500, David Wright wrote:
> > On Thu 24 Aug 2017 at 10:20:52 (-0400), Dan Ritter wrote:
> > > There are, of course, five different ways to do this (at a
> > > minimum):
> > >
> > > 1. /dev/sda1 is based on
expected to always be available from
> boot-time onwards.
You just made an assumption that does not match my reality, and
you didn't even realize that you made it. :) The SD card may
already be plugged in and contain the OS itself.
But seriously, the only point I'm trying to make here i
On Thu 24 Aug 2017 at 12:59:46 (-0400), Dan Ritter wrote:
> On Thu, Aug 24, 2017 at 11:40:28AM -0500, David Wright wrote:
> > On Thu 24 Aug 2017 at 12:02:11 (-0400), The Wanderer wrote:
> > > On 2017-08-24 at 11:43, David Wright wrote:
> > >
> > > > On Thu 24 Aug 2017 at 10:20:52 (-0400), Dan Ritt
On Thu 24 Aug 2017 at 13:35:17 (-0400), Greg Wooledge wrote:
> On Thu, Aug 24, 2017 at 11:51:48AM -0500, David Wright wrote:
> > For you, they wrote the last screenful of
> > https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
>
> One of the bullet points on that pa
On Thu, Aug 24, 2017 at 11:51:48AM -0500, David Wright wrote:
> For you, they wrote the last screenful of
> https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
One of the bullet points on that page says:
* Stable interface names even if you have to replace broken
On Thu, Aug 24, 2017 at 11:40:28AM -0500, David Wright wrote:
> On Thu 24 Aug 2017 at 12:02:11 (-0400), The Wanderer wrote:
> > On 2017-08-24 at 11:43, David Wright wrote:
> >
> > > On Thu 24 Aug 2017 at 10:20:52 (-0400), Dan Ritter wrote:
> > If things ever do reach a point where that is no longe
On Thu 24 Aug 2017 at 11:56:55 (-0400), The Wanderer wrote:
> At my workplace, we have over 4,000 computers, which run Windows most of
> the time but are occasionally booted to a bare-bones live-CD type of
> Linux environment (and not a particularly customizable one) for
> diagnostic and/or mainte
On Thu 24 Aug 2017 at 12:02:11 (-0400), The Wanderer wrote:
> On 2017-08-24 at 11:43, David Wright wrote:
>
> > On Thu 24 Aug 2017 at 10:20:52 (-0400), Dan Ritter wrote:
>
> >> Getting back to the original point, NIC names -- virtually every
> >> computer has exactly one or two NICs, and is best
On Thu, Aug 24, 2017 at 10:43:56AM -0500, David Wright wrote:
> On Thu 24 Aug 2017 at 10:20:52 (-0400), Dan Ritter wrote:
> > There are, of course, five different ways to do this (at a
> > minimum):
> >
> > 1. /dev/sda1 is based on discovery order. Changes in discovery order
> > may indicate a sig
On Thu 24 Aug 2017 at 09:17:00 (-0400), The Wanderer wrote:
> On 2017-08-24 at 07:52, to...@tuxteam.de wrote:
>
> > On Thu, Aug 24, 2017 at 01:11:27PM +0200, Hans wrote:
> >
> >> Hi folks,
> >
> >> I stumbled over the new network names (i.e. wl0p8 instead of wlan0), and
> >> of
> >> course I kn
On 2017-08-24 at 11:43, David Wright wrote:
> On Thu 24 Aug 2017 at 10:20:52 (-0400), Dan Ritter wrote:
>> Getting back to the original point, NIC names -- virtually every
>> computer has exactly one or two NICs, and is best served by eth0
>> and wlan0. The computers with 3-5 NICs are usually bes
On 2017-08-24 at 11:48, Darac Marjal wrote:
> On Thu, Aug 24, 2017 at 08:30:33AM -0500, Dave Sherohman wrote:
>
>> On Thu, Aug 24, 2017 at 09:17:00AM -0400, The Wanderer wrote:
>>> To the best of my awareness, the rationale for calling this
>>> "predictable network interface names" is that, on a
On Thu, Aug 24, 2017 at 08:30:33AM -0500, Dave Sherohman wrote:
On Thu, Aug 24, 2017 at 09:17:00AM -0400, The Wanderer wrote:
However, I'll point out that machines with this many network interfaces
are *by far* the exception rather than the rule; indeed, even machines
with more than *one* interf
On Thu 24 Aug 2017 at 10:20:52 (-0400), Dan Ritter wrote:
> On Thu, Aug 24, 2017 at 08:30:33AM -0500, Dave Sherohman wrote:
> > This closely parallels the move from using /dev/sdXn to UUIDs for
> > referring to filesystems. Probably superior in theory and doesn't cause
> > any issues as long as y
On Thu, Aug 24, 2017 at 08:30:33AM -0500, Dave Sherohman wrote:
> On Thu, Aug 24, 2017 at 09:17:00AM -0400, The Wanderer wrote:
> > However, I'll point out that machines with this many network interfaces
> > are *by far* the exception rather than the rule; indeed, even machines
> > with more than *
On 2017-08-24 at 09:30, Dave Sherohman wrote:
> On Thu, Aug 24, 2017 at 09:17:00AM -0400, The Wanderer wrote:
>
>> However, I'll point out that machines with this many network
>> interfaces are *by far* the exception rather than the rule; indeed,
>> even machines with more than *one* interface ea
On Thu, Aug 24, 2017 at 09:17:00AM -0400, The Wanderer wrote:
> However, I'll point out that machines with this many network interfaces
> are *by far* the exception rather than the rule; indeed, even machines
> with more than *one* interface each of wired and wireless are reasonably
> rare.
In the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Aug 24, 2017 at 09:17:00AM -0400, The Wanderer wrote:
> On 2017-08-24 at 07:52, to...@tuxteam.de wrote:
[...]
> However, I'll point out that machines with this many network interfaces
> are *by far* the exception rather than the rule [...]
I
On 2017-08-24 at 07:52, to...@tuxteam.de wrote:
> On Thu, Aug 24, 2017 at 01:11:27PM +0200, Hans wrote:
>
>> Hi folks,
>
>> I stumbled over the new network names (i.e. wl0p8 instead of wlan0), and of
>> course I know, that this is obviously the newe standard (please correct me,
>> i
>> I am wr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Aug 24, 2017 at 01:11:27PM +0200, Hans wrote:
> Hi folks,
>
> I stumbled over the new network names (i.e. wl0p8 instead of wlan0), and of
> course I know, that this is obviously the newe standard (please correct me, i
> I am wrong).
Relax.
No, this is not just debian, you'll find it on archlinux as well.
On Thu, 24 Aug 2017, Hans wrote:
Date: Thu, 24 Aug 2017 07:11:27
From: Hans
To: debian-user@lists.debian.org
Subject: Question to new network device names
Resent-Date: Thu, 24 Aug 2017 11:14:06 + (UTC)
Resent-From: d
On 24-08-17, Hans wrote:
> Hi folks,
>
> I stumbled over the new network names (i.e. wl0p8 instead of wlan0), and of
> course I know, that this is obviously the newe standard (please correct me, i
> I am wrong).
>
> What I would like to know: Is this new naming scheme an international
> standa
Hi folks,
I stumbled over the new network names (i.e. wl0p8 instead of wlan0), and of
course I know, that this is obviously the newe standard (please correct me, i
I am wrong).
What I would like to know: Is this new naming scheme an international standard
on all linux distributions, or is this
On Tuesday 27 April 2010 13:46:23 Frank McCormick wrote:
> I recently installed Ubuntu 10.04 on the "other" partition on my
> hd ( /dev/hda3) and came across a problem no one on the
> Ubuntu forums could really resolve.
> Grub2 was installed at the same time as Ubuntu, and the whole
> installation
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I recently installed Ubuntu 10.04 on the "other" partition on my
hd ( /dev/hda3) and came across a problem no one on the
Ubuntu forums could really resolve.
Grub2 was installed at the same time as Ubuntu, and the whole
installation worked fine..for Ub
Rick Pasotto wrote:
> In the past I've successfully used:
>
> cdrdao write --device ATA:0,0,0 --driver generic-mmc vcd.toc
>
> to create an SVCD disk. Now, however, this gives the message:
>
> Error trying to open /dev/hdb exclusively (Device or resource busy)...
> retrying in 1 second
>
> This is
In the past I've successfully used:
cdrdao write --device ATA:0,0,0 --driver generic-mmc vcd.toc
to create an SVCD disk. Now, however, this gives the message:
Error trying to open /dev/hdb exclusively (Device or resource busy)... retrying
in 1 second
This is really strange since /dev/hdb is a
also sprach Douglas A. Tutty <[EMAIL PROTECTED]> [2008.11.16.0054 +0100]:
> Lets say you have an old server with 12 disks on two scsi busses an
> you're using mdadm (rather than a hardware raid card). Lets say that
> all 12 drives are in one array (just to make life interesting). One of
> those d
On Sun,17.Aug.08, 13:35:18, abel wrote:
> question 1 -->
[...]
> Are the new menu.lst lines correct?
> question 2 -->
> update-grub should be run after the update to /etc/fstab.
> correct?
Read menu.lst, it's self-documenting.
Regards,
Andrei
--
If you can't explain it simply, you don't un
On Tue, 12 Aug 2008 10:21:30 +0200
Aniruddha <[EMAIL PROTECTED]> wrote:
> On Tue, 2008-08-12 at 10:26 +0300, Andrei Popescu wrote:
> > I *think* it works, but this is your data...
> >
> > > I suspect that running update-grub isn't mandatory, I can always
> > > update m
On Sunday 17 August 2008 20:35, abel wrote:
>On Tue, 12 Aug 2008 02:32:04 +0300
>
>Andrei Popescu <[EMAIL PROTECTED]> wrote:
> > I prefer to use labels, because they are readable (compared to
> > UUID) ;)
> >
> > $ grep '^# kopt' /boot/grub/menu.lst
> > # kopt=root=LABEL=sid
On Tue, 12 Aug 2008 02:32:04 +0300
Andrei Popescu <[EMAIL PROTECTED]> wrote:
> I prefer to use labels, because they are readable (compared to
> UUID) ;)
>
> $ grep '^# kopt' /boot/grub/menu.lst
> # kopt=root=LABEL=sid ro vga=0x368
>
> You have to run 'update-grub' after
On 08/12/08 11:00, Aniruddha wrote:
On Tue, 2008-08-12 at 07:21 -0500, Ron Johnson wrote:
Instead, check out:
# tune2fs -L
I added labels to mounted devices using this method. And if I'm
remembering incorrectly, then the command will hopefully return an
error message.
What is the differen
On Tue, 2008-08-12 at 07:21 -0500, Ron Johnson wrote:
> Instead, check out:
> # tune2fs -L
>
> I added labels to mounted devices using this method. And if I'm
> remembering incorrectly, then the command will hopefully return an
> error message.
>
> --
> Ron Johnson, Jr.
> Jefferson LA USA
>
On 08/12/08 03:21, Aniruddha wrote:
On Tue, 2008-08-12 at 10:26 +0300, Andrei Popescu wrote:
I *think* it works, but this is your data...
I suspect that running update-grub isn't mandatory, I can always update
menu.lst by hand right?
Of course, but if you update the kernel stanza directly yo
On Tue, 2008-08-12 at 10:26 +0300, Andrei Popescu wrote:
> I *think* it works, but this is your data...
>
> > I suspect that running update-grub isn't mandatory, I can always update
> > menu.lst by hand right?
>
> Of course, but if you update the kernel stanza directly your changes
> will be o
On Tue, 2008-08-12 at 18:10 +1000, Alex Samad wrote:
> > What do you mean with 'rm /etc/blkid.tab'?
>
> this is where blkid stores is db of information, I have found when you
> have label/uuid problems then it is good to remove this, have a look at
> man blkid
>
Thanks! I have a look at it.
-
On Tue, Aug 12, 2008 at 08:43:14AM +0200, Aniruddha wrote:
> On Tue, 2008-08-12 at 11:15 +1000, Alex Samad wrote:
> > On Tue, Aug 12, 2008 at 02:32:04AM +0300, Andrei Popescu wrote:
> > > On Tue,12.Aug.08, 01:04:00, Aniruddha wrote:
> > > > Regularly my hard disk d
On Tue,12.Aug.08, 08:41:47, Aniruddha wrote:
> Thanks for the tip, this sounds like a good idea especially since I
> don't expect the label to change that much ^^ Can I rerun e2label on a
> mounted partition? The man page isn't that informative.
I *think* it works, but this is your data...
>
On Tue, 2008-08-12 at 11:15 +1000, Alex Samad wrote:
> On Tue, Aug 12, 2008 at 02:32:04AM +0300, Andrei Popescu wrote:
> > On Tue,12.Aug.08, 01:04:00, Aniruddha wrote:
> > > Regularly my hard disk device names change ( e.g. from sdc to sdh to sdb
> > > etc). When this ha
On Tue, 2008-08-12 at 02:32 +0300, Andrei Popescu wrote:
> I prefer to use labels, because they are readable (compared to UUID) ;)
>
> $ grep '^# kopt' /boot/grub/menu.lst
> # kopt=root=LABEL=sid ro vga=0x368
>
> You have to run 'update-grub' after changing this
>
> $ grep sid /etc/fstab
> LABE
On Tue, Aug 12, 2008 at 02:32:04AM +0300, Andrei Popescu wrote:
> On Tue,12.Aug.08, 01:04:00, Aniruddha wrote:
> > Regularly my hard disk device names change ( e.g. from sdc to sdh to sdb
> > etc). When this happens it becomes impossible to boot.
> >
> > To preven
On Tue,12.Aug.08, 01:04:00, Aniruddha wrote:
> Regularly my hard disk device names change ( e.g. from sdc to sdh to sdb
> etc). When this happens it becomes impossible to boot.
>
> To prevent this from happening I 've added 'disk/by id' to fstab
> (because the disk
On Tue, 2008-08-12 at 00:15 +0100, Robin wrote:
> 2008/8/12 Shachar Or <[EMAIL PROTECTED]>:
> I used get it occasionally if I had usb mass storage device plugged in
> when the computer was booted.
This is how it started for me, now it doesn't matter if I have an usb
device plugged in or not. Udev
On Tue, 2008-08-12 at 02:11 +0300, Shachar Or wrote:
> On Tuesday 12 August 2008 02:04, Aniruddha wrote:
> > Regularly my hard disk device names change ( e.g. from sdc to sdh to sdb
> > etc). When this happens it becomes impossible to boot.
> >
> > To prevent this from
2008/8/12 Shachar Or <[EMAIL PROTECTED]>:
> On Tuesday 12 August 2008 02:04, Aniruddha wrote:
>> Regularly my hard disk device names change ( e.g. from sdc to sdh to sdb
>> etc). When this happens it becomes impossible to boot.
>>
>> To prevent this from happening
On Tuesday 12 August 2008 02:04, Aniruddha wrote:
> Regularly my hard disk device names change ( e.g. from sdc to sdh to sdb
> etc). When this happens it becomes impossible to boot.
>
> To prevent this from happening I 've added 'disk/by id' to fstab
> (because the
Regularly my hard disk device names change ( e.g. from sdc to sdh to sdb
etc). When this happens it becomes impossible to boot.
To prevent this from happening I 've added 'disk/by id' to fstab
(because the disks uuid were also changing) and 'boot from uuid' to my
menu.ls
es get doled out by the system. Can someone
>> explain, or refer me to a good explanation, of how hardware is
>> discovered and named.
libata unifies access to disks (pata and sata) and is bound into a scsi
subsystem, so all the device names become scsi device names.
>
>
&g
ChadDavis wrote:
After a new lenny installation on a new motherboard, my PATA drive came
up as 'sdb'. I expected hda. I don't really care, but it does lead me
to wonder how these names get doled out by the system. Can someone
explain, or refer me to a good explanation, of how hardware is
di
After a new lenny installation on a new motherboard, my PATA drive came up
as 'sdb'. I expected hda. I don't really care, but it does lead me to
wonder how these names get doled out by the system. Can someone explain, or
refer me to a good explanation, of how hardware is discovered and named.
cking down the
partition assignments using the UUID associated with
a partition. That works, and survives adding and
removing controllers. You can also give the file
systems labels with e2label(8).
So it seems device names can no longer be relied on
to stay the same when you add in new devices, and the
wo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Dec 04, 2006 at 10:16:18AM +0100, Marcin Giedz wrote:
> Hello,
>
> I've got several Intel server platforms on every platform I
> upgraded BIOS to the latest version and installed Debian Etch. On five
> of them I have two ethernet interf
Hello,
I've got several Intel server platforms on every platform I
upgraded BIOS to the latest version and installed Debian Etch. On five
of them I have two ethernet interfaces eth0/eth1 but ONLY one has eth1
eth2 actually eth2/eth1 - this order.
debian:~# cat /proc/net/dev
Inter-| Re
able to mount my partitions using
the old device names--good thing. I
> > Anyone know how to create devfs?
>
> mount -t devfs - /dev
That worked but it creates weird time stamps:
# ls -al /dev/
total 4
drwxr-xr-x1 root root0 Dec 31 1969 .
drwxr-xr-x 26
>>>>> "Herbert" == Herbert Pirke <[EMAIL PROTECTED]> writes:
Herbert> As far as I know, some block device names changed with the
Herbert> 2.4 kernel, so I wonder if that changes a lot. Maybe some
Herbert> changed/added simlinks fix the problem.
Normall
, bzImage... etc.
as it used to be for 2.2.x updates.
As far as I know, some block device names changed with
the 2.4 kernel, so I wonder if that changes a lot.
Maybe some changed/added simlinks fix the problem.
Also, is it possible to have a 2.2 and a 2.4 kernel on
one machine and let lilo either
On Mon, 12 Jul 1999, Jason Carley wrote:
> Hi all,
>
> I am now trying to get my scanner installed under linux and sane. I have
> loaded the
> kernel module which promptly finds my scanner. /proc/scsi/scsi reports it
> found.
> Only problem, I am used to linking /dev/scanner to /dev/sg0 (for
Hi all,
I am now trying to get my scanner installed under linux and sane. I have
loaded the
kernel module which promptly finds my scanner. /proc/scsi/scsi reports it
found.
Only problem, I am used to linking /dev/scanner to /dev/sg0 (for SCSI device 0).
There is no /dev/sg* on my slink system.
81 matches
Mail list logo
