You are not logged in.
Pages: 1
Hi,
I thought that after the fairly important changes introduced with the udev upgrade and impacting various related packages, it might be an idea to distribute a new install CD with everything set up ready to work?
I found the upgrade fairly hairy, and I'm sure you wouldn't want Arch beginners to find their systems broken the first time they upgrade after installing from the 0.7.1 CD.
Cheers,
Samsara
.
Offline
Can't recall that anything major has happened since 7.1 release, which was only a couple of weeks back, but may just be me...
Offline
I think most of the changes you're thinking about were all from the 0.7 release...the new 0.7.1 should include all of those and cut down on a lot of the confusion for new installers. See: Arch Linux 0.7.1 (Noodle) Released
Offline
I'm betting the next iso we see will be 0.8.0, as I'd be very surprised to see a 0.7.2 iso come out.
oz
Offline
0.7.2 would be worth a release anyway, as 0.7.1 does not create cdrom/dvdrom nodes for scsi or sata drives. Users have to know about that, if they have to "loaddisk" some modules before installation. For the record, you have to run
mknod /dev/scd0 b 11 0
for the first device, scd1 b 11 1 for the second, etc.
Frumpus ♥ addict
[mu'.krum.pus], [frum.pus]
Offline
0.7.2 would be worth a release anyway, as 0.7.1 does not create cdrom/dvdrom nodes for scsi or sata drives. Users have to know about that, if they have to "loaddisk" some modules before installation. For the record, you have to run
mknod /dev/scd0 b 11 0
for the first device, scd1 b 11 1 for the second, etc.
That's not true. It might only be a module autoloading issue - but if the scsi cdrom module is loaded (I think it was the sr_mod module), then those device nodes (including the /dev/{cdrom,dvd,cdrw,dvdrw} links) exist.
Offline
Can someone just confirm that the following changes really are in 0.7.1:
As of version 076, udev will now perform all the functions that hotplug used to handle, thus removing the need for it. As well, the latest udev will want to remove pcmcia-cs since it has been deprecated in favor of pcmciautils.
Note that this is all 2.6 stuff. If you are still running a 2.4 kernel, stay with hotplug and pcmcia-cs.
If you were using hotplug in your DAEMONS array to auto-load your modules, you should replace it with one of the other auto-detection utilities: hwdetect or hwd.
To use hwd: Just install the lshwd package and replace hotplug with hwd in your DAEMONS array.
To use hwdetect: Look for a line in /etc/rc.conf that starts with MOD_AUTOLOAD and set it to "yes". If you don't have the line, add it:
MOD_AUTOLOAD="yes"
(From http://www.archlinux.org/news.php)
Regards,
Samsara
.
Offline
I've been told that hwdetect is the standard in 0.7.1 together with udev.
Did you actually follow the install guide?
http://www.archlinux.org/docs/en/guide/ … guide.html
Offline
Can someone just confirm that the following changes really are in 0.7.1:
As of version 076, udev will now perform all the functions that hotplug used to handle, thus removing the need for it. As well, the latest udev will want to remove pcmcia-cs since it has been deprecated in favor of pcmciautils.
Note that this is all 2.6 stuff. If you are still running a 2.4 kernel, stay with hotplug and pcmcia-cs.
If you were using hotplug in your DAEMONS array to auto-load your modules, you should replace it with one of the other auto-detection utilities: hwdetect or hwd.
To use hwd: Just install the lshwd package and replace hotplug with hwd in your DAEMONS array.
To use hwdetect: Look for a line in /etc/rc.conf that starts with MOD_AUTOLOAD and set it to "yes". If you don't have the line, add it:
MOD_AUTOLOAD="yes"
Of course they are.
Offline
I've been told that hwdetect is the standard in 0.7.1 together with udev.
Did you actually follow the install guide?
http://www.archlinux.org/docs/en/guide/ … guide.html
When I originally installed 0.7 many moons ago, yes. At the moment, I'm on Ubuntu, but it's annoying me with several things.
Samsara
.
Offline
Can someone just confirm that the following changes really are in 0.7.1:
As of version 076, udev will now perform all the functions that hotplug used to handle, thus removing the need for it. As well, the latest udev will want to remove pcmcia-cs since it has been deprecated in favor of pcmciautils.
Note that this is all 2.6 stuff. If you are still running a 2.4 kernel, stay with hotplug and pcmcia-cs.
If you were using hotplug in your DAEMONS array to auto-load your modules, you should replace it with one of the other auto-detection utilities: hwdetect or hwd.
To use hwd: Just install the lshwd package and replace hotplug with hwd in your DAEMONS array.
To use hwdetect: Look for a line in /etc/rc.conf that starts with MOD_AUTOLOAD and set it to "yes". If you don't have the line, add it:
MOD_AUTOLOAD="yes"
In a way, yes. MOD_AUTOLOAD is an abstraction. The reaction to MOD_AUTOLOAD does not matter. In 0.7.1, MOD_AUTOLOAD uses hwdetect. After an update, it uses pure udev. There is no difference to a user.
Offline
samsara wrote:Can someone just confirm that the following changes really are in 0.7.1:
As of version 076, udev will now perform all the functions that hotplug used to handle, thus removing the need for it. As well, the latest udev will want to remove pcmcia-cs since it has been deprecated in favor of pcmciautils.
Note that this is all 2.6 stuff. If you are still running a 2.4 kernel, stay with hotplug and pcmcia-cs.
If you were using hotplug in your DAEMONS array to auto-load your modules, you should replace it with one of the other auto-detection utilities: hwdetect or hwd.
To use hwd: Just install the lshwd package and replace hotplug with hwd in your DAEMONS array.
To use hwdetect: Look for a line in /etc/rc.conf that starts with MOD_AUTOLOAD and set it to "yes". If you don't have the line, add it:
MOD_AUTOLOAD="yes"
In a way, yes. MOD_AUTOLOAD is an abstraction. The reaction to MOD_AUTOLOAD does not matter. In 0.7.1, MOD_AUTOLOAD uses hwdetect. After an update, it uses pure udev. There is no difference to a user.
So having both MOD_AUTOLOAD="yes" and the new udev installed is bad? Is that where I went wrong?
Cheers,
Samsara
.
Offline
That's not true. It might only be a module autoloading issue - but if the scsi cdrom module is loaded (I think it was the sr_mod module), then those device nodes (including the /dev/{cdrom,dvd,cdrw,dvdrw} links) exist.
Hm, trust me, I have scsi AND sata dvd devices. None of them recieves a node. Well, I haven't had this issues with a pure scsi system, to be honest. And the modules are loaded - as I told you, I just have to create the node. Furthermore, I had reported a bug about it, that was reported to be fixed some days after the iso was finished and leleased. But I know what to do to work around the bug, and as long as no others complain, it's ok for me.
Frumpus ♥ addict
[mu'.krum.pus], [frum.pus]
Offline
brain0 wrote:That's not true. It might only be a module autoloading issue - but if the scsi cdrom module is loaded (I think it was the sr_mod module), then those device nodes (including the /dev/{cdrom,dvd,cdrw,dvdrw} links) exist.
Hm, trust me, I have scsi AND sata dvd devices. None of them recieves a node. Well, I haven't had this issues with a pure scsi system, to be honest. And the modules are loaded - as I told you, I just have to create the node. Furthermore, I had reported a bug about it, that was reported to be fixed some days after the iso was finished and leleased. But I know what to do to work around the bug, and as long as no others complain, it's ok for me.
I had a similar problem a while back with it not creating nodes for my flash drive. jskier and judd helped me out though:
http://bbs.archlinux.org/viewtopic.php?p=134142
Offline
Reviving a month-old thread, but I just noticed something... when I last looked at the Arch front page, it showed 0.8 as being the next pending release after 0.7.1, but it appears that perhaps there will be an Arch 0.7.2 release, because that's now what is showing as "pending", with no mention of version 0.8, at all.
Maybe it's an attempt to get all the new kernel, udev, initrd, and xorg stuff into one release in the near future.
oz
oz
Offline
http://archlinux.org/~jason/newsletters … ml#devland
devland point 3.
They've changed the release schedule.
Dusty
Offline
Thanks, Dusty...
I do remember reading that in the newsletter now, but had forgotten about it. Hopefully, 0.7.2 will be all nice and tidy, and 100% bug free.
Like that's gonna ever happen!
oz
oz
Offline
Hi,
I thought that after the fairly important changes introduced with the udev upgrade and impacting various related packages, it might be an idea to distribute a new install CD with everything set up ready to work?
I found the upgrade fairly hairy, and I'm sure you wouldn't want Arch beginners to find their systems broken the first time they upgrade after installing from the 0.7.1 CD.
Cheers,
Samsara
.
Most of the people that I know have broadband, and I have been burning copies of the BASE iso so there isnt anything on there. I install packages off of the Internet and it works perfectly every time.
Offline
According to the newsletter on Feb 5, 2006:
We plan on having maintenance releases every 3 months, their version numbers will be X.Y.Z (like 0.7.1). Major releases will happen when there are large changes to the installation environment (udev, initrd, installer). The next maintenance release will be in April.
Offline
Come on, we REALLY need 0.7.2. It has kde 3.5.1 -- xorg7 -- new udev .. Too many changes from 0.7.1
My +1 for 0.7.2
Rohan.
Offline
xorg 7 and udev maybe, but KDE isn't even on the install CDs, so what difference does it make, you still have to sync it.
The point is Arch is rolling release. The only reason for a new release is if installing from the install CD and then running pacman -Syu is not easy for some reason, eg a major config change (yes, xorg 7 and udev qualify!)
Dusty
Offline
Pages: 1