home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   alt.os.linux.slackware      I think its the one without Selinux crap      87,272 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 87,202 of 87,272   
   Eric Pozharski to All   
   Status report 0x0 [was: Virtualbox EFI w   
   25 Nov 25 18:17:18   
   
   [continued from previous message]   
      
     Indeed, 'lilo' complains about zeppelin being non-first but proceeds   
     nevertheless even without forcing.  What is kind of sad:  it's 2025,   
     what is "first disk" anyway.  Good thing, 'lilo' is dead and can't get   
     any worse (except, one day, it won't build;  I prefer not to think   
     about it).   
      
     Then, storing boot sector in MBR works and is effective.  *Aiming*   
     'lilo' at MBR of zeppelin has its issues.  What is needed is *stable*   
     pointer to usb-bob.  And udev is of no help.   isn't even   
     joke;   is  level unstable;     
     and  are about partitions (neither even features   
     links to whole disk);  is another joke, I guess, and   
     is missing from Slackware proper.   _pretends_ to be solid   
     candidate, but there is a catch -- I see naming conventions are   
     version (of udev) dependent;  otoh, udev absolutely insists on   
     exposing manufacturer and that's unstable -- usb-bob will die any   
     moment and I don't feel like hunting for another, so it's going to be   
     microSD.  And then udev will expose manufacturer of cardreader.  I'm   
     certain udev people have reasons to be this difficult.   
      
     For now I've set "boot=" of  to "/dev/sdz" and this is   
     reasonably safe for now.  Then each time I need to update boot sector   
     I tell 'lilo' what to look for.  And rest assured, it's "rm -rf *"   
     scary.  This will be fixed someday.   
      
   * Short comment on "this usb-stick boots"   
      
     Each and every box (six so far) I've tried has its The Secure Boot   
     present and disabled (I've access to some boxes that have The Secure   
     Boot enabled, haven't even tried).  My understanding is, that bios is,   
     in fact, a wrapper about underlying efi and then lilo uses that bios   
     but it's efi that enables booting.  It remains mystery if zeppelin   
     would boot without lurking in shadows efi (and such box must be   
     x86_64).   
      
   And that would be everything for report 0x0.  Should have taken notes on   
   the way, my bad.   
      
   --   
   Torvalds' goal for Linux is very simple: World Domination   
   Stallman's goal for GNU is even simpler: Freedom   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca