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: Bruce S. <bw...@ar...> - 2003-10-28 18:07:38
|
> > I start building the 1.0 Images tomorrow (Tuesday) night, Unless the mailings lists are 24 hours slow again (they haven't been), today is Tuesday. Tomorrow is Wednesday. We are still in the same time zone, right? Or did you forget to set your clocks back? ;-) So, are you starting build tonight (Tue) or tomorrow night (Wed)? - BS |
|
From: Bruce S. <bw...@ar...> - 2003-10-28 18:04:55
|
> second mental note: ask bruce if save-config works on the usb, as it looks > that the fs is readonly, but only before trying it at home :) At one time there was a problem if you booted up your USB with the write protect switch on. I don't know if it was ever fixed. - BS |
|
From: Bruce S. <bw...@ar...> - 2003-10-28 18:01:14
|
> >OK, I made a bunch of changes and checked it in 1.1 (untested!). > > > >Can you try it and see what happens? > >I don't have a devfs system for testing. > > > >I also added a grub entry for memtest86, if it's installed. > > I think this is stuff which should go into 1.0, too. > What do you think ? Sure, if tests show it to work. > I start building the 1.0 Images tomorrow (Tuesday) night, so please test it > immediatelly. I can try it on a non-devfs system, but I don't have any devfs systems to test it on. - BS |
|
From: Heiko Z. <hz...@pr...> - 2003-10-28 16:57:04
|
On 10/28/2003 11:38:22 AM Bruce Smith wrote: >> > Do you think it would be safe to test for a symlink in the script?= >> > >> > if [ -L /dev/sda ]; then >> > # (replace /dev/sda with the variable of the device entered) >> >> why not ask everything needed to the user? print a warning on the >screen, and if the user screws it, then it'll be his/her fault. >> >> pd.- should the memtest86 option be available to the usb stick? mayb= e >we could make memtest a default appl on every dl version (its very >small [<300kb] and very useful) > >OK, I made a bunch of changes and checked it in 1.1 (untested!). > >Can you try it and see what happens? >I don't have a devfs system for testing. > >I also added a grub entry for memtest86, if it's installed. I think this is stuff which should go into 1.0, too. What do you think ? I start building the 1.0 Images tomorrow (Tuesday) night, so please tes= t it immediatelly. cya Heiko = |
|
From: Bruce S. <bw...@ar...> - 2003-10-28 16:38:29
|
> > Do you think it would be safe to test for a symlink in the script? > > > > if [ -L /dev/sda ]; then > > # (replace /dev/sda with the variable of the device entered) > > why not ask everything needed to the user? print a warning on the screen, and if the user screws it, then it'll be his/her fault. > > pd.- should the memtest86 option be available to the usb stick? maybe we could make memtest a default appl on every dl version (its very small [<300kb] and very useful) OK, I made a bunch of changes and checked it in 1.1 (untested!). Can you try it and see what happens? I don't have a devfs system for testing. I also added a grub entry for memtest86, if it's installed. - BS |
|
From: Diego T. <dt...@co...> - 2003-10-28 15:02:45
|
On Tue, Oct 28, 2003 at 09:44:07AM -0500, Bruce Smith wrote: > Do you think it would be safe to test for a symlink in the script? > > if [ -L /dev/sda ]; then > # (replace /dev/sda with the variable of the device entered) why not ask everything needed to the user? print a warning on the screen, and if the user screws it, then it'll be his/her fault. pd.- should the memtest86 option be available to the usb stick? maybe we could make memtest a default appl on every dl version (its very small [<300kb] and very useful) -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Diego T. <dt...@co...> - 2003-10-28 14:58:40
|
On Mon, Oct 27, 2003 at 06:32:57PM -0500, Heiko Zuerker wrote: > >man? i remembered saying "do not copy manpages on cd". > > > man, doc and info should be empty... > > You want to fix it ? will do my best :)) I want to keepp everything i need for a raid server on a 128mb stick. -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Diego T. <dt...@co...> - 2003-10-28 14:57:05
|
On Tue, Oct 28, 2003 at 09:02:41AM -0500, Bruce Smith wrote: > > > > > >So the problem is beyond that point, because grub doesn't recognize > > >root /dev/host0.../disc as a valid option. > > > > I'm sure it's this line. > > LVM doesn't like the symlinks either,when you use devfs you need to use the > > "real" device name. you were right. Doing some sort of manual configuration: DEVICE=/dev/scsi/host0/bus0/target0/lun0/disc GRUBPART=0 PARTITION=/dev/scsi/host0/bus0/target0/lun0/part1 resulsts in a perfectly booting usb stick on an epia cl10000 motherboard. I'm quite happy :) pd.- look at freevix-0.72.tar.bz2 (www.freevix.org). Its a small distro optimized for running a clone of mplayer+fluxbox on an epia board. wow! -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Bruce S. <bw...@ar...> - 2003-10-28 14:53:49
|
> >Do all devfs systems have symlinks? Is that a standard part of devfs? > > The symlinks are created by the devfsd, which is a special daemon to > support software which can't handle the devfs. > Every distrib "should" support this, though I'm not certain. Do you think it would be safe to test for a symlink in the script? if [ -L /dev/sda ]; then # (replace /dev/sda with the variable of the device entered) - BS |
|
From: Diego T. <dt...@co...> - 2003-10-28 14:42:16
|
On Tue, Oct 28, 2003 at 09:02:41AM -0500, Bruce Smith wrote: > > Do all devfs systems have symlinks? Is that a standard part of devfs? symlinks are provided by devsfd, the daemon. -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Heiko Z. <hz...@pr...> - 2003-10-28 14:39:32
|
On 10/28/2003 09:02:41 AM Bruce Smith wrote:
>> >> > This line is most likely the problem:
>> >> >
>> >> > GRUBPART=3D$(expr ${PARTITION##/dev/[hs]d[a-z]} - 1)
>> >>
>> >> Yeah, that'll do it. I'll take a look tomorrow.
>> >
>> >Not sure. Because on my system, (as i'm running devfsd), i have
>> >/dev/sda and /dev/sda1 as links
>> >to /dev/host0.../disc and blahblahblah/part1.
>> >
>> >So the problem is beyond that point, because grub doesn't recognize=
>> >root /dev/host0.../disc as a valid option.
>>
>> I'm sure it's this line.
>> LVM doesn't like the symlinks either,when you use devfs you need to
>use the
>> "real" device name.
>
>Do all devfs systems have symlinks? Is that a standard part of devfs?=
The symlinks are created by the devfsd, which is a special daemon to
support software which can't handle the devfs.
Every distrib "should" support this, though I'm not certain.
cya
Heiko
=
|
|
From: Bruce S. <bw...@ar...> - 2003-10-28 14:03:23
|
> >> > This line is most likely the problem:
> >> >
> >> > GRUBPART=$(expr ${PARTITION##/dev/[hs]d[a-z]} - 1)
> >>
> >> Yeah, that'll do it. I'll take a look tomorrow.
> >
> >Not sure. Because on my system, (as i'm running devfsd), i have
> >/dev/sda and /dev/sda1 as links
> >to /dev/host0.../disc and blahblahblah/part1.
> >
> >So the problem is beyond that point, because grub doesn't recognize
> >root /dev/host0.../disc as a valid option.
>
> I'm sure it's this line.
> LVM doesn't like the symlinks either,when you use devfs you need to use the
> "real" device name.
Do all devfs systems have symlinks? Is that a standard part of devfs?
- BS
|
|
From: Heiko Z. <hz...@pr...> - 2003-10-28 13:53:35
|
On 10/28/2003 02:51:48 AM Diego Torres wrote:
>On Mon, Oct 27, 2003 at 09:35:04PM -0500, Bruce Smith wrote:
>> > >and because of this, none of the commands entered to grub work. :=
/
>help! :)
>> > >
>> > I guess we need some intelligence in the script.
>> > This line is most likely the problem:
>> >
>> > GRUBPART=3D$(expr ${PARTITION##/dev/[hs]d[a-z]} - 1)
>>
>> Yeah, that'll do it. I'll take a look tomorrow.
>
>Not sure. Because on my system, (as i'm running devfsd), i have
>/dev/sda and /dev/sda1 as links
>to /dev/host0.../disc and blahblahblah/part1.
>
>So the problem is beyond that point, because grub doesn't recognize
>root /dev/host0.../disc as a valid option.
I'm sure it's this line.
LVM doesn't like the symlinks either,when you use devfs you need to use=
the
"real" device name.
Heiko
=
|
|
From: Diego T. <dt...@co...> - 2003-10-28 07:52:40
|
On Mon, Oct 27, 2003 at 09:35:04PM -0500, Bruce Smith wrote:
> > >and because of this, none of the commands entered to grub work. :/ help! :)
> > >
> > I guess we need some intelligence in the script.
> > This line is most likely the problem:
> >
> > GRUBPART=$(expr ${PARTITION##/dev/[hs]d[a-z]} - 1)
>
> Yeah, that'll do it. I'll take a look tomorrow.
Not sure. Because on my system, (as i'm running devfsd), i have /dev/sda and /dev/sda1 as links
to /dev/host0.../disc and blahblahblah/part1.
So the problem is beyond that point, because grub doesn't recognize root /dev/host0.../disc as a valid option.
>
> What distribution are you running? Does it come standard with devfs?
Debian unstable.
--
-- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799
-- Use of a keyboard or mouse may be linked to serious injuries or disorders.
Diego Torres - dt...@co... - Madrid / España
|
|
From: Bruce S. <bw...@ar...> - 2003-10-28 02:49:41
|
> >problem found. i'm using devfsd, so:
> ># cat grub-tmp-map
> >(fd0) /dev/floppy/0
> >(hd0) /dev/ide/host0/bus0/target0/lun0/disc
> >(hd1) /dev/ide/host0/bus1/target0/lun0/disc
> >(hd2) /dev/ide/host2/bus0/target0/lun0/disc
> >(hd3) /dev/ide/host2/bus1/target0/lun0/disc
> >(hd4) /dev/scsi/host0/bus0/target0/lun0/disc
> >
> >and because of this, none of the commands entered to grub work. :/ help! :)
> >
> I guess we need some intelligence in the script.
> This line is most likely the problem:
>
> GRUBPART=$(expr ${PARTITION##/dev/[hs]d[a-z]} - 1)
Yeah, that'll do it. I'll take a look tomorrow.
What distribution are you running? Does it come standard with devfs?
- BS
|
|
From: Heiko Z. <he...@zu...> - 2003-10-28 02:21:37
|
Diego Torres wrote:
>On Mon, Oct 27, 2003 at 07:35:10PM -0500, Bruce Smith wrote:
>
>
>>If you're running it from anywhere else, it'll probably die.
>>
>>
>
>problem found. i'm using devfsd, so:
># cat grub-tmp-map
>(fd0) /dev/floppy/0
>(hd0) /dev/ide/host0/bus0/target0/lun0/disc
>(hd1) /dev/ide/host0/bus1/target0/lun0/disc
>(hd2) /dev/ide/host2/bus0/target0/lun0/disc
>(hd3) /dev/ide/host2/bus1/target0/lun0/disc
>(hd4) /dev/scsi/host0/bus0/target0/lun0/disc
>
>and because of this, none of the commands entered to grub work. :/ help! :)
>
>
I guess we need some intelligence in the script.
This line is most likely the problem:
GRUBPART=$(expr ${PARTITION##/dev/[hs]d[a-z]} - 1)
cya
Heiko
|
|
From: Bruce S. <bw...@ar...> - 2003-10-28 02:16:47
|
> problem found. i'm using devfsd, so: > # cat grub-tmp-map > (fd0) /dev/floppy/0 > (hd0) /dev/ide/host0/bus0/target0/lun0/disc > (hd1) /dev/ide/host0/bus1/target0/lun0/disc > (hd2) /dev/ide/host2/bus0/target0/lun0/disc > (hd3) /dev/ide/host2/bus1/target0/lun0/disc > (hd4) /dev/scsi/host0/bus0/target0/lun0/disc > > and because of this, none of the commands entered to grub work. :/ help! :) Ah, OK. What's it do when you enter "/dev/scsi/host0/bus0/target0/lun0/disc" when it asks for the device file? - BS |
|
From: Diego T. <dt...@co...> - 2003-10-28 01:47:27
|
On Mon, Oct 27, 2003 at 07:35:10PM -0500, Bruce Smith wrote: > > If you're running it from anywhere else, it'll probably die. problem found. i'm using devfsd, so: # cat grub-tmp-map (fd0) /dev/floppy/0 (hd0) /dev/ide/host0/bus0/target0/lun0/disc (hd1) /dev/ide/host0/bus1/target0/lun0/disc (hd2) /dev/ide/host2/bus0/target0/lun0/disc (hd3) /dev/ide/host2/bus1/target0/lun0/disc (hd4) /dev/scsi/host0/bus0/target0/lun0/disc and because of this, none of the commands entered to grub work. :/ help! :) -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Heiko Z. <he...@zu...> - 2003-10-28 01:31:18
|
Hey, I just replaced krb5 with heimdal, which compiles fine with the stack smashing protector. I hope everything works fine and now we can add krb5 support to other programs. cya Heiko |
|
From: Diego T. <dt...@co...> - 2003-10-28 00:46:57
|
On Mon, Oct 27, 2003 at 07:35:10PM -0500, Bruce Smith wrote: > > If you're running it from anywhere else, it'll probably die. when and by whom is the file grub-tmp-map created? -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Diego T. <dt...@co...> - 2003-10-28 00:46:09
|
On Mon, Oct 27, 2003 at 07:35:10PM -0500, Bruce Smith wrote: > > > It appears like you may have entered something like: > > > "/dev/sda" instead of "/dev/sda1" > > > > i entered /dev/sda1 > > Where are you running the script from (what directory)? i'm running it from the dist directory (and yes, i'm executing ./install-on-usb). -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Diego T. <dt...@co...> - 2003-10-28 00:40:24
|
> >Error 11: Unrecognized device string > >grub> setup > > > >Error 11: Unrecognized device string > >grub> quit > >syncing and unmounting (this could take a while) > > > I'm not familiar with grub. same here. because of that i tried to use lilo, with no success :( -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Bruce S. <bw...@ar...> - 2003-10-28 00:37:07
|
> > What exactly did you enter when it ask for partition name? > > It appears like you may have entered something like: > > "/dev/sda" instead of "/dev/sda1" > > i entered /dev/sda1 Where are you running the script from (what directory)? I think it requires you run "./install-on-usb" from the "dist" directory, where you unpacked the tarball, or output directory of "make dist". If you're running it from anywhere else, it'll probably die. - BS |
|
From: Diego T. <dt...@co...> - 2003-10-28 00:30:32
|
On Mon, Oct 27, 2003 at 07:11:22PM -0500, Bruce Smith wrote:
> What exactly did you enter when it ask for partition name?
> It appears like you may have entered something like:
> "/dev/sda" instead of "/dev/sda1"
i entered /dev/sda1
i've inserted the following:
$grub_shell --batch --device-map=$device_map <<-EOF
quit
EOF
install_drive=$(grep "$1\$" $device_map|cut -f1)
root_drive="${install_drive%%)},0)"
+echo install_drive: $install_drive
+echo root_drive: $root_drive
+echo dolar1: $1
+echo dolar2: $2
+echo device_map: $device_map
$grub_shell --batch --device-map=$device_map <<-EOF
root $root_drive
setup $force_lba $install_drive
quit
EOF
And this is the output:
copying files...
grep: grub-tmp-map: File not found
install_drive:
root_drive: ,0)
dolar1: /dev/sda
dolar2: 0
device_map: grub-tmp-map
And thats true, when is the file grub-tmp-map created?
--
-- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799
-- Use of a keyboard or mouse may be linked to serious injuries or disorders.
Diego Torres - dt...@co... - Madrid / España
|
|
From: Heiko Z. <he...@zu...> - 2003-10-28 00:29:20
|
Diego Torres wrote: >i've found several problems when using the install-on-usb script. > >installing lilo as a bootloader is commented. Therefore, i suppose that its deprecated. > Kind of. We left it in there, so people can use/modify it if they want to. >If not, there is an error: > >Last chance, do you really want to continue ? (y/n) >mke2fs 1.33 (21-Apr-2003) >Filesystem label= >OS type: Linux >Block size=1024 (log=0) >Fragment size=1024 (log=0) >32256 inodes, 129008 blocks >6450 blocks (5.00%) reserved for the super user >First data block=1 >16 block groups >8192 blocks per group, 8192 fragments per group >2016 inodes per group >Superblock backups stored on blocks: > 8193, 24577, 40961, 57345, 73729 > >Writing inode tables: done >Writing superblocks and filesystem accounting information: done > >This filesystem will be automatically checked every 33 mounts or >180 days, whichever comes first. Use tune2fs -c or -i to override. >tune2fs 1.33 (21-Apr-2003) >Setting maximal mount count to -1 >copying files... >cp: cannot stat `/boot/boot.b': No such file or directory >syncing and unmounting (this could take a while) > > >and thats true, because /boot is on my partition, not in the tarball, neither on the lfs. > It actually requires that you have lilo installed. We could get rid of those messages by including the necessary files. But then again, grub is the one which should be used. ;-) >when using grub i get also a strange error: > >Setting maximal mount count to -1 >copying files... >Probing devices to guess BIOS drives. This may take a long time. > > >GRUB version 0.93 (640K lower / 3072K upper memory) > >[ Minimal BASH-like line editing is supported. For the first word, TAB >lists possible command completions. Anywhere else TAB lists the possible >completions of a device/filename.] >grub> quit > >GRUB version 0.93 (640K lower / 3072K upper memory) > >[ Minimal BASH-like line editing is supported. For the first word, TAB >lists possible command completions. Anywhere else TAB lists the possible >completions of a device/filename.] >grub> root ,0) > >Error 11: Unrecognized device string >grub> setup > >Error 11: Unrecognized device string >grub> quit >syncing and unmounting (this could take a while) > > > I'm not familiar with grub. Heiko |
35 messages has been excluded from this view by a project administrator.
