Menu
▾
▴
devil-linux-develop — developer discussions
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(55) |
Oct
(44) |
Nov
(156) |
Dec
(123) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(130) |
Feb
(156) |
Mar
(162) |
Apr
(171) |
May
(97) |
Jun
(127) |
Jul
(58) |
Aug
(81) |
Sep
(86) |
Oct
(45) |
Nov
(41) |
Dec
(84) |
| 2003 |
Jan
(71) |
Feb
(87) |
Mar
(133) |
Apr
(152) |
May
(151) |
Jun
(232) |
Jul
(320) |
Aug
(237) |
Sep
(271) |
Oct
(536) |
Nov
(301) |
Dec
(393) |
| 2004 |
Jan
(393) |
Feb
(184) |
Mar
(314) |
Apr
(225) |
May
(139) |
Jun
(77) |
Jul
(87) |
Aug
(75) |
Sep
(139) |
Oct
(50) |
Nov
(8) |
Dec
(28) |
| 2005 |
Jan
(66) |
Feb
(63) |
Mar
(14) |
Apr
(14) |
May
(8) |
Jun
(23) |
Jul
(21) |
Aug
(6) |
Sep
(29) |
Oct
(55) |
Nov
(38) |
Dec
(8) |
| 2006 |
Jan
(5) |
Feb
(10) |
Mar
(1) |
Apr
(15) |
May
(32) |
Jun
(44) |
Jul
(11) |
Aug
(8) |
Sep
(9) |
Oct
(14) |
Nov
(4) |
Dec
(3) |
| 2007 |
Jan
(3) |
Feb
(3) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
(35) |
Aug
(49) |
Sep
(8) |
Oct
(42) |
Nov
(44) |
Dec
(7) |
| 2008 |
Jan
(2) |
Feb
(7) |
Mar
(8) |
Apr
(80) |
May
(74) |
Jun
(29) |
Jul
(5) |
Aug
(7) |
Sep
(6) |
Oct
(1) |
Nov
|
Dec
|
| 2009 |
Jan
(8) |
Feb
(19) |
Mar
(3) |
Apr
(24) |
May
(22) |
Jun
(23) |
Jul
(8) |
Aug
(23) |
Sep
(8) |
Oct
(27) |
Nov
(52) |
Dec
(27) |
| 2010 |
Jan
(36) |
Feb
(29) |
Mar
(17) |
Apr
(28) |
May
(21) |
Jun
(4) |
Jul
|
Aug
(28) |
Sep
(18) |
Oct
(6) |
Nov
(34) |
Dec
(16) |
| 2011 |
Jan
(18) |
Feb
(12) |
Mar
|
Apr
|
May
(9) |
Jun
(1) |
Jul
(5) |
Aug
(5) |
Sep
(7) |
Oct
(16) |
Nov
(26) |
Dec
(17) |
| 2012 |
Jan
(6) |
Feb
(34) |
Mar
(52) |
Apr
(10) |
May
(3) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(4) |
Nov
(1) |
Dec
(4) |
| 2013 |
Jan
(5) |
Feb
|
Mar
|
Apr
(5) |
May
(4) |
Jun
|
Jul
|
Aug
(14) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
(2) |
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
(11) |
| 2015 |
Jan
(5) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: SourceForge.net <no...@so...> - 2003-12-25 02:41:45
|
Bugs item #865577, was opened at 2003-12-24 21:41 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=865577&group_id=34096 Category: Base System Group: all Status: Open Resolution: None Priority: 5 Submitted By: Heiko Zuerker (smiley73) Assigned to: Nobody/Anonymous (nobody) Summary: net::ssleay not working Initial Comment: webmin can't run in https mode without this. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=865577&group_id=34096 |
|
From: <no...@fr...> - 2003-12-25 00:48:29
|
This email is to inform you about the release of version '1.0.3' of 'GNU Transport Layer Security Library' through freshmeat.net. All URLs and other useful information can be found at http://freshmeat.net/projects/gnutls/ The changes in this release are as follows: A bug in gnutls_bye() which made it return an error code of INVALID_REQUEST instead of success has been corrected. A bug in the GNUTLS_KEY key usage definitions has been corrected. Project description: GNU Transport Layer Security Library is a library which implements a secure layer over a reliable transport layer such as TCP/IP. It implements the TLS 1.0 and SSL 3.0 protocols, accompanied with authentication methods such as X.509, OpenPGP, and SRP. Trove categories: [Development Status ] 5 - Production/Stable [License ] OSI Approved :: GNU General Public License (GPL), OSI Approved :: GNU Lesser General Public License (LGPL) [Operating System ] POSIX, Unix [Programming Language] C [Topic ] Security :: Cryptography, Software Development :: Libraries If you would like to cancel subscription to releases of this project, login to freshmeat.net and choose 'home' from the personal menubar at the top of the page. You'll be presented with a list of projects you're subscribed to in the right column, which you may cancel by highlighting the project in question and clicking the 'delete' button. Sincerely, freshmeat.net ____________________________| Advertising |____________________________ Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1709&alloc_id=4213&op=click ____________________________| Advertising |____________________________ |
|
From: SourceForge.net <no...@so...> - 2003-12-24 22:45:36
|
Bugs item #864037, was opened at 2003-12-21 12:48 Message generated for change (Settings changed) made by smiley73 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=864037&group_id=34096 Category: Base System Group: v1.1 >Status: Open Resolution: None Priority: 5 Submitted By: Heiko Zuerker (smiley73) Assigned to: Heiko Zuerker (smiley73) Summary: ProPolice + Libsafe + Pax + PIE Initial Comment: http://www.linuxfromscratch.org/hints/downloads/files/winter.txt this is a description to get all together working. ---------------------------------------------------------------------- Comment By: Heiko Zuerker (smiley73) Date: 2003-12-24 15:01 Message: Logged In: YES user_id=112133 LIBSafe is implemented and the support stuff for PIE is running in a test-compile right night. ProPolice and PAX are already included anyway. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=864037&group_id=34096 |
|
From: SourceForge.net <no...@so...> - 2003-12-24 20:01:12
|
Bugs item #864037, was opened at 2003-12-21 12:48 Message generated for change (Comment added) made by smiley73 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=864037&group_id=34096 Category: Base System Group: v1.1 >Status: Pending Resolution: None Priority: 5 Submitted By: Heiko Zuerker (smiley73) >Assigned to: Heiko Zuerker (smiley73) Summary: ProPolice + Libsafe + Pax + PIE Initial Comment: http://www.linuxfromscratch.org/hints/downloads/files/winter.txt this is a description to get all together working. ---------------------------------------------------------------------- >Comment By: Heiko Zuerker (smiley73) Date: 2003-12-24 15:01 Message: Logged In: YES user_id=112133 LIBSafe is implemented and the support stuff for PIE is running in a test-compile right night. ProPolice and PAX are already included anyway. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=864037&group_id=34096 |
|
From: <no...@fr...> - 2003-12-24 18:50:08
|
This email is to inform you about the release of version '3.1.15' of 'procps' through freshmeat.net. All URLs and other useful information can be found at http://freshmeat.net/projects/procps/ The changes in this release are as follows: This release supports the NSA's high-security SELinux on the 2.6.0 kernel, without any additional libraries required. Thread support no longer sets off chkrootkit on buggy 2.4.xx kernels (the PID 0 problem). Now "top" works on terminals with auto-margin problems. Project description: procps is a package of utilities which includes ps, vmstat, top, w, skill, snice, pgrep, pkill, free, sysctl, pmap, uptime, and kill. These utilities report what is running, who is logged in, how long the system has been running, and what is using up memory. They can be used to kill processes and change run-time kernel configuration values. Trove categories: [Environment ] Console (Text Based) [Intended Audience ] End Users/Desktop [License ] OSI Approved :: GNU General Public License (GPL) [Topic ] System :: Monitoring If you would like to cancel subscription to releases of this project, login to freshmeat.net and choose 'home' from the personal menubar at the top of the page. You'll be presented with a list of projects you're subscribed to in the right column, which you may cancel by highlighting the project in question and clicking the 'delete' button. Sincerely, freshmeat.net ____________________________| Advertising |____________________________ Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1709&alloc_id=4213&op=click ____________________________| Advertising |____________________________ |
|
From: Heiko Z. <he...@zu...> - 2003-12-24 15:01:21
|
Bruce Smith wrote: >>I also create a "bug" on sourceforge, that the checkfs script is not >>working properly, so we won't forgett it again. >> >> > >I think I figured it out. I put a fsck right before every mount. >It seems to work fine for ext3, checking only when needed. > > Once the changes are done, I can check how it behaves on my reiserfs. Heiko |
|
From: Heiko Z. <he...@zu...> - 2003-12-24 14:36:16
|
Tim Tait wrote: > It looks like all I need to do to support the Promise PDC2026x IDE > controller is enable some kernel options. I ran 'make menuconfig' in > the kernel directory and picked what I hoped was the right stuff, but > it looked like some of usual DL stuff was not set so I am a little > worried. It told me to do 'make dep' next, but that failed, something > about missing sources. So I ran a dl 'make clean' and 'make > menuconfig' and 'make build' but I have no idea what exactly I am > going to get. How does one check to see what really got put into the > kernel? > > Is the right was to customize the kernel for DL? If I just want to > enable a few things is there a better way? Thanks- > > Tim > > ps: The speed issue appears to have nothing to do with raid, it is a > write speed problem. Looks like PIO is used for write (3.3MB/s), and > UDMA (55MB/s) for read. Odd. > Just changing some kernel options end re-compiling the kernel doesn't work very well. Best way is to change the parameters and see if it correctly re-compiles by executing build/scripts/build.sh build opt=linux When the compile runs fine, then you have to change the values in build/scripts/config/config_linux and start over with a "make mrproper unpack......" I quickly checked the kernel config and the support for the Promise controllers is in there. Is the BIOS for the controller enable? Is there any quick-boot you could disable ? Heiko |
|
From: Bruce S. <bw...@ar...> - 2003-12-24 14:34:41
|
> >> Now to make a fairly simple script more complicated ... what about > >> fsck? The checkfs script isn't going to do it. > >> And it's not easy because they aren't listed in fstab. > >> What's the best way to handle fsck's? > > > > That's one of the points I wanted to do the fstab list in > > the script in memory to eg. run the fsck in the correct order. > > > We could define the order this way: first check everything in lvmtab and > then the rest. Yeah, that's what I was thinking late last night. Now to rewrite it ... :-) > I also create a "bug" on sourceforge, that the checkfs script is not > working properly, so we won't forgett it again. I think I figured it out. I put a fsck right before every mount. It seems to work fine for ext3, checking only when needed. - BS |
|
From: Heiko Z. <he...@zu...> - 2003-12-24 14:21:21
|
Hey, Friedrich Lobenstock wrote: > This patch fixes the corner case an empty directory to be copied > to the jail dir. the patch doesn't apply. root:/data/build/config# patch -i ../../patch-jail-new2 -p0 patching file etc/init.d/jail Hunk #1 FAILED at 81. I attached the current CVS version of the jail script Heiko |
|
From: Heiko Z. <he...@zu...> - 2003-12-24 14:01:17
|
Friedrich Lobenstock wrote: > Bruce Smith wrote on 24.12.2003 04:19 MET: > >> Now to make a fairly simple script more complicated ... what about >> fsck? The checkfs script isn't going to do it. >> And it's not easy because they aren't listed in fstab. >> What's the best way to handle fsck's? > > > That's one of the points I wanted to do the fstab list in > the script in memory to eg. run the fsck in the correct order. > We could define the order this way: first check everything in lvmtab and then the rest. I also create a "bug" on sourceforge, that the checkfs script is not working properly, so we won't forgett it again. Heiko |
|
From: SourceForge.net <no...@so...> - 2003-12-24 13:55:30
|
Bugs item #865396, was opened at 2003-12-24 08:55 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=865396&group_id=34096 Category: Configuration / Scripts Group: None Status: Open Resolution: None Priority: 5 Submitted By: Heiko Zuerker (smiley73) Assigned to: Nobody/Anonymous (nobody) Summary: checkfs Initial Comment: checkfs doesn't do much at the moment, this has to be corrected or some additional functionality has to be added to mountfs. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410643&aid=865396&group_id=34096 |
|
From: Tim T. <t....@co...> - 2003-12-24 07:56:16
|
It looks like all I need to do to support the Promise PDC2026x IDE controller is enable some kernel options. I ran 'make menuconfig' in the kernel directory and picked what I hoped was the right stuff, but it looked like some of usual DL stuff was not set so I am a little worried. It told me to do 'make dep' next, but that failed, something about missing sources. So I ran a dl 'make clean' and 'make menuconfig' and 'make build' but I have no idea what exactly I am going to get. How does one check to see what really got put into the kernel? Is the right was to customize the kernel for DL? If I just want to enable a few things is there a better way? Thanks- Tim ps: The speed issue appears to have nothing to do with raid, it is a write speed problem. Looks like PIO is used for write (3.3MB/s), and UDMA (55MB/s) for read. Odd. |
|
From: Friedrich L. <fl...@fl...> - 2003-12-24 03:59:54
|
Hi! This patch fixes the corner case an empty directory to be copied to the jail dir. -- MfG / Regards Friedrich Lobenstock ____________________________________________________________________ Friedrich Lobenstock Linux Services Lobenstock URL: http://www.lsl.at/ Email: fl...@fl... ____________________________________________________________________ |
|
From: Friedrich L. <fl...@fl...> - 2003-12-24 03:47:11
|
Bruce Smith wrote on 24.12.2003 04:19 MET: > Now to make a fairly simple script more complicated ... > what about fsck? The checkfs script isn't going to do it. > And it's not easy because they aren't listed in fstab. > What's the best way to handle fsck's? That's one of the points I wanted to do the fstab list in the script in memory to eg. run the fsck in the correct order. -- MfG / Regards Friedrich Lobenstock ____________________________________________________________________ Friedrich Lobenstock Linux Services Lobenstock URL: http://www.lsl.at/ Email: fl...@fl... ____________________________________________________________________ |
|
From: Heiko Z. <he...@zu...> - 2003-12-24 03:35:16
|
Bruce Smith wrote: >>>>>Yes, it was my understanding that we exactly do this. >>>>> >>>>> >>>>I can do that. So the only entries in the default lvmtab file are: >>>>/home /opt & swap ??? >>>> >>>> >>>Probably but why not put the standard LVs there too so the >>>user has a place to lock at than to dig into the source of >>>the script to find out where things get mounted. >>> >>> >>I still think we should this make "automatic", either it's in lvmtab or >>it get's mounted under /var >> >> > >Yes, I'll all "#" comments and we can explain that. > >Now to make a fairly simple script more complicated ... >what about fsck? The checkfs script isn't going to do it. >And it's not easy because they aren't listed in fstab. >What's the best way to handle fsck's? > > Very good question. Reiserfs for example shouldn't need a fsck, I know that ext2/3 will complain after a while.... To be honest, I don't think that our checkfs is doing anything (take a look in it). I copied it a long long time ago from LFS and never ever touch it again..... Heiko P.S. I'm going offline now, 'night ! |
|
From: Bruce S. <br...@ar...> - 2003-12-24 03:19:20
|
> >>> Yes, it was my understanding that we exactly do this. > >> > >> I can do that. So the only entries in the default lvmtab file are: > >> /home /opt & swap ??? > > > > Probably but why not put the standard LVs there too so the > > user has a place to lock at than to dig into the source of > > the script to find out where things get mounted. > > I still think we should this make "automatic", either it's in lvmtab or > it get's mounted under /var Yes, I'll all "#" comments and we can explain that. Now to make a fairly simple script more complicated ... what about fsck? The checkfs script isn't going to do it. And it's not easy because they aren't listed in fstab. What's the best way to handle fsck's? - BS |
|
From: Heiko Z. <he...@zu...> - 2003-12-24 03:05:21
|
Friedrich Lobenstock wrote: > Bruce Smith wrote on 24.12.2003 03:34 MET: > >>>>> All LVs get mounted under /var when they're not "special". >>>>> You get a list of all available LVs in this folder: >>>>> /proc/lvm/VGs/devil-linux/LVs/ >>>> >>>> >>>> If we find a LV xyz in the VG devil-linux that is not listet >>>> in /etc/sysconfig/lvmtab we try to create /var/xyz/ and mount >>>> it there. Is that what you mean? >>> >>> >>> Yes, it was my understanding that we exactly do this. >> >> >> >> I can do that. So the only entries in the default lvmtab file are: >> /home /opt & swap ??? > > > Probably but why not put the standard LVs there too so the > user has a place to lock at than to dig into the source of > the script to find out where things get mounted. I still think we should this make "automatic", either it's in lvmtab or it get's mounted under /var >> How is /proc/lvm/VGs/devil-linux/LVs/ different than >> /dev/devil-linux/ ? Or which is the best one to use? > > > /proc/lvm/VGs/devil-linux/LVs/ is probably the cleaner way. Before > a certain release of LVM it was not possible to get the info via > that path, that's why I did stick with the "old" way when I did the > current script. Yeah so let's use the proc >> You can mount disks on existing directories on the CD, you just can't >> create new directories. (i.e. I can mount something under /mnt) >> >> So, if the directory doesn't already exist, try to create it. If it >> can't be created then display an error. > > > What I meant was if we have to creat a directory we might want to > check first if the filesystem is read-only and display an error > in this case. Can the mkdir fail because of something else? If > not, then just checking if mkdir fails would do it too I think. > Agreed, checking if mkdir fails, should be the easiest way. Heiko |
|
From: Bruce S. <bw...@ar...> - 2003-12-24 02:56:45
|
> > I can do that. So the only entries in the default lvmtab file are: > > /home /opt & swap ??? > > Probably but why not put the standard LVs there too so the > user has a place to lock at than to dig into the source of > the script to find out where things get mounted. I'd rather add comments in the file explaining how it works. > > How is /proc/lvm/VGs/devil-linux/LVs/ different than > > /dev/devil-linux/ ? Or which is the best one to use? > > /proc/lvm/VGs/devil-linux/LVs/ is probably the cleaner way. Before > a certain release of LVM it was not possible to get the info via > that path, that's why I did stick with the "old" way when I did the > current script. OK. > > You can mount disks on existing directories on the CD, you just can't > > create new directories. (i.e. I can mount something under /mnt) > > > > So, if the directory doesn't already exist, try to create it. If it > > can't be created then display an error. > > What I meant was if we have to creat a directory we might want to > check first if the filesystem is read-only and display an error > in this case. Can the mkdir fail because of something else? If > not, then just checking if mkdir fails would do it too I think. I don't think it matters how mkdir fails. If it fails for any reason, the mount will not work, so we might as well just display the error. - BS |
|
From: Heiko Z. <he...@zu...> - 2003-12-24 02:51:17
|
Bruce Smith wrote: >>>>All LVs get mounted under /var when they're not "special". >>>>You get a list of all available LVs in this folder: >>>>/proc/lvm/VGs/devil-linux/LVs/ >>>> >>>> >>>If we find a LV xyz in the VG devil-linux that is not listet >>>in /etc/sysconfig/lvmtab we try to create /var/xyz/ and mount >>>it there. Is that what you mean? >>> >>> >>Yes, it was my understanding that we exactly do this. >> >> > >I can do that. So the only entries in the default lvmtab file are: >/home /opt & swap ??? > > Yes I would say so. Heiko |
|
From: Friedrich L. <fl...@fl...> - 2003-12-24 02:50:13
|
Bruce Smith wrote on 24.12.2003 03:34 MET: >>>>All LVs get mounted under /var when they're not "special". >>>>You get a list of all available LVs in this folder: >>>>/proc/lvm/VGs/devil-linux/LVs/ >>> >>>If we find a LV xyz in the VG devil-linux that is not listet >>>in /etc/sysconfig/lvmtab we try to create /var/xyz/ and mount >>>it there. Is that what you mean? >> >>Yes, it was my understanding that we exactly do this. > > > I can do that. So the only entries in the default lvmtab file are: > /home /opt & swap ??? Probably but why not put the standard LVs there too so the user has a place to lock at than to dig into the source of the script to find out where things get mounted. > How is /proc/lvm/VGs/devil-linux/LVs/ different than > /dev/devil-linux/ ? Or which is the best one to use? /proc/lvm/VGs/devil-linux/LVs/ is probably the cleaner way. Before a certain release of LVM it was not possible to get the info via that path, that's why I did stick with the "old" way when I did the current script. > You can mount disks on existing directories on the CD, you just can't > create new directories. (i.e. I can mount something under /mnt) > > So, if the directory doesn't already exist, try to create it. If it > can't be created then display an error. What I meant was if we have to creat a directory we might want to check first if the filesystem is read-only and display an error in this case. Can the mkdir fail because of something else? If not, then just checking if mkdir fails would do it too I think. -- MfG / Regards Friedrich Lobenstock ____________________________________________________________________ Friedrich Lobenstock Linux Services Lobenstock URL: http://www.lsl.at/ Email: fl...@fl... ____________________________________________________________________ |
|
From: Heiko Z. <he...@zu...> - 2003-12-24 02:46:15
|
Bruce Smith wrote: >>>>All LVs get mounted under /var when they're not "special". >>>>You get a list of all available LVs in this folder: >>>>/proc/lvm/VGs/devil-linux/LVs/ >>>> >>>> >>>If we find a LV xyz in the VG devil-linux that is not listet >>>in /etc/sysconfig/lvmtab we try to create /var/xyz/ and mount >>>it there. Is that what you mean? >>> >>> >>Yes, it was my understanding that we exactly do this. >> >> > >I can do that. So the only entries in the default lvmtab file are: >/home /opt & swap ??? > >How is /proc/lvm/VGs/devil-linux/LVs/ different than >/dev/devil-linux/ ? Or which is the best one to use? > > I don't know, pick one. ;-) >>>>We also have do be carefull, I'm pretty sure a lot of people would >>>>try to mount an LV e.g. under /some-mount-point and then complain it >>>>doesn't work. Of course it will not work, because they can't create >>>>the mount point on the CD.... >>>> >>>> >>>That case can be handled by the script. We can even check the >>>directory where the mount should occour and then check if the >>>filesystem there is ro or rw. Good point. Better to prepare now >>>before the users come asking for help where they shouldn't have >>>gone in the first place ;-) >>> >>> >>yeah good point. >> >> > >You can mount disks on existing directories on the CD, you just can't >create new directories. (i.e. I can mount something under /mnt) > Yeah, but you know that some users won't understand that logic. ;-) >So, if the directory doesn't already exist, try to create it. If it >can't be created then display an error. > > Yeah that should be the easiest way. Heiko |
|
From: Bruce S. <bw...@ar...> - 2003-12-24 02:34:20
|
> >> All LVs get mounted under /var when they're not "special". > >> You get a list of all available LVs in this folder: > >> /proc/lvm/VGs/devil-linux/LVs/ > > > > If we find a LV xyz in the VG devil-linux that is not listet > > in /etc/sysconfig/lvmtab we try to create /var/xyz/ and mount > > it there. Is that what you mean? > > Yes, it was my understanding that we exactly do this. I can do that. So the only entries in the default lvmtab file are: /home /opt & swap ??? How is /proc/lvm/VGs/devil-linux/LVs/ different than /dev/devil-linux/ ? Or which is the best one to use? > >> We also have do be carefull, I'm pretty sure a lot of people would > >> try to mount an LV e.g. under /some-mount-point and then complain it > >> doesn't work. Of course it will not work, because they can't create > >> the mount point on the CD.... > > > > That case can be handled by the script. We can even check the > > directory where the mount should occour and then check if the > > filesystem there is ro or rw. Good point. Better to prepare now > > before the users come asking for help where they shouldn't have > > gone in the first place ;-) > > yeah good point. You can mount disks on existing directories on the CD, you just can't create new directories. (i.e. I can mount something under /mnt) So, if the directory doesn't already exist, try to create it. If it can't be created then display an error. - BS |
|
From: Heiko Z. <he...@zu...> - 2003-12-24 01:51:15
|
Friedrich Lobenstock wrote: > Heiko Zuerker wrote on 23.12.2003 23:55 MET: > >> Bruce Smith wrote: >> >>> Here's the new default /etc/sysconfig/lvmtab: >>> (first column is the lv name under vg devil-linux) >>> >>> swap swap swap defaults 0 0 >>> home /home auto defaults 0 0 >>> opt /opt auto defaults 0 0 >>> log /var/log auto defaults 0 0 >>> spool /var/spool auto defaults 0 0 >>> squid /var/squid auto defaults 0 0 >>> tmp /var/tmp auto defaults 0 0 >>> data /var/data auto defaults 0 0 >>> imap /var/imap auto defaults 0 0 >>> mail /var/mail auto defaults 0 0 >>> >>> Left as-is, the mountfs script will function exactly the same as it >>> does >>> now, using the lvmtab file for it's mount parameters (instead of being >>> hard coded). LV's that don't exist will be silently skipped (as >>> opposed >>> to error messages if they were in fstab). As far as sorting by >>> depth, it's not going to happen. The file will be >>> read sequentially and people will have to add nested mounts in the >>> correct order in lvmtab. >>> >>> This simply gives people the ability the add/change LV's, plus adding >>> the ability so specify mount options (like "quota"). >> >> >> [...] >> All LVs get mounted under /var when they're not "special". >> You get a list of all available LVs in this folder: >> /proc/lvm/VGs/devil-linux/LVs/ > > > If we find a LV xyz in the VG devil-linux that is not listet > in /etc/sysconfig/lvmtab we try to create /var/xyz/ and mount > it there. Is that what you mean? Yes, it was my understanding that we exactly do this. >> We also have do be carefull, I'm pretty sure a lot of people would >> try to mount an LV e.g. under /some-mount-point and then complain it >> doesn't work. Of course it will not work, because they can't create >> the mount point on the CD.... > > > That case can be handled by the script. We can even check the > directory where the mount should occour and then check if the > filesystem there is ro or rw. Good point. Better to prepare now > before the users come asking for help where they shouldn't have > gone in the first place ;-) yeah good point. Heiko |
|
From: Heiko Z. <he...@zu...> - 2003-12-24 01:46:20
|
Diego Torres wrote: >On Tue, Dec 23, 2003 at 07:03:12PM -0500, Heiko Zuerker wrote: > > > >>>and also, if i ignore/timeout the script that asks to "update" the config >>>stuff after a version change, and i issue a save-config... why the script >>>asks me the next time i boot up if i want to update the config? >>> >>>it sounds better to me the idea of a save-config script that updates the >>>version stored on the /etc file. >>> >>> >>> >>We do that on purpose, since you could cause to much problems ( and >>support for us ) by using out-dated scripts/configs. >> >> > >time for a save-config --force-update-version switch ? :) > > > With a "on you on risk and don't even bother and try to get support for this" message ? Then yes, go ahead and do it. Heiko |
|
From: Friedrich L. <fl...@fl...> - 2003-12-24 01:32:10
|
Heiko Zuerker wrote on 23.12.2003 23:55 MET: > Bruce Smith wrote: > >> Here's the new default /etc/sysconfig/lvmtab: >> (first column is the lv name under vg devil-linux) >> >> swap swap swap defaults 0 0 >> home /home auto defaults 0 0 >> opt /opt auto defaults 0 0 >> log /var/log auto defaults 0 0 >> spool /var/spool auto defaults 0 0 >> squid /var/squid auto defaults 0 0 >> tmp /var/tmp auto defaults 0 0 >> data /var/data auto defaults 0 0 >> imap /var/imap auto defaults 0 0 >> mail /var/mail auto defaults 0 0 >> >> Left as-is, the mountfs script will function exactly the same as it does >> now, using the lvmtab file for it's mount parameters (instead of being >> hard coded). LV's that don't exist will be silently skipped (as opposed >> to error messages if they were in fstab). >> As far as sorting by depth, it's not going to happen. The file will be >> read sequentially and people will have to add nested mounts in the >> correct order in lvmtab. >> >> This simply gives people the ability the add/change LV's, plus adding >> the ability so specify mount options (like "quota"). > > [...] > All LVs get mounted under /var when they're not "special". > You get a list of all available LVs in this folder: > /proc/lvm/VGs/devil-linux/LVs/ If we find a LV xyz in the VG devil-linux that is not listet in /etc/sysconfig/lvmtab we try to create /var/xyz/ and mount it there. Is that what you mean? > We also have do be carefull, I'm pretty sure a lot of people would try > to mount an LV e.g. under /some-mount-point and then complain it doesn't > work. Of course it will not work, because they can't create the mount > point on the CD.... That case can be handled by the script. We can even check the directory where the mount should occour and then check if the filesystem there is ro or rw. Good point. Better to prepare now before the users come asking for help where they shouldn't have gone in the first place ;-) -- MfG / Regards Friedrich Lobenstock ____________________________________________________________________ Friedrich Lobenstock Linux Services Lobenstock URL: http://www.lsl.at/ Email: fl...@fl... ____________________________________________________________________ |
35 messages has been excluded from this view by a project administrator.
