Re: [opensuse-factory] Using LVM by default for new installations?
On 1 Jun 2006 at 16:18, jdd wrote: Lenz Grimmer wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, jdd wrote: if you can garanty that one hard drive failure won't make me lose all my data, I'ok (I have several HD, of course, each with part of my system) In what respect would that be different from a hard disk failure with regular partitions? Are you implying that using LVM increases the risk of data loss? Please elaborate. AFAIK, if LVM uses 4 disks and one of them fails, the hole file system is lost. With the usual system only the file system on the faulty disk is lost. If you have one filesystem spanning 4 disks, then yes. Otherwise: no. Maybe it's even partially available. Regards, Ulrich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Update stack test build
On 1 Jun 2006 at 16:40, Andreas Hanke wrote: Hi, I'd like to know if / propose that the following bugs are candidates for inclusion in the package management update: - Option to disable missing signature complaints is not persistent https://bugzilla.novell.com/show_bug.cgi?id=175845 Not because of its severity - it's actually labelled as Minor in Bugzilla - but because of the number of duplicates. It seems to annoy quite a lot of people. Fix available - can it be included? I think that's basically a dangerous option (Think of your webbrowser having a global option trust expired and invalid certificates for secure connections: You would want it per certificate, not globally) - Too many YaST/zmd related directories left behind in /var/tmp https://bugzilla.novell.com/show_bug.cgi?id=178292 OK, /var/tmp is semi-permanent; only /tmp is really /tmp. Meaning: No file should be in /tmp if the application terminated, but that's permissible for /var/tmp. So it depends on the details. Probably rather cosmetic, but ugly. No fix available so far according to Bugzilla, and not that important. But maybe later? - Taboo flag is not persistent in the package manager https://bugzilla.novell.com/show_bug.cgi?id=164445 https://bugzilla.novell.com/show_bug.cgi?id=153337 Was it before? I don't think so. That would be bad for future updates. I think it shpould not be persistent. This one has several duplicates which are not yet marked as such. Doesn't seem to be implemented at all right now, but is a needed feature. Later? Regards, Ulrich Andreas Hanke - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Using LVM by default for new installations?
On 1 Jun 2006 at 17:45, Carl-Daniel Hailfinger wrote: jdd wrote: given modern disks are large, is it possible to have LVM strictly assigned at one disk, or separate LVM to each disk? Of course. Actually you can have LVM per partition, right? [...] Ulrich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Using LVM by default for new installations?
On 1 Jun 2006 at 17:51, Carl-Daniel Hailfinger wrote: Ulrich Windl wrote: On 1 Jun 2006 at 15:08, Lenz Grimmer wrote: [...]Logical Volumes[...] I'd like to propose that SUSE Linux considers switching to this scheme for new installations by default, too - I now filed this as an enhancement request in Bugzilla: https://bugzilla.novell.com/show_bug.cgi?id=180762 What do others think about that? If it boots... ;-) Works perfectly for me and my configuration is even more complicated: - GRUB on hda - /boot on hdb5 - / on LVM on hdb - mount-by-label for all filesystems - I can move hdb around as I want (hdc, hdd etc.) and only have to change one line in GRUB, no aother changes necessary. My 10.0 also boots from LVM as well, but not with my own compiled kernel (before LVM I had no problems). That would bring up the point of documenting the boot magic that's going on (and the secret options available for the init shell script in initrd). I guess there's some problem in initrd, but that's painful to debug by trial (boot) and error (reset). Regards, Ulrich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Update stack test build
Dňa Pi 2. Jún 2006 08:37 Ulrich Windl napísal: On 1 Jun 2006 at 16:40, Andreas Hanke wrote: [snip] Probably rather cosmetic, but ugly. No fix available so far according to Bugzilla, and not that important. But maybe later? - Taboo flag is not persistent in the package manager https://bugzilla.novell.com/show_bug.cgi?id=164445 https://bugzilla.novell.com/show_bug.cgi?id=153337 Was it before? I don't think so. That would be bad for future updates. I think it shpould not be persistent. No, it was not persistent before. Stano - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Updated Software Management Test Repository
We're currently pushing out an update to the package/patch management stack and I'm asking for additional testing. The previous repository did not show any new bugs but we fixed a couple of more bugs and made this time a repository with a real patch in it for testing. Please read the text below for instructions. For testing the update stack do the following steps as root: * start yast2 installation source via the yast2 control center or directly as yast2 inst_source. Add as additional software catalog: ftp://ftp.suse.com/pub/people/aj/10.1-packagemanagement-update-test (or use one of the mirrors once they are updated) and then leave the module via Finish. It will take some minutes to download data and setup the catalog. IMPORTANT: If you tested my old sources already, you need to download the metadata again (this is not needed afterwards anymore, it's one of the fixes in this new update). Skip this step and go to the next one: * start yast2 online update via the yast2 control center or directly as yast2 online_update. The patch summary should show a couple of patches and select only the libzypp update (with a black mark). Press Accept to apply the update. It will take some time to download packages and install them. * You can now remove the software catalog you added in the first step. Use yast2 inst_source and delete the catalog. * Restart zmd with rczmd restart. * Restart the zen-updater applet on your desktop (it will stop itself since zmd gets stopped during the update). * Everything is set now. You can now install further patches with: - the desktop applet zen-updater - the command line tool rug (via rug patches;rug in -t patch patchname) - yast2 online_update zen-updater will inform you about new patches. We will really soon release now this as official update and therefore need your testing. The only fix I'm waiting for is the following: Bug 180698 - zen-updater always shows patch dhcp (basically if a patch has been issued twice, it is always shown in zen-updater) IMPORTANT: Please report *all* bugs in bugzilla.novell.com and *always* CC [EMAIL PROTECTED] (Harald Müller-Ney) on the bugreport and mention that you're using AJ's updated package stack from 2006-06-02. The update contains the following packages (basically the complete package stack): * autoyast2 * libzypp * libzypp-zmd-backend * ruby-zypp * rug * suseRegister * yast2 * yast2-installation * yast2-instserver * yast2-ncurses * yast2-online-update * yast2-packager * yast2-perl-bindings * yast2-pkg-bindings * yast2-qt * zen-updater * zmd The most important changes are: * Do not create anymore /.gnupg (the directory can be removed) (#171055) * Handle daemons launched in rpm %post that do not close filedescriptors (#174548) * Really get all package descriptions (#159109) * Support large files, e.g. DVDs as installation source (#173753) * Handle update source setup after installation (#172665) * Do not add duplicate update sources (#168740) * Fix yast2 instserver module so that it works with 10.1 (#171157) * Do not exit in online_update when only packages (and no patches) are selected for installation or deletion (#175668) * Improve syncronising sources between yast and zmd (#168740, 175174, 175159, 175173) * Fix segmentation fault with non-signed repositories (#173291) * Handle system proxy setting with zmd (#160830) * Fix zen-updater bugs when installing packages (#171171, 174740) * Update packages to follow ABI change in libzypp. * Optimize and fix downloading of type zypp * Fix refreshing repositories of type zypp (#154990) * Add support for key handling to zmd, rug, zen-updater (#173920) * Fix zen-updater to handle installation of patch and package together (#178015) * Option to disable missing signature complaints is not persistent (#175845) Thanks for testing and bug reporting, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], http://www.suse.de/~aj/ SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 pgps8teliz9Hj.pgp Description: PGP signature
Re: [opensuse-factory] Updated Software Management Test Repository
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Andreas! Andreas Jaeger wrote: We're currently pushing out an update to the package/patch management stack and I'm asking for additional testing. Excellent, looks like this is quite needed ;) The previous repository did not show any new bugs but we fixed a couple of more bugs and made this time a repository with a real patch in it for testing. Please read the text below for instructions. For testing the update stack do the following steps as root: * start yast2 installation source via the yast2 control center or directly as yast2 inst_source. Add as additional software catalog: ftp://ftp.suse.com/pub/people/aj/10.1-packagemanagement-update-test (or use one of the mirrors once they are updated) and then leave the module via Finish. It will take some minutes to download data and setup the catalog. Done. IMPORTANT: If you tested my old sources already, you need to download the metadata again (this is not needed afterwards anymore, it's one of the fixes in this new update). Skip this step and go to the next one: FYI, I did apply the updates from your previous directory before. * start yast2 online update via the yast2 control center or directly as yast2 online_update. The patch summary should show a couple of patches and select only the libzypp update (with a black mark). Press Accept to apply the update. It will take some time to download packages and install them. Worked like described above. * You can now remove the software catalog you added in the first step. Use yast2 inst_source and delete the catalog. Here a popup window appeared, stating: Error: Cannot stop '/etc/init.d/novell-zmd' service. I clicked OK, and the inst_source module finished. Not sure if this is critical. Are there any logs that would help here? Bugzilla? * Restart zmd with rczmd restart. Done. * Restart the zen-updater applet on your desktop (it will stop itself since zmd gets stopped during the update). Hmm, the applet stayed in the KDE panel for me. To be safe, I restarted it manually. Strange, before I restarted it, I stated that 11 patches are available. After the restart, these are gone (no orange exclamation mark anymore). Bugzilla? * Everything is set now. You can now install further patches with: - the desktop applet zen-updater - the command line tool rug (via rug patches;rug in -t patch patchname) - yast2 online_update zen-updater will inform you about new patches. We will really soon release now this as official update and therefore need your testing. The only fix I'm waiting for is the following: Bug 180698 - zen-updater always shows patch dhcp (basically if a patch has been issued twice, it is always shown in zen-updater) IMPORTANT: Please report *all* bugs in bugzilla.novell.com and *always* CC [EMAIL PROTECTED] (Harald Müller-Ney) on the bugreport and mention that you're using AJ's updated package stack from 2006-06-02. The update contains the following packages (basically the complete package stack): * autoyast2 * libzypp * libzypp-zmd-backend * ruby-zypp * rug * suseRegister * yast2 * yast2-installation * yast2-instserver * yast2-ncurses * yast2-online-update * yast2-packager * yast2-perl-bindings * yast2-pkg-bindings * yast2-qt * zen-updater * zmd The most important changes are: * Do not create anymore /.gnupg (the directory can be removed) (#171055) * Handle daemons launched in rpm %post that do not close filedescriptors (#174548) * Really get all package descriptions (#159109) * Support large files, e.g. DVDs as installation source (#173753) * Handle update source setup after installation (#172665) * Do not add duplicate update sources (#168740) * Fix yast2 instserver module so that it works with 10.1 (#171157) * Do not exit in online_update when only packages (and no patches) are selected for installation or deletion (#175668) * Improve syncronising sources between yast and zmd (#168740, 175174, 175159, 175173) * Fix segmentation fault with non-signed repositories (#173291) * Handle system proxy setting with zmd (#160830) * Fix zen-updater bugs when installing packages (#171171, 174740) * Update packages to follow ABI change in libzypp. * Optimize and fix downloading of type zypp * Fix refreshing repositories of type zypp (#154990) * Add support for key handling to zmd, rug, zen-updater (#173920) * Fix zen-updater to handle installation of patch and package together (#178015) * Option to disable missing signature complaints is not persistent (#175845) Thanks for testing and bug reporting, Thanks for working hard on getting these remaining issues fixed! Bye, LenZ - -- - -- Lenz Grimmer [EMAIL PROTECTED] -o) [ICQ: 160767607 | Jabber: [EMAIL PROTECTED]
Re: [opensuse-factory] Updated Software Management Test Repository
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! Andreas Jaeger wrote: * You can now remove the software catalog you added in the first step. Use yast2 inst_source and delete the catalog. Here a popup window appeared, stating: Error: Cannot stop '/etc/init.d/novell-zmd' service. I clicked OK, and the inst_source module finished. Not sure if this is critical. Are there any logs that would help here? Bugzilla? Bugzilla - with /var/log/zmd-messages.log appended. OK, this is now filed as BUG#181126 - hope it helps. * Restart the zen-updater applet on your desktop (it will stop itself since zmd gets stopped during the update). Hmm, the applet stayed in the KDE panel for me. To be safe, I restarted it manually. Strange, before I restarted it, I stated that 11 patches are available. After the restart, these are gone (no orange exclamation mark anymore). Bugzilla? Check with rug patches what it outputs - and then it might be worth a report. It really depends. I guess I need to get used to the output of this tool first. rug patches lists a number of patches, but I guess none of these apply for me, hence the applet is silent: - --++--++- 1 | Active | ZYPP | SUSE-Linux-10.1-DVD9-x86-x86_64-10.1-0-20060601-155143 | cd:///?devices=/dev/hdcalias=SUSE-Linux-10.1-DVD9-x86-x86_64-10.1-0-20060601-155143 2 | Active | ZYPP | SUSE-Linux-10.1-Updates | http://ftp.gwdg.de/pub/suse/update/10.1/ 3 | Active | ZYPP | 20060602-013154 | http://ftp.gwdg.de/pub/linux/misc/packman/suse/10.1/ 4 | Active | ZYPP | 20060602-014612 | http://software.opensuse.org/download/KDE:/KDE3/SUSE_Linux_10.1/ [EMAIL PROTECTED]:~ rug catalogs Sub'd? | Name | Service - ---++--- Yes| SUSE-Linux-10.1-Updates| SUSE-Linux-10.1-Updates Yes| SUSE-Linux-10.1-DVD9-x86-x86_64-10.1-0-20060601-155143 | SUSE-Linux-10.1-DVD9-x86-x86_64-10.1-0-20060601-155143 Yes| 20060602-013154| 20060602-013154 Yes| 20060602-014612| 20060602-014612 [EMAIL PROTECTED]:~ rug patches Catalog | Name | Version | Category| Status - +---+-+-+--- SUSE-Linux-10.1-Updates | aaa_skel | 1444-0 | recommended | Not needed SUSE-Linux-10.1-Updates | avahi | 1399-0 | security| Not Applicable SUSE-Linux-10.1-Updates | cron | 1440-0 | security| Not needed SUSE-Linux-10.1-Updates | dhcdbd| 1315-0 | recommended | Not needed SUSE-Linux-10.1-Updates | dhcp | 1316-0 | recommended | Not needed SUSE-Linux-10.1-Updates | dhcp | 1424-0 | recommended | Not needed SUSE-Linux-10.1-Updates | dia | 1435-0 | security| Not Applicable SUSE-Linux-10.1-Updates | dia | 1421-0 | security| Not Applicable SUSE-Linux-10.1-Updates | dovecot | 1398-0 | security| Not Applicable SUSE-Linux-10.1-Updates | foomatic-filters | 1436-0 | security| Not needed SUSE-Linux-10.1-Updates | gnome2-SuSE | 1428-0 | recommended | Not Applicable SUSE-Linux-10.1-Updates | gtk-sharp2| 1427-0 | recommended | Not needed SUSE-Linux-10.1-Updates | ivman | 1423-0 | recommended | Not Applicable SUSE-Linux-10.1-Updates | java-1_5_0-sun| 1438-0 | security| Not Applicable SUSE-Linux-10.1-Updates | kdeadmin3 | 1439-0 | recommended | Not Applicable SUSE-Linux-10.1-Updates | kdebase3 | 1449-0 | recommended | Not needed SUSE-Linux-10.1-Updates | ksh | 1452-0 | recommended | Not Applicable SUSE-Linux-10.1-Updates | libextractor | 1426-0 | security| Not Applicable System | libzypp | 1455-0 | recommended | Applied SUSE-Linux-10.1-Updates | mysql | 1312-0 | security| Not Applicable SUSE-Linux-10.1-Updates | nagios-www| 1311-0 | security| Not Applicable SUSE-Linux-10.1-Updates | netbeans | 1451-0 | optional| Not Applicable SUSE-Linux-10.1-Updates | NetworkManager| 1434-0 | security| Not needed SUSE-Linux-10.1-Updates | openldap2 | 1323-0 | recommended | Not Applicable SUSE-Linux-10.1-Updates | opera | 1313-0 | security| Not needed SUSE-Linux-10.1-Updates | pdns | 1314-0 | security| Not Applicable SUSE-Linux-10.1-Updates | powersave | 1430-0 | recommended | Not needed SUSE-Linux-10.1-Updates | qt3 | 1441-0 | recommended | Not needed SUSE-Linux-10.1-Updates | rekall| 1432-0 | recommended
Re: [opensuse-factory] Using LVM by default for new installations?
Ulrich Windl wrote: On 1 Jun 2006 at 16:53, jdd wrote: sharing a partition between several disks don't seems so nice to me (when not strictly necessary), but when a drive fails, anyway all it's content is lost so... we could have to good and not the bad? Our last database server had 46 disks connected to twelve SCSI HBAs. You really do not want to have 26 mirrored filesystems. Believe me. rte-read my post (you quoted it) I beleive you have raid also, no? do you think this is standard install :-) jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Using LVM by default for new installations?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, jdd wrote: can you expand that? I don't understand. do you mean that one can make partitions on a drive then set lvm to be used only on this partition? Yes, sure. On my Laptop, I have one big partition, labelled as LVM. Inside of this partition, LVM manages the volumes, which contain all my different file systems (various root file systems, swap, usr/local and my encrypted home file system). I can add/remove and resize these at will, within the boundaries of that partition. If I needed more space for these volumes, I could even assign another partition on the same disk to it (e.g. by removing my windows partition and adding it to the physical volume, or by adding another hard disk. Then the volumes could span across both disks. if so, it's very good. Yes, it's very sweet! I always have seen LVM advertised as a mean to have one partition spanning several disks That is possible, but not a requirement. I'd like to recommend you to take a look at the LVM HOWTO, it explains the capabilities of LVM quite nicely: http://tldp.org/HOWTO/LVM-HOWTO/ Bye, LenZ - -- - -- Lenz Grimmer [EMAIL PROTECTED] -o) [ICQ: 160767607 | Jabber: [EMAIL PROTECTED]/\\ http://www.lenzg.org/ V_V -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFEgBohSVDhKrJykfIRAuGjAJ9r9MlBf1C+kyQwYJbtcDNJCjpAcwCfU8BD 0IXnJc/4NPlSpJCCoY7GCAU= =9ZEK -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Using LVM by default for new installations?
On 2 Jun 2006 at 12:47, jdd wrote: Ulrich Windl wrote: On 1 Jun 2006 at 17:45, Carl-Daniel Hailfinger wrote: jdd wrote: given modern disks are large, is it possible to have LVM strictly assigned at one disk, or separate LVM to each disk? Of course. Actually you can have LVM per partition, right? can you expand that? I don't understand. AFAIK, LVM ist just a data structure on a block device. So /dev/hda1 is such a device just as /dev/hda is. do you mean that one can make partitions on a drive then set lvm to be used only on this partition? This or these partitions. Yes. if so, it's very good. I always have seen LVM advertised as a mean to have one partition spanning several disks Yes you can, you can make more insane things as well however. I have LVM on top of MD on top of partitions (EVMS): Everything mirrored plus almost everything in LVM. Regards, Ulrich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Updated Software Management Test Repository
Lenz Grimmer [EMAIL PROTECTED] writes: Hi! Andreas Jaeger wrote: * You can now remove the software catalog you added in the first step. Use yast2 inst_source and delete the catalog. Here a popup window appeared, stating: Error: Cannot stop '/etc/init.d/novell-zmd' service. I clicked OK, and the inst_source module finished. Not sure if this is critical. Are there any logs that would help here? Bugzilla? Bugzilla - with /var/log/zmd-messages.log appended. OK, this is now filed as BUG#181126 - hope it helps. Thanks. * Restart the zen-updater applet on your desktop (it will stop itself since zmd gets stopped during the update). Hmm, the applet stayed in the KDE panel for me. To be safe, I restarted it manually. Strange, before I restarted it, I stated that 11 patches are available. After the restart, these are gone (no orange exclamation mark anymore). Bugzilla? Check with rug patches what it outputs - and then it might be worth a report. It really depends. I guess I need to get used to the output of this tool first. rug patches lists a number of patches, but I guess none of these apply for me, hence the applet is silent: [...] [EMAIL PROTECTED]:~ rug patches Catalog | Name | Version | Category| Status - +---+-+-+--- SUSE-Linux-10.1-Updates | aaa_skel | 1444-0 | recommended | Not needed SUSE-Linux-10.1-Updates | avahi | 1399-0 | security| Not Applicable A Needed would have meant something but those are all fine, you do not need them. So, this looks ok, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], http://www.suse.de/~aj/ SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 pgpikFAPtpIHg.pgp Description: PGP signature
Re: [opensuse-factory] Update stack test build
Hi, Ulrich Windl schrieb: I think that's basically a dangerous option (Think of your webbrowser having a global option trust expired and invalid certificates for secure connections: You would want it per certificate, not globally) But in any case there's a problem there, an option in the UI that doesn't behave as expected. If the option is there, it should do something and if it's decided that the option is dangerous, it should be removed. Otherwise Bugzilla will be flooded by complaints about unexpected behaviour. OK, /var/tmp is semi-permanent; only /tmp is really /tmp. Meaning: No file should be in /tmp if the application terminated, but that's permissible for /var/tmp. So it depends on the details. I'm not sure. Looking at the increased number of YaST-related directories in /var/tmp after each YaST session, it seems that new temp files are created each time and the old ones are not used again, so it doesn't seem necessary to keep them around. Actually I think it should be the other way round: If they are just used during one YaST session and never used again, they should be in /tmp, not /var/tmp. - Taboo flag is not persistent in the package manager https://bugzilla.novell.com/show_bug.cgi?id=164445 https://bugzilla.novell.com/show_bug.cgi?id=153337 Was it before? I don't think so. You are right, it wans't. I never noticed that because I never needed it before. That would be bad for future updates. I think it shpould not be persistent. I think it should be. There are not only security updates, but also optional ones which might introduce problems - there's always a risk that an update can introduce problems. At least for optional, not security critical updates, not installing them is a viable solution. There should be an option to block these permanently. Actually the first dhcp update for 10.1 *was* broken, I was offline after applying it. That's why I noticed it. Right now the taboo option doesn't seem to do anything else than the do not install option. Andreas Hanke - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Using LVM by default for new installations?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, houghi wrote: I just looked at what is now there and to make it clear that it was not LVM. Could be anything, I guess. FAT32? :-) Almost - FAT32 might be a bit too low-end for that. But it's pretty common to use ext2 for /boot - you don't really need more and using a journalled file system like ext3/ReiserFS/XFS/JFS would just eat up disk space. There is not much to journal as the content of /boot won't change very frequently. And if you keep /boot at a reasonable small size, an fsck should not take that long anyway. I do not believe that at this moment it is relevant in the discussion what it will become later. Right, this is the trivial part ;) OK. I understand. To avaid confusion, we use different names for someting that fr the layman like me is the same. ;-) Right, in the both are just containers for a file system. With a fresh installation, you have the option to mix the old and the proposed GRUB menu.lst. The following is from memory, so names might be a bit different and you will need to look for yourself. Where you can select the way things are partitioned and the software to install choose the secon tab, Advanced. There you can select how to boot. If you select GRUB, you have a button in the lower right, Other, where you can do a Merge with what you have now. The names come out a bit awkward, but you should be able to keep your current settings AND your new ones in one go from boot on. Right, now I remember there used to be something like that. I will have to take a closer look next time I perform a fresh install. I see very much the advantages. It would solve also issues where you first had only /home and / as volumes (partitions makes more sence still, but whatever) on the LVM and then suddenly realize that you want to keep /srv with a new installation. You could then resize / and /home, add /a new volume /srv and move all the data over from / to /srv. Exactly! Do the new installation and still have what you wanted to keep. Am I correct in this idea? Yes, that's how it works. LVM scans the disk for existing volumes and the YaST2 LVM frontend lists these similar to already existing partitions. You can assign these to new mount points without formatting. If so, then by all means. Pitty it was not clear when it was decided to go to / and /home, Would have een great to do at the same time and would have stopped the part where people said to also have a seperate /opt, /srv, /var, /boot, /whatever. It really depends what purpose the system is used for. For a server, this might make sense. For a desktop workstation, I think a separation between the root file system and /home should be sufficient. Unless somebody can think of a huge drawback, I am convinced now. Thanks ;) Bye, LenZ - -- - -- Lenz Grimmer [EMAIL PROTECTED] -o) [ICQ: 160767607 | Jabber: [EMAIL PROTECTED]/\\ http://www.lenzg.org/ V_V -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFEgGHUSVDhKrJykfIRAlnpAJ4/Vpkuz777tWdyyWYlDWXY274DwgCfSbtl 5ZCUNl4Ls89NgsdAD+AkOHA= =8kqS -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] High Utilization with zen components
Hello everyone, This has probably been addressed somewhere in a thread somewhere, but I can't see it. Anyway, I've noticed that whenever I do anything with the new software management tools (ZEN tools), my system's fans crank up. I check top and see that my utilization is in the high 90's or even 100. I don't know if it's a bug or not, but it bothers me a great deal. I don't like my system to have to crank up the fans to do something as simple as check to see if there are updates available, or install an RPM. I have a desktop, but I think laptop users would be screaming about this, as it's gonna kill their batteries a lot sooner. -Chad - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] High Utilization with zen components
Fredag 02 juni 2006 18:24 skrev Chad Groneman: I don't know if it's a bug or not, but it bothers me a great deal. I don't like my system to have to crank up the fans to do something as simple as check to see if there are updates available, or install an RPM. It's well known that the new package management has severe performance issues. To a degree where one might categorize it as a bug. Work is being done on this. See: http://opensuse.org/Using_10.1 And keep in mind this list is for community/development talk. Technical problems with released versions should be discussed on suse-linux-e. Martin / cb400f - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Using LVM by default for new installations?
On Fri, Jun 02, 2006 at 06:05:41PM +0200, Lenz Grimmer wrote: Snip AOL ;-) Do the new installation and still have what you wanted to keep. Am I correct in this idea? Yes, that's how it works. LVM scans the disk for existing volumes and the YaST2 LVM frontend lists these similar to already existing partitions. You can assign these to new mount points without formatting. One last question. So the only risk is that if one disk breaks, all your data is gone. If so, then by all means. Pitty it was not clear when it was decided to go to / and /home, Would have een great to do at the same time and would have stopped the part where people said to also have a seperate /opt, /srv, /var, /boot, /whatever. It really depends what purpose the system is used for. For a server, this might make sense. For a desktop workstation, I think a separation between the root file system and /home should be sufficient. Many people will have something like /music or /Pr0n that they share with otheres and thus not place it in /home To me it is not completely clear where in fhs you should place user data that you share with others. If Alice, Ben and Carl want to listen to music each of them has, where should you place that? `man hier` tells me that /usr should be read only. So you can't add music without root permission. /home is for the users and I do not want others snooping in my directory. I see nothing that is specificaly to share data. -- houghi http://houghi.org http://www.plainfaqs.org/linux/ http://www.netmeister.org/news/learn2quote.html Today I went outside. My pupils have never been tinier... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Using LVM by default for new installations?
On Fri, Jun 02, 2006 at 08:14:44PM +0200, jdd wrote: so plain ext2 is definitively the best choice. As said, that is trivial at this point what it is. It's also a good idea to keep a separate /boot partition, just in case some old hardaware with faulty BIOS (may be there are still some around) If you have old hardware with a faulty BIOS, you can alweays edit it. I don't want it on my new hardware with a working Bios if I can avoid it. The only reason that it is needed is that you can not boot it with /boot being on LVM, otherwise please as little partiotioning as possible. We have had this discussion before with the seperation of /home and /. Please don't start it all over again. -- houghi http://houghi.org http://www.plainfaqs.org/linux/ http://www.netmeister.org/news/learn2quote.html Today I went outside. My pupils have never been tinier... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] High Utilization with zen components
Am Freitag, 2. Juni 2006 18:24 schrieb Chad Groneman: This has probably been addressed somewhere in a thread somewhere, but I can't see it. Anyway, I've noticed that whenever I do anything with the new software management tools (ZEN tools), my system's fans crank up. I check top and see that my utilization is in the high 90's or even 100. Hm, I've removed the new utils, beagle (it's a nice tool, but when it's indexing the disk, the computer get's realy working hard) and mono itselve. YaST now works much better, updating/adding a install-source imidiatly ends after pressing ok and not minutes later, software installation also ends when it's finished and not ages behind that. It's nearly like SUSE 10.0, only YOU is missing... -- Machs gut| http://www.iivs.de/schwinde/buerger/tremmel/ | http://packman.links2linux.de/ Manfred | http://www.knightsoft-net.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Using LVM by default for new installations?
Op vrijdag 2 juni 2006 19:06, schreef houghi: Yes, that's how it works. LVM scans the disk for existing volumes and the YaST2 LVM frontend lists these similar to already existing partitions. You can assign these to new mount points without formatting. One last question. So the only risk is that if one disk breaks, all your data is gone. The LVM will most likely be on 1 disk (for home systems). The the early days disk were small and than LVM was used to obtain bigger file systems. Nowadays disks are big enough and LVM is used for convenience to be able to resize partition. 1 disadvantage by introducing LVM is another layer that can break. I use LVM as well, and when I have to do something with it, I always have to look up the commands as I never remember these If so, then by all means. Pitty it was not clear when it was decided to go to / and /home, Would have een great to do at the same time and would have stopped the part where people said to also have a seperate /opt, /srv, /var, /boot, /whatever. It really depends what purpose the system is used for. For a server, this might make sense. For a desktop workstation, I think a separation between the root file system and /home should be sufficient. Many people will have something like /music or /Pr0n that they share with otheres and thus not place it in /home To me it is not completely clear where in fhs you should place user data that you share with others. If Alice, Ben and Carl want to listen to music each of them has, where should you place that? `man hier` tells me that /usr should be read only. So you can't add music without root permission. /home is for the users and I do not want others snooping in my directory. I see nothing that is specificaly to share data. Well call it /home/share, /home/4allgoodpeople, /home/4all, etc -- Richard Bos Without a home the journey is endless - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Updated Software Management Test Repository
Hi, Andreas Jaeger schrieb: IMPORTANT: Please report *all* bugs in bugzilla.novell.com and *always* CC [EMAIL PROTECTED] (Harald Müller-Ney) on the bugreport and mention that you're using AJ's updated package stack from 2006-06-02. Knowing this, it should probably go directly into Bugzilla, but anyway I'd like to ask here first: The previous set of test packages included yast2-devel-2.13.59-0.2.i586.rpm. The new one doesn't include yast2-devel at all. This breaks the integrity of the package tree: - yast2-devel cannot be installed any more because it has a versioned dependency on the old, replaced yast2 package - If a user selects yast2-devel for installation anyway, he will be prompted to downgrade yast2 again, followed by downgrades of other packages It's quite similar to #179018. = Is yast2-devel left out intentionally or is it a bug? Andreas Hanke - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Using LVM by default for new installations?
Hi Lenz, So yes, the partitioner would need to create two additional regular partitions: - a small one (~100MB is more than sufficient) for /boot Arrg, I was very happy to have seen that gone for good. SUSE doesn't even boot any more on boxes with a BIOS too old to need separate /boot. That'll be the reason why Red Cr oops never got rid of it. /dev/hda1 (~20GB) - Windows XP (NTFS) /dev/hda2 (~150MB) - Linux /boot (ext2) /dev/hda3 (~1.5GB) - Linux swap (as the current suspend to disk kernel code requires swap to be outside the LVM - swsusp2 has fixed that and can suspend to swap managed by the device mapper) /dev/hda4 (~58GB) - Linux LVM Inside the LVM I currently have defined the following volumes: That all looks very sensible. I don't see a big problem with repartitioning non-LVM disks myself (shrink, lower partition boundary, create/resize filesystem above new boundary), but with LVM it would be a tad easier and somewhat safer. After too many disasters I always use raid1 though for / and /home, perhaps others, but not for /data, because the play area and collection of ISOs doesn't need it. Although there are voices to the contrary, I've had good experience with Linux soft raid. How stable is, in your opinion, the soft raid1 (or raid5) combined with LVM when something fails somewhere? Thanks, Volker -- Volker Kuhlmann is list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] SUSE 10.1 sources DVD
Will there be a DVD again with the sources corresponding to the packages in the boxed set (like there was for 10.0)? Thanks, Volker -- Volker Kuhlmann is list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] SUSE 10.1 sources DVD
On Sat, 3 Jun 2006, Volker Kuhlmann wrote: Will there be a DVD again with the sources corresponding to the packages in the boxed set (like there was for 10.0)? We have two source DVDs lying around -- but as of now they didn't get pushed out to the mirrors. And I'd actually prefer to just offer .jigdo files for those, as the .src.rpms are in the ftp anyway. 196KSUSE-Linux-10.1-GM-SOURCE-DVD1.iso.iso.jigdo 21M SUSE-Linux-10.1-GM-SOURCE-DVD1.iso.template 4.0KSUSE-Linux-10.1-GM-SOURCE-DVD2.iso.iso.jigdo 304KSUSE-Linux-10.1-GM-SOURCE-DVD2.iso.template 22M total Regards Christoph - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] SUSE 10.1 sources DVD
Hi, On Sat, 3 Jun 2006, Volker Kuhlmann wrote: Will there be a DVD again with the sources corresponding to the packages in the boxed set (like there was for 10.0)? No, not in the box. Maybe they will burn and send you one upon personal request. Cheers -e -- Eberhard Moenkeberg ([EMAIL PROTECTED], [EMAIL PROTECTED]) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] SUSE 10.1 sources DVD
We have two source DVDs lying around -- but as of now they didn't get pushed out to the mirrors. And I'd actually prefer to just offer .jigdo files for those, as the .src.rpms are in the ftp anyway. From a mirroring point of view, some jiggledy-scripty which downloads the files and reconstructs the DVDs would make very good sense. Looks like jigdo does just that, are the source dvd jigdo files online yet? How is disk integrity handled? ISO md5 isn't going to do it as long as mkisofs always puts the mastering time into the iso. Thanks, Volker -- Volker Kuhlmann is list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
