Re: /boot nonexistant on sun4cdm install disk set

[William Cordis]

On Sun, Aug 13, 2000 at 06:28:08PM -0400, Ben Collins wrote:
> On Sun, Aug 13, 2000 at 06:08:02PM -0400, Adam Di Carlo wrote:
> > Try the newer 3 August versions, I think.
> > 
> > If that fails, please submit a bug against boot-floppies.
> 
> No, there should be no /boot in the root.bin. The /boot that silo uses is
> /target/boot. Silo us run as "silo -r /target" so that it will chroot to
> the new installed filesystem. Try running that and see if there is an
> error. I'm wondering what happened to make you think it failed. Was there
> an error message? If so, what was it?
Ok.. /boot shouldn't exist.  Two problems still stand with the latest boot-
floppies.

1.  DHCP doesn't work correctly, all the information is recieved, the 
interface goes up, the route's are correct, but no DNS.  No matter what
I do.  I checked /etc/resolv.conf, nothing there.  The information is in
/tmp/resolv.conf but even if I manually set up the device afterward it doesn't
work.  It works fine if I set it up manually the first time with the same info
as it recieves from the DHCP server.  

2.  SILO still does not work.  I think it may have to do with the way I was
partitioning the drive.  It would not work without a Whole Disk partition
though that isn't mentioned in the documentation.  Now it claims to be successfull
but can't create a boot floppy and when I reboot is says it can't read /vmlinuz.

My original partition scheme was this.

1   ext2   /boot
2   swap   LinuxSwap
3   ext2  /

I changed it to this:

1   Boot  ???
2   swap  LinuxSwap
3   Sun   Whole Disk
4   ext2  /boot
5   ext2  /

Is there something I'm missing in the install guide


William Cordis


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: /boot nonexistant on sun4cdm install disk set

[Ben Collins]

> 1.  DHCP doesn't work correctly, all the information is recieved, the 
> interface goes up, the route's are correct, but no DNS.  No matter what
> I do.  I checked /etc/resolv.conf, nothing there.  The information is in
> /tmp/resolv.conf but even if I manually set up the device afterward it doesn't
> work.  It works fine if I set it up manually the first time with the same info
> as it recieves from the DHCP server.  

That's a general problem then, I suspect.

> 
> Is there something I'm missing in the install guide
> 

Yeah, don't make a seperate /boot partition. SILO is not like LILO. It
actually reads the ext2 filesystem directly. This is something I could not
solve in the boot-floppies easily, so you have to work around it. I don't
think you'll lose much by not having /boot on its own partition.

-- 
 ---===-=-==-=---==-=--
/  Ben Collins  --  ...on that fantastic voyage...  --  Debian GNU/Linux   \
`  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  '
 `---=--===-=-=-=-===-==---=--=---'


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: DHCP and /boot

[William Cordis]

On Tue, Aug 15, 2000 at 10:04:28AM -0400, Ben Collins wrote:
> > 1.  DHCP doesn't work correctly, all the information is recieved, the 
> > interface goes up, the route's are correct, but no DNS.  No matter what
> > I do.  I checked /etc/resolv.conf, nothing there.  The information is in
> > /tmp/resolv.conf but even if I manually set up the device afterward it doesn't
> > work.  It works fine if I set it up manually the first time with the same info
> > as it recieves from the DHCP server.  
> 
> That's a general problem then, I suspect.
> 
Are you saying I should file a bug or would you like me to do some debuging. I 
don't really have to get this machine up and running right now so if you have
something you want me to try or look for I could do it.
> > 
> > Is there something I'm missing in the install guide
> > 
> 
> Yeah, don't make a seperate /boot partition. SILO is not like LILO. It
> actually reads the ext2 filesystem directly. This is something I could not
> solve in the boot-floppies easily, so you have to work around it. I don't
> think you'll lose much by not having /boot on its own partition.
Hrm.. Ok.  I somehow got the wrong message and thought I needed to keep
the kernel below some cylinder number.  I'll try that. Thanks.

William Cordis


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Potato now stable

[Branden Robinson]

[Please followup to -devel, since I do not yet subscribe to -boot]

On Tue, Aug 15, 2000 at 10:06:10AM +0200, Bas Zoetekouw wrote:
> I personally would like having hardware detection stuff in woody.

This is something Progeny is attempting to accomplish for our version of
Debian later this year.  Ian Murdock has spent some time looking into it.

Of course, everything Progeny does will be made available to the community,
particularly the Debian community.

This seems like a good time to ask; how would the boot-floppies team feel
about creating a branch in CVS for Progeny?  There are probably some things
we (Progeny) will do that Debian doesn't want to fool with.

We can of course set up our own CVS repository if need be, but this seems a
good way to do development out in the open.

-- 
G. Branden Robinson |   I just wanted to see what it looked like
Debian GNU/Linux|   in a spotlight.
[EMAIL PROTECTED]  |   -- Jim Morrison
http://www.debian.org/~branden/ |

 PGP signature

Re: /boot nonexistant on sun4cdm install disk set

[Steve Bowman]

On Tue, Aug 15, 2000 at 09:52:37AM -0400, William Cordis wrote:

[snip]
> 
> My original partition scheme was this.
> 
> 1   ext2   /boot
> 2   swap   LinuxSwap
> 3   ext2  /
> 
> I changed it to this:
> 
> 1   Boot  ???
> 2   swap  LinuxSwap
> 3   Sun   Whole Disk
> 4   ext2  /boot
> 5   ext2  /

ISTR that I needed to keep the Whole Disk partition when using Sun
disklabels - yep, there it is.  I also STR that I had problems when
I removed it and that it was created by default (with fdisk?).  As I
recall, I removed it the first time, had problems (that may have been
entirely unrelated), and when I repartitioned the disk I left in the
Whole Disk partition and everything worked fine.

I'm sure someone will correct me if it turns out to be entirely unneeded.

> 
> Is there something I'm missing in the install guide
> 
> 
> William Cordis
> 

-- 
Steve Bowman  <[EMAIL PROTECTED]> (preferred)
Buckeye, AZ   <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
  

Powered by Debian GNU/Linux 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#67771: modconf or not?

[Martin Schulze]

reopen 67771
thanks

Martin Schulze wrote:
> The bug was fixed by reinstalling whiptail...

Sorry, tausq is right.  The bug is persitant.  After a brandnew installation
I was not able to run modconf after I rebooted the system.

Randolph Chung wrote:
> please try running modconf as
> bash -x modconf

[...]
+ directory=modconf: /dev/tty: Device not configured
[...]


Regards,

Joey

-- 
Life is too short to run proprietary software.  -- Bdale Garbee

Please always Cc to me when replying to me on the lists.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#69197: base: Inadequate backup instructions and tools

[era eriksson]

Package: base
Version: 2815
Severity: wishlist

This should probably be severity: 2 or something like that but due to
the nature of this report, I think "wishlist" is the most appropriate.

I have a slightly old installation and if this has been fixed in newer
releases of Debian, I'll have to apologize. Also, there's -- obviously
-- a lot more homework I could have done, but I thought it better to
send in a simple report now rather than probably never get it done.

The perceived problem is that the base system doesn't appear to have
any facilities for making backups, beyond including basic tools such
as cpio(1) and tar(1). If the system is supposed to be usable by a
neophyte with limited administration experience (as I believe is the
intention), at the very least the FAQ and/or policy should contain a
few notes about the importance of backups and some tips on common
backup procedures.

I would also recommend including a simple backup script. The problem
here of course is that it needs to be robust, yet be usable on wildly
differing sorts of hardware, ranging from basic 386:es with only a
floppy disk for backups, to monster servers with multiple tape drives,
removable disks, local network services (backup over ftp? NFS? rsync?
HTTP PUT?), etc.

I believe NetBSD comes with a barely adequate dump(8) which could
perhaps be used as a starting point. Another candidate I'd like to
mention is the tob package, although it is "tape-oriented", as the
name implies. But it might not be too hard to adapt it to use other
media as well.

Unfortunately, I'm unable to upgrade to the most recent Debian in
order to see if this has been improved; much less play around with a
clean install of the latest release. Of course, I'd love to be wrong
on this. But if this bug report is warranted, at least I hope I can
help give Somebody Else (tm) a nudge in the right direction.

Thank you for your time,

/* era */

-- System Information
Debian Release: 2.0
Kernel Version: Linux away 2.0.34 #1 Sun Feb 28 21:48:09 EET 1999 i586 unknown



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#67771: modconf or not?

[Adam Di Carlo]

Holy cow.  Or some other explicitive.

So, uh, modconf is utterly broken on potato boot floppies?
i386 only?  Does the new whiptail fix it?

(If so, I'm going to go ahead an burn 2.2.17 very soon)

-- 
.Adam Di [EMAIL PROTECTED]http://www.onShore.com/>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: DHCP and /boot

[Adam Di Carlo]

William Cordis <[EMAIL PROTECTED]> writes:

> On Tue, Aug 15, 2000 at 10:04:28AM -0400, Ben Collins wrote:
> > > 1.  DHCP doesn't work correctly, all the information is recieved, the 
> > > interface goes up, the route's are correct, but no DNS.  No matter what
> > > I do.  I checked /etc/resolv.conf, nothing there.  The information is in
> > > /tmp/resolv.conf but even if I manually set up the device afterward it doesn't
> > > work.  It works fine if I set it up manually the first time with the same info
> > > as it recieves from the DHCP server.  

If it broken in Potato it must have happened quite recently.

> > That's a general problem then, I suspect.

Or just sparc version?

> Are you saying I should file a bug or would you like me to do some
> debuging. I don't really have to get this machine up and running
> right now so if you have something you want me to try or look for I
> could do it.

Please do file a big fat bug.  Boot with the 'debug' flag.  If you
can, submit /var/log/messages there (with the dbootstrap log) with the
report.  If not, then look thru /var/log/messages for clues and
include that musing in the report.


> > > Is there something I'm missing in the install guide
> > 
> > Yeah, don't make a seperate /boot partition. SILO is not like LILO. It
> > actually reads the ext2 filesystem directly. This is something I could not
> > solve in the boot-floppies easily, so you have to work around it. I don't
> > think you'll lose much by not having /boot on its own partition.

I don't think having /boot in a separate partition is a good idea
ever.  Should we deprecate that in the documentation?  Or just for
sparc?

William, can you file a diff. bug against the documentation to mention
this issue?

> Hrm.. Ok.  I somehow got the wrong message and thought I needed to keep
> the kernel below some cylinder number.  I'll try that. Thanks.

Ah, no, that is i386 BIOS hackery only.

-- 
.Adam Di [EMAIL PROTECTED]http://www.onShore.com/>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: DHCP and /boot

[Ben Collins]

> > Hrm.. Ok.  I somehow got the wrong message and thought I needed to keep
> > the kernel below some cylinder number.  I'll try that. Thanks.
> 
> Ah, no, that is i386 BIOS hackery only.

Actually some older sparc PROM's cannot handle this either (1024 cyl.
limit). But I've never come up against it.

-- 
 ---===-=-==-=---==-=--
/  Ben Collins  --  ...on that fantastic voyage...  --  Debian GNU/Linux   \
`  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  '
 `---=--===-=-=-=-===-==---=--=---'


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]