#4 No MB/BIOS checks made with conf-files.

closed-rejected
Sergei Haller
None
3
2004-06-01
2004-05-26
Dennis Jansen
No

If nvram is run in the distribution directory:
nvram-wakeup -C nvram-wakeup.conf
it uses the sample config and a time is set, the rtc is
overwritten at the wrong spot.
This is really dangerous.

Also as help I think it'd be good to automatically do a
backup of the complete nvram before starting.
"dd if=/dev/nvram of=nvram_backup_date"

I hope this will be fixed as I almost messed up my
nvram...

Oh, and sorry if the request sounded as if open-source
developers were the slaves they are ;-P.

I greatly appreciate your work!

Greetings

Dennis

Discussion

  • Sergei Haller
    Sergei Haller
    2004-05-26

    Logged In: YES
    user_id=76018

    > No MB/BIOS checks made with conf-files.

    no. that's how it is documented in the manual.

    > If nvram is run in the distribution directory:
    > nvram-wakeup -C nvram-wakeup.conf
    > it uses the sample config

    yes. That's the file you specified.

    > ... the rtc is overwritten at the wrong spot.

    that's why there is an option --nowrite.
    even if you don't use this option, you should check first
    if READING the wakeup settings works correctly and THEN
    try to write to it.

    > Also as help I think it'd be good to automatically do a
    > backup of the complete nvram before starting.
    > "dd if=/dev/nvram of=nvram_backup_date"

    no. depending on your system some information may change
    there in the meantime so restoring this file back, you might
    destroy some information.

    > I hope this will be fixed as I almost messed up my
    > nvram...

    I don't consider this behaviour a bug.
    BTW.: did you read the README?

     
  • Sergei Haller
    Sergei Haller
    2004-05-26

    • assigned_to: nobody --> bistr-o-math
    • status: open --> open-rejected
     
  • Dennis Jansen
    Dennis Jansen
    2004-05-27

    Logged In: YES
    user_id=673104

    Yes I did read the README. I just think that it would be very
    easy to implement and most importantly very _user friendly_.
    It is such a difference that I though of it as a bug.

    Also the situation might happen to many people: Accidently
    changing into the wrong directory or using the wrong config
    file, thinking it was the one you already checked that worked
    with the nowrite and debug-option and then flashing the
    wrong information.

    IMHO this is very dangerous behavior and thereby can be
    considered a bug. But it is obviously matter of interpretation. I
    wasn't telling anyone it had to be done. All I say is that is
    would be _very_ useful and user-friendly to do so and would
    thereby help spread the popularity and recognition of the
    program.

    B.t.w. I really like the idea and the implementation of this
    program!

    I hope you can better understand my reasons for filing this at
    all and specifically as a bug.

     
  • Dennis Jansen
    Dennis Jansen
    2004-05-27

    • priority: 5 --> 3
     
  • Sergei Haller
    Sergei Haller
    2004-05-27

    Logged In: YES
    user_id=76018

    > Also the situation might happen to many people:
    > Accidently changing into the wrong directory or ...

    do you consider this behaviour a bug of 'rm':
    you want to delete all files in /tmp. But then accidently
    change into /etc instead of /tmp and type 'rm * .*' All
    files in /etc are removed. Is it a bug in 'rm'? No, 'rm'
    just removed the files you specified.

    the same is here. You specify a file, nvram-wakeup uses it.
    How sould it know that it is the wrong file???

    and BTW, it doesn't have anything to do with user-friendlyness.
    in opposite, it would be user-unfriendly, if nvram-wakeup
    would ask you again and again: "you specified the file ...
    Are you really sure it is the right file?"

    And if you read the README, you read the Warning in the
    beginning telling you that writing to NVRAM is dangerous.
    And thus you double-checked that you are using the right
    file before you used it, didn't you?

    Sorry, but this is not a bug.

     
  • Dennis Jansen
    Dennis Jansen
    2004-05-27

    Logged In: YES
    user_id=673104

    If rm could for example with a "delete this file"-flag check if
    the file is the right one, you bet it would be implemented by
    now ;)
    A single line with the BIOS type and stuff could be put into the
    config files without a problem...

    But oh well, I give up. You won! My opinion is still the same,
    but I guess I'll have to start my own project for my opinion to
    make the difference. :P

    And: Wow, you're really fast on doing the updates!
    Too bad people always have their own ideas and opinions,
    huh?

     
  • Sergei Haller
    Sergei Haller
    2004-05-28

    Logged In: YES
    user_id=76018

    > If rm could for example with a "delete this file"-flag
    > check if the file is the right one, you bet it would be
    > implemented by now ;)

    yeah, but how should nvram-wakeup know that the specified
    file is the wrong one???

     
  • Dennis Jansen
    Dennis Jansen
    2004-05-28

    Logged In: YES
    user_id=673104

    >how should nvram-wakeup know that the specified
    >file is the wrong one???
    By checking the already integrated lines:
    "
    ## - Mainboard vendor: "ASUSTeK Computer INC."
    ## - Mainboard type: "A7N8X-E"
    ## - Mainboard revision: "REV 2.xx"
    ## - BIOS vendor: "Phoenix Technologies, LTD"
    ## - BIOS version: "ASUS A7N8X-E Deluxe ACPI BIOS
    Rev 1010"
    ## - BIOS release: "03/16/2004"
    "
    If they don't belong to this system, require for example a
    -force parameter to be set.

     
  • Sergei Haller
    Sergei Haller
    2004-06-01

    Logged In: YES
    user_id=76018

    no. these are just comments. You can safely remove them.
    The only reason they are there is that the _user_ can check
    if he is using the right file before he uses ist.

     
  • Sergei Haller
    Sergei Haller
    2004-06-01

    • status: open-rejected --> closed-rejected