Mailinglist Archive: opensuse-bugs (5398 mails)
| < Previous | Next > |
[Bug 269741] Normal boot procedure altered by presence past Suspend to Disk Operation
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Wed, 6 Jun 2007 04:18:29 -0600 (MDT)
- Message-id: <20070606101829.B2F59CC786@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=269741
duwe@xxxxxxxxxx changed:
What |Removed |Added
----------------------------------------------------------------------------
Info Provider|seife@xxxxxxxxxx |alpha096@xxxxxxxxxx
------- Comment #20 from duwe@xxxxxxxxxx 2007-06-06 04:18 MST -------
Scott, in the context of operating systems the term "file" has a distinct
meaning. I usually resides inside a file system (sic!). Since windoze fills up
the disk on installation with one big file system, it needs to create a --
potentially fragmented -- file to swap VM page frames.
On any unixoid operating system, a _partition_ on the disk is usually reserved
for swapping (->the "swap partition" or just "swap"), which has nothing to do
with file systems, besides that like an FS it also resides in a partition, and
has a /dev device node associated, which can be _accessed_ like a file (in
unix, everything is a file ;-)
So, Comment#6 does not contradict itself. But it still has one unanswered
question: after resuming once, and a crash at a certain point which you still
have to specify yet, on the next boot, do you see
1. grub's boot menu offerings ?
2. the "Loading image data pages ... XX%" progress indicator? a.k.a resume ?
Note that both are technically fairly independent; we only try to keep them
correlated for consistency reasons. May I assume we all agree that the correct
behaviour is either no menu and resume when crashed/reset before a defined
point in the resume process, and a boot menu without resume after that point?
And you are seeing something different?
You mentioned someone at suse.de who knows how to reproduce the problem; mind
to give us the name? Besides, a good old hwinfo might also be of interest.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
duwe@xxxxxxxxxx changed:
What |Removed |Added
----------------------------------------------------------------------------
Info Provider|seife@xxxxxxxxxx |alpha096@xxxxxxxxxx
------- Comment #20 from duwe@xxxxxxxxxx 2007-06-06 04:18 MST -------
Scott, in the context of operating systems the term "file" has a distinct
meaning. I usually resides inside a file system (sic!). Since windoze fills up
the disk on installation with one big file system, it needs to create a --
potentially fragmented -- file to swap VM page frames.
On any unixoid operating system, a _partition_ on the disk is usually reserved
for swapping (->the "swap partition" or just "swap"), which has nothing to do
with file systems, besides that like an FS it also resides in a partition, and
has a /dev device node associated, which can be _accessed_ like a file (in
unix, everything is a file ;-)
So, Comment#6 does not contradict itself. But it still has one unanswered
question: after resuming once, and a crash at a certain point which you still
have to specify yet, on the next boot, do you see
1. grub's boot menu offerings ?
2. the "Loading image data pages ... XX%" progress indicator? a.k.a resume ?
Note that both are technically fairly independent; we only try to keep them
correlated for consistency reasons. May I assume we all agree that the correct
behaviour is either no menu and resume when crashed/reset before a defined
point in the resume process, and a boot menu without resume after that point?
And you are seeing something different?
You mentioned someone at suse.de who knows how to reproduce the problem; mind
to give us the name? Besides, a good old hwinfo might also be of interest.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
| < Previous | Next > |